Safeguards and weightless of electronic chain of command consolidated for virtual patient evaluation.

The Internet of Things (IoT), 5G cellular technology, and Cyber-Physical Systems (CPS) are enabling a wide range of IoT-based application cases that are both intelligent. As one of the most impactful applications of the Internet of Things (IoT), healthcare makes use of AAL (Ambient Assisted Living), mobile health (mHealth), and electronic health (eHealth). Spending on health is a significant portion of people's income. Traditional medicine is prone to long delays, waste of money and effort, and even death. RVO (Remote Victim Observation) can be utilized to circumvent problems associated with traditional healthcare facilities because of IoT's intelligence and predictive power. With the help of IoT-based RVO and wearable devices, sensor networks, and other digital infrastructure, we can detect oncoming situations before they become life-threatening or even fatal. IoT integration with healthcare units was demonstrated in order to build a trustworthy, available, and secure RVO system. Secure end to end communication, encryption of RFID data, and privacy protection are all part of the proposed solution. An android wearable watch (Biosensor | Body sensor), a server using REST framework, and a smartphone app to monitor and detect falls, blood pressure, and heart rate are all part of the system. As a bonus, the peace and quiet of this secluded location contribute to the attraction. Using this RVO could improve health care and quality of life, according to an empirical investigation.

Introduction

Rapid advances in mobile and networking technology have resulted in numerous new and exciting applications. They use Wi-Fi, 4G LTE, Zigbee, and Bluetooth wireless communication in their programmes. These are the most commonly used mobile gadgets in daily life. A service like remote medical monitoring and care is described in Moosavi et al. [29] and Simplicio et al. [38]. Several countries have recently launched programmes to address the growing healthcare needs of an ageing population. A full medical network can be built using wireless technology, sensors, actuators and the internet of things Yang et al. [48]. It’s interaction with the internet of things will improve future medical and healthcare applications Ray et al. [34].

To protect medication administration and tracking, the medical industry currently relies on IT. Radio Frequency Identification (RFID) is employed in this process. Blood samples and other medical data can all be recognised using this method in a novel manner. The elderly and children, as well as many other real world scenarios Simplicio et al. [39], Chiuchisan et al. [9], Khemissa et al. [23], Yang et al. [46] and Imtyaz Ahmed et al. [4], can be properly monitored through the use of various real-world instances. Better medical care will be required as the world’s population ages. Therefore, it is critical that these folks obtain medical attention without having to visit a hospital. Extended and distant medical monitoring can be made possible by the use of mobile healthcare services, GPS location, rural medical care, wheelchairs, and other equipment and technology that makes this possible.

As technology has advanced, physiologic sensing devices have kept pace. Devices like this one are smaller and more power efficient. As a result, they are suitable for long-term body sensing in wearable devices. Personal wireless devices are connected to sensors on the body via the body area network (BAN), as seen in Lee et al. [25], Abbas et al. [2], Liang et al. [27], Yang et al. [47] and G Kannan et al. [22]. The recent advancements in Internet of Things (IoT) technology have made it possible to integrate healthcare services and enable remote healthcare monitoring in near real time. This study analyses a stimulating setting in order to reach this goal. Personal wireless devices integrated with sensors can be used to collect and send physiological data from victims. This information can be used for both diagnosis and treatment by medical experts.

A third party reader can access the wearable device’s data. Victims’ medical records will be more readily available to medical professionals, regardless of where they are located: in the hospital or at home. Body sensors send data to a device or data reader Chen et al. [18], Han et al. [16], Zhao et al. [52] and Whitmore et al. [44]. Medical workers can gather and communicate victim data, which can then be used by doctors to diagnose and treat victims. Governments at all levels can benefit from this data, including the federal government. Wearable sensors generate a great deal of “big data,” which is referred to as the volume of data they collect on a regular basis. Cloud computing and cloud based distributed programming frameworks must be employed in order to process this data.

BodyCloud was proposed by Fortino et al. [11] as a name for a body sensor network (BSN). An internet protocol was designed to communicate with a network of body sensors. C-SPINE a BSN architecture was introduced in Fortino et al. [12] as an alternative. However, several sensors can communicate at the same time using this technique. Hardware architecture was established for the same reason. In addition to the cloud-based architecture previously stated, it looks at various other BSN configurations Gravina et al. [15]. Despite technological developments in this field, many people continue to employ outmoded methods to harm or even violate the privacy of their victims. Those with nefarious motives could launch an assault. Readers can be given erroneous sensing data by an attacker that results in inaccurate diagnosis. As a result, the victim’s treatment could be placed on hold or even put at risk.

