Accommodating Hybrid IPv4v6 Network Support

• US 20110038372A1
• Filed: 08/12/2010
• Published: 02/17/2011
• Est. Priority Date: 08/12/2009
• Status: Abandoned Application

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Wijayanathan, Maiyuran, Arzelier, Claude Jean-Frederic, Naqvi, Noushad
• Application Number:
  US12/855,540
• Publication Number:
  US 20110038372A1
• Time in Patent Office: Days
• US Class Current: 370/389
• CPC Class Codes: H04L 2101/659 Internet protocol version 6 [IPv6] addresses
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/167 Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6 translation of Internet protocol [IP] addresses H04L61/2503
• CPC Class Codes: H04W 36/0033 with transfer of context information
• CPC Class Codes: H04W 76/20 Manipulation of established connections
• CPC Class Codes: H04W 8/26 Network addressing or numbering for mobility support
• CPC Class Codes: H04W 80/045 involving different protocol versions, e.g. MIPv4 and MIPv6

Abstract

A user equipment (UE) is provided. The UE comprises at least one component that is configured to detect an event of one of the UE changing routing area and the UE changing radio access technology from a long-term evolution (LTE) network to a global system for mobile communications enhanced data rates for GSM evolution radio access network (GERAN) or to a universal mobile telecommunication system terrestrial radio access network (UTRAN) and, responsive to detecting the event, to deactivate one of a packet data protocol (PDP) context and an evolved packet system (EPS) bearer.

Claims

1. A user equipment (UE) comprising a processor configured to:

receive a message; and

responsive to the message indicating a first Internet Protocol (IP) version type, deactivate at least one of a packet data protocol (PDP) context and an evolved packet system (EPS) bearer that are associated with a second IP version type, wherein the at least one of the PDP context and the EPS bearer had been previously activated by the UE.

2. The UE of claim 1 wherein the processor is further configured to:

receive the message with the first IP version type as IPv6; and

deactivate the PDP context for the second IP version type as IPv4v6.

3. The UE of claim 2 wherein the processor is further configured to:

reactivate the PDP context with the first IP version type as IPv6.

4. The UE of claim 1 wherein the processor is further configured to:

receive the message with the first IP version type as IPv4; and

deactivate the PDP context for the second IP version type as IPv4v6.

5. The UE of claim 4 wherein the processor is further configured to:

reactivate the PDP context with the first IP version type as IPv4.

6. The UE of claim 1 wherein the processor is configured to:

receive the message with the first IP version type as IPv4v6 single; and

deactivate the PDP context for the second IP version type as IPv4v6 double.

7. The UE of claim 5 wherein the processor is further configured to:

reactivate the PDP context with the IP version type as IPv4.

8. The UE of claim 5 wherein the processor is further configured to:

reactivate the PDP context with the IP version type as IPv6.

9. The UE of claim 1 wherein the processor is further configured to:

reactivate at least one of a second PDP context and a second EPS bearer that are associated with the first IP version type.

10. The UE of claim 9 wherein the processor is further configured to:

reactivate at least one of a third PDP context and a third EPS bearer that are associated with the first IP version type, wherein reactivation of the at least one of the third PDP context and the third EPS bearer is performed separately from reactivation of the at least one of the second PDP context and the second EPS bearer.

11. The UE of claim 1 wherein the processor is further configured to:

reactivate a plurality of PDP contexts, wherein reactivation of the plurality of PDP contexts is performed separately.

12. The UE of claim 1 wherein the processor is further configured to:

deactivate at least one of a second PDP context and a second EPS bearer that are associated with the second IP version type, wherein the at least one of the second PDP context and the second EPS bearer had been previously activated by the UE.

13. The UE of claim 12 wherein the processor is further configured to:

reactivate at least one of a third PDP context and a third EPS bearer that are associated with the first IP version type.

14. The UE of claim 1 wherein the processor is further configured to:

avoid reactivation of the at least one of the PDP context and the EPS bearer that are associated with the second IP version type.

15. An access node, comprising:

at least one component configured to transmit one of a mobility message or a system information message to a user equipment (UE), wherein the mobility message or the system information message contains an internet protocol (IP) version field that identifies a type of internet protocol addressing supported.

