Abstract
in a radio telecommunications network a serving gateway support node controls connections between user equipment nodes and a packet-based network that pass through at least one serving gateway and at least one packet gateway. The serving gateway support node detects failure of communications to a first serving gateway. The serving gateway support node responds to the detected failure by initiating relocation of existing connections through the first serving gateway to instead pass through a second serving gateway. The serving gateway support node detects recovery of communications to the first serving gateway and responds by ceasing relocation of at least some of the existing connections that have not yet been relocated to the second serving gateway. Related methods serving gateways and packet gateways are also disclosed.
| Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | |||||
|---|---|---|---|---|---|---|---|---|---|
| Declaration Date | Declaration Reference | Declaring Company | Specification Number | ||||||
| 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
Specification Information
Specification Information
Technologies
Family Information
| All Granted Patents In Patent Family : | ---- |
| All Pending Patents In Patent Family : | ---- |
| Publication No | Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| Declaration Date | Declaration Reference | Declaring Company | Specification Number | |||||||
| US2012063300A1 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | Yes | Basis Patent | ||||
| US2012063300A1 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | Yes | Basis Patent | ||||
| US2012063300A1 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| US8848516B2 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | Yes | Basis Patent | ||||
| US8848516B2 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | Yes | Basis Patent | ||||
| US8848516B2 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| CN103202064A | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| CN103202064A | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| CN103202064A | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| EP2617235A2 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| EP2617235A2 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| EP2617235A2 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| EP2617235B1 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| EP2617235B1 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| EP2617235B1 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| EP2693806A2 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| EP2693806A2 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| EP2693806A2 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| EP2693806A3 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| EP2693806A3 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| EP2693806A3 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| JP2013537387A | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| JP2013537387A | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| JP2013537387A | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| JP5957454B2 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| JP5957454B2 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| JP5957454B2 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| KR101802005B1 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| KR101802005B1 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| KR101802005B1 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| KR20130107302A | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| KR20130107302A | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| KR20130107302A | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| WO2012035450A2 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| WO2012035450A2 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| WO2012035450A2 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | Yes | Basis Patent | ||||
| WO2012035450A3 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| WO2012035450A3 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| WO2012035450A3 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | Yes | Basis Patent | ||||
| JP2015195622A | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| JP2015195622A | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| JP2015195622A | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| JP6063530B2 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| JP6063530B2 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| JP6063530B2 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| BR112013006149A2 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| BR112013006149A2 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| BR112013006149A2 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| CA2811467C | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| CA2811467C | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| CA2811467C | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| CN109257787A | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| CN109257787A | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| CN109257787A | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| CN109257787B | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| CN109257787B | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| CN109257787B | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| EP2693806B1 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| EP2693806B1 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| EP2693806B1 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| PL2693806T3 | 4G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| PL2693806T3 | 4G,3G,2G | 24/06/2015 | ISLD-201506-018 | ERICSSON INC | No | Family Member | ||||
| PL2693806T3 | 5G | 19/09/2023 | ISLD-202309-053 | ERICSSON INC | No | Family Member | ||||
| Publication No | Technology | Declaration Information | Specification Information | Explicitly Disclosed | Patent Type | Status | National Phase Entries | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Declaration Date | Declaration Reference | Declaring Company | Specification Information | |||||||||
| ----- | ----- | ----- | ----- | ----- |
S1
|
----- | ----- | ----- | ----- | |||
Technologies
Mobility and handover
Product
Gateway node
Use Cases
Services
Mobility Management
Claim
1. A serving gateway support node that controls connections through at least one serving gateway of a radio telecommunications network, the serving gateway support node comprising circuitry configured to: detect failure of communications to a first serving gateway;initiate relocation of existing connections through the first serving gateway to instead pass through a second serving gateway in response to the detected failure of communications;detect recovery of communications to the first serving gateway; and cease relocation of at least some of the existing connections that have not yet been relocated to the second serving gateway in response to the detected recovery of communications.
2. The serving gateway support node of Claim 1, wherein: the circuitry is further configured to respond to the first serving gateway having completed a restart by restoring at least some of the existing connections to the first serving gateway .that have not yet been relocated to the second serving gateway.
3. The serving gateway support node of Claim 2, wherein:the circuitry is further configured to restore at least some of the existing. connections to the first serving gateway that have not yet been relocated to the second serving gateway by communicating context information to the first serving gateway for each of the existing connections that is to be restored to the first serving gateway.
4. The serving gateway support node of Claim 3, wherein:the context information communicated from the serving gateway support node to the first serving gateway for each of the existing connections that is to be restored to the first serving gateway includes identification of the connection, an Internet Protocol address of a packet gateway, a tunneling identifier, a Quality of Service value, and/or a bearer ID.
5. The serving gateway support node of Claim 2, wherein: the circuitry is further configured to signal, after the first serving gateway restarts, the first serving gateway to report a same restart counter to a packet gateway that the first serving gateway earlier reported to the packet gateway prior to the first serving gateway restarting to avoid the packet gateway terminating the connections that are being restored to the first serving gateway.
6. The serving gateway support node of Claim 1, wherein the circuitry is further configured to:receive messages from a first group of user equipment nodes indicating that they each have at least one packet awaiting communication through a first group of connections through the first serving gateway;determine that a second group of user equipment nodes have a second group of connections through the first serving gateway and that each of the second group of user equipment nodes have no packet awaiting communication; and relocate all of the first group of connections to the second serving gateway before relocating the second group of connections to the second serving gateway.
7. The serving gateway support node of Claim 1, wherein the circuitry is further configured to:relocate one of the existing connections for a user equipment node, which is in an Idle state Signalling Reduction (ISR) mode and is presently registered with both a S4-Serving GPRS Support Node (S4-SGSN) and a Mobility Management Entity (MME), by transferring context information for the first serving gateway through a S3 message from one of the S4-SGSN and MME to the other one of the S4-SGSN and MME.
8. The serving gateway support node of Claim 1, wherein the circuitry is further configured to:detect an event triggering handover of a user equipment node, which has not yet been relocated to the second serving gateway, from the serving, gateway support node to another serving gateway support node: and relocating the existing connections associated with the user equipment node by communicating from the serving gateway support node to the other serving gateway support an instruction in a GPRS Tunneling Protocol (GTP) message to carry out relocation of the first existing connection from the serving gateway support node to the other serving gateway support node.
9. The serving gateway support node of Claim 1, wherein the circuitry is further configured to:detect an event triggering handover of a user equipment node from another serving gateway support node;receive context information from the other serving gateway support node that identifies existing connections associated with the user equipment node;determine that the existing connections identified by the context information pass through the first serving gateway; and relocate the existing connections identified by the context information from the first serving gateway to the second serving gateway in response to the detected failure of communications with the first serving gateway
10. The serving gateway support node of Claim 1, wherein the circuitry is further configured to:detect an event triggering handover of a user equipment node, which has not yet been relocated to the second serving gateway, from the serving gateway support node to another serving gateway support node; and responsive to the detected event, communicate a message to the other serving gateway support node that identifies an invalid Fully Qualified Domain Name for the first serving gateway and/or an invalid Fully Qualified Temporary Endpoint Identifier for the first serving gateway
11. The serving gateway support node of Claim 1, wherein: the circuitry is further configured to respond to expiration of a threshold time since having started relocation of the existing connections and continuing failed communications by ceasing relocation of any remaining:, ones of the existing connections that have not yet been relocated to pass through the second serving gateway
12. A method for controlling connections that pass through at least one serving gateway of a radio telecommunications network, the method comprising the steps of detecting failure of communications to a first serving gateway;responding to the detected failure by a serving gateway support node initiating, relocation of existing connections through the first serving gateway to instead pass through a second serving gateway;detecting recovery of communications to the .first serving gateway; and responding to the detected recovery by the serving gateway support node ceasing relocation of at least some of the existing connections that have not yet been relocated to pass through the second serving gateway
13. The method of Claim 12, further comprising the steps of:detecting that the first serving gateway has completed a restart or recovered from communication failure; and responding to the detected restart by the serving gateway support node restoring at least some of the existing connections to the first serving gateway that have not yet been relocated to pass through the second serving. gateway
14. The method of Claim 13, wherein the step of responding to the detected restart by the serving gateway support node restoring at least some of the existing connections to the first serving gateway comprises:communicating context information to the first serving gateway for each of the existing connections that is to be restored to the first serving gateway, wherein the context, information comprises identification of the connection, an Internet Protocol address of a packet gateway, a tunneling identifier, a Quality of Service value, and/or a bearer ID,15. The method of Claim 12, further comprising the steps of: receiving messages from a first group of user equipment nodes indicating that they each have at least one packet awaiting communication through a first group of connections through the first serving gateway;determining that a second group of user equipment nodes have a second group of connections through the first serving gateway and that each of the second group of user equipment nodes has no packet awaiting communication; and relocating all of the first group of connections to the second serving gateway before relocating the second group of connections to the second serving gateway
16. The method of Claim 12, further comprising the step of:detecting at the serving gateway support node an event triggering handover of a user equipment node, which has not yet been relocated to the second serving gateway, from the serving gateway support node to another serving gateway support node; and relocating a first one of the existing connections associated with the user equipment node by communicating from the serving gateway support node to the other serving gateway support an instruction in a GPRS Tunneling Protocol (GTP) message to carry out relocation of the first existing connection from the serving gateway support node to the other serving gateway support node.17. The method of Claim 12, further comprising the step of:detecting at the serving gateway support node an event triggering handover of a user equipment node, Which has not vet been relocated to the second. serving gateway, from the serving gateway support node to another serving gateway support node; and responsive to the detected event, communicating a message to the other serving gateway support node that identifies an invalid Fully Qualified Domain Name for the first serving gateway and/or an invalid Fully Qualified Temporary Endpoint Identifier for the first serving gateway.', 'IS. The method of Claim 12, further comprising the step of:responding to expiration of a threshold time since having started relocation of the existing connections and a continuing failure of communications to the first serving gateway by the serving gateway support node ceasing relocation of any remaining ones of the existing connections that have not yet been relocated to pass through the second serving gateway.19. A method for controlling connections that pass through at least one serving gateway of a radio telecommunications network, the method comprising the steps of:receiving at a serving gateway support node a first message from an operator requesting that at least some connections be offloaded from a first serving gateway; and responding to the first message by the serving gateway support node relocating at least some of the connections from the first serving gateway to a second serving gateway.
20. The method of Claim 19, further comprising the step of:responding to the first message by the serving gateway support node instructing user equipment nodes, which are associated with each of the connections to be relocated, to move to an ECM-idle, PMM-idle, or GPRS-standby state before the serving gateway support node relocates the corresponding connections to the second serving gateway.
21. The method of Claim 19, wherein the step of responding to the first message by the serving gateway support node relocating at least some of the connections from the first serving gateway to a second serving gateway, comprises:relocating existing connections for a user equipment node, which is active in an Idle state Signalling Reduction (ISR) mode and is registered with both a S4-based Serving GPRS Support Node (S4-SGSN) and a Mobility Management Entity (MME) at a same time, by transferring context information for the first serving gateway through a S3 message from one of the S4-SGSN and MME to the other one of the S4-SGSN and MME.
22. A serving gateway comprising circuitry that is configured to:receive a connection restoration message from a serving gateway support node after the serving gateway has restarted; and respond to the connection restoration message by restoring in memory of the serving gateway at least some connections, which existed before the serving gateway restarted, between user equipment nodes and a packet-based network that passed through the serving gateway.
23. The serving gateway of Claim 22, wherein:the circuitry is further configured to restore context information in the memory from the connection restoration message that includes, for each of the existing connections that is to be restored, identification of the connection, an Internet Protocol address of a packet gateway, a tunneling identifier, and/or a Quality of Service value.
24. A packet gateway comprising circuitry that is configured to:determine whether a serving gateway support node supports a connection relocation mode through which the serving gateway support node relocates connections from a first serving gateway of a radio telecommunications network to a second serving gateway in response to the serving gateway support node detecting failure of communications to the first serving gateway;detect failure of communications to the first serving gateway;respond to the detected failure of communications and determining that the serving gateway support node supports the connection relocation mode by retaining in a memory of the packet gateway context information for any connections that the packet gateway has that pass through the first serving gateway; and respond to the detected failure of communications to the first serving gateway and determining that the serving gateway support node does not support the connection relocation mode by deleting from the memory of the packet gateway the context information for any connections that the packet gateway has that pass through the first serving gateway.
25. The packet gateway of Claim 24, wherein the circuitry is further configured to: detect failure of communications to the first serving gateway by detecting when the first serving gateway has restarted; respond to detecting that the first serving gateway has restarted and determining that the serving gateway support node supports the connection relocation mode by retaining in the memory of the packet gateway the context information for any connections that the packet gateway has that pass through the first serving gateway; and respond ro detecting that the first serving gateway has restarted and determining that the serving gateway support node does not support the connection relocation mode by deleting from the memory of the packet gateway the context information for any connections that the packet gateway has that pass through the first serving gateway.']
Associated Portfolios
Licensor Claim Chart
 Claim Chart |
 Technology |
 Creation Date |
 Download |
|---|---|---|---|
|
Claim charts will soon be available!
|
|||
SUMMARY
ClaimChart-CA2811467A1-STO
Patent number:CA2811467A1
Claim Chart Type : SEP Claim Chart
Price: 200 €
To view claim charts you must become a Gold or Platinum Member.
Upgrade your subscriptionYou have reached the maximum number of patents which can be associated to your account per your subscription. If you wish to associate more patents
Please upgrade your subscription.Note:
The information in blue was extracted from the third parties (Standard Setting Organisation, Espacenet)
The information in grey was provided by the patent holder
The information in purple was extracted from the FrandAvenue
Explicitly disclosed patent:openly and comprehensibly describes all details of the invention in the patent document.
Implicitly disclosed patent:does not explicitly state certain aspects of the invention, but still allows for these to be inferred from the information provided.
Basis patent:The core patent in a family, outlining the fundamental invention from which related patents or applications originate.
Family member:related patents or applications that share a common priority or original filing.