METHOD OF IMPLEMENTING UE CAPABILITY EXCHANGE AND ROUTE CONTROL FOR PARALLEL IMS AND CS SERVICES

• US 20150223054A1
• Filed: 04/01/2015
• Published: 08/06/2015
• Est. Priority Date: 03/28/2005
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: ZHU, Dongming, WU, Yajuan
• Granted Patent: US 10,237,726 B2
• Time in Patent Office: Days
• US Class Current: 1/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/1094 Inter-user-equipment sessions transfer or sharing
• CPC Class Codes: H04L 65/1095 Inter-network session transfer or sharing
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities
• CPC Class Codes: H04W 8/24 Transfer of terminal data

Abstract

The present invention discloses a method of implementing UE capability exchange and a method of route control for parallel IMS and CS services in communication system, so as to distinguish among multiple UEs sharing a same IMPU during capability exchange and route control. Said method comprises: each of UEs involved in capability exchange sending its capability information to the opposite party respectively; the opposite party storing these information as well as the correlation between the information and the service ID; The UE including equipment ID of the opposite UE in an initiated service request; service control function entity in the network utilizing the equipment ID to query the established correlation among equipment ID, service ID, and address of the UE, so as to determine the address of the destination UE and route the service request to the destination UE. Said equipment ID identifies effectively a UE in the network.

Claims

1. A method comprising:

receiving, by a second UE, an equipment ID of a first User Equipment (UE) and capability information of the first UE, sent from the first UE; and

storing, by the second UE, the equipment ID of the first UE and the capability information of the first UE;

wherein the equipment ID uniquely identifies the first UE among multiple UEs sharing a same IP multimedia public user identity (IMPU).

2. The method of claim 1, further comprising:

receiving, by the second UE, a message including a received equipment ID;

judging, by the second UE, whether the capability information corresponding to the received equipment ID included in the message is stored locally in the second UE; and

performing, by the second UE, service handling in accordance with the result of the judging.

3. The method of claim 2, with performing service handling in accordance with the result of the judging comprising at least one of:

initiating, by the second UE, a capability exchange if the capability information corresponding to the received equipment ID included in the message is not stored locally in the second UE; and

initiating, by the second UE, a CSI related operation in subsequent interaction in accordance with the capability information corresponding to the received equipment ID included in the message, if the capability information corresponding to the received equipment ID included in the message is stored locally in the second UE.

4. The method of claim 1, wherein a version number of the capability information is received by the second UE and wherein the second UE is capable of judging whether the capability information has been changed in accordance with the version number of the capability information.

5. The method of claim 2, wherein the message comprises one of a session setup request, a capability inquiry request, a message request, a call control related message, a user information related message, a response of a session setup request, a response of a capability inquiry request, a response of a message request, a response of a call control related message, and a response of a user information related message.

6. The method of claim 1, wherein the equipment ID includes at least one of an International Mobile Equipment Identity (IMEI), a Media Access Control (MAC) address, and a Mobile Equipment Identity (MEID).

7. The method of claim 1, further comprising:

starting, by the second UE, a timer when storing the capability information; and

deleting, by the second UE, the capability information when the timer expires.

8. The method of claim 7, further comprising one of:

resetting, by the second UE, the timer if the second UE receives a service request or a response of a service request including the equipment ID, and the capability information is stored locally in the second UE; and

resetting, by the second UE, the timer if the capability information has been used during session negotiation.

9. A method comprising:

receiving, by a second UE, an equipment ID of a first User Equipment (UE), a service ID of a user of the first UE, and capability information of the first UE, sent from the first UE; and

storing, by the second UE, the equipment ID of the first UE, the service ID of the user of the first UE, and the capability information of the first UE;

wherein the equipment ID uniquely identifies the first UE among multiple UEs sharing a same IP multimedia public user identity (IMPU).

10. The method of claim 9, further comprising:

receiving, by the second UE, a message including a received equipment ID;

judging, by the second UE, whether the capability information corresponding to the received equipment ID in the message is stored locally in the second UE; and

performing, by the second UE, service handling in accordance with result of the judging.

11. The method of claim 10, with performing service handling in accordance with the result of the judging comprising at least one of:

initiating, by the second UE, a capability exchange if the capability information corresponding to the received equipment ID included in the message is not stored locally in the second UE; and

