Routing of Messages for Mobile Communication Devices During Emergency Calls

• US 20120302196A1
• Filed: 01/07/2011
• Published: 11/29/2012
• Est. Priority Date: 01/08/2010
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Chin, Chen Ho, Burbidge, Richard Charles
• Granted Patent: US 9,497,792 B2
• Time in Patent Office: Days
• US Class Current: 455/404.1
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04W 4/90 Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• CPC Class Codes: H04W 48/17 Selecting a data network PoA [Point of Attachment]
• CPC Class Codes: H04W 76/25 Maintenance of established connections
• CPC Class Codes: H04W 76/27 Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 76/50 for emergency connections

Abstract

A method implemented in a UE. NAS signaling is initiated or performed for an emergency call in order to establish a connection between the UE and one of a plurality of core networks (CNs). In a non-limiting example, the NAS signaling is initiated or performed after the ending of a prior established connection or emergency call. A determination is made whether the UE is already attached for emergency bearer services. Responsive to the UE being already attached for emergency bearer services, a NAS layer of a protocol stack of the UE causes transmission of a UE identification (ID) when requesting a radio resource control (RRC) connection for further NAS signaling. The UE ID includes data which can be used to determine to which CN of the plurality of CNs the connection should be directed.

Claims

1. A method implemented in a user equipment (UE), the method comprising:

initiating non-access stratum (NAS) signaling in order to establish a connection between the UE and one of a plurality of core network (CN) elements;

determining whether the UE is already attached for emergency bearer services;

responsive to the UE being already attached for emergency bearer services, causing transmission, by a NAS layer of a protocol stack of the UE, of a UE identification (ID) when requesting a radio resource control (RRC) connection for further NAS signaling, wherein the UE ID comprises data which is used to determine to which CN of a plurality of CNs the connection should be directed.

2. The method of claim 1 wherein the NAS signaling is used to perform at least one of a tracking area update (TAU), receiving an emergency call, or initiating an emergency call.

3. The method of claim 1 wherein the UE has ended a previous emergency call and moved to IDLE mode while remaining attached for emergency bearer services.

4. The method of claim 1 wherein the UE ID is inserted into a RRC_CONNECTION_REQUEST message.

5. The method of claim 1 wherein the UE ID comprises one of a “

system architecture evolution temporary mobile subscriber identity”

(S-TMSI), an “

international mobile subscriber identity”

(IMSI), and an “

international mobile equipment identifier”

(IMEI).

6. The method of claim 1 wherein the NAS layer is required to transmit both the UE ID and one or more elements of the group consisting of:

a “

globally unique mobility management entity identifier”