Hackers may take private information with the intent of extorting money or other harm. It is critical that healthcare facilities employ privacy and security safeguards when implementing IoT for remote health monitoring. There must be a set of encryption and authentication protocols in place for anti-adversarial attacks to work. By prohibiting unauthorised access to critical information, the public interest will be safeguarded. In order to prevent the misuse of private medical information, privacy must be safeguarded Zhou et al. [53], Ali et al. [7], Mollera et al. [28] and Kim et al. [24].

A flurry of ideas for IoT integration has been floated previously. The problem is that many of them weren’t made with healthcare in mind Simplicio et al. [38] and Ray et al. [34]. If these solutions are employed, healthcare applications Moosavi et al. [29], Yang et al. [48] may not be effectively protected. In Simplicio et al. [38], an IoT solution is described for establishing a session key between two parties. Authentication and session management were completely overlooked by the researchers. Ray et al. [34] outlines an RFID ownership transfer mechanism for Internet of Things (IoT) use. There must be a way for the RFID reader and tag to verify each other’s identities, but this has nothing to do with medical care. It has been decided to use IoT to improve mobility healthcare. The implementation of challenge response systems also made advantage of mobile sensors and users. Encryption was, on the other hand, a topic that had very little information available about it. In Yang et al. [48], a framework for an IoT-enabled integrated healthcare unit is proposed. Body sensors, servers, and data senders and receivers are not covered by their protocol, but users and servers are.

A BAN based architecture should include the victim, medical reader, medical server, and other stakeholders, according to him and others. This approach has a security issue that has been uncovered. The protocol appears to contain body sensors and wireless hubs, although it appears to be lacking in detail. Encrypted connections between medical readers and the wireless hub are ignored. In the world of wearables and biometric sensors, there is no way to verify each other’s identities. A compelling setting is used to provide a foundation for remote victim observation in this study, which addresses these issues. There are no compromises in terms of data security or individual privacy in the proposed framework. This paper presents a novel method for secure end to end communications in a remote victim observation IoT application. A complete system model is given before a security technique is recommended. This study’s findings can now be used by researchers and healthcare providers to develop remote victim observation systems.

For privacy concerns, mutual authentication, data integrity, user untraceability, and the absence of replay attacks must be met by the suggested approach. Secrecy must be maintained in both directions in order to meet industry standards. Authentication is the method by which a recipient determines whether or not the sender is genuine. Both parties will be able to use mutual authentication. It’s crucial in a BAN. Senders and receivers must be able to verify each other’s identities Yao et al. [49]. Without encryption, data on a network can be intercepted and used against the sender. It is possible to alter this type of data. It is also necessary to consider the data’s integrity. The sender’s message appears to have been misconstrued in this case. Because of this, it’s necessary to create data transmission protocols that prevent against manipulation and maintain data integrity throughout the network.

Users’ true physical locations are hidden from each other when connected to a network. Using the data sent by an assault, it is possible to pinpoint a person’s physical position. Chen et al. [19] This is a security concern that BANs must deal with. Data can be intercepted if it is transmitted across a network that does not have adequate authentication or permission. A repeat performance by these fraudsters could lead to the theft of sensitive information. A recurrence is an example of this type of attack. Avoiding this type of attack is a security concern. It’s possible to hack the session key during a session between two BAN participants. That’s because they can speak with the victim using their session key at any time. This should be avoided in BAN to preserve the security of communications. With the help of reverse and forward secrecy Chen et al. [20], this can be achieved. A more secure internet of things is our goal with this paper’s proposed study. Our contributions to the organisation can be seen in the following list of achievements.

We have created a mechanism for securely delivering data while protecting the privacy of the recipient in IoT use cases like remote victim observation (RVO).

Body sensors, data servers, receivers, and transmitters are just some of the many components that go into creating a system model. The RVO case study appears to have the support of all of these individuals and organisations.

In order to monitor a victim’s vital signs (such as blood pressure and heart rate), a smartphone app has been developed for the victim, the doctor, and the victim’s close family member.

A server side capability is being created to save, analyse, and make available to users on demand victim health data.

It is necessary to test RVO to check if it fits the aforementioned security requirements after implementing the recommended security strategy.

In the second section of the study, we conduct a literature review on IoT use cases such remote victim observation to assess their security. Section 3 contains research on safe IoT applications with an RVO (Motivational Scenario). Using the inspiring case in Section 3 as a backdrop, the implementation in Section 4 goes further. Stakeholders and the various stages of the proposed plan are detailed in Section 5. The planned course of action is considered in this section. Section 7 concludes with recommendations for future research.

Related work

