Method for transmitting application packet data

• US 20040148425A1
• Filed: 01/13/2004
• Published: 07/29/2004
• Est. Priority Date: 06/29/2001
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Hurtta, Tuija, Haumont, Serge, Reichler, Thomas, Axerud, Bo
• Application Number:
  US10/481,756
• Publication Number:
  US 20040148425A1
• Time in Patent Office: Days
• US Class Current: 709/236
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1096 Supplementary features, e.g. call forwarding or call holding systems providing special services or facilities to telephony subscribers H04M3/42
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/327 in the session layer [OSI layer 5]
• CPC Class Codes: H04W 80/04 Network layer protocols, e.g. mobile IP [Internet Protocol]
• CPC Class Codes: H04W 80/10 adapted for application session management, e.g. SIP [Session Initiation Protocol] connection management H04W76/00; arrangements for session management H04L67/14
• CPC Class Codes: H04W 92/02 Inter-networking arrangements

Abstract

The present invention concerns a method for transmitting application packet data via a first packet data network between a terminal and a second packet data network, said application packet data being transmitted using an application protocol operated on top of a protocol stack, said protocol stack comprising plural individual stacke protocol layers adopted for said transmission within said first packet data network, wherein said application packet data are addressed to the terminal and distinguishable according to a service type implemented for said terminal using said application, the method comprising the steps of: detecting said service type, and dependent on the transmission direction of said application packet data, removing and/or adding at least one of said plural individual protocol layers for a specific one of detected service type. The present invention also concerns accordingly adapted terminals and network nodes.

Claims

1. A method for transmitting application packet data

via a first packet data network between a terminal and

a second packet data network,

said application packet data being transmitted using an application protocol

operated on top of a protocol stack, said protocol stack comprising

plural individual stacked protocol layers adopted for said transmission within said first packet data network,

wherein said application packet data are addressed to the terminal and distinguishable according to a service type implemented for said terminal using said application,

the method comprising the steps of:

detecting said service type, and

dependent on the transmission direction of said application packet data, removing and/or adding at least one of said plural individual protocol layers for a specific one of detected service type.

2. A method according to claim 1, wherein

removing and/or adding at least one of said plural individual protocol layers is accomplished by removing and/or adding header information related to said respective protocol layer.

3. A method according to claim 1 or 2, wherein

removing/adding at least one of said plural individual protocol layers is effected at a gateway node of said first packet data network to said second packet data network.

4. A method according to claim 3, wherein

in downlink transmission from said second packet data network towards said terminal, said at least one of said plural individual protocol layers is removed, and

in uplink transmission from said terminal towards said second packet data network, said at least one of said plural individual protocol layers is added.

5. A method according to claim 1 or 2, wherein adding/removing at least one of said plural individual protocol layers is effected at said terminal communicating via said first packet data network with said second packet data network.

6. A method according to claim 5, wherein

in downlink transmission terminating at said terminal, said at least one of said plural individual protocol layers is added, and

in uplink transmission originating at said terminal, said at least one of said plural individual protocol layers is removed.

7. A method according to claim 1, wherein

the service type is indicated by the terminal to a gateway node.

8. A method according to claim 1, wherein

the service type of an application is distinguishable from a context defined for said terminal and application.

9. A method according to claim 8, wherein

a context definition comprises service type, address information of a terminal for which said service is implemented, and a quality of service definition.

10. A method according to claims 8 or 9, wherein the context definition additionally comprises

filter information, application type information, destination address and type of header to be added.

11. A method according to any of the preceding claims, wherein

in case different applications in the terminal share the same address, the gateway maps downlink packets to the appropriate context using a filter mechanism.

12. A method according to any of the preceding claims, wherein

protocol headers to be added are determined from said context and/or configured information.

13. A gateway node of a first packet data network,

said gateway node being adapted to transmit application packet data between a terminal connectable to said first packet data network and a second packet data network) connectable to said packet data network,

said application packet data being transmitted using an application protocol

operated on top of a protocol stack, said protocol stack comprising

plural individual stacked protocol layers adopted for said transmission within said first packet data network,

wherein said application packet data are addressed to the terminal and distinguishable according to a service type implemented for said terminal using said application,

said gateway node comprising

detection means adapted to detect said service type, and

selection means adapted to selectively remove and/or add at least one of said plural individual protocol layers dependent on the transmission direction of said application packet data, for a specific one of detected service type.

14. A gateway node according to claim 13, wherein said selection means is adapted to remove and/or add header information related to said respective protocol layer.

15. A gateway node according to claim 13 or 14, wherein said selection means is adapted

to remove said at least one of said plural individual protocol layers in downlink transmission from said second packet data network towards said terminal, and

to add said at least one of said plural individual protocol layers in uplink transmission from said terminal towards said second packet data network.

16. A gateway node according to claim 13 or 14, wherein

said selection means is adapted to add protocol headers based on information from said context and/or configured information.

17. A gateway node according to claim 13,

wherein said detection means is adapted to distinguish the service type of an application from a context defined for said application.

18. A gateway node according to claim 15 or 16, wherein

said detection means is adapted to select the appropriate context using a filter mechanism if different applications in the terminal share the same address.

19. A gateway node according to claim 17, wherein

a context definition comprises application type information, address information of a terminal for which said service is implemented, and a quality of service definition.

20. A gateway node according to claims 17 to 19, wherein the context definition additionally comprises

filter information, application type information, destination address and type of header to be added.

21. A terminal

connectable to a first packet data network and

adapted to transmit application packet data via said first packet data network to a second packet data network connectable to said first packet data network and to receive application packet data via said first packet data network from said second packet data network,

said application packet data being transmitted using an application protocol

operated on top of a protocol stack, said protocol stack comprising

plural individual stacked protocol layers adopted for said transmission within said first packet data network,

wherein said application packet data are addressed to the terminal and distinguishable according to a service type implemented for said terminal using said application,

said terminal comprising

detection means adapted to detect said service type,

activation means to establish a connection to a gateway node and

selection means adapted to selectively remove and/or add at least one of said plural individual protocol layers dependent on the transmission direction of said application packet data, for a specific one of detected service type.

22. A terminal according to claim 21,

wherein said detection means is adapted to distinguish the service type of an application from a context defined for said application.

23. A terminal according to claim 21 or 22, wherein

said detection means is adapted to select the appropriate context if different applications in the terminal share the same address.

24. A terminal according to claim 21, wherein

said activation means is adapted to establish one or many contexts in a gateway node.

25. A terminal according to claim 21, wherein said selection means is adapted to remove and/or add header information related to said respective protocol layer.

26. A terminal according to claim 21 or 25, wherein said selection means is adapted

to add said at least one of said plural individual protocol layers in downlink transmission terminating at said terminal, and

to remove said at least one of said plural individual protocol layers in uplink transmission originating at said terminal.

27. A terminal according to claim 22, wherein

a context definition comprises service type, address information of a terminal for which said service is implemented, and a quality of service definition.

28. A terminal according to claim 22, wherein

the context definition further comprises filter information, destination address, application type information and type of header to be added.