Personal network access control system and method
A server is provided that includes a processor such that for a Session Initiation Protocol (SIP) request containing a Uniform Resource Identifier (URI) identifying the first device, the processor is programmed to promote adding a URI and redirecting the SIP request to a second device. The added URI used by the second device to invoke a Personal Network Management (PNM) Controller function.
1. A user device of a personal network, comprising:
a transceiver configured to receive a Session Initiation Protocol (SIP) request addressed to the user device of the personal network, the SIP request comprising:
an “Accept Contact” header,
a target uniform resource identifier (URI) parameter identifying a second user device of the personal network, and
an identification of an originating user; and
a processor configured to perform a personal network management (PNM) controller function upon receipt of the SIP request at the user device,
wherein the “Accept Contact” header comprises an indication that the user device is requested to invoke the PNM controller function performed by the processor,
wherein the “Accept Contact” header includes an IMS Application Reference Identifier (IARI) value that contains the indication, the indication comprising a PNM-specific indication.
2. The user device of claim 1 , wherein the SIP request is redirected by an application server (AS) that initially receives the SIP request from the originating user.
3. The user device of claim 2 , wherein the AS redirects the SIP request to the user device upon determining that the originating user is not part of the personal network.
4. The user device of claim 1 , wherein the PNM-specific indication includes “3gpp-application.ims.iari.PNM-Controller”.
5. The user device of claim 1 , wherein the “Accept Contact” header includes the PNM-specific indication to inform the user device that the SIP request pertains to a PNM Controller request rather than an ordinary call forwarding message.
6. The user device of claim 1 , wherein the originating user's identification informs the user device that the originating user is not part of the personal network.
7. A non-transitory computer readable medium comprising instructions executable by a processor to cause a user device to implement a method, the method comprising:
receiving, at the user device, a Session Initiation Protocol (SIP) request addressed to the user device of the personal network, the SIP request comprising:
an “Accept Contact” header,
a target uniform resource identifier (URI) parameter identifying a second user device of the personal network, and
an identification of an originating user;
determining, by the user device, that the “Accept Contact” header comprises an indication that the user device is requested to invoke a personal network management (PNM) application on the user device; and
performing, by the PNM application, a PNM controller function upon determining that the “Accept Contact” header comprises the indication requesting the user device to invoke the PNM application,
wherein the “Accept Contact” header includes an IMS Application Reference Identifier (IARI) value that contains the indication, the indication comprising a PNM-specific indication.
8. The non-transitory computer readable medium of claim 7 , wherein the SIP request is redirected by an application server (AS) that initially receives the SIP request from the originating user.
9. The non-transitory computer readable medium of claim 8 , wherein the AS redirects the SIP request to the user device upon determining that the originating user is not part of the personal network.
10. The non-transitory computer readable medium of claim 7 , wherein the PNM-specific indication includes “3gpp-application.ims.iari.PNM-Controller”.
11. The non-transitory computer readable medium of claim 7 , wherein the “Accept Contact” header includes the PNM-specific indication to inform the user device that the SIP request pertains to a PNM Controller request rather than an ordinary call forwarding message.
12. The non-transitory computer readable medium of claim 7 , wherein the originating user's identification informs the user device that the originating user is not part of the personal network.
13. A method implemented by a user device of a personal network, the method comprising:
receiving, at the user device, a Session Initiation Protocol (SIP) request addressed to the user device of the personal network, the SIP request comprising:
an “Accept Contact” header,
a target uniform resource identifier (URI) parameter identifying a second user device of the personal network, and
an identification of an originating user;
determining, by the user device, that the “Accept Contact” header comprises an indication that the user device is requested to invoke a personal network management (PNM) application on the user device; and
performing, by the PNM application, a PNM controller function upon determining that the “Accept Contact” header comprises the indication requesting the user device to invoke the PNM application,
wherein the “Accept Contact” header includes an IMS Application Reference Identifier (IARI) value that contains the indication, the indication comprising a PNM-specific indication.
14. The method of claim 13 , wherein the SIP request is redirected to the user device by an application server (AS) that initially receives the SIP request from the originating user.
15. The method of claim 14 , wherein the AS redirects the SIP request to the user device upon determining that the originating user is not part of the personal network.
16. The method of claim 13 , wherein the PNM-specific indication includes “3gpp-application.ims.iari.PNM-Controller”.
17. The method of claim 13 , wherein the “Accept Contact” header includes the PNM-specific indication to inform the user device that the SIP request pertains to a PNM Controller request rather than an ordinary call forwarding message.
18. The method of claim 13 , further comprising the user device determining that the originating user is not part of the personal network based on the originating user's identification.
19. The method of claim 14 , wherein the “Accept Contact” header includes a Reason field indicating that the SIP request pertains to a PNM Controller request rather than an ordinary call forwarding message, and wherein the Reason field is added by the AS before redirecting the SIP request to the user device.
20. The method of claim 13 , wherein the user device is a PNM controller user equipment (UE) configured to manage functions of the personal network, wherein the second user device is a PNM controllee UE, and wherein the PNM controller UE determines which UEs external to the personal network are permitted to access each PNM controllee UE in the personal network.