There have been significant advances in remote victim observation research, as outlined in this section. According to Yew et al. [50], a real-time monitoring system for victims was proposed. After analysing an ECG from a cardiac victim, the monitoring findings were published online or via an app. Message Queuing Telemetry Transport (MQTT) was used to disseminate their information. Better still, jitter and noise signals would be decreased or eliminated entirely. Healthcare and patient monitoring architecture was described by Akkaset et al. [6]. An IoT-based WBAN-based system was created to monitor victims oxygen saturation and pulse rate. An in-depth case study was utilised to gauge the system’s overall performance. In terms of data transmission, energy consumption, and general stability, it was shown to be more efficient than the current system. Shanin et al. [37] used the Internet of Things (IoT) to construct an e-Health record system that enables for remote victim surveillance. All of their vitals were being tracked by the device, including their pulse, temperature, and heart rate. In order to authenticate the identity of an individual, RFID can be employed. Maintaining a close eye on victims while also allowing for secure contact is critical to their well-being. Saha et al. [35] claims to have created IoT based health monitoring system Hassanalieragh et al. [17]. To make use of the sensors, a sensor network that was interconnected with the internet was created. Using a smartphone app, the vital signs of a victim can now be tracked in real-time.

A group led by Hassanalieragh et al. [17] and Mohammed Imtyaz Ahmed et al. [5] examined the challenges and opportunities presented by the Internet of Things in healthcare. Several layers of commonality were found in remote health monitoring, they found. Data gathering and transmission, cloud computing, and data storage are all examples of this. Researchers observed that remote health monitoring systems can be enhanced. A cloud based system called fog computing was employed by Rais et al. [33] to monitor remote victims. Fog aided offloading lowered power consumption while improving device performance. For real time victim monitoring, Uddin et al. [42] and his colleagues used the Internet of Things and it’s numerous layers. Using these instruments, temperature, ECG, and humidity may all be monitored. Abawajy and Hassan et al. [1], pioneered Pervasive Patient Health Monitoring (PPHM). This thorough architecture for remote health monitoring includes an analysis of the scheme’s energy efficiency and scalability.

The rising usage of sensors and IoT networks in the real world has opened the door for remote victim observation, according to Gomez et al. [13]. Users, clients, and servers all have a role in the system’s structure. Both the victim and the doctor can use the system simultaneously. Three devices are linked to the system. This internet based system includes an ECG Glucometer, a sound device, and other components. By Wan et al. [43], an proposed a system known as Wearable IoT cloud-based health monitoring system was presented for real time health monitoring (WISE). Based on a body area sensor network (BASN), WISE is a wearable integrated sensor system. Rahman et al. [32] presented an RFID-based privacy preserving paradigm for healthcare systems Gope et al. [14]. The authors provided a variety of authentication and access control measures. The authors have offered many models for achieving privacy in IoT applications. They evaluated RFID to near field communication (NFC) and decided to go with RFID because of its distance, the advantages of Internet of Things (IoT) integration in healthcare, as well as privacy and security are highlighted. Due to the lack of cloud aided effective security measures as disadvantages, using an Internet of Things connected RFID-based information system, it is possible to keep track of the health status of victims. Security measures are in place to protect healthcare-related information. For example, they discovered ways to improve the overall quality of the healthcare system while protecting victims privacy by using an RFID-based technology.

Gope et al. [14]. presented RFID-based privacy preserving authentication for scattered IoT application cases. For the final step in the authentication procedure, we turned to the hash function. An authentication mechanism is used in conjunction with RFID network clustering to develop this system. As a result, it can protect against phishing and malware attacks. It was designed by Wu et al. [45] for medical applications to use an RFID based anonymous authentication method. An RFID system based on a hash algorithm served as the foundation for the system. Christos et al. [40] A 6G mobile network and smart buildings are all part of Stergiou and his colleagues security architecture. Technology such as edge and cloud computing are used to achieve its goals. Blockchain technology is employed by Espisito et al. [10] when it comes to the administration of distributed identification and authorisation components. Finally, the FIWARE platform can be used to access the data. According to Tewari and Gupta et al. [41], cross-layer and IoT security issues can be compared to traditional security issues. Four-image encryption was created using the computer generated hologram, chaos, and Quaternion Fresnel Yu et al. [51] transformations, according to Yu and colleagues. In order to detect COVID-19 using deep learning, Sedik et al. [36] advocated using LSTM and Convolutional Neural Networks (CNN). Adat and Gupta et al. [3] studied the security of IoT devices Pu and Li et al. [31] suggested a lightweight authentication method based on a hybrid approach in order to combine a chaotic system with a physically unclonable function. “Man in the Middle” attacks can be used to target unmanned aerial vehicles, according to Li and Pu et al. [26]. Using lightweight signatures, they devised a defence against the attack. Existing remote health monitoring systems employ a wide range of techniques, according to the research. RFID based authentication has been proved to improve IoT security. Remote victim observation in an IoT integrated healthcare system will need a solution that is even more secure than WBAN.