(GUMMED, a “

mobility management entity identifier”

(MMEI), and a “

mobility management entity code”

(MMEC).

7. The method of claim 1 wherein the method further comprises:

responsive to the UE not being already attached for emergency bearer services, either leaving blank or specifying an invalid value for a registered mobility management entity (MME) field within an RRC_CONNECTION_SETUP_COMPLETE message.

8. The method of claim 1 wherein the UE facilitates determining to which CN the connection should be directed by specifying a preferred mobility management entity (MME) indicated in a registered MME field of an RRC_CONNECTION_SETUP_COMPLETE message.

9. The method of claim 1 wherein, when requesting the RRC connection for further NAS signaling, the NAS layer transmits a “

system architecture evolution temporary mobile subscriber identity”

(S-TMSI), and wherein a “

mobility management entity code”

(MMEC) portion of the S-TMSI indicates the CN.

10. The method of claim 1 wherein the NAS signaling comprises a tracking area update (TAU).

11. A method implemented in a user equipment (UE), the method comprising:

deciding to request access to a network;

determining whether a network component, to which access is made, should perform other network component or core network element selection;

responsive to a UE determination that the network component should not perform other network component or core network element selection, providing an indicator, wherein the indicator comprises data that indicates to the network component that the network component should not independently perform other network component or core network element selection.

12. The method of claim 11 wherein determining whether the network component should perform other network component or core network element selection comprises determining whether a mobility management entity (MME) should perform the other network component or core network element selection.

13. The method of claim 11 wherein the indicator comprises data that indicates a particular MME which the network component should select.

14. The method of claim 11 wherein the indicator comprises a “

MME_Selection_Not_Allowed”

indicator.

15. The method of claim 11 further comprising providing the indicator in a RRC_CONNECTION_REQUEST message or a RRC_CONNECTION_SETUP_COMPLETE message.

16. The method of claim 11 wherein deciding to request access to the network and determining if the network component should perform other network component or core network element selection are performed by a non-access stratum (NAS) layer of the UE, wherein, before providing, the NAS layer passes the indicator to an access stratum (AS) layer of the UE, and wherein the AS layer performs providing.

17. The method of claim 11 wherein, responsive to a UE determination that the network component should perform other network component or core network element selection, populating one of a RRC_CONNECTION_REQUEST message or a RRC_CONNECTION_SETUP_COMPLETE message with a second indicator, wherein the second indicator comprises data that indicates to the network component that the network component should independently perform other network component or core network element selection.

18. A user equipment (UE) comprising:

a processor configured such that the UE initiates non-access stratum (NAS) signaling in order to establish a connection between the UE and one of a plurality of core network (CN) elements;

wherein the processor is further configured such that the UE determines whether the UE is already attached for emergency bearer services, and wherein the processor is further configured such that the UE, responsive to the UE being already attached for emergency bearer services, causes transmission, by a NAS layer of a protocol stack of the UE, of a UE identification (ID) when requesting a radio resource control (RRC) connection for further NAS signaling, wherein the UE ID comprises data which is used to determine to which CN of a plurality of CNs the connection should be directed.

19. The UE of claim 18 wherein the UE is further configured to use the NAS signaling to perform at least one of a tracking area update (TAU), receiving an emergency call, or initiating an emergency call.

20. The UE of claim 18 wherein the UE is further configured such that, after ending a previous emergency call and moving to IDLE mode, the UE will remain attached for emergency bearer services.

21. The UE of claim 18 wherein the UE is further configured to insert the UE ID into a RRC_CONNECTION_REQUEST message.

22. The UE of claim 18 wherein the UE ID comprises one of a “

system architecture evolution temporary mobile subscriber identity”

(S-TMSI), an “

international mobile subscriber identity”

(IMSI), and an “

international mobile equipment identifier”

(IMEI).

23. The UE of claim 18 wherein the UE is further configured such that the NAS layer is required to transmit both the UE ID and one or more elements of the group consisting of:

a “

globally unique mobility management entity identifier”

(GUMMED, a “

mobility management entity identifier”

(MMEI), and a “

mobility management entity code”

(MMEC).

24. The UE of claim 18 wherein the UE is further configured to cause the UE, responsive to the UE not being already attached for emergency bearer services, either to leave blank or to specify an invalid value for a registered mobility management entity (MME) field within an RRC_CONNECTION_SETUP_COMPLETE message.

25. The UE of claim 18 wherein the UE is further configured to cause the UE to facilitate determining to which CN the connection should be directed by specifying a preferred mobility management entity (MME) indicated in a registered MME field of an RRC_CONNECTION_SETUP_COMPLETE message.

26. The UE of claim 18 wherein the UE is further configured to, when requesting the RRC connection for further NAS signaling, cause the NAS layer to transmit a “

system architecture evolution temporary mobile subscriber identity”

(S-TMSI), and wherein a “

mobility management entity code”

(MMEC) portion of the S-TMSI indicates the CN.

27. The UE of claim 18 wherein the NAS signaling comprises a tracking area update (TAU).

28. A user equipment (UE) comprising:

a processor configured such that the UE will decide to request access to a network, determine whether a network component, to which access is made, should perform other network component or core network element selection, and, responsive to a UE determination that the network component should not perform other network component or core network element selection, provide an indicator, wherein the indicator comprises data that indicates to the network component that the network component should not independently perform other network component or core network element selection.

29. The UE of claim 28 wherein the processor is further configured such that the UE determining whether the network component should perform other network component or core network element selection comprises the UE determining whether a mobility management entity (MME) should perform the other network component or core network element selection.

30. The UE of claim 28 wherein the indicator comprises data that indicates a particular MME which the network component should select.

31. The UE of claim 28 wherein the indicator comprises a “

MME_Selection_Not_Allowed”

indicator.

32. The UE of claim 28 wherein the processor is further configured such that the UE will further provide the indicator in a RRC_CONNECTION_REQUEST message or a RRC_CONNECTION_SETUP_COMPLETE message.

33. The UE of claim 28 wherein the processor is further configured such that the UE will decide to request access to the network and determine if the network component should perform other network component or core network element selection in a non-access stratum (NAS) layer of the UE, wherein, before providing, the processor is further configured such that the UE NAS layer passes the indicator to an access stratum (AS) layer of the UE, and wherein the processor is further configured such that the UE AS layer will perform providing.

34. The UE of claim 28 wherein the processor is further configured such that the UE, responsive to a UE determination that the network component should perform other network component or core network element selection, will populate one of a RRC_CONNECTION_REQUEST message or a RRC_CONNECTION_SETUP_COMPLETE message with a second indicator, wherein the second indicator comprises data that indicates to the network component that the network component should independently perform other network component or core network element selection.