Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A small cell eNodeB access system, comprising: a control plane gateway, which is connected to a radio access network and a core network, and set to set up a control plane link between the core network and the radio access network; as an aggregation and distribution node of control plane signalings, aggregate and send signalings from different radio access network nodes to the core network, or distribute signalings from the core network to different radio access network nodes; and manage and coordinate one or more radio access network nodes; a user plane gateway, which is connected to the radio access network and the core network, and set to set up a user plane link between the core network and the radio access network; as an aggregation and distribution node of user plane data, aggregate and send data from different radio access network nodes to the core network, or distribute data come from the core network to different radio access network nodes; and a connection link set up between the control plane gateway and the user plane gateway; the system further comprising a mobility management entity (MME) connecting with the control plane gateway, a serving gateway (SGW) connecting with the user plane gateway and the MME, a macro eNodeB connecting with the control plane gateway and the user plane gateway respectively, and a small cell eNodeB respectively connecting with the control plane gateway and the user plane gateway.
A small cell network system includes a control plane gateway, a user plane gateway, a mobility management entity (MME), a serving gateway (SGW), a macro eNodeB, and a small cell eNodeB. The control plane gateway connects the radio access network and core network, setting up a control plane link for control signaling. It aggregates control signals from radio access network nodes to the core network, distributes core network signals to radio access network nodes, and manages radio access network nodes. The user plane gateway similarly connects the radio access network and core network, setting up a user plane link for user data. It aggregates data from radio access network nodes to the core network and distributes core network data to radio access network nodes. A link is established between the control plane and user plane gateways enabling their cooperation.
2. The small cell eNodeB access system of claim 1 , wherein the control plane gateway is further set to implement control and management of the user plane gateway via the set up connection link, and wherein the control and management of the user plane gateway comprises: controlling setup, deletion and modification of connections between the user plane gateway and the core network, as well as between the user plane gateway and the radio access network node.
The small cell network system from the previous description includes the control plane gateway managing the user plane gateway through their established connection link. This control and management include setting up, deleting, and modifying connections between the user plane gateway and the core network, and between the user plane gateway and a radio access network node (e.g., macro eNodeB or small cell eNodeB). The control plane gateway handles resource allocation and configuration of the user plane gateway to optimize data flow within the small cell network.
3. The small cell eNodeB access system of claim 1 , wherein: there are one or more control plane gateways; and there are one or more user plane gateways.
The small cell network system from the first description can be scaled to include multiple control plane gateways and multiple user plane gateways. This allows for increased capacity and redundancy within the network, enabling it to handle a larger number of connected devices and to maintain service availability even if one or more gateways fail. Load balancing can be implemented across the multiple gateways.
4. The small cell eNodeB access system of claim 1 , wherein: the user plane gateway and the control plane gateway are independent physical nodes; the MME is set to connect to the control plane gateway via a S1-MME1 interface, connect to the SGW via a S11 interface; and also set to support managing a control plane link with the control plane gateway; the SGW is set to connect to the user plane gateway via a S1-U1 interface; and also set to support managing a S1-U1 interface connection with the user plane gateway; the control plane gateway is set to connect to the MME via a S1-MME1 interface, and connect to the macro eNodeB and/or small cell eNodeB via a S1-MM2 interface, connect to the user plane gateway via a X-1 interface; and further set to support a function of managing the control plane link with the MME and managing a control plane link with an eNodeB, and to manage the S1-U1 interface connection set up between the user plane gateway and the SGW as well as a S1-U2 interface connection set up between the user plane gateway and the eNodeB; the user plane gateway is set to connect to the SGW via the S1-U1 interface, connect to the macro eNodeB or small cell eNodeB via a S1-U2 interface and connect to the control plane gateway via the X-1 interface; and set to, under control of the control plane gateway, support managing the S1-U1 interface connection with the SGW as well as managing the S1-U2 interface connection with the eNodeB; the macro eNodeB is set to connect to the control plane gateway via a S1-MME2 interface, and connect to the user plane gateway via the S1-U2 interface; and further set to support managing the control plane link with the control plane gateway and managing a S1-U2 interface connection with the user plane gateway; the small cell eNodeB is set to connect to the user plane gateway via a S1-U2 interface, connect to the control plane gateway via a S1-MME2 interface; also set to support managing the control plane link with the control plane gateway and managing a S1-U2 interface connection with the user plane gateway.
In the small cell network system described initially, the user plane gateway and control plane gateway are separate physical entities. The MME connects to the control plane gateway via an S1-MME1 interface and to the SGW via an S11 interface, managing the control plane link. The SGW connects to the user plane gateway via an S1-U1 interface, managing this connection. The control plane gateway connects to the MME via S1-MME1, to macro/small eNodeBs via S1-MM2, and to the user plane gateway via X-1. The user plane gateway connects to the SGW via S1-U1, to macro/small eNodeBs via S1-U2, and to the control plane gateway via X-1, supporting the S1-U1/U2 management under control plane gateway. Macro/small eNodeBs connect to the control plane gateway via S1-MME2 and the user plane gateway via S1-U2, managing these links.
5. The small cell eNodeB access system of claim 4 , wherein: the control plane gateway is further set to connect to other control plane gateways via a X-C interface, used for an inter-node negotiation when moving across the control plane gateways; or the user plane gateway is further set to connect to other user plane eNodeBs via a X-U interface, used for transmitting data between nodes when moving across the user plane gateways.
In the small cell network system with separate gateways described in claim 4, the control plane gateway connects to other control plane gateways via an X-C interface for inter-node negotiation during UE mobility events (handovers). Alternatively, the user plane gateway connects to other user plane gateways via an X-U interface, used for transmitting user data between nodes when a UE moves across user plane gateway coverage areas. This ensures seamless data transfer during handovers.
6. The small cell eNodeB access system of claim 1 , wherein, the control plane gateway and the user plane gateway are co-located in a same physical entity, in this case, a X-1 interface between the control plane gateway and the user plane gateway is an internal interface; or the control plane gateway and the user plane gateway are co-located and set in a macro eNodeB; the MME is set to connect to the macro eNodeB via a S1-MME1 interface, connect to the SGW via a S11 interface; also set to support managing a control plane link with the control plane gateway set in the macro eNodeB; the SGW is set to connect to the macro eNodeB via a S1-U1 interface; further set to support managing a S1-U1 connection with the user plane gateway set in the macro eNodeB; the macro eNodeB is set to connect to the MME via a S1-MME1 interface, and have a S1-U2 interface and a S1-MME2 interface with the small cell eNodeB; and further set to support managing a control plane link with the small cell eNodeB, and support managing a S1-U2 connection with the small cell eNodeB; the small cell eNodeB is set to have the S1-U2 interface and the S1-MME2 interface with the macro eNodeB; also set to support managing the control plane link and the S1-U2 connection with the macro eNodeB; or the control plane gateway and the user plane gateway are co-located and set in a macro eNodeB, one gateway is also set between the macro eNodeB and a small cell eNodeB, and also responsible for managing a control plane and user plane of the small cell eNodeB; the MME is set to connect to the macro eNodeB via a S1-MME1 interface, and connect to the SGW via a S11 interface; and further set to support managing a control plane link with the control plane gateway set in the macro eNodeB; the SGW is set to connect to the macro eNodeB via a S1-U1 interface; further set to support managing a S1-U1 connection with the user plane gateway set in the macro eNodeB; the macro eNodeB is set to connect to the MME via the S1-MME1 interface and set up S1-U2 interface and S1-MME2 interface connections with the small cell eNodeB via a gateway; also set to support managing a control plane link with the gateway; the gateway is set to support managing a control plane link and user plane link with an eNodeB; the small cell eNodeB is set to set up the S1-U2 interface and S1-MME2 interface connections with the macro eNodeB via the gateway; further set to support setting up a data radio bearer (DRB) of LTE system with a UE and communicating in the DRB, and support managing a control plane link and a S1-U2 interface connection with the gateway, the small cell eNodeB access system further comprises a X-3 interface connection set up between the macro eNodeB and the small cell eNodeB via the gateway.
In one configuration of the small cell network system described initially, the control plane gateway and user plane gateway are located within the same physical device, making the X-1 interface (between them) an internal interface. Alternatively, both gateways reside within a macro eNodeB. The MME connects to the macro eNodeB via S1-MME1 and to the SGW via S11, managing the control plane link. The SGW connects to the macro eNodeB via S1-U1, managing the S1-U1 connection. The macro eNodeB has S1-U2 and S1-MME2 interfaces with the small cell eNodeB, managing the small cell eNodeB’s control plane link and S1-U2 connection. In another version with gateways within the macro eNodeB, there's a separate gateway between the macro and small cell eNodeBs, managing both the control and user planes for the small cell eNodeB, connected via X-3.
7. The small cell eNodeB access system of claim 4 , wherein: the control plane gateway is set in a macro eNodeB, and the user plane gateway is an independent entity; the MME is set to connect to the macro eNodeB via a S1-MME1 interface, and connect to the SGW via a S11 interface; the SGW is set to connect to the user plane gateway via a S1-U1 interface; also set to support managing a S1-U1 interface connection with the user plane gateway; the macro eNodeB is provided with a control plane gateway; set to connect to the MME via a S1-MME1 interface, connect to a small cell eNodeB via a S1-MM2 interface, wherein interfaces between the macro eNodeB and the user plane gateway comprise a X-1 interface and a S1-U2 interface; further set to support managing a S1-U2 interface connection with a user plane gateway, support managing a control plane link with the small cell eNodeB; control the user plane gateway to manage the S1-U1 interface connection between the user plane gateway and the SGW, as well as a S1-U2 interface connection between the user plane gateway and an eNodeB; the user plane gateway is set to connect to the SGW via the S1-U1 interface, connect to the macro eNodeB via the S1-U2 interface and X-1 interface, connect to the small cell eNodeB via a S1-U2 interface; further set to support managing the S1-U1 interface connection with the SGW, as well as managing the S1-U2 interface connection with the eNodeB; the small cell eNodeB is set to connect to the user plane gateway via the S1-U2 interface, connect to the macro eNodeB via the S1-MME2 interface; support setting up a data radio bearer of LTE system with a UE and communicating in the DRB, as well as support managing a control plane link with the control plane gateway and manage a S1-U2 interface connection with the user plane gateway; or the macro eNodeB and the small cell eNodeB are connected via a X-3 interface; or the user plane gateway is set in the SGW; the control plane gateway is set in the MME; the MME is provided with a control plane gateway; and the MME is set to connect to the SGW via a S11 interface and a X-1 interface, and respectively connect to the macro eNodeB and the small cell eNodeB via a S1-MME2 interface; also set to support managing two S1-MME2 interfaces for one user to respectively connect to different eNodeBs; the SGW is provided with a user plane gateway; and the SGW is set to connect to the MME via the S11 interface and the X-1 interface, and respectively connect to the macro eNodeB and the small cell eNodeB via a S1-U2 interface; and further set to support managing two S1-U2 interfaces for one user to respectively connect to different eNodeBs.
In one variation of the small cell network system described in claim 4, the control plane gateway resides within the macro eNodeB, while the user plane gateway is a separate, independent entity. The MME connects to the macro eNodeB (containing the control plane gateway) via S1-MME1, and to the SGW via S11. The SGW connects to the user plane gateway via S1-U1, managing this interface. The macro eNodeB connects to the small cell eNodeB via S1-MM2. Interfaces between the macro eNodeB and user plane gateway are X-1 and S1-U2. Alternatively, the user plane gateway is within the SGW and the control plane gateway is within the MME, connected by S11 and X-1, each connecting to the macro/small cell eNodeBs via S1-U2 and S1-MME2 respectively, supporting dual connections to different eNodeBs.
8. A method for a small cell eNodeB access system implementing network access, wherein the small cell eNodeB access system is provided with, a control plane gateway, which is connected to a radio access network and a core network, and set to set up a control plane link between the core network and the radio access network; a user plane gateway, which is connected to the radio access network and the core network, and set to set up a user plane link between the core network and the radio access network; a connection link which is set up between the control plane gateway and the user plane gateway; the method comprises: respectively setting up the control plane link and the user plane link; processing control plane data of an access UE through the set up control plane link, and processing user plane data of the access UE through the set up user plane link; wherein the small cell eNodeB access system further comprises a mobility management entity (MME) connecting with the control plane gateway, a serving gateway (SGW) connecting with the user plane gateway and the MME, a macro eNodeB connecting with the control plane gateway and the user plane gateway respectively, and a small cell eNodeB respectively connecting with the control plane gateway and the user plane gateway.
A method for network access in a small cell network system. The system includes a control plane gateway, a user plane gateway, a link between them, an MME, an SGW, a macro eNodeB, and a small cell eNodeB. The method involves setting up a control plane link and a user plane link. Control plane data from a User Equipment (UE) is processed through the control plane link, while user plane data from the UE is processed through the user plane link. This separation of control and data allows for simultaneous data transmission and reception with different eNodeBs.
9. The method of claim 8 , further comprising: via the set up connection link, the control plane gateway controlling and managing the user plane gateway, wherein, the control plane gateway controlling and managing the user plane gateway comprises: setting up, deleting, and modifying a connection between the user plane gateway and the core network, as well as, setting up, deleting and modifying a connection between the user plane gateway and a radio access network node.
The method described in the previous claim further includes the control plane gateway controlling and managing the user plane gateway via their connection link. This management involves setting up, deleting, and modifying connections between the user plane gateway and the core network, as well as connections between the user plane gateway and a radio access network node (e.g., macro eNodeB or small cell eNodeB). This allows the control plane to dynamically adjust the data path based on network conditions and UE needs.
10. The method of claim 8 , wherein, there are two or more user plane gateways; the method further comprises: setting up a connection link between the user plane gateways; through the set up connection link, implementing transmitting data between nodes when a UE moves across the user plane gateways.
The network access method from claim 8, for networks with multiple user plane gateways, includes establishing a connection link between these gateways. This link enables data transmission between the nodes when a UE moves across the coverage area of different user plane gateways. This ensures continuity of service as the UE roams between different areas handled by different user plane gateways.
11. The method of claim 8 , wherein, the method further comprises: the control plane gateway completing an inter-node negotiation via the connection link when a UE moves across the control plane gateways.
The network access method from claim 8 includes the control plane gateway completing an inter-node negotiation via the connection link when a UE moves across different control plane gateways. This negotiation allows the gateways to exchange context information and coordinate the handover of the UE's control plane connection, maintaining session continuity.
12. The method of claim 8 , wherein, said processing the control plane data of the access UE via the set up control plane link comprises: via the set up control plane link, the control plane gateway processing the control plane data, aggregating and sending signalings from different radio access network nodes to the core network, or distributing signalings from the core network to different radio access network nodes.
Processing control plane data in the method from claim 8 comprises the control plane gateway, using the established control plane link, processing this data. This processing includes aggregating and sending signaling from different radio access network nodes to the core network, or distributing signaling from the core network to different radio access network nodes. This centralized control plane management simplifies network operation.
13. The method of claim 12 , wherein, the aggregating or distributing comprises: managing signaling connections between the core network and the control plane gateway, as well as the control plane gateway and the radio access network nodes; maintaining UE-related context information, comprising mapping relationships of signaling connections between the core network and the control plane gateway, as well as between the control plane gateway and the radio access network nodes; managing the signaling connections according to signalings of the core network or the radio access network nodes.
The aggregation or distribution of control plane data in the method of claim 12 includes managing signaling connections between the core network and the control plane gateway, and between the control plane gateway and the radio access network nodes. It also involves maintaining UE-related context information, which includes mapping relationships of signaling connections between the core network and the control plane gateway, and between the control plane gateway and the radio access network nodes. Finally, the signaling connections are managed according to signaling received from either the core network or the radio access network nodes.
14. The method of claim 13 , further comprising: when a UE supports a plurality of streams, the UE storing the signaling connections between the control plane gateway and a plurality of radio access network nodes.
The method from claim 13 further specifies that when a UE supports multiple data streams, the UE stores the signaling connections between the control plane gateway and multiple radio access network nodes. This allows the UE to maintain multiple simultaneous connections for increased bandwidth and reduced latency.
15. The method of claim 13 , further comprising: instructing the user plane gateway to manage a corresponding data connection; or wherein the mapping relationship is a one-to-one mapping relationship; forwarding the signaling according to the mapping relationship; or, the mapping relationship is a one-to-many relationship mapping, forwarding by proxy the signaling according to a specified rule; or wherein, when there is moving across the control plane gateways, between the control plane gateways, the method further comprises: migrating context configuration information related to a corresponding UE or an air interface connection.
The method from claim 13 further includes instructing the user plane gateway to manage a corresponding data connection. If the mapping relationship is one-to-one, the signaling is forwarded accordingly. If the relationship is one-to-many, the signaling is forwarded by proxy according to a specified rule. When moving across control plane gateways, the method also involves migrating context configuration information related to a corresponding UE or air interface connection between the control plane gateways.
16. The method of claim 8 , wherein, said processing the user plane data of the access UE via the set up user plane link comprises: through the set up user plane link, the user plane gateway processing the user plane data, aggregating and sending data from different radio access network nodes to the core network, or distributing data from the core network to different radio access network nodes.
The method of processing user plane data described in claim 8 comprises the user plane gateway, using the established user plane link, processing the user plane data. This processing includes aggregating and sending data from different radio access network nodes to the core network, or distributing data from the core network to different radio access network nodes. This optimizes data flow within the network.
17. The method of claim 16 , wherein, the aggregating or distributing comprises: managing data channels between the core network and the user plane gateway, as well as between the user plane gateway and the radio access network; maintaining a mapping relationship of data channels between the core network and the user plane gateway as well as between the user plane gateway and the radio access network nodes; and forwarding data in accordance with a mapping relationship, and managing the mapping relationship.
In the method of claim 16, the aggregating or distributing of user plane data includes managing data channels between the core network and the user plane gateway, as well as between the user plane gateway and the radio access network. A mapping relationship of data channels between the core network and the user plane gateway, and between the user plane gateway and radio access network nodes is maintained. Data is then forwarded in accordance with this mapping relationship and the mapping relationship is managed.
18. The method of claim 17 , wherein, the mapping relationship is a one-to-one mapping relationship; or the mapping relationship is a one-to-many mapping relationship, in this case, the user plane gateway maintains the one-to-many relationship in context information of one UE: in an uplink direction, the user plane gateway aggregates a plurality of data channels into one data channel to transmit; in a downlink direction, the user plane gateway distributes data according to a preset rule.
The method from claim 17 includes a one-to-one or one-to-many mapping relationship. For one-to-many, the user plane gateway maintains the relationship in the UE's context information. In the uplink direction, the gateway aggregates multiple data channels into one. In the downlink, it distributes data based on a preset rule. This allows for flexible data routing and bandwidth management.
19. The method of claim 18 , further comprising, when there is moving across the user plane gateways, managing including setting up, deleting and modifying a data channel between the user plane gateways; and, maintaining the mapping relationship of data channels between the access network nodes or the core network and the user plane gateway, forwarding data according to the mapping relationship, and supporting a management of the mapping relationship.
The method from claim 18 also includes that when there's a move across user plane gateways, managing (setup, deletion, modification) a data channel between these gateways. It also involves maintaining the mapping relationship of data channels between access network nodes or the core network and the user plane gateway, forwarding data accordingly, and supporting management of the mapping relationship. This enables seamless data transfer during handovers.
Unknown
December 12, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.