Interface between 3GPP networks and 3GPP2 networks for WAP text messaging

• US 8,447,280 B2
• Filed: 07/18/2011
• Issued: 05/21/2013
• Est. Priority Date: 07/18/2011
• Status: Expired due to Fees

• Current Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Original Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Inventors: Cai, Yigang, Ganguly, Gopa, Singh, Sanjeev, Shah, Shaumir
• Primary Examiner(s): DOAN, KIET M
• Application Number:
  US13/184,809
• Publication Number:
  US 20130023253A1
• Time in Patent Office: 673 Days
• Field of Search: 455/458, 455/466, 455/414.1, 455/435.1, 455/420, 455/566, 370/331, 370/356, 370/328, 370/419, 705/26.1
• US Class Current: 455/414.1
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 80/12 Application layer protocols, e.g. WAP [Wireless Application Protocol]

Abstract

Systems and methods are disclosed for interworking WAP text messages between 3GPP and 3GPP2 networks. One embodiment comprises a system that receives a WAP text message from a sending entity that supports 3GPP standards, where the WAP text message is in a 3GPP format. The system determines that a receiving entity for the WAP text message supports 3GPP2 standards, and converts the WAP text message from the 3GPP format to a 3GPP2 format. The system then transmits the WAP text message in the 3GPP2 format to the receiving entity.

Claims

1. A system comprising:

an interface operable to receive a Wireless Application Protocol (WAP) text message from a sending entity that supports 3^rd Generation Partnership Project (3GPP) standards, wherein the WAP text message is in a 3GPP format; and

a controller operable to determine that a receiving entity for the WAP text message supports 3^rd Generation Partnership Project 2 (3GPP2) standards, and to convert the WAP text message from the 3GPP format to a 3GPP2 format;

the interface is further operable to transmit the WAP text message in the 3GPP2 format to the receiving entity;

wherein;

the controller is further operable to parse the WAP text message in 3GPP format to identify User Data Header (UDH) parameters, and to map the UDH parameters to User Data parameters of the 3GPP2 Teleservice Layer.

2. The system of claim 1 wherein:

the controller is further operable to map Information Element Data from an Information Element having an Information Element Identifier set to “

05”

to a source port parameter and a destination port parameter in the Teleservice Layer.

3. The system of claim 1 wherein:

the controller is further operable to map Information Element Data from an Information Element having an Information Element Identifier set to “

00”

to a number-of-segments parameter and a segment-number parameter in the Teleservice Layer.

4. The system of claim 1 wherein:

the controller is further operable to receive multiple segments for the WAP text message in 3GPP format, to aggregate the multiple segments into a single segment, and to convert the single segment of the WAP text message to the 3GPP2 format.

5. A method comprising:

receiving a Wireless Application Protocol (WAP) text message from a sending entity that supports 3^rd Generation Partnership Project (3GPP) standards, wherein the WAP text message is in a 3GPP format;

determining that a receiving entity for the WAP text message supports 3^rd Generation Partnership Project 2 (3GPP2) standards;

converting the WAP text message from the 3GPP format to a 3GPP2 format; and

transmitting the WAP text message in the 3GPP2 format to the receiving entity;

wherein converting the WAP text message from the 3GPP format to a 3GPP2 format comprises;

parsing the WAP text message in 3GPP format to identify User Data Header (UDH) parameters; and

mapping the UDH parameters to User Data parameters of the 3GPP2 Teleservice Layer.

6. The method of claim 5 wherein mapping the UDH parameters comprises:

mapping Information Element Data from an Information Element having an Information Element Identifier set to “

05”

to a source port parameter and a destination port parameter in the Teleservice Layer.

7. The method of claim 5 wherein mapping the UDH parameters comprises:

mapping Information Element Data from an Information Element having an Information Element Identifier set to “

00”

to a number-of-segments parameter and a segment-number parameter in the Teleservice Layer.

8. The method of claim 5 further comprising:

receiving multiple segments for the WAP text message in 3GPP format'"'"'

aggregating the multiple segments into a single segment; and

converting the single segment of the WAP text message to the 3GPP2 format.

9. A system comprising:

an interface operable to receive a Wireless Application Protocol (WAP) text message from a sending entity that supports 3^rd Generation Partnership Project 2 (3GPP2) standards, wherein the WAP text message is in a 3GPP2 format; and

a controller operable to determine that a receiving entity for the WAP text message supports 3^rd Generation Partnership Project (3GPP) standards, and to convert the WAP text message from the 3GPP2 format to a 3GPP format;

the interface is further operable to transmit the WAP text message in the 3GPP format to the receiving entity;

wherein;

the controller is further operable to parse the WAP text message in 3GPP2 format to identify User Data parameters of the 3GPP2 Teleservice Layer, and to map the User Data parameters to User Data Header (UDH) parameters of the Mobile Application Part (MAP) Short Message Transport Layer (SM-TL).

10. The system of claim 9 wherein:

the controller is further operable to map a source port parameter and a destination port parameter in the Teleservice Layer to Information Element Data from an Information Element having an Information Element Identifier set to “

05”

.

11. The system of claim 9 wherein:

the controller is further operable to map a number-of-segments parameter and a segment-number parameter in the Teleservice Layer to Information Element Data from an Information Element having an Information Element Identifier set to “

00”

.

12. The system of claim 9 wherein:

the controller is further operable to determine that after conversion, a length of the WAP text message exceeds a length limit in the 3GPP format, and to segment the WAP text message into multiple segments in the 3GPP format.

13. A method comprising:

receiving a Wireless Application Protocol (WAP) text message from a sending entity that supports 3^rd Generation Partnership Project 2 (3GPP2) standards, wherein the WAP text message is in a 3GPP2 format;

determining that a receiving entity for the WAP text message supports 3^rd Generation Partnership Project (3GPP) standards;

converting the WAP text message from the 3GPP2 format to a 3GPP format; and

transmitting the WAP text message in the 3GPP format to the receiving entity;

wherein converting the WAP text message from the 3GPP2 format to a 3GPP format comprises;

parsing the WAP text message in 3GPP2 format to identify User Data parameters of the 3GPP2 Teleservice Layer; and

mapping the User Data parameters to User Data Header (UDH) parameters of the Mobile Application Part (MAP) Short Message Transport Layer (SM-TL).

14. The method of claim 13 wherein mapping the User Data parameters comprises:

mapping a source port parameter and a destination port parameter in the Teleservice Layer to Information Element Data from an Information Element having an Information Element Identifier set to “

05”

.

15. The method of claim 13 wherein mapping the User Data parameters comprises:

mapping a number-of-segments parameter and a segment-number parameter in the Teleservice Layer to Information Element Data from an Information Element having an Information Element Identifier set to “

00”

.

16. The method of claim 13 further comprising:

determining that after conversion, a length of the WAP text message exceeds a length limit in the 3GPP format; and

segmenting the WAP text message into multiple segments in the 3GPP format.