This application relates to wireless communication technologies, and more particularly, to a method, a apparatus and a system for transmitting a gateway address, which are used to solve the problem in the prior art that a DeNB is incapable of assisting an MME in selecting an SGW/PGW for a mobile relay node (RN). The method for transmitting a gateway address in an embodiment of this application comprises: a base station determining, when determining an access device to be a mobile RN, a gateway IP address of a mobility anchor serving as a gateway of the mobile RN; and sending the determined gateway IP address to a mobility management entity (MME) corresponding to the mobile RN. In the embodiment of this application, the DeNB is capable of assisting the MME in selecting a suitable mobility anchor for the mobile RN as the SGW/PGW, thereby guaranteeing normal work of the mobile RN.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for transmitting a gateway address, wherein the method comprises: determining, by an eNB, a gateway IP address of a mobility anchor which serves as a gateway of a mobile Relay Node, RN, upon determining an accessing device to be the mobile RN; and transmitting, by the eNB, the determined gateway IP address to a Mobility Management Entity, MME, serving for the mobile RN, wherein before determining the gateway IP address of the mobility anchor, the method further comprises: transmitting, by the eNB, an Interface Setup Request messages comprising identification information indicating that the eNB is a donor eNB.
This invention relates to wireless communication systems, specifically addressing the challenge of efficiently transmitting gateway address information for mobile Relay Nodes (RNs) in cellular networks. The method involves an evolved Node B (eNB) determining the IP address of a mobility anchor serving as a gateway for a mobile RN when an accessing device is identified as such. The eNB then transmits this gateway IP address to the Mobility Management Entity (MME) responsible for the mobile RN. Before determining the gateway IP address, the eNB sends an Interface Setup Request message that includes identification information indicating it is a donor eNB, which facilitates proper network configuration. The solution ensures seamless communication by enabling the MME to correctly route traffic through the appropriate gateway for the mobile RN, improving network efficiency and reliability in scenarios involving relayed connections. The method leverages existing network protocols and signaling to integrate relay node functionality without requiring extensive modifications to the core network infrastructure.
2. The method according to claim 1 , wherein if there are more than one mobility anchors, then before the eNB determines the gateway IP address of the mobility anchor, the method further comprises: selecting, by the eNB, one of the mobility anchors as the gateway of the mobile RN according to a requirement of load balancing; or selecting one of the mobility anchors as the gateway of the mobile RN dependent upon capacity of each mobility anchor; or selecting randomly one of the mobility anchors as the gateway of the mobile RN.
The method from the previous description (an eNB determining a gateway IP address for a mobile Relay Node and sending it to the MME) is enhanced when multiple mobility anchors are available. Before the eNB determines the gateway IP address, it selects one of the mobility anchors to act as the gateway for the mobile RN. This selection can be based on load balancing requirements, the capacity of each mobility anchor, or by randomly choosing one of the available mobility anchors. This ensures efficient resource utilization and prevents overload of any single mobility anchor.
3. The method according to claim 1 , wherein the gateway IP address determined by the eNB is one of: an IP address of an S1 interface of the mobility anchor; and an IP address of an X2 interface of the mobility anchor.
In the method where an eNB determines and transmits a gateway IP address for a mobile Relay Node, the gateway IP address determined by the eNB is either the IP address of the S1 interface of the mobility anchor (the interface between the eNB and the mobility anchor) or the IP address of the X2 interface of the mobility anchor (another interface between eNBs, possibly used for relaying). This provides the MME with the correct address for establishing connectivity and managing the mobile RN's data flow.
4. The method according to claim 3 , wherein if the S1 interface is set up between the eNB and the mobility anchor, then before the S1 interface is set up, the method further comprises: the eNB indicating that the eNB is a donor eNB in all of transmitted S1 Interface Setup Request messages, or the eNB indicating that the eNB is a donor eNB in an S1 Interface Setup Request message transmitted to the mobility anchor; or if the X2 interface is set up between the eNB and the mobility anchor, then before the X2 interface is set up, the method further comprises: the eNB indicating that the eNB is a donor eNB in all of transmitted X2 Interface Setup Request messages, or the eNB indicating that the eNB is a donor eNB in an X2 Interface Setup Request message transmitted to the mobility anchor.
In the method where an eNB determines and transmits a gateway IP address for a mobile Relay Node, if an S1 interface is used between the eNB and mobility anchor, the eNB indicates it's a donor eNB either in all S1 Interface Setup Request messages or specifically in the S1 Interface Setup Request message sent to that mobility anchor. Similarly, if an X2 interface is used, the eNB indicates it's a donor eNB in all X2 Interface Setup Request messages or just the one sent to the mobility anchor. This explicit signaling ensures the mobility anchor is aware of the eNB's role in supporting the mobile RN.
5. The method according to claim 1 , wherein the eNB determines the accessing device to be a stationary RN or a mobile RN in a way that: the eNB determines the accessing device to be a stationary RN or a mobile RN according to indication information received from the accessing device.
In the method where an eNB determines and transmits a gateway IP address for a mobile Relay Node, the eNB identifies whether an accessing device is a stationary or mobile RN based on indication information received from the accessing device itself. The RN explicitly signals its mobility status to the eNB, allowing the eNB to take appropriate actions, such as gateway selection and MME notification, as described in other claims.
6. The method according to claim 5 , wherein after the eNB receives the indication information from the accessing device, the method further comprises: transmitting, by the eNB, the indication information to the MME serving for the mobile RN to indicate to the MME that the accessing device is a mobile RN.
Following the process where an eNB receives mobility indication information from an accessing device (determining if it's a stationary or mobile RN) and determines and transmits a gateway IP address for a mobile Relay Node, the eNB forwards this indication information to the MME serving the mobile RN. This informs the MME that the accessing device is indeed a mobile RN, enabling the MME to manage the RN's mobility and connectivity accordingly.
7. The method according to claim 5 , wherein the eNB receives the indication information from a Radio Resource Control, RRC, message.
In the method where an eNB receives mobility indication information from an accessing device (determining if it's a stationary or mobile RN) and determines and transmits a gateway IP address for a mobile Relay Node, the indication information from the accessing device is received within a Radio Resource Control (RRC) message. This leverages existing radio signaling protocols to efficiently convey the RN's mobility status to the eNB.
8. The method according to claim 2 , wherein the eNB determines the accessing device to be a stationary RN or a mobile RN in a way that: the eNB determines the accessing device to be a stationary RN or a mobile RN according to indication information received from the accessing device.
The method where an eNB selects a mobility anchor (gateway) for a mobile RN based on load balancing, capacity, or random selection (where multiple mobility anchors are available) is enhanced because the eNB identifies whether an accessing device is a stationary or mobile RN based on indication information received from the accessing device itself. The RN explicitly signals its mobility status to the eNB, allowing the eNB to take appropriate actions, such as gateway selection and MME notification, as described in other claims.
9. The method according to claim 3 , wherein the eNB determines the accessing device to be a stationary RN or a mobile RN in a way that: the eNB determines the accessing device to be a stationary RN or a mobile RN according to indication information received from the accessing device.
In the method where the gateway IP address determined by the eNB for a mobile Relay Node is the S1 or X2 interface address, the eNB identifies whether an accessing device is a stationary or mobile RN based on indication information received from the accessing device itself. The RN explicitly signals its mobility status to the eNB, allowing the eNB to take appropriate actions, such as gateway selection and MME notification, as described in other claims.
10. The method according to claim 4 , wherein the eNB determines the accessing device to be a stationary RN or a mobile RN in a way that: the eNB determines the accessing device to be a stationary RN or a mobile RN according to indication information received from the accessing device.
In the method where an eNB signals its donor eNB status to the mobility anchor via S1 or X2 interface setup messages, the eNB identifies whether an accessing device is a stationary or mobile RN based on indication information received from the accessing device itself. The RN explicitly signals its mobility status to the eNB, allowing the eNB to take appropriate actions, such as gateway selection and MME notification, as described in other claims.
11. A method for transmitting an own gateway address, wherein the method comprises: receiving, by a mobility anchor, an Interface Setup Request message from an eNB; and transmitting, by the mobility anchor, its gateway IP address to the eNB, wherein before the mobility anchor transmits its gateway IP address to the eNB, the method further comprises: determining, by the mobility anchor, that the Interface Setup Request message comprises identification information indicating that the eNB is a donor eNB.
A method for a mobility anchor to provide its gateway IP address to an eNB. The mobility anchor receives an Interface Setup Request message from an eNB. The mobility anchor then transmits its own gateway IP address to the eNB. However, before transmitting its IP address, the mobility anchor checks if the Interface Setup Request message contains identification information indicating that the eNB is a donor eNB. This ensures that the mobility anchor only provides its IP address to eNBs configured to support mobile relay nodes.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
December 31, 2012
March 28, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.