Motivating scenario

Research shows that security and lightweight design with multiple IoT layers are critical. Reusable components in the system simplify the research process considerably. Testing the framework’s capabilities is done through prototype applications. An IoT enabled healthcare scenario is depicted in Fig. 1. As a result, learning more about it is a primary goal of this study. This is an example of “Remote Victim Observation (RVO)”.

Fig. 1

Architecture of RVO and IoT procedure

Remote victim observation is therefore brought to light. In addition, the case study’s many participants must be able to communicate with each other in it to be successful. If this scenario is implemented without adequate security measures, victim information and communications could be put at danger. The sensitivity of healthcare data necessitates the use of a security architecture. Android wear OS is installed on all of the victim’s wearable devices. This device can tell you whether a victim’s vital signs are out of whack. Victims and their families are informed if any of the signs are not as they should be. The ability to monitor your heart rate, blood pressure, and even determine if you’ve fallen is now at your fingertips. The data is stored on an android server and accessed through the app. It is possible for a doctor or a victim’s family member to view victim information via an android server. When developing a secure RFID authentication system, an end to end communication system, and privacy protection, the following scenario must be used as a motivating factor. This proposed scheme is controlled remote victim vital signs in abnormalities and protect the life of human with secure and privacy of their data to lead better quality of life and it is monitoring the patient data to respective doctors and relatives.

Implementation of motivating scenario

Temperature, blood pressure, heart rate and blood sugar levels can all be monitored remotely using devices that can provide real-time data on health indices like these. To do this, we intend to develop a system that comprises mobile services, server-side processing, and data collection (from sensors or from simulation). Everyone participating in the system—victims and caregivers alike—is connected to it in some way.

Assisting victims and the elderly with their data collection (sensors). When compared to more time consuming methods, the process of automatically detecting data from a victim is more efficient. Their medical records will be accessible to their primary care physicians and family members. Victims and their families will be alerted if sensors detect an abnormal health status among the elderly/infirm members of the community. Victims’ basic conditions and precise whereabouts are verified before emergency assistance are dispatched. In addition, family doctors can access a variety of victim data through the device. To better comprehend a victim’s or elderly person’s medical status, doctors use medical history data. It is also possible to monitor and analyse certain disorders using this method. Health care policies and services can be tailored to meet the requirements of individuals and groups.

According to study, more than a third of all seniors who fall seek for assistance because they are either unresponsive or disoriented. We don’t want to be in the same situation again. Family members of the elderly can also call emergency assistance.

Figure 2 depicts all of the RVO IoT use case’s actions. A remote victim’s fall, blood pressure, and heart rate can all be monitored using this device. Using wearable technology with a body sensor, you can keep an eye on these important metrics. It is feasible for a doctor and a victim’s relative (Attendant) to access the victim’s medical records via a mobile app. It is possible to look at sensor data, make an emergency call, and see the doctor’s opinion. To evaluate if a victim’s condition is normal, the system can analyse data.

Fig. 2

Features of health data and from a remote victim

According to Fig. 3, interactions between the victim, doctor, and relative all have a role in this condition. This smartphone software allows for simultaneous use by three persons. Before contacting a doctor or a relative, a victim can check health information and the doctor’s opinions (Attendant). Apps can be used to maintain track of victims who have fallen and can no longer communicate with a medical expert. Once the victim has been correctly identified and is able to access the main activity, an interface for any eligible operations may be found. Your heart rate and blood pressure are critical medical measures. An HTTP request is made to the server each time one of these options is selected. During an emergency, the victim can use the app to reach both the doctor and a close relative.

Fig. 3

Smartphone steps

RVO packages are used for server side features. The services it offers can be used for a wide range of purposes. Any number of functions can be performed by mobile apps, but the server is always in control. The server keeps track of data and establishes safe connections, as detailed in Section 7. The motivating scenario (RVO) aims to illustrate a comprehensive security architecture that enables secure, lightweight, and privacy preserving communication between all parties. As a result, the RVO integrated into the Internet of Things is extremely secure. Figure 4 shows a web based application for updating user profiles and contact information.

Fig. 4

Sequence server side functionality

Several participants are depicted in Fig. 5 as part of the overall system. All items in an Internet of Things (IoT) environment must be uniquely identified. With their long range and absence of line of sight, RFID tags are a better option than barcodes for this application. To keep track of things in the Internet of Things, RFID tags are employed. To read the information stored on an RFID tag, you’ll need an RFID reader. An RFID tag and a reader are included in the proposed system.

Fig. 5

Privacy and security overview