initiating, by the second UE, a CSI related operation in subsequent interaction in accordance with the capability information corresponding to the received equipment ID included in the message, if the capability information corresponding to the received equipment ID included in the message is stored locally in the second UE.

12. The method of claim 9, wherein a version number of the capability information is received by the second UE and wherein the second UE is capable of judging whether the received capability information has been changed in accordance with the version number of the received capability information.

13. The method of claim 10, wherein the message comprises one of a session setup request, a capability inquiry request, a message request, a call control related message, a user information related messages, a response of a session setup request, a response of a capability inquiry request, a response of a message request, a response of a call control related message, and a response of a user information related messages.

14. The method of claim 9, wherein the equipment ID includes at least one of an International Mobile Equipment Identity (IMEI), a Media Access Control (MAC) address, and a Mobile Equipment Identity (MEID).

15. The method of claim 9, further comprising:

starting, by the second UE, a timer after storing the capability information; and

deleting, by the second UE, the capability information when the timer expires.

16. The method of claim 15, further comprising one of:

resetting, by the second UE, the timer if the second UE receives a service request or a response of a service request including the equipment ID, and the capability information is stored locally in the second UE; and

resetting, by the second UE, the timer if the capability information has been used during session negotiation.

17. The method of claim 9, wherein the service ID is an IP Multimedia Public Identity (IMPU).

18. The method of claim 9, wherein the service ID is a MSISDN number.

19. A device comprising a processor coupled to a memory having a computer readable instruction stored thereon that, when executed by the processor, configures the device to:

receive an equipment ID of a User Equipment (UE) and capability information of the UE, sent from the UE; and

store the equipment ID of the UE and the capability information of the UE;

wherein the equipment ID uniquely identifies the UE among multiple UEs sharing a same IP multimedia public user identity (IMPU).

20. The device of claim 19, wherein the device is further configured to:

receive a message including a received equipment ID;

judge whether the capability information corresponding to the received equipment ID included in the message is stored locally in the device; and

perform service handling in accordance with a result of the judging.

21. The device of claim 19, wherein a version number of the capability information is received by the device and wherein the device is further configured to judge whether the capability information has been changed in accordance with the version number of the capability information.

22. The device of claim 19, wherein the equipment ID includes at least one of an International Mobile Equipment Identity (IMEI), a Media Access Control (MAC) address, and a Mobile Equipment Identity (MEID).

23. The device of claim 19, wherein the device is further configured to:

start a timer after storing the capability information; and

delete the capability information when the timer expires.

24. The device of claim 23, wherein:

the device is configured to reset the timer if the device receives a service request or a response of a service request including the equipment ID, and the capability information is stored locally in the device;

or

the device is configured to reset the timer if the capability information has been used during session negotiation.

25. A device comprising a processor coupled to a memory having a computer readable instruction stored thereon that, when executed by the processor, configures the device to:

receive an equipment ID of a User Equipment (UE), a service ID of a user of the UE, and capability information of the UE, sent from the UE; and

store the equipment ID of the UE, the service ID of the user of the UE, and the capability information of the UE;

wherein the equipment ID uniquely identifies the UE among multiple UEs sharing a same IP multimedia public user identity (IMPU).

26. The device of claim 25, wherein the device is further configured to:

receive a message including a received equipment ID;

judge whether the capability information corresponding to the received equipment ID included in the message is stored locally in the device; and

perform service handling in accordance with a result of the judging.

27. The device of claim 25, wherein a version number of the capability information is received by the device and wherein the device is further configured to judge whether the capability information has been changed in accordance with the version number of the capability information.

28. The device of claim 25, wherein the equipment ID includes at least one of an International Mobile Equipment Identity (IMEI), a Media Access Control (MAC) address, and a Mobile Equipment Identity (MEID).

29. The device of claim 25, wherein the device is further configured to:

start a timer after storing the capability information; and

delete the capability information when the timer expires.

30. The device of claim 29, wherein:

the device is configured to reset the timer if the device receives a service request or a response of a service request including the equipment ID, and the capability information is stored locally in the device;

or

the device is configured to reset the timer if the capability information has been used during session negotiation.

31. The device of claim 25, wherein the service ID is an IP Multimedia Public Identity (IMPU).

32. The device of claim 25, wherein the service ID is a MSISDN number.