16. The access node of claim 15, wherein the mobility message is one of a MobilityFrom EUTRACommand message, a PhysicalChannelReconfiguration message, a CELL CHANGE ORDER FROM UTRAN message, a PS handover command message, a Cell Change Order message, a RAU Accept message, a Tracking Area Update Accept message, and an Attach Accept message.

17. The access node of claim 15, wherein the type of internet protocol addressing comprises an internet protocol version 4 (IPv4) version type, an internet protocol version 6 (IPv6) version type, and internet protocol version 4 and version 6 double (IPv4v6 double) version type, and an internet protocol version 4 and version 6 single (IPv4v6 single) version type.

18. The access node of claim 15, wherein the IP version field identifies the type of internet protocol addressing supported by a serving general packet radio service support node (SGSN).

19. The access node of claim 15, wherein the IP version field identifies the type of internet protocol addressing supported for each access point name (APN) reserved for UEs.

20. The access node of claim 15, wherein the IP version field identifies the type of internet protocol addressing supported for each access point name (APN) associated with an active PDP context of the UE.

21. The access node of claim 15, wherein the IP version field identifies the type of Internet protocol addressing supported for each PDP context activated for the UE.

22. A user equipment (UE), comprising:

a processor configured to decode an internet protocol (IP) version field in a mobility message and to adapt a data communication function of the UE based on the IP version field.

23. The UE of claim 22, wherein at least one of the UE, a packet data protocol (PDP) context, and an evolved packet system (EPS) bearer context is configured for double internet protocol (IP) version 4 and version 6 (IPv4v6) type addressing before the mobility message is received by the UE, and wherein the processor is further configured to:

when the IP version field indicates IP version 4 type addressing, deactivate a PDP context or an EPS bearer associated with an application of the UE that uses IP version 6 type addressing.

24. The UE of claim 22, wherein at least one of the UE, a packet data protocol (PDP) context, and an evolved packet system (EPS) bearer context is configured for double internet protocol (IP) version 4 and version 6 (IPv4v6) type addressing before the mobility message is received by the UE, and wherein the processor is further configured to:

when the IP version field indicates IP version 6 type addressing, deactivate a PDP context or an EPS bearer associated with an application of the UE that uses IP version 4 type addressing.

25. The UE of claim 22, wherein at least one of the UE, a packet data protocol (PDP) context, and an evolved packet system (EPS) bearer context is configured for internet protocol (IP) version 4 (IPv4) type addressing before the mobility message is received by the UE, and wherein the processor is further configured to:

when the IP version field indicates IP version 6 type addressing, deactivate a PDP context of the UE.

26. The UE of claim 22, wherein at least one of the UE, a packet data protocol (PDP) context, and an evolved packet system (EPS) bearer context is configured for internet protocol (IP) version 6 (IPv6) type addressing before the mobility message is received by the UE, and wherein the processor is further configured to:

when the IP version field indicates IP version 4 type addressing, deactivate a PDP context of the UE.

27. The UE of claim 22, wherein at least one of the UE, a packet data protocol (PDP) context, and an evolved packet system (EPS) bearer context is configured for double internet protocol (IP) version 4 and version 6 (IPv4v6) type addressing before the mobility message is received by the UE, and wherein the processor is further configured to:

when the IP version field indicates IP versions 4 and 6 single type addressing (IPv4v6 single), deactivate a PDP context or an EPS bearer that uses double hybrid IPv4 and IPv6 version type addressing.

28. The UE of claim 22, wherein at least one of the UE, a packet data protocol (PDP) context, and an evolved packet system (EPS) bearer context is configured for double internet protocol (IP) version 4 and version 6 (IPv4v6) type addressing before the mobility message is received by the UE, and wherein the processor is further configured to:

when the IP version field indicates IP versions 4 and 6 single type addressing (IPv4v6 single), activate a PDP context or an EPS bearer for IPv4 version types addressing.

29. The UE of claim 22 wherein at least one of the UE, a packet data protocol (PDP) context, and an evolved packet system (EPS) bearer context is configured for double internet protocol (IP) version 4 and version 6 (IPv4v6) type addressing before the mobility message is received by the UE, and wherein the processor is further configured to:

when the IP version field indicates IP versions 4 and 6 single type addressing (IPv4v6 single), activate a PDP context or an EPS bearer for IPv6 version types addressing.

