## 3 Proposed SPMIPv6 Protocol
### Mobility Scenario of IP-WSN Based on SPMIPv6  
To represent mobility scenarios, we consider a state-of-the-art technology based patient care unit in a specialized hospital. Figure 3 represent such type of scenario where a patient can get special care both in the hospital and personal home care and from a remote specialized hospital. In this scenario, we try to depict different type of mobility in SPMIPv6 environment [17]. Sensor nodes are deployed on the body of the patients as well as all over the environment. The patient care unit ensures real time care and observation of the patients from a central specialized doctor's forum. In case of emergency, patient can move from one place to another with its complete set-up so that seamless connectivity with the sophisticated medical equipment remains established and doctor can monitor the patient online from the central doctor's research group. All the floors are considered as single SPMIPv6 domain. Inside the SPMIPv6 domain there are six floors considered as individual SMAG domain.  
The mobility issue considered in this scenario are: Case-I: Movement of nodes within the same SMAG domain of the SPMIPv6 domain, Case-II: Movement of nodes between different SMAGs of the same SPMIPv6 domain, Case-III: Movement of nodes between different SMAGs of different SPMIPv6 domains, Case-IV: Movement of a SMAG-based personal area network (PAN) within the same SPMIPv6 domain, Case-V: Movement of a SMAG-based PAN between different SPMIPv6  
Figure 3: Mobility scenario in SPMIPv6-based patient care unit.  
domains, Case-VI: Patient monitoring in personal home environment. These scenarios are explained below:  
Case-I: In this case, the mobility of the nodes will be handled by the appropriate SMAG, without the involvement of the SLMA. This, the simplest mobility scenario, arises frequently in hospital management: a patient can move within the PAN of a single branch of the hospital for different purposes such as exercise and getting fresh air.  
Case-II: In this case, mobility will be handled by the appropriate SMAG with minimal initiative from the SLMA. The initial coordination will be performed by the SLMA alone; then the SMAG will oversee the remaining procedures. In our hospital management model, a patient can move from one PAN to another PAN in the same branch of the hospital.  
Case-III: In this case, mobility is inter-domain, using the public PMIPv6 domain. The LMA, AAA, and SLMA will coordinate with one other. In our hospital management model, a patient can move on an emergency basis from one PAN of a hospital branch to a PAN of another branch of the same hospital.  
Case-IV: In this case, mobility is based on the network mobility (NEMO) protocol [14], confined to the same domain. Only the SLMA and corresponding SMAGs will be involved. In our hospital management model, a patient with the whole set up can move from one PAN to another PAN.  
Case-V: This case is also based on NEMO protocol, but is much different from Case-IV. In our hospital management model, a patient can move on an emergency basis with its whole setup from one branch of a hospital to the more specialized branch of the same hospital.  
Case-VI: Due to the increasing number of aging demographic group, we consider this case so that a patient can be monitor continuously from the patient's personal environment as discussed in our recent paper.  
Although some of the mobility scenarios may seem complicated in case of IP based wireless sensor network, still they have been considered for the future research. Because of the essence of huge deployment of IP sensor network in health care, departmental store and industrial automation, this mobility scenario will eventually come true in the near future.