The suggested system is built on a number of design choices. The programme was divided into two parts a server component and a user facing component. In both mobile and web based applications, the backend is a component on the server. An abnormal occurrence might be displayed on the victim’s mobile client application while information is saved on the server. The recommended method should be used and implemented in order to ensure secure remote victim observation. Real world healthcare applications can be employed using this technology. Remote victim observation is one example of how it can be put to use in the real world. In many nations, the lack of real time victim monitoring leads in a significant number of deaths.

Proposed scheme for RVO IoT use case

RVO’s secure communications are covered in this section (Section 6).

How the RVO IoT use case is implemented. Tracking health data, such as falls, blood pressure, and heart rate, from a remote victim is possible with this device. Wearable technology with a body sensor can keep tabs on these critical indicators. By using the smartphone app, both the victim’s doctor and the person who is taking care of them can look over their medical records. Sensor data can be examined, emergency calls can be made, and the doctor’s opinions can be viewed. For example, the system can analyse a victim’s condition to determine if it is a normal or abnormal state.

The system’s conceptualization.

Based on the example in Section 3, this diagram depicts the overall system design. Both a sender and a receiver for both the doctor and the victim, a mobile app will alert them when something is off with their health.

A battery powered circuit is used to monitor vital signs, such as blood pressure and heart rate, in victims. In addition to that, he’s sporting a smartwatch.

Sensor data is transmitted to a distant server through Bluetooth.

The data sent to this receiver is evaluated by this receiver. For this operation, a smartphone app will be used by both the doctor and the victim.

The data is stored on a server and analysed by a computer programme. Data exchanges must be documented for security reasons. Figure 5 depicts a rough sketch of the design.

Based on a system architectural concept, we have created this diagram to show the many parties involved in communication. Confidentiality and safety are ensured by a few simple steps. See Fig. 5 for an overall view of how things will go.

Both the sender and the recipient must have a channel account. However, it’s a safe bet. It’s necessary to know who sent the message and who it was intended for. The unique identifier (UUID) is the name given to the identifier (UUID). System parameters are computed on the server using elliptic curve groups. The a & b curve parameters, the G generator point, the ord (G), and the cofactor are employed (h). Secure and lighter.

All data senders and body sensors must be registered B. A. The data sender and body sensor safely transfer identifiers to the data receiver. The data receiver returns polynomial parameters.

A data transmitter collects data from a body sensor after successful authentication has been accomplished. Data that has been encrypted is fed into the system.

By supplying the recipient with information, the sender validates the recipient’s identity. It is defined by its elliptic curve group (ECG) and it’s unique identifier (ID). The sender sends the recipient’s encrypted health information after they have both authenticated each other.

An initialization, registration (using a transmitter and receiver), authentication and communication are the three stages of the suggested technique. Table 1 depicts the system’s identifiers.

Table 1

Notations

Notation	Description
CHKx	x’ s verified message
Dx(m)	Message m is decrypted using session key x.
E/Fq	An elliptic curve E over Fq
Ex(m)	Message m is encrypted using session key x.
Fq	A prime finite field
HiO	ith one-way hash function
IDHS	Body sensor id
IDMR	Medical reader id
IDPR	The personal reader id
IDx	Denotes a random number. Elliptic curve group uses it.
Ki	Denotes a polynomial function of information related to elliptic curve.
Sx	Signature of elliptic curve group of x.
ci	The session key and transaction number encrypted sensing data
Data	Data sensed by body sensor.
f(x, y)	Denotes f(x, y) equal to f(y, x) as polynomial function.
G	Denotes cyclic additive group with composite order q
hO	A one-way hash function
P	The group G’s generator
PEK	It is the session key established between two parties namely data receiver and data sender
PK	Denotes a public key which is in the system PK = sP
Q	Denotes a k-bit prime
r, a, b	Random numbers
S	A secret key of the system
T ID	Denotes a transaction ID
A7=B	Checks whether A and B are equal

Initialization phase for the system

During the initialization step, the server computes required parameters and sends public parameters to the data sender and data receiver.

The steps that make up the initialization procedure are described below.

The steps that make up the initialization procedure are described below. A tuple of elliptic curve groups labeled (Fp, E/Fp, G, P) and a k-bit prime marked as p are considered by the server.

A tuple of elliptic curve groups labeled (Fp, E/Fp, G, P) and a k-bit prime marked as p are considered by the server. As demonstrated in Eq. 1, the server also computes a public key using a secret key represented by s.

After that, the server chooses a hash function (H1(), H2(), H3(), H4()) to distribute to all data senders and receivers (Fp, E/Ep, G, P, PK, H1(), H2(), H3(), H4()).

Registration of body sensors

The body sensor must be registered by the data receiver. The steps are as follows:

The body sensor selects and sends to the receiver a Universally Unique ID (UUID) specified as IDHS.

The data receiver then computes the polynomial f (x, y) and sends it to the body sensor as (HPHS, SID).