30. The UE of claim 22 wherein at least one of the UE, a packet data protocol (PDP) context, and an evolved packet system (EPS) bearer context is configured for double internet protocol (IP) version 4 and version 6 (IPv4v6) type addressing before the mobility message is received by the UE, and wherein the processor is further configured to:

when the IP version field indicates IP version 6 type addressing, activate a PDP context or an EPS bearer for IPv6 version type addressing.

31. The UE of claim 22 wherein at least one of the UE, a packet data protocol (PDP) context, and an evolved packet system (EPS) bearer context is configured for double internet protocol (IP) version 4 and version 6 (IPv4v6) type addressing before the mobility message is received by the UE, and wherein the processor is further configured to:

when the IP version field indicates IP version 4 type addressing, activate a PDP context or an EPS bearer for IPv4 version type addressing.

32. The UE of claim 22, wherein the mobility message is one of a MobilityFrom EUTRACommand message, a PhysicalChannelReconfiguration message, a CELL CHANGE ORDER FROM UTRAN message, a PS handover command message, a Cell Change Order message, a RAU Accept message, a Tracking Area Update Accept message, and an Attach Accept message.

33. A user equipment (UE), comprising:

at least one component configured to determine an internet protocol addressing version of an access node and, responsive to determining the internet protocol addressing version of the access node, to deactivate one of a packet data protocol (PDP) context and an evolved packet system (EPS) bearer.

34. The user equipment of claim 33, wherein the at least one component determines the internet protocol addressing version of the access node by reading an internet protocol version field transmitted by the access node in one of a mobility message and a system information message.

35. The user equipment of claim 33, wherein the at least one component is further configured to reactivate the one of the PDP context and the EPS bearer based on the internet protocol addressing version of the access node.

36. A user equipment (UE), comprising:

at least one component configured to detect a time-out of a data transfer of an application and, responsive to detecting the time-out of the data transfer of the application to deactivate one of a packet data protocol (PDP) context based on a first internet protocol addressing version and an evolved packet system (EPS) bearer based on the first internet protocol addressing version, wherein the one of the PDP context and the EPS bearer is associated with the application, and

to reactivate the one of the PDP context and the EPS bearer based on a second internet protocol addressing version.

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

receiving a message; and

responsive to the message indicating a first Internet Protocol (IP) version type, deactivating at least one of a packet data protocol (PDP) context and an evolved packet system (EPS) bearer that are associated with a second IP version type, wherein the at least one of the PDP context and the EPS bearer had been previously activated by the UE.

38. The method of claim 37 further comprising:

reactivating at least one of a second PDP context and a second EPS bearer that are associated with the first IP version type.

39. The method of claim 38 further comprising:

reactivating at least one of a third PDP context and a third EPS bearer that are associated with the first IP version type, wherein reactivating the at least one of the third PDP context and the third EPS bearer is performed separately from reactivating at least one of the second PDP context and the second EPS bearer.

40. The method of claim 37 further comprising:

reactivating a plurality of PDP contexts, wherein reactivation of the plurality of PDP contexts is performed separately.

41. The method of claim 37 further comprising:

deactivating at least one of a second PDP context and a second EPS bearer that are associated with the second IP version type, wherein the at least one of the second PDP context and the second EPS bearer had been previously activated by the UE.

42. The method of claim 41 further comprising:

reactivating at least one of a third PDP context and a third EPS bearer that are associated with the first IP version type.

43. The method of claim 37 further comprising:

avoiding reactivation of the at least one of the PDP context and the EPS bearer that are associated with the second IP version type.

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

determining an Internet protocol addressing version of an access node; and

responsive to determining the internet protocol addressing version of the access node, deactivating one of a packet data protocol (PDP) context and an evolved packet system (EPS) bearer.

45. The method of claim 44 further comprising:

determining the internet protocol addressing version of the access node by reading an internet protocol version field transmitted by the access node in one of a mobility message and a system information message.

46. The method of claim 44 further comprising:

reactivating the one of the PDP context and the EPS bearer based on the internet protocol addressing version of the access node.

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

detecting a time-out of a data transfer of an application;

responsive to detecting the time-out of the data transfer of the application, deactivating one of a packet data protocol (PDP) context based on a first internet protocol addressing version and an evolved packet system (EPS) bearer based on the first internet protocol addressing version, wherein the one of the PDP context and the EPS bearer is associated with the application, and

reactivating the one of the PDP context and the EPS bearer based on a second internet protocol addressing version.