Method To Inform User Equipment To Perform Register Procedure In Wireless Communication System and Related Communication Device

• US 20110244823A1
• Filed: 03/31/2011
• Published: 10/06/2011
• Est. Priority Date: 04/02/2010
• Status: Abandoned Application

• Current Assignee: HTC Corporation
• Original Assignee: HTC Corporation
• Inventors: Chen, Te-Ming
• Application Number:
  US13/076,442
• Publication Number:
  US 20110244823A1
• Time in Patent Office: Days
• US Class Current: 455/404.1
• CPC Class Codes: H04W 68/00 User notification, e.g. alerting and paging, for incoming communication, change of service or the like

Abstract

Method for a network requesting a UE to initiate a register procedure includes the network sending a paging message to the UE to request the UE to initiate the register procedure; wherein the UE is in a RRC connected mode, and register state of the UE is invalid due to a network failure. The UE is allowed to acquire specific information other than an ETWS notification, a CMAS notification, or a system information change indicator from the paging message.

Claims

1. A method for a network requesting a UE to initiate a register procedure, comprising:

the network sending a paging message to the UE to request the UE to initiate the register procedure;

wherein the UE is in a radio resource control (RRC) connected mode, and register state of the UE is invalid.

2. The method of claim 1, wherein the UE acquires a specific information other than an ETWS notification, a CMAS notification, or a system information change indicator from the paging message.

3. The method of claim 2, wherein the specific information includes identity of the UE other than a system architecture evolution (SAE) temporary mobile subscriber identity (S-TMSI) of the UE.

4. The method of claim 3, wherein the identity included in the specific information is an international mobile subscriber identity (IMSI) or an internal mobile equipment identity (IMEI) of the UE.

5. The method of claim 3, wherein the UE checks if the identity included in the specific information matches identity of the UE.

6. The method of claim 5, wherein when the identity included in the specific information matches the identity of the UE, the UE informs an upper layer that the paging message is received.

7. The method of claim 6, wherein the UE sends the identity included in the specific information to the upper layer.

8. A method for a network requesting a user equipment (UE) to initiate a register procedure, comprising:

a network sending a specific message to the UE to request the UE to initiate the register procedure;

wherein the UE is in a radio resource control (RRC) connected mode, and register state of the UE is invalid.

9. The method of claim 8, wherein the specific message is a paging message.

10. The method of claim 9, wherein the network includes a specific field in the paging message.

11. The method of claim 10, wherein the specific field includes identity of the UE other than a system architecture evolution (SAE) temporary mobile subscriber identity (S-TMSI) of the UE.

12. The method of claim 11, wherein the identity included in the specific field is an international mobile subscriber identity (IMSI) or an internal mobile equipment identity (IMEI) of the UE.

13. The method of claim 11, wherein the UE checks if the identity included in the specific field matches identity of the UE.

14. The method of claim 13, wherein when the identity included in the specific field matches the identity of the UE, the UE informs an upper layer that the paging message is received.

15. The method of claim 14, wherein the UE sends the identity included in the specific field to the upper layer.

16. The method of claim 8, further comprising:

allowing the UE in the RRC connected state to acquire specific paging information other than broadcast information.

17. The method of claim 16, wherein the broadcast information is an earthquake and tsunami warning system (ETWS) notification, a commercial mobile alert system (CMAS) notification, or a system information change indicator.

18. The method of claim 8, wherein the specific message is an RRC connection release message.

19. The method of claim 18, wherein the network includes a specific release cause in the RRC connection release message.

20. The method of claim 19, wherein the specific release cause is “

loadBalancingTAURequired”

.

21. The method of claim 19, wherein the specific release cause is a dedicated release cause to ask the UE to perform the register procedure.

22. The method of claim 8, wherein the specific message is a global unique temporary identity (GUTI) reallocation command message.

23. The method of claim 22, wherein the UE performs a GUTI reallocation procedure after receiving the GUTI reallocation command message and the network allocates a new identity to the UE.

24. The method of claim 8, wherein the UE enters an RRC idle mode after receiving the specific message.

25. The method of claim 8, wherein the specific message is a dedicated message to request the UE to perform the register procedure.

26. The method of claim 8, wherein the register state of the UE is invalid because a tracking area identity list or an S-TMSI of the UE is not available due to a network failure.

27. The method of claim 26, wherein the register procedure is an attach procedure or a tracking area update procedure.

28. A communication device comprising a central processing unit (CPU) and memory, the memory containing program code executable by the CPU for performing following steps:

receiving a specific message to initiate a register procedure from a network;

wherein the communication device is in a radio resource control (RRC) connected mode, and register state of the communication device is invalid.

29. The communication device of claim 28, wherein the specific message is a paging message, and the paging message includes a specific field, and the specific field includes identity of the communication device other than a system architecture evolution (SAE) temporary mobile subscriber identity (S-TMSI) of the communication device.

30. The communication device of claim 29, wherein the communication device checks if the identity included in the specific field matches identity of the communication device.

31. The communication device of claim 30, wherein when the identity included in the specific field matches the identity of the communication device, the communication device informs an upper layer that the paging message is received.

32. The communication device of claim 31, wherein the communication device sends the identity included in the specific field to the upper layer.

33. The communication device of claim 28, wherein the communication device in the RRC connected state is allowed to acquire specific paging information other than broadcast information.

34. The communication device of claim 28, wherein the specific message is an RRC connection release message, and the RRC connection release message includes a specific release cause.

35. The communication device of claim 34, wherein the specific release cause is “

loadBalancingTAURequired”

.

36. The communication device of claim 34, wherein the specific release cause is a dedicated release cause to ask the communication device to perform the register procedure.

37. The communication device of claim 28, wherein the specific message is a global unique temporary identity (GUTI) reallocation command message, and the communication device performs a GUTI reallocation procedure after receiving the GUTI reallocation command message and the network allocates a new identity to the communication device.

38. The communication device of claim 28, wherein the communication device enters an RRC idle mode after receiving the specific message.

39. The communication device of claim 28, wherein the specific message is a dedicated message to request the communication device to perform the register procedure.