The computations are the same as in Eqs. 2 and 3. SID stands for sensor identification number. C1 denotes the session key and transaction number encrypted sensing data.

The body sensor receives the same (HPHS, SID) and stores it in memory.

Data sender registration

It is necessary to register the data sender, as well as the data receiver and server. The steps are as follows:

An IDPR is chosen as a Universally Unique ID (UUID) by the data transmitter and sent to the receiver.

The data receiver then computes and communicates the polynomial f (x, y) to the data sender (HPPR, SID). The calculations in Eqs. 4 and 5 are the same. SID stands for sensor identification number. C2 denotes the session key and transaction number encrypted sensing data.

The body sensor receives the same (HPHS, SID) and stores it in memory.

The data sender chooses and sends an IDPR identity to the server.

Before delivering (RPR, SPR) to the data reader, the server chooses a random number r and computes (Eqs. 6, 7, and 8), P denotes the group G’s generator.

After that, the data reader does the Eq. 9 verification. After successful verification, that (RPR, SPR) will be saved in the personal reader’s memory.

Data receiver registration

The server’s database should be updated to include the data recipient. Direct mutual authentication between the data transmitter and receiver is possible. The server registration for the data recipient is as follows. The data receiver received the victim data and it can be process to the server, it communicates to victim attendant and doctor through the mobile app to protect the life of the victim.

The data receiver selects and sends an IDMR identity to the server.

The server then performs the computations in Eqs. 10, 11, and 12 with a random number r before delivering (RMR, SMR) to the data receiver.

When the data recipient receives it, Eq. 13 is used to confirm it. If the verification is successful, the data is saved in the memory of the data receiver.

Authentication and communication

The data reader must connect to the data receiver in order to send data or use any other service. As a result, mutual authentication is essential between the two parties. The steps for authentication and communication are as follows.

The data transmitter computes (Eq. 14) and sends (IDPR, c) to the body sensor when it requires victim health data from the body sensor. C3 denotes the session key and transaction number encrypted sensing data.

It is verified by the body sensor. The body sensor executes the calculations in Eqs. 15, 16, and 17 after successful verification and sends (IDHS, d, e) to the data sender.

The data sender computes and verifies the information (as in Eqs. 18 and 19). After successful verification, the data sender provides health data to the data receiver.

The data sender then chooses a random number a, calculates (as in Eq. 20), and sends to the data receiver (IDPR, RPR, TPR).

In Eqs. 21, 22, 23, 24, and 25, the data receiver uses a random number b to determine the session key.

The data receiver then chooses a transaction id (TID), computes (as in Eqs. 26, 27), and transmits the data (IDMR, RMR, TMR, g, CHKPM)

Using Eqs. 28, 29, 30, and 31, the data sender computes and verifies the session key.

After successful verification, the data sender confirms the legality of the data receiver. It does so by computing Eqs. 32, 33, 34, and 35 and transmitting them to the data receivers as (IDPR, CHKMP, ci)

The data receiver then performs a CHKMP check.

After successful verification, the session between the two parties is successfully constructed. Once the session key is established, the data receiver computes data and changes the transaction number (as in Eqs. 36 and 37, respectively) for further communication.

Security evaluation

Using the motivating case depicted in Fig. 1, as well as the system model depicted in Fig. 5, Section 5’s method is evaluated. Everything from processing and transmission costs to replay attack protection and user untraceability is thoroughly scrutinised.

Mutual authentication

The sender and recipient are both confirmed to be who they say they are. To complete the process, a new session key is generated. By deploying an unlicensed data receiver, the proposed solution prevents an adversary from gaining access to sensitive victim health information. The attacker is doomed to fail because the illicit data recipient is not registered. A precise calculation of the session key is impossible. This means that the attacker will be unable to identify the true sender of the compromised data. An attacker also cannot make advantage of unauthorised data transmitters. An unregistered reader has access to sensitive material, but the recipient or server is ignorant of it. Mutual authentication protects IoT based healthcare against these threats.

Privacy of users

A person’s current location can be obtained as part of several privacy attacks. Since location data is extremely private, avoid this at all costs. Known as “User untraceability,” this is what we mean. A few examples: The recipient’s or sender’s location. One of the alternatives for data readers is CHKMP. It is chosen at random for each communication round in order to thwart attempts to trace it’s location. This method protects both your identity and your whereabouts.

Data integrity

Another aspect of IoT security to consider is the integrity of the data. ECC is a mechanism for encrypting data and creating session keys that is available for purchase. Signatures such as kpm1-kpm2 and kpm3-kpm3 cannot be used by an adversary to produce session keys (KMP1, KMP2). Only by creating a successful session key can proper communication be achieved. When a data receiver sends an email to a hostile attacker, for example, the email may be intercepted and forwarded. The ability of legitimate data senders to check the integrity of their own data thwarts attacks. It’s also impossible for an intruder to crack the session key. The lawful data sender has the ability to authenticate incoming communications, therefore any data integrity attack will be thwarted by this capability. As a result, any opponents who try to change the subject will be doomed to a defeat.

