IP Library Granted Patent US 9,924,454
Granted Patent B2
US 9,924,454 · App. 13/216,040 · Granted Mar 20, 2018

Method, apparatus and system for establishing connection

Inventors: Shanshan Wang (Shanghai, CN); Ying Hu (Shenzhen, CN)
Assignee: Nokia Technologies Oy
H04W48/17H04L41/048H04L43/18H04W76/022H04W80/045H04W8/12H04W80/04
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 9,924,454
App. No.
13/216,040
Granted
Mar 20, 2018
Kind
B2
Abstract

A method for establishing a connection is provided. The method includes the following steps. A mobility management entity generates a create bearer context request message and sends the message to a selected serving gateway. The create bearer context request message at least includes address information of at least one packet data network gateway and corresponding indication information of the protocol type of connection establishment. The serving gateway receives and analyzes the create bearer context request message, and determines the protocol type of the connection according to the indication information of the protocol type of connection establishment. The serving gateway processes the create bearer context request message with the determined protocol type of connection. A mobility management entity, a serving gateway, and a network system which are able to reduce time delay when connection is established are further provided.

Claims (59)

1. A method for establishing a connection, comprising:

generating, by a mobility management entity (MME) in a system architecture evolution (SAE), a create bearer context request message; and

sending, by the MME, the create bearer context request message to a selected serving gateway in the SAE, wherein the create bearer context request message comprises an address of a packet data network gateway (PDN GW) and information of a protocol type that is supported by the PDN GW and is used for an interface between the selected serving gateway in the SAE and the PDN GW.

2. The method according to the claim 1 , wherein the protocol type comprises at least one of a General Packet Radio Service Tunneling Protocol (GTP), a Proxy Mobile IP Protocol (PMIP), and a Client Mobile IP Protocol (CMIP).

3. A method for establishing a connection, comprising:

receiving, by a serving gateway in a system architecture evolution (SAE), a create bearer context request message from a mobility management entity (MME) in the SAE;

obtaining, by the serving gateway, from the received create bearer context request message, an address of a packet data network gateway (PDN GW) and information of a protocol type that is supported by the PDN GW and is used for an interface between the serving gateway in the SAE and the PDN GW;

determining, by the serving gateway, that the protocol type is a General Packet Radio Service Tunneling Protocol (GTP), a Proxy Mobile IP Protocol (PMIP) or a Client Mobile IP Protocol (CMIP); and

processing, by the serving gateway, the create bearer context request message based on the protocol type.

4. The method according to claim 3 , wherein the protocol type is GTP, and wherein processing the create bearer context request message comprises:

sending, by the serving gateway, a create bearer context request message to the PDN GW after determining that the protocol type is GTP.

5. A method for establishing a connection, implemented in a system comprising at least a mobility management entity, a serving gateway, and a packet data network gateway, the method comprising:

generating, by the mobility management entity, a create bearer context request message and sending the create bearer context request message to the serving gateway, wherein the create bearer context request message comprises an address of the packet data network gateway and information of a protocol type that is supported by the packet data network gateway and is used for an interface between the serving gateway and the packet data network gateway;

receiving, by the serving gateway, the create bearer context request message, obtaining, by the serving gateway, the address of the packet data network gateway and the information of the protocol type, and determining, by the serving gateway, that the protocol type is a General Packet Radio Service Tunneling Protocol (GTP), a Proxy Mobile IP Protocol (PMIP) or a Client Mobile IP Protocol (CMIP); and

processing, by the serving gateway, the create bearer context request message based on the packet type.

6. The method according to claim 5 , wherein processing the create bearer context request message comprises:

sending, by the serving gateway, a create bearer context request information to the packet data network gateway if the protocol type is GTP; or

sending, by the serving gateway, a PMIP-binding update message to the packet data network gateway and establishing a PMIP tunnel between the serving gateway and the packet data network gateway if the protocol type is PMIP; or

assigning and sending, by the serving gateway, a care-of address to a user equipment to perform a CMIP registration if the protocol type is CMIP.

7. A mobility management entity, comprising:

a receiver configured to obtain address of a packet data network gateway and information of a protocol type that is supported by the packet data network gateway and is used for an interface between the packet data network gateway and a serving gateway; and

a processor coupled to the receiver and configured to generate a create bearer context request message that includes the address of the packet data network gateway and the information of the protocol type, and send the create bearer context request message to the serving gateway.

