IP Library Granted Patent US 7,406,057
Granted Patent B2
US 7,406,057 · App. 10/493,809 · Granted Jul 29, 2008

Method for handling of messages between a terminal and a data network

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,406,057
App. No.
10/493,809
Granted
Jul 29, 2008
Kind
B2
Abstract

A method for handling of messages between a terminal and a data network, in which messages of a specific protocol are handled using correspondingly defined specific contexts for messages of the protocol. Messages based on the same specific protocol relate to different service categories. A message is received at the network, and an analysis of the message is performed to determine a service category of the received message. A different specific context is assigned to each received message dependent on the analyzed service category.

Claims (39)

1. A method for handling of messages between a terminal and a data network, wherein messages of a specific protocol are handled using defined specific contexts for messages of said protocol, and wherein messages based on the same specific protocol relate to different service categories, said method comprising the steps of:

receiving a message at said network,

analyzing said service category of said received message, and

assigning a specific context to said message dependent on the analyzed service category,

wherein contexts for messages of a specific protocol rely on a same context address defined between the terminal and the data network, and

wherein said assigning comprises the further step of marking said message dependent on the analyzed service category, and setting a routing indicator dependent on said marking, said routing indicator being adapted to selectively assign said specific context to said message.

2. A method according to claim 1 , wherein said marking is effected by setting header information in said message to a value corresponding to the service category.

3. A method according to claim 2 , wherein said marking is effected by setting Differentiated Service CodePoints using the Differentiated Service bit field in the message header.

4. A method according to claim 1 , wherein said marking is effected by setting transport protocol port numbers to a value corresponding to the service category.

5. A method according to claim 1 , wherein said routing indicator to which said marking is mapped is a traffic flow template TFT.

6. A method according to claim 1 , wherein said different service categories are indicated by a service type identifier included in the message, and said analyzing is based on said service type identifier.

7. A method according to claim 1 , wherein at a network node receiving said message there is defined a profile for each message type adapted to allocate a service category to each received message, and said analyzing is based on said profile.

8. A method according to claim 7 , wherein said profile for each message type defines a policy for an action to be taken on said message.

9. A data network control entity for use in a data network, wherein messages of a specific protocol are handled using defined specific contexts for messages of said protocol, and wherein messages based on the same specific protocol relate to different service categories, said entity comprising:

a transmission means adapted to receive a message at said network entity,

an analyzing means adapted to analyze said service category of said received message,

a marking means adapted to mark packets based on a result of said analysis by said analyzing means,

wherein said transmission means is further adapted to forward said marked packets to a data network access node, and

wherein contexts for messages of a specific protocol rely on a same context address defined between the terminal and the data network access node.

10. An entity according to claim 9 , wherein said marking means is further adapted to mark said message dependent on the analyzed service category.

11. An entity according to claim 10 , wherein said marking is effected by setting header information in said message to a value corresponding to the service category.

12. A method according to claim 11 , wherein said marking is effected by setting Differentiated Service CodePoints using the Differentiated Service bit field in the message header.

13. A method according to claim 10 , wherein said marking is effected by setting transport protocol port numbers to a value corresponding to the service category.

14. A data network comprising at least a data network control entity according to claim 9 , further comprising a data network access node for use in a data network, wherein messages of a specific protocol are handled using defined specific contexts for messages of said protocol, and wherein messages based on the same specific protocol relate to different service categories, said node comprising a transmission means adapted to receive marked packets from a data network control entity, a mapping means adapted to map a marking of a received packet to a routing indicator, and an assigning means adapted to assign a specific context to said message dependent on the mapped routing indicator, wherein contexts for messages of a specific protocol rely on a same context address defined between the terminal and the data network.

15. A data network access node for use in a data network, wherein messages of a specific protocol are handled using defined specific contexts for messages of said protocol, and wherein messages based on the same specific protocol relate to different service categories, said node comprising:

a transmission means adapted to receive marked packets from a data network control entity,

a mapping means adapted to map a marking of a received packet to a routing indicator, and

an assigning means adapted to assign a specific context to said message dependent on the mapped routing indicator,

wherein contexts for messages of a specific protocol rely on a same context address defined between the terminal and the data network.

16. An access node according to claim 15 , wherein said routing indicator to which said marking is mapped is a traffic flow template.

17. A method for handling of messages between a terminal and a data network, wherein messages of a specific protocol are handled using defined specific contexts for messages of said protocol, and wherein messages based on the same specific protocol relate to different service categories, said method comprising the steps of:

receiving a message at said network,

analyzing said service category of said received message, and

assigning a specific context to said message dependent on the analyzed service category,

wherein contexts for messages of a specific protocol rely on a same context address defined between the terminal and the data network,

wherein defining said specific contexts for messages of said protocol comprises the steps of: configuring part of mapping information allocating marking information to corresponding routing indicator information in response to a context activation request from said terminal to an access node of said data network.

18. A method according to claim 17 , wherein said context activation request is detected at said access node as a first context activation request and configuring is effected based on the fact that a first request is a request for a predetermined context.

19. A method according to claim 17 , wherein said context activation request indicates the requested context and configuring is effected based on the detected requested context.

20. A method according to claim 17 , further comprising the steps of returning marking information used for marking packets from said data network to said terminal in response to a previous request from said terminal to said data network, subsequently requesting, from said terminal to said data network, the activation of a context using the marking information returned to said terminal in said returning step, and configuring part of mapping information using the returned marking information.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 10, 2019
From: INTELLECTUAL VENTURES ASSETS 121 LLC
To: LF CAPITAL PARTNERS, LLC
Reel/Frame 049425/0231 →
NUNC PRO TUNC ASSIGNMENT Recorded Jan 10, 2019
From: INTELLECTUAL VENTURES I LLC
To: INTELLECTUAL VENTURES ASSETS 121 LLC
Reel/Frame 047961/0289 →
MERGER Recorded Jul 22, 2011
From: SPYDER NAVIGATIONS L.L.C.
To: INTELLECTUAL VENTURES I LLC
Reel/Frame 026637/0611 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 28, 2007
From: NOKIA CORPORATION
To: SPYDER NAVIGATIONS L.L.C.
Reel/Frame 019893/0477 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 27, 2004
From: ISOMAKI, MARKUS; HURTTA, TUIJA; HAUMONT, SERGE
To: NOKIA CORPORATION
Reel/Frame 015693/0807 →