Reverse confidentiality

Data integrity and communication between sender and receiver are ensured by the session key. Even if an attacker gains access to such a session, the proposed technique ensures forward and backward confidentiality. Because the session is generated randomly, the attacker cannot utilize the compromised session key to attack. The current round will fail if the attacker uses a compromised session key. As a result, the method can manage both forward and reverse secrecy.

Preventing replay attacks

Messages are sent and received in the RVO IoT application use case. These communications may be intercepted by attackers. To transmit identical communications to the target data sender or receiver, attackers can mimic a legal data sender or recipient. Security is enhanced by changing the message for each round. The proposed method does not allow for replay attacks because the same message cannot be sent repeatedly. Because the messages are continually changing, a replay assault is guaranteed to fail.

Accessibility

According to our findings, the IoT RVO application possesses a secure security technique. Keeping the system safe while enabling the desired functionality is doable. The dependability of the hardware has not been verified. RVO, on the other hand, has been thoroughly tested and found to be dependable. Because cloud services are always available, regardless of time or location, your system’s availability is increased when you use the cloud.

Fee for computing

For the strategy’s computing expenses, see Table 2. data transfer, authentication, and communication are all considered while registering body sensors. When determining the final decision, all parties involved are considered. Sensors and other input/output devices are included.

Table 2

Computed cost of comparison

Phase | Party	Server	Data receiver	Data sender	Body sensor
Registration of body sensor	N/A	1TP + 1TH	N/A	N/A
Registration of data sender	2TMul + 1TH	1TP + 1TH	2TMul + 1TH + 1TCmp	N/A
Registration of data receiver	2TMul + 1TH	2TMul + 1TH + 1TCmp	N/A	N/A
Authentication & communication	N/A	5TMul + 1TH + 1TCmp	1TP + 5TMul + 7TH + 2TCmp + 3TENC	5TP + 2TH + 1TCmp1TENC

There are a variety of symbols used to indicate the cost of calculation in the table the computational cost of symmetric encryption is abbreviated (TEnc). According to the (TCmp) abbreviation, “computed cost of comparison” is “computed cost of comparison.” How long does it take to solve the hash function. The cost of multiplying two numbers is referred to as (TMul). TH is the price associated with computing a polynomial function. For body sensor registration, a polynomial function and a hash function are required. Data transmitter registration necessitates two multiplications and a hash function; receiver registration necessitates a polynomial and a hash function. A hash function, two multiplications, and a comparison are required by the server to register data receivers, whereas the receiver only needs one. Time consuming components of computing are authentication and communication. To conduct the data receiver’s symmetric encryption and comparison, the data sender must perform five multiplications and one polynomial operation as well as seven hash functions; the body sensor must perform two comparisons.

Using Table 3, we can see how much the scheme’s communication expenses have changed over time. Message length, number of cycles, and time all factor into the available bandwidth, which ranges from 14 Mpbs to 100 Mbps at various phases of processing.

Table 3

Communication cost analysis

Phase/Item	Length of message	Number of rounds	14 Mbps Speed (3G)	100 Mbps Speed (4G)
Registration of body sensor	400 bits	2	0.029 ms	0.004 ms
Registration of data sender	880 bits	4	0.063 ms	0.009 ms
Registration of data receiver	480 bits	2	0.034 ms	0.005 ms
Authentication & communication	2448 bits	5	0.175 ms	0.024 ms

Testing of the proposed strategy’s communication abilities. A 256-bit AES key is assumed to be required for messages like random number, pid, and id, as is a hash key of 160 bits and an elliptic curve modular key of 160 bits. The length of the message and the number of rounds have an impact on the overall time. 3G and 4G networks operate at different speeds. The greatest cycles are consumed during authentication and communication. Only 0.024 milliseconds are required at 4G speeds. It takes five rounds and 0.175% of a second to complete the test with 3G speeds.

Feature analysis

Then he and others Chen et al. [21] Many features of the system should be compared, including the capacity to prevent replay attacks, anonymity of users, and forward and backward secrecy. The following are the comparison’s specifics: Item #4 (Table 4).

Table 4

Features compared with He et al.’s Scheme (Y for Yes, N for N)

Feature/Scheme	Scheme of He et al. [18]	Proposed Scheme
Comprehensive Scheme	N	Y
Forward and Backward Secrecy	N	Y
Replay Attack Prevention	Y	Y
User Untraceability	Y	Y
Data Integrity	Y	Y
Mutual Authentication	N	Y