8. The mobility management entity according to claim 7 , wherein the protocol type comprises one of a General Packet Radio Service Tunneling Protocol (GTP), a Proxy Mobile IP Protocol (PMIP) and a Client Mobile IP Protocol (CMIP).

9. The mobility management entity according to claim 7 , further comprising:

a storage device configured to store the address of the packet data network gateway and the information of the protocol type.

10. A serving gateway, comprising:

a receiver configured to receive a create bearer context request message from a mobility management entity (MME) in a system architecture evolution (SAE), wherein the create bearer context request message comprises an address of a packet data network gateway (PDN GW) and information of a protocol type that is supported by the PDN GW and is used for an interface between the PDN GW and the serving gateway;

a processor coupled to the receiver and configured to determine that the protocol type is a General Packet Radio Service Tunneling Protocol (GTP), a Proxy Mobile IP Protocol (PMIP) or a Client Mobile IP Protocol (CMIP), and process the create bearer context request message based on the protocol type.

11. The serving gateway according to claim 10 , further comprising:

a transmitter configured to send a create bearer context request message to the PDN GW to establish a connection with the PDN GW, based on the determination that the protocol type is GTP.

12. A network system comprising:

a mobility management entity,

a serving gateway, and

a packet data network gateway,

wherein the mobility management entity is configured to generate a create bearer context request message and send the create bearer context request message to the serving gateway,

wherein the create bearer context request message comprises an address of the packet data network gateway and information of a protocol type that is supported by the packet data network gateway and is used for an interface between the packet data network gateway and the serving gateway; and

wherein the serving gateway is configured to receive the create bearer context request message from the mobility management entity, determine that the protocol type is a General Packet Radio Service Tunneling Protocol (GTP), a Proxy Mobile IP Protocol (PMIP), or a Client Mobile IP Protocol (CMIP), and process the create bearer context request message based on the protocol type.

13. The network system according to claim 12 , further comprising:

a Home Subscriber Server (HSS), configured to store the address of the packet data network gateway and the information of the protocol type; or

a Domain Name Service Server (DNS) server, configured to store the address of the packet data network gateway and the information of the protocol type.

14. The method according to claim 1 , further comprising:

obtaining, by the MME, the address of the PDN GW and the information of the protocol type from at least one of a home subscriber server (HSS) and a domain name service server (DNS).

15. The method according to claim 1 , wherein the address of the PDN GW and the information of the protocol type are configured in the MME.

16. The method according to claim 4 , further comprising:

receiving, by the serving gateway, from the packet data network gateway, a create bearer context response comprising an IP address allocated for a user equipment.

17. The method according to claim 16 , further comprising:

creating, by the serving gateway, a entry in an evolved packet system (EPS) bearer table.

18. The method according to claim 3 , wherein processing the create bearer context request message comprises:

sending, by the serving gateway, a PMIP-binding update message to the packet data network.

19. The method according to claim 18 , further comprising:

receiving, by the serving gateway, from the packet data network gateway, a PMIP-binding update response message comprising an IP address allocated for a user equipment.

20. The method according to claim 19 , further comprising:

creating, by the serving gateway, a entry in an evolved packet system (EPS) bearer table.

21. The method according to claim 3 , wherein the protocol type is CMIP, and wherein processing the create bearer context request message comprises:

assigning and sending, by the serving gateway, a care-of address to a user equipment to perform a CMIP registration after determining that the protocol type is CMIP.

22. The serving gateway according to claim 10 , further comprising:

a transmitter configured to send a PMIP-binding update message to establish a PMIP tunnel between the serving gateway and the PDN GW, based on the determination that the protocol type is PMIP.

23. The serving gateway according to claim 10 , further comprising:

a transmitter configured to send a care-of address to a user equipment to perform a CMIP registration, based on the determination that the protocol type is CMIP.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 14, 2018
From: HUAWEI TECHNOLOGIES CO., LTD.
To: NOKIA TECHNOLOGIES OY
Reel/Frame 045337/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 8, 2016
From: WANG, SHANSHAN; HU, YING
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 040604/0722 →
Priority Claims (2)
CN 2007 1 0028575 · Jun 14, 2007 · national
CN 2007 1 0165080 · Nov 7, 2007 · national
Continuity (3)
Continuation 12471663 · May 26, 2009
Continuation PCTCN2008071158 · May 31, 2008
Related Publication 20110305202A1 · Dec 15, 2011