A complete method to safeguard the privacy of numerous parties has been presented for healthcare apps linked to the internet of things. He and his colleagues’ technique lack features like forward and reverse secrecy, but this one has. The He et al. approach lacks mutual authentication. Data integrity, user anonymity, and replay protection are all included in both systems, as well. The proposed method can be used in IoT use cases such as “Remote Victim Observation” to provide greater security and privacy for communications.

Information leakage and privacy comparison

Consequently, privacy is a crucial problem in this investigation. To measure privacy, the value ranges from 0.0 to 1 (R denote privacy as a function of the number), with 1 being the most secure and 0.0 the least secure. There are a staggering number of tags that have been hacked when it comes to privacy. Tags are counted by the letter N. A system’s integrity depends on every tag in it. The amount of personal information that has been compromised is measured by the number of tags that have been compromised Nohl et al. [30].

Table 5 shows the level of privacy for each method as well as the number of compromised nodes.

Table 5

Level of privacy vs. number of compromised tags

No. of compromised tags (C)	Level of privacy (R)
	PriSens [32]	Group based authentication [8]	Proposed
0	0.995	1	1
10	0.745	0.75	0.75
20	0.545	0.55	0.55
30	0.393	0.398	0.4
40	0.28355	0.28855	0.29
50	0.2139	0.2189	0.22
60	0.14425	0.14925	0.15
70	0.1144	0.1194	0.12
80	0.10445	0.10945	0.11
90	0.0945	0.0995	0.1
100	0.791	0.796	0.8
110	0.04475	0.04975	0.05
120	0.04475	0.04975	0.05
130	0.0348	0.0398	0.04
140	0.02485	0.02985	0.03
150	0.02485	0.02985	0.03
160	0.0149	0.0199	0.02

How many tags have been hacked and how much privacy they have is illustrated in Fig. 6. The number of tags is represented by the horizontal axis, while the level of privacy is represented by the vertical axis. It is more likely that a tag will be hacked if it is more private. Researchers observed that the proposed approach provides a higher level of privacy than currently available for a wide variety of compromised tags. As a result of this approach, a higher level of privacy can be observed.

Fig. 6

Level of privacy comparison

Table 6 shows how information leakage is measured against the number of compromised nodes for each strategy.

Table 6

Information leakage vs. number of compromised tags

No. of compromised tags (C)	Information leakage (bits)
	Proposed	Group based authentication [8]	PriSens [32]
0	0	0	0
10	0.95	1.5	1
20	1.9	3	2
30	2.85	4.5	3
40	3.325	5.25	3.5
50	3.61	5.7	3.8
60	3.895	6.15	4.1
70	4.18	6.6	4.4
80	4.465	7.05	4.7
90	4.75	7.5	5
100	5.035	7.95	5.3
110	5.32	8.4	5.6
120	5.605	8.85	5.9
130	5.89	9.3	6.2
140	6.175	9.75	6.5
150	6.46	10.2	6.8
160	6.745	10.65	7.1

Figure 7 shows the number of compromised tags in proportion to the amount of information that has been released. It is shown on the horizontal and vertical axes: the number of compromised tags and the amount of data leaked in bits. Data leakage is being exacerbated by an increase in the number of compromised tags. Because of the lesser number of vulnerable nodes, the proposed solution had a lower impact on information leakage. Data leaking can be prevented more effectively with the proposed solution than with current solutions.

Fig. 7

Information leakage against number of compromised tags

Conclusion and future work

Item to item communication has become easier because to recent technology advancements (physical and digital). When it comes to connecting physical and digital devices, the Internet of Things (IoT) and radio frequency identification (RFID) have made this ideal come true. Fog computing, mobile cloud computing, and cloud computing can all be used in IoT applications. Connecting billions of devices and items is possible with the Internet of Things (IoT). It has had a substantial (positive) impact on a wide number of industries around the world. The Internet of Things is revolutionising healthcare by allowing victims to monitor their own health remotely, which improves both their quality of life and the quality of care they receive. As a result of the large range of devices, protocols, and standards used in IoT applications, these applications are open to numerous dangers. Concerns about the security of Internet of Things (IoT) applications require additional investigation. “Remote Victim Observation” use case for Internet of Things will be studied empirically as a consequence. When building an effective model, keep in mind that it’s made up of a number of parts that connect in a way that’s both safe and private. All of the critical security factors were handled in our plan of action. This solution protects users from being traced and prevents replay assaults. Secrecy is maintained both in the present and in the past. In the IoT case study, this technique was compared to He et alis. and found to have higher communication security capabilities than those of the latter. This system’s ultimate goal is to become a wireless body area network (WBAN) that integrates IoT and has a significant impact on the medical industry.