WO2020100053A1 - Mécanisme de redirection pour supporter le partage/découpe de réseau avec division uc-ud pour le rétablissement - Google Patents

Mécanisme de redirection pour supporter le partage/découpe de réseau avec division uc-ud pour le rétablissement Download PDF

Info

Publication number
WO2020100053A1
WO2020100053A1 PCT/IB2019/059739 IB2019059739W WO2020100053A1 WO 2020100053 A1 WO2020100053 A1 WO 2020100053A1 IB 2019059739 W IB2019059739 W IB 2019059739W WO 2020100053 A1 WO2020100053 A1 WO 2020100053A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
target base
resources
plmn
source
Prior art date
Application number
PCT/IB2019/059739
Other languages
English (en)
Inventor
Alexander Vesely
Matteo FIORANI
Gunnar Mildh
Angelo Centonza
Julien Muller
Gino Luca Masini
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2020100053A1 publication Critical patent/WO2020100053A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/19Connection re-establishment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/18Selecting a network or a communication service
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08Access point devices
    • H04W88/085Access point devices with remote components
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W92/00Interfaces specially adapted for wireless communication networks
    • H04W92/04Interfaces between hierarchically different network devices
    • H04W92/12Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • Systems and methods disclosed herein relate to network sharing or network slicing in a wireless network including base stations having a Centralized Unit (CU) / Distributed Unit (DU) split.
  • CU Centralized Unit
  • DU Distributed Unit
  • FIG. 1 depicts the current Fifth Generation (5G) Radio Access Network (RAN) architecture, as described in Third Generation Partnership Project (3GPP) Technical Specification (TS) 38.401 (see e.g., V15.3.0).
  • the Next Generation (NG) architecture can be further described as follows.
  • the NG-RAN consists of a set of NG Node Bs (gNBs) connected to a 5G Core Network (5GC) through an NG interface.
  • a gNB can support Frequency Division Duplex (FDD) mode, Time Division Duplex (TDD) mode, or dual mode operation.
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • gNBs can be interconnected through an Xn interface.
  • a gNB may consist of a gNB Central Unit (gNB-CU) and gNB Distributed Units (gNB-DUs).
  • gNB-CU gNB Central Unit
  • gNB-DU gNB Distributed Units
  • a gNB-DU is connected to a gNB-CU via an FI logical interface.
  • One gNB-DU is connected to only one gNB-CU.
  • NG, Xn, and FI are logical interfaces.
  • the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • EN-DC New Radio - Dual Connectivity
  • the Sl-U and X2-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU.
  • the gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.
  • the NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL).
  • RNL Radio Network Layer
  • TNL Transport Network Layer
  • the NG-RAN architecture e.g. the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL.
  • NG, Xn, FI the related TNL protocol and the functionality are specified.
  • the TNL provides services for user plane transport and signaling transport.
  • each gNB is connected to all Access and Mobility Management Functions (AMFs) within an AMF Region.
  • the AMF Region can be as defined in 3GPP TS 23.501 (see, e.g., V15.3.0).
  • the FI interface supports the exchange of signaling information between the endpoints, in addition the interface shall support data transmission to the respective endpoints;
  • the FI is a point-to-point interface between the
  • endpoints (a point-to-point logical interface should be feasible even in the absence of a physical direct connection between the endpoints);
  • one gNB-CU and set of gNB-DUs are visible to other logical nodes as a gNB.
  • the gNB terminates X2, Xn, NG and Sl-U interfaces;
  • the CU may be separated in Control Plane (CP) and User Plane (UP).
  • CP Control Plane
  • UP User Plane
  • MOCN Multi Operator Core Network
  • Single Cell ID / TAC cell configuration refers to the "classical" MOCN configuration, which was defined up to Release 13 for 3G and 4G. Such configuration foresaw to share not only cell radio resources but also Cell IDs and TACs, i.e. the same value for a Cell ID / TAC was used by all operators, the cells and Tracking Areas (TAs) could be only distinguished globally, i.e. as Cell Group Identities (CGIs) or Tracking Area Identities (TAIs), with the Public Land Mobile Network (PLMN) ID prefix. This required operators to coordinate those IDs. Multiple Cell ID / TAC cell configuration is able to overcome those restrictions, and broadcast information associated with a single physical cell resource is able to indicate more than one Cell ID / TAC pair, each of which is associated with an operator's network.
  • CGIs Cell Group Identities
  • TAIs Tracking Area Identities
  • PLMN Public Land Mobile Network
  • the multiple Cell ID / TAC cell configuration offers several possibilities, but the most common is one where several separate operator networks logically operate their own networks. This is very much in line with the intention of this configuration option. Operators have the benefit of configuring and operating their own network, independent from configuration and operating strategies of the networks of other operators. Actual sharing of physical cell resources would work as for the "classical" MOCN scenarios, where fixed or dynamic quotas would regulate the usage radio resources.
  • 3GPP is currently working on standardization of 5G CN and New Radio (NR) access. In this work there is a lot of focus to support network slicing. Below is a short description of network slicing.
  • network slicing is an important part of the vision for the 5G System architecture.
  • NVMN Next Generation Mobile Network
  • network slicing consists of deploying multiple end-to-end logical networks in support of independent business operations.
  • each instance of a slice should be possible to realize as a logical network corresponding to a shared
  • FIG. 2 depicts an example of multiple slice instances deployed in the same network infrastructure.
  • the infrastructure and assets utilization will be much more cost- and energy-efficient while the logical separation allows for a flexible and independent configuration and management of the slices without compromising stability and security. Enabling slice realization over a common physical infrastructure would of course not prevent the realization of a slice instance by means of dedicated resources and assets.
  • Network slicing is an end to end concept, where a given network slice could be made up of different dedicated or shared sub-network instances. For example, it is possible to deploy network supporting two slices using a shared RAN sub-network instance used by both slices and two dedicated core network sub-network instances for each slice. In this case the RAN would have a selection function connecting UEs of one slice to the correct core network instance.
  • a method performed by a shared distributed unit for connection reestablishment for a User Equipment is disclosed.
  • the shared distributed unit comprises: (a) a distributed unit of a first target base station associated with a first Public Land Mobile Network (PLMN) or a first network slice and (b) a distributed unit of a second target base station associated with a second PLMN or a second network slice, wherein the first target base station and the second target base station share resources.
  • PLMN Public Land Mobile Network
  • a second target base station associated with a second PLMN or a second network slice
  • the method comprises receiving, from the UE at the distributed unit of the first target base station, a connection reestablishment request comprising an identity of the UE in a source cell to which the UE was connected prior to sending the connection reestablishment request and an identity of the source cell.
  • the method further comprises sending an initial message to a central unit of the first target base station, the initial message comprising: (a) the identity of the UE in the source cell, (b) the identity of the source cell, and (c) information regarding a second cell served by the second target base station using the shared resources, wherein the shared resources comprise physical layer resources, Medium Access Control (MAC) layer resources, or both physical layer resources and MAC layer resources.
  • MAC Medium Access Control
  • connection reestablishment request is a Radio Resource Control (RRC) Reestablishment Request.
  • RRC Radio Resource Control
  • the information regarding the second cell served by the second target base station using the shared physical layer and/or MAC layer resources comprises a Cell Group Identifier (CGI) of the second cell, a PLMN identity (ID) of the second PLMN associated with the second cell, or both a CGI of the second cell and the PLMN ID of the second PLMN associated with the second cell.
  • CGI Cell Group Identifier
  • ID PLMN identity
  • the initial message comprises at least a portion of the connection reestablishment request.
  • the method further comprises receiving, from a central unit of the second target base station, a message that transfers the connection reestablishment procedure for the UE from the distributed unit of the first target base station to the distributed unit of the second target base station, and completing the connection reestablishment procedure.
  • Embodiments of a shared distribution unit for connection reestablishment for a UE are also disclosed.
  • the shared distributed unit comprises: (a) a distributed unit of a first target base station associated with a first PLMN or a first network slice and (b) a distributed unit of a second target base station associated with a second PLMN or a second network slice, wherein the first target base station and the second target base station share resources.
  • the shared distributed unit is adapted to receive, from the UE at the distributed unit of the first target base station, a connection reestablishment request comprising an identity of the UE in a source cell to which the UE was connected prior to sending the connection reestablishment request and an identity of the source cell.
  • the shared distribution unit is further adapted to send an initial message to a central unit of the first target base station, the initial message comprising: (a) the identity of the UE in the source cell, (b) the identity of the source cell, and (c) information regarding a second cell served by the second target base station using the shared resources, wherein the shared resources comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • Embodiments of a node implementing a shared distributed unit for connection reestablishment for a UE are also disclosed.
  • the shared distributed unit comprises: (a) a distributed unit of a first target base station associated with a first PLMN or a first network slice and (b) a distributed unit of a second target base station associated with a second PLMN or a second network slice, wherein the first target base station and the second target base station share resources.
  • the node comprises a network interface and processing circuitry associated with the network interface.
  • the processing circuitry is configured to cause the node to receive, from the UE at the distributed unit of the first target base station, a connection reestablishment request comprising an identity of the UE in a source cell to which the UE was connected prior to sending the connection reestablishment request and an identity of the source cell.
  • the processing circuitry is further configured to cause the node to send an initial message to a central unit of the first target base station, the initial message comprising: (a) the identity of the UE in the source cell, (b) the identity of the source cell, and (c) information regarding a second cell served by the second target base station using the shared resources, wherein the shared resources comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • the first target base station shares resources with a second target base station associated with a second PLMN or a second network slice.
  • the method comprises receiving an initial message from a shared distributed unit of the first target base station and the second target base station.
  • the initial message comprises: (a) an identity of the UE in a source cell to which the UE was connected prior to sending a connection reestablishment request that triggered the initial message, (b) the identity of the source cell, and (c) information regarding a second cell served by the second target base station using the shared resources, wherein the shared resources comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • the method further comprises sending, to a central unit of a first source base station associated with the first PLMN or the first network slice, a request to retrieve a UE context of the UE.
  • the request comprises the identity of the UE in the source cell, the identity of the source cell, and the information regarding the second cell served by the second target base station using the shared resources. Using this information, UE context retrieval for the connection reestablishment procedure can be redirected to a correct central unit.
  • the connection reestablishment request is a RRC Reestablishment Request.
  • the information regarding the second cell served by the second target base station using the shared resources comprises a CGI of the second cell, a PLMN ID of the second PLMN associated with the second cell, or both a CGI of the second cell and the PLMN ID of the second PLMN associated with the second cell.
  • both the initial message and the request comprise at least a portion of the connection reestablishment request.
  • Embodiments of a central unit of a first target base station associated with a first PLMN or a first network slice for a connection reestablishment procedure for a UE are also disclosed.
  • the first target base station shares resources with a second target base station associated with a second PLMN or a second network slice, and the central unit is adapted to receive an initial message from a shared distributed unit of the first target base station and the second target base station.
  • the initial message comprises: (a) an identity of the UE in a source cell to which the UE was connected prior to sending a connection reestablishment request that triggered the initial message, (b) the identity of the source cell, and (c) information regarding a second cell served by the second target base station using the shared resources, wherein the shared resources comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • the central unit is further adapted to send, to a central unit of a first source base station associated with the first PLMN or the first network slice, a request to retrieve a UE context of the UE.
  • the request comprising the identity of the UE in the source cell, the identity of the source cell, and the information regarding the second cell served by the second target base station using the shared resources.
  • UE context retrieval for the connection reestablishment procedure can be redirected to a correct central unit.
  • the first target base station shares resources with a second target base station associated with a second PLMN or a second network slice
  • the node comprises a network interface and processing circuitry associated with the network interface.
  • the processing circuitry is configured to cause the node to receive an initial message from a shared distributed unit of the first target base station and the second target base station.
  • the initial message comprises: (a) an identity of the UE in a source cell to which the UE was connected prior to sending a connection reestablishment request that triggered the initial message, (b) the identity of the source cell, and (c) information regarding a second cell served by the second target base station using the shared resources, wherein the shared resources comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • the processing circuitry is further configured to cause the node to send, to a central unit of a first source base station associated with the first PLMN or the first network slice, a request to retrieve a UE context of the UE.
  • the request comprises the identity of the UE in the source cell, the identity of the source cell, and the information regarding the second cell served by the second target base station using the shared resources.
  • the first source base station shares resources with a second source base station associated with a second PLMN or a second network slice
  • the method comprises receiving, from a central unit of a first target base station associated with the first PLMN or the first network slice, a request to retrieve a UE context of the UE.
  • the request comprises: (a) an identity of the UE in a source cell to which the UE was connected prior to connection reestablishment, (b) the identity of the source cell, and (c) information regarding a second cell served by a second target base station that shares resources with the first target base station, wherein the resources shared by the first and second source base stations and the resources shared by the first and second target base stations comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • the method further comprises determining that the UE context of the UE cannot be found by the central unit of the first source base station.
  • the method further comprises, upon determining that the UE context of the UE cannot be found, sending a message to a shared distributed unit of the first source base station and the second source base station that allocated the identity of the UE in the source cell to initiate redirection of the request to retrieve the UE context of the UE to a correct central unit of the second source base station.
  • the request to retrieve the UE context of the UE further comprises at least a portion of a connection reestablishment request message sent by the UE to initiate the connection reestablishment procedure.
  • the message sent to the shared distributed unit of the first source base station and the second source base station that allocated the identity of the UE in the source cell comprises: (a) the identity of the UE in the source cell, (b) at least a portion of a connection reestablishment request message sent by the UE to initiate the connection reestablishment procedure, (c) at least a portion of the request to retrieve the UE context of the UE, (d) the information regarding the second cell served by the second target base station using the shared resources, or (e) any combination of two or more of (a) - (d).
  • the information regarding the second cell served by the second target base station using the shared resources comprises a CGI of the second cell, a PLMN ID of the second PLMN associated with the second cell, or both the CGI of the second cell and the PLMN ID of the second PLMN associated with the second cell.
  • Embodiments of a central unit of a first source base station associated with a first PLMN or a first network slice for a connection reestablishment procedure for a UE are also disclosed.
  • the first source base station shares resources with a second source base station associated with a second PLMN or a second network slice
  • the central unit is adapted to receive, from a central unit of a first target base station associated with the first PLMN or the first network slice, a request to retrieve a UE context of the UE.
  • the request comprises: (a) an identity of the UE in a source cell to which the UE was connected prior to connection reestablishment, (b) the identity of the source cell, and (c) information regarding a second cell served by a second target base station that shares resources with the first target base station, wherein the resources shared by the first and second source base stations and the resources shared by the first and second target base stations comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • the central unit is further adapted to determine that the UE context of the UE cannot be found by the central unit of the first source base station and, upon determining that the UE context of the UE cannot be found, send a message to a shared distributed unit of the first source base station and the second source base station that allocated the identity of the UE in the source cell to initiate redirection of the request to retrieve the UE context of the UE to a correct central unit of the second source base station.
  • the first source base station shares resources with a second source base station associated with a second PLMN or a second network slice
  • the node comprises a network interface and processing circuitry associated with the network interface.
  • the processing circuitry is configured to cause the node to receive, from a central unit of a first target base station associated with the first PLMN or the first network slice, a request to retrieve a UE context of the UE.
  • the request comprises: (a) an identity of the UE in a source cell to which the UE was connected prior to connection reestablishment, (b) the identity of the source cell, and (c) information regarding a second cell served by a second target base station that shares resources with the first target base station, wherein the resources shared by the first and second source base stations and the resources shared by the first and second target base stations comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • the processing circuitry is further configured to cause the node to determine that the UE context of the UE cannot be found by the central unit of the first source base station and, upon determining that the UE context of the UE cannot be found, send a message to a shared distributed unit of the first source base station and the second source base station that allocated the identity of the UE in the source cell to initiate redirection of the request to retrieve the UE context of the UE to a correct central unit of the second source base station.
  • Embodiments of a method performed by a second shared distributed unit of: (a) a first source base station associated with a first PLMN or a first network slice, (b) the identity of the source cell, and (c) a second source base station associated with a second PLMN or a second network slice, for a connection reestablishment procedure for a UE are disclosed.
  • the first source base station and the second source base station share resources, and the method comprises receiving, from a central unit of the first source base station, a message to initiate redirection of a request to retrieve a UE context of the UE to a correct central unit.
  • the message comprises: (a) an identity of the UE in a source cell to which the UE was connected prior to connection reestablishment and (b) information regarding a second cell served by a second target base station associated with the second PLMN or the second network slice that shares resources with a first target base station associated with the first PLMN or the first network slice, wherein the resources shared by the first and second source base stations and the resources shared by the first and second target base stations comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • the method further comprises identifying a correct central unit of the second source base station from which to retrieve the UE context of the UE based on the message to initiate redirection of the request to retrieve the UE context of the UE, and sending, to the correct central unit of the second source base station, a message that redirects the request to retrieve the UE context of the UE to the correct central unit of the second source base station.
  • the message to initiate redirection of the request to receive a UE context of the UE comprises the identity of the UE in the source cell and the information regarding the second cell served by the second target base station.
  • the message to initiate redirection of the request to receive a UE context of the UE comprises at least a portion of a connection
  • the message that redirects the request to retrieve the UE context of the UE comprises the identity of the UE in the source cell and the information regarding the second cell served by the second target base station using the shared resources.
  • the message that redirects the request to retrieve the UE context of the UE comprises at least a portion of a connection reestablishment request transmitted by the UE to initiate connection reestablishment.
  • the information regarding the second cell served by the second target base station using the shared resources comprises a CGI of the second cell, a PLMN ID of the second PLMN associated with the second cell, or both the CGI of the second cell and the PLMN ID of the second PLMN associated with the second cell.
  • Embodiments of a second shared distributed unit of: (a) a first source base station associated with a first PLMN or a first network slice and (b) a second source base station associated with a second PLMN or a second network slice, for a connection reestablishment procedure for a UE are also disclosed.
  • the first source base station and the second source base station share resources
  • the second shared distributed unit is adapted to receive, from a central unit of the first source base station, a message to initiate redirection of a request to retrieve a UE context of the UE to a correct central unit.
  • the message comprises: (a) an identity of the UE in a source cell to which the UE was connected prior to connection
  • the second shared distributed unit is further adapted to identify a correct central unit of the second source base station from which to retrieve the UE context of the UE based on the message to initiate redirection of the request to retrieve the UE context of the UE, and send, to the correct central unit of the second source base station, a message that redirects the request to retrieve the UE context of the UE to the correct central unit of the second source base station.
  • Embodiments of a node implementing a second shared distributed unit of: (a) a first source base station associated with a first PLMN or a first network slice and (b) a second source base station associated with a second PLMN or a second network slice, for a connection reestablishment procedure for a UE are also disclosed.
  • the first source base station and the second source base station share resources
  • the node comprises a network interface and processing circuitry associated with the network interface.
  • the processing circuitry configured to cause the node to receive, from a central unit of the first source base station, a message to initiate redirection of a request to retrieve a UE context of the UE to a correct central unit.
  • the message comprises: (a) an identity of the UE in a source cell to which the UE was connected prior to connection reestablishment, (b) the identity of the source cell, and (c) information regarding a second cell served by a second target base station associated with the second PLMN or the second network slice that shares resources with a first target base station associated with the first PLMN or the first network slice, wherein the resources shared by the first and second source base stations and the resources shared by the first and second target base stations comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • the processing circuitry is further configured to cause the node to identify a correct central unit of the second source base station from which to retrieve the UE context of the UE based on the message to initiate redirection of the request to retrieve the UE context of the UE, and send, to the correct central unit of the second source base station, a message that redirects the request to retrieve the UE context of the UE to the correct central unit of the second source base station.
  • Embodiments of a method performed by a central unit of a second source base station associated with a second PLMN or a second network slice for a connection reestablishment procedure for a UE are also disclosed.
  • the second source base station shares resources with a first source base station associated with a first PLMN or a first network slice
  • the method comprises receiving, from a shared distributed unit of the first source base station and the second source base station, a message that redirects a request to retrieve a UE context of the UE to the central unit of the second source base station.
  • the method further comprises, upon receiving the message, retrieving the UE context of the UE, and sending the UE context of the UE to a central unit of a second target base station associated with the second PLMN or the second network slice that shares resources with a first target base station associated with the first PLMN or the first network slice, wherein the central unit of the second target base station is associated with a shared distributed unit of the first target base station and the second target base station at which a respective connection reestablishment request was received from the UE.
  • the message that redirects the request to retrieve the UE context of the UE comprises the identity of the UE in the source cell and the information regarding the second cell served by the second target base station using the shared resources.
  • the message that redirects the request to retrieve the UE context of the UE comprises at least a portion of the connection reestablishment request from the UE.
  • the information regarding the second cell served by the second target base station using the shared resources comprises a CGI of the second cell, a PLMN ID of the second PLMN associated with the second cell, or both the CGI of the second cell and the PLMN ID of the second PLMN associated with the second cell.
  • Embodiments of a central unit of a second source base station associated with a second PLMN or a second network slice for a connection reestablishment procedure for a UE are also disclosed.
  • the second source base station shares resources with a first source base station associated with a first PLMN or a first network slice
  • the central unit is adapted to receive, from a shared
  • the central unit is further adapted to, upon receiving the message, retrieve the UE context of the UE, and send the UE context of the UE to a central unit of a second target base station associated with the second PLMN or the second network slice that shares resources with a first target base station associated with the first PLMN or the first network slice, wherein the central unit of the second target base station is associated with a shared distributed unit of the first target base station and the second target base station at which a respective connection
  • Embodiments of a node implementing a central unit of a second source base station associated with a second PLMN or a second network slice for a connection reestablishment procedure for a UE are also disclosed.
  • the second source base station shares resources with a first source base station associated with a first PLMN or a first network slice
  • the node comprises a network interface and processing circuitry associated with the network interface.
  • the processing circuitry is configured to cause the node to receive, from a shared distributed unit of the first source base station and the second source base station, a message that redirects a request to retrieve a UE context of the UE to the central unit of the second source base station.
  • the processing circuitry is further configured to cause the node to, upon receiving the message, retrieve the UE context of the UE, and send the UE context of the UE to a central unit of a second target base station associated with the second PLMN or the second network slice that shares resources with a first target base station associated with the first PLMN or the first network slice, wherein the central unit of the second target base station is associated with a shared distributed unit of the first target base station and the second target base station at which a respective connection reestablishment request was received from the UE.
  • Embodiments of a method performed by a central unit of a second target base station associated with a second PLMN or a second network slice, for connection reestablishment for a UE are also disclosed.
  • the second target base station shares resources with a first target base station associated with a first PLMN or a first network slice
  • the method comprises receiving a UE context of the UE from a central unit of a second source base station associated with the second PLMN or the second network slice.
  • the second source base station shares resources with a first source base station associated with the first PLMN or the first network slice and the resources shared by the first and second target base stations, and the resources shared by the first and second source base stations comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • the method further comprises sending, to a shared distributed unit of the first target base station and the second target base station, a message that triggers transfer of the connection reestablishment request procedure from a distributed unit of the first target base station to a distributed unit of the second target base station.
  • Embodiments of a central unit of a second target base station associated with a second PLMN or a second network slice, for connection reestablishment for a UE are also disclosed.
  • the second target base station shares resources with a first target base station associated with a first PLMN or a first network slice
  • the central unit is adapted to receive a UE context of the UE from a central unit of a second source base station associated with the second PLMN or the second network slice, wherein the second source base station shares resources with a first source base station associated with the first PLMN or the first network slice and the resources shared by the first and second target base stations and the resources shared by the first and second source base stations comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • the central unit is further adapted to send, to a shared distributed unit of the first target base station and the second target base station, a message that triggers transfer of the connection reestablishment request procedure from a distributed unit of the first target base station to a distributed unit of the second target base station.
  • Embodiments of a node implementing a central unit of a second target base station associated with a second PLMN or a second network slice, for connection reestablishment for a UE are also disclosed.
  • the second target base station shares resources with a first target base station associated with a first PLMN or a first network slice
  • the node comprises a network interface and processing circuitry associated with the network interface.
  • the processing circuitry is configured to cause the node to receive a UE context of the UE from a central unit of a second source base station associated with the second PLMN or the second network slice, wherein the second source base station shares resources with a first source base station associated with the first PLMN or the first network slice and the resources shared by the first and second target base stations and the resources shared by the first and second source base stations comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • the processing circuitry is further configured to cause the node to send, to a shared distributed unit of the first target base station and the second target base station, a message that triggers transfer of the connection reestablishment request procedure from a distributed unit of the first target base station to a distributed unit of the second target base station.
  • Embodiments of a method performed for connection reestablishment of a UE in a cellular communications system are also disclosed.
  • the method comprises, at a shared distributed unit that comprises: (a) a distributed unit of a first target base station associated with a first PLMN or a first network slice and (b) a distributed unit of a second target base station associated with a second PLMN or a second network slice, wherein the first target base station and the second target base station share resources, receiving, from the UE at the distributed unit of the first target base station, a connection reestablishment request comprising an identity of the UE in a source cell to which the UE was connected prior to sending the connection
  • the method further comprises, at the shared distributed unit, sending an initial message to a central unit of the first target base station, the initial message comprising: (a) the identity of the UE in the source cell, (b) the identity of the source cell, and (c) information regarding a second cell served by the second target base station using the shared resources, wherein the shared resources comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources.
  • the method further comprises, at the central unit of the first target base station, receiving the initial message from the shared distributed unit of the first target base station and the second target base station and sending, to a central unit of a first source base station associated with the first PLMN or the first network slice, a request to retrieve a UE context of the UE.
  • the request comprises the identity of the UE in the source cell, the identity of the source cell, and the information regarding the second cell served by the second target base station using the shared resources.
  • the method further comprises, at the central unit of the first source base station, wherein the first source base station shares resources with a second source base station associated with a second PLMN or a second network slice and the resources shared by the first and second target base stations comprise physical layer resources, MAC layer resources, or both physical layer resources and MAC layer resources, receiving the request to retrieve the UE context of the UE from the central unit of the first target base station.
  • the method further comprises, at the central unit of the first source base station, determining that the UE context of the UE cannot be found by the central unit of the first source base station and, upon determining that the UE context of the UE cannot be found, sending a message to a shared distributed unit of the first source base station and the second source base station that allocated the identity of the UE in the source cell to initiate redirection of the request to retrieve the UE context of the UE to a correct central unit of the second source base station.
  • the method further comprises, at the second shared distributed unit, receiving, from the central unit of the first source base station, the message to initiate redirection of the request to retrieve the UE context of the UE to a correct central unit.
  • the method further comprises, at the second shared distributed unit, identifying a correct central unit of the second source base station from which to retrieve the UE context of the UE based on the message to initiate redirection of the request to retrieve the UE context of the UE, and sending, to the correct central unit of the second source base station, a message that redirects the request to retrieve the UE context of the UE to the correct central unit of the second source base station.
  • the method further comprises, at the correct central unit of the second source base station, receiving, from the shared distributed unit of the first source base station and the second source base station, the message that redirects the request to retrieve the UE context of the UE to the central unit of the second source base station.
  • the method further comprises, at the correct central unit of the second source base station, upon receiving the message, retrieving the UE context of the UE, and sending the UE context of the UE to a central unit of the second target base station, wherein the central unit of the second target base station is associated with the shared distributed unit of the first target base station and the second target base station at which the connection reestablishment request was received from the UE.
  • the method further comprises, at the central unit of the second target base station, receiving the UE context of the UE from the correct central unit of the second source base station, and sending, to the shared distributed unit of the first target base station and the second target base station, a message that triggers transfer of the connection reestablishment request procedure from the distributed unit of the first target base station to the distributed unit of the second target base station.
  • FIG 1 depicts the current Fifth Generation (5G) Radio Access Network (RAN) architecture, as described in Third Generation Partnership Project (3GPP)
  • Figure 2 depicts an example of multiple slice instances deployed in the same network infrastructure
  • Figure 3 illustrates an example split Centralized Unit (CU) / Distributed Unit (DU) deployment that uses networking sharing;
  • Figure 4 illustrates an example split CU/DU deployment that uses network slices
  • FIG. 5 shows one example of a Radio Resource Control (RRC)
  • Figure 6 illustrates the split CU/DU architecture used by the RRC
  • Figure 7 illustrates an example of a system in which embodiments of the present disclosure may be implemented
  • Figure 8 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • Figure 9 is a schematic block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • NG-RAN Next Generation
  • ID Cell Identity
  • TAC Tracking Area Code
  • gNB Centralized Unit
  • DU Distributed Unit
  • gNB-DU Physical DU
  • PFIY Physical
  • MAC Medium Access Control
  • FIG. 3 shows such a deployment. It is assumed that the logical Public Land Mobile Network (PLMN) specific gNB-DUs and the common PHY/MAC box, schematically shown, are in one physical entity, whereas gNB-CUs are separate from each other. It is also shown that one PLMN specific gNB-CU and gNB-DU and the PHY/MAC entity form one logical gNB. In other words, in the example of Figure 3, there are three PLMNs, which are denoted as PLM NA, PLM NB, and PLMNc.
  • PLMNA, PLMNB, and PLMNc have respective logical gNBs, which are denoted as gNB A , gNB e , and gNB c , connected to respective Fifth Generation Core Networks (5GCs), which are denoted as 5GCA, 5GCB, and 5GCc.
  • 5GCs Fifth Generation Core Networks
  • the three logical gNBs have respective TACs, denoted as TAC a , TACB, and TACc, and respective cell IDs, denoted as CellID A , CellID B , and CelllDc.
  • the three logical gNBs include separate gNB-CUs, which are denoted as CU A , CU B , and CUc, having respective FI interfaces to respective gNB-DUs, which are denoted as DUA, DUB, and DUc.
  • the gNB-DUs share common cell resources and schedulers (e.g., common PFIY and MAC).
  • the physical implementation of the entity that includes the gNB-DUs and the shared PFIY and MAC layer resources is sometimes referred to herein as a "shared gNB-DU" (e.g., shared gNB-DU A / B /c) ⁇ So, the shared gNB-DU having the PFIY and MAC layer resources provides the gNB-DU A , the gNB-DU B , and the gNB-DUc with necessary data for sending it via FI to the respective gNB-CUs (i.e., gNB-CU A , gNB- CU B , and gNB-CU c ).
  • shared gNB-DU e.g., shared gNB-DU A / B /c
  • the gNB-DU A , the gNB-DU e , and the gNB-DU c are "pure" FI protocol termination points, where the shared gNB-DU is the actual actuator when it comes to communicating with the UE.
  • the PLMN specific CUs are not inter-connected, nor are the 5GC nodes.
  • each gNB-CU serves a specific PLMN (or a subset of PLMNs).
  • This deployment scenario is not fully supported by the current Third Generation Partnership Project (3GPP) specifications. Specifically, there is no proper support for the following procedures:
  • RRC Reestablishment At Radio Resource Control (RRC) Reestablishment, the User Equipment (UE) sends an RRC Reestablishment Request message to the gNB-DU.
  • the gNB-DU is then supposed to select the correct gNB-CU for the UE i.e., a gNB-CU that serves the PLMN selected by the UE.
  • the RRC Reestablishment Request message does not include a PLMN ID. Therefore, the gNB-DU may send the RRC Reestablishment Request message to the wrong gNB- CU i.e., a gNB-CU that does not serve the PLMN selected by the UE.
  • the wrong gNB-CU will then try to retrieve the UE context, but it will inevitably fail.
  • the wrong gNB-CU will then try to send an RRC Setup message to the UE i.e., it will fail the RRC Re-establishment procedure and revert to an Initial Attach
  • the problem above is also valid in other cases where the operator wants to support multiple gNB-CUs, e.g. in deployments using network slices where different core network instances are deployed for different end to end slices and there is a desire to deploy different gNB-CU instances for each slice possible co-located with the core network instance.
  • the network slices can utilize the same physical
  • FIG. 4 An example of such scenario is depicted in Figure 4.
  • slice A there are three slices, which are denoted as slice A, slice B, and slice C, and corresponding logical gNBs, which are denoted as gNB A , gNB e , and gNBc, connected to respective 5GC instances, which are denoted as 5GC A , 5GC B , and 5GCc.
  • gNB A logical gNBs
  • 5GC instances which are denoted as 5GC A , 5GC B , and 5GCc.
  • the three logical gNBs include separate gNB-CUs, which are denoted as CU A , CUB, and CUc, having respective FI interfaces to respective gNB-DUs, which are denoted as DU A , DUB, and DUc.
  • the gNB- DUs share common cell resources and scheduler (e.g., common PFIY and MAC).
  • PFIY and MAC e.g., common PFIY and MAC
  • the UE instead of PLMN ID, the UE would use a slice ID or a slice selection assistance information (Single Network Slice Selection Assistance Information (S-NSSAI)) as described below:
  • S-NSSAI Single Network Slice Selection Assistance Information
  • RRC Reestablishment At RRC Reestablishment, the UE sends an RRC
  • the gNB-DU may send the RRC
  • Reestablishment Request message to the wrong gNB-CU i.e., a gNB-CU that does not serve the Slice selected by the UE.
  • the wrong gNB-CU will then try to retrieve the UE context, but it will inevitably fail.
  • the wrong gNB-CU will then try to send an RRC Setup message to the UE i.e., it will fail the RRC Re ⁇ establishment procedure and revert to an Initial Attach procedure.
  • aforementioned problem(s) with the RRC Reestablishment procedure are disclosed herein.
  • One example embodiment is as follows. If the UE was served by shared radio resources in an old cell (which is also referred to herein as the source cell or the cell to which the UE was connected prior to RRC reestablishment) and a wrong old RAN node (e.g., a wrong old gNB-CU, which is also referred to herein as a wrong source gNB-CU) is chosen at RRC reestablishment, this wrong old RAN node / old gNB-CU contacts the shared radio equipment that allocated the Cell Radio Network Temporary Identifier (C- RNTI) (e.g., the (correct) old gNB-DU, which is also referred to herein as the (correct) source gNB-DU) to redirect a context retrieval message to the correct old gNB-CU.
  • C- RNTI Cell Radio Network Temporary Identifier
  • a context retrieval result is then provided to a (correct) new RAN node (e.g., a (correct) new gNB-CU, which is also referred to herein as a (correct) target gNB-CU for RRC re ⁇ establishment).
  • the new RAN node communicates with a (correct) new gNB-DU for the RRC re-establishment and the UE, as if the new RAN node had received the
  • RRCReestablishmentRequest message from the new gNB-DU.
  • the first UE context retrieval could fail with an indication of the proper PLMN ID that the UE was served by before re ⁇ establishment.
  • a similar process may be used for RRC reestablishment with network slices.
  • Embodiments of the present disclosure provide a deterministic solution, which is not based on trial-and-error, for the case where the old cell (i.e., the source cell to which the UE was connected prior to RRC reestablishment) and the new cell (i.e., the target cell to which the UE is attempting to connect to via the RRC reestablishment) are shared by the same sharing operator(s).
  • An example of this deterministic solution is as follows. The UE provides its old C-RNTI / Physical Cell Identity (PCI) to a new shared gNB-DU when requesting RRC reestablishment.
  • PCI Physical Cell Identity
  • the old shared gNB-DU may have stored a mapping between the old C-RNTI / PCI of the UE and a corresponding PLMN- specific old gNB-CU.
  • the old shared gNB-DU would then be able to identify, in a deterministic way, the correct old gNB-CU, without the need of a trial/error procedure.
  • the UE context can be retrieved from the correct old gNB-CU.
  • a new solution for re-establishment is provided that supports network sharing and/or network slicing with CU-DU split, where different logical CUs and DUs share the same physical radio resources.
  • FIG. 5 shows one example of a RRC Reestablishment procedure in accordance with some embodiments of the present disclosure. Note that this example is for an architecture such as that illustrated in Figure 3 that supports network sharing with CU-DU split, where different logical gNB-CUs and gNB-DUs share the same physical radio resources and where the different logical gNB-CUs and gNB-DUs are associated with different PLMN IDs.
  • a similar process can be used for the architecture of Figure 4 that supports network slicing with CU-DU split, where different logical gNB-CUs and gNB-DUs share the same physical radio resources and where the different logical gNB- CUs and gNB-DUs are associated with different network slices.
  • Figure 6 illustrates the architecture used in the process of Figure 5.
  • the RRC Reestablishment procedure of Figure 5 involves a new (i.e., target) gNB A 600, a new (i.e., target) gNB e 602, an old (i.e., source) gNB A 604, and an old (i.e., source) gNB e 606.
  • the new gNB A 600 and the new gNB e 602 share PFIY and MAC layer resources as described above.
  • the new gNB A 600 and the new gNB e 602 include a new (i.e., target) shared gNB-DU A / B 604 that includes a new (i.e., target) gNB- DU A 610A, a new (i.e., target) gNB-DU B 610B, and shared PFIY and MAC layer
  • the new gNB A 600 also includes a new (i.e., target) gNB-CU A 612A that, e.g., communicates with the new gNB-DU A 610A via an FI interface.
  • the new gNB e 602 also includes a new (i.e., target) gNB-CU B 612B that, e.g., communicates with the new gNB-DU B 610B via an FI interface.
  • the old gNB A 604 and the old gNB B 606 also share PHY and MAC layer resources as described above.
  • the old gNB A 604 and the old gNB e 606 include an old (i.e., source) shared gNB-DU A / B 614 that includes an old (i.e., source) gNB-DU A 616A, an old (i.e., source) gNB-DU B 616B, and shared PHY and MAC layer resources.
  • the old gNB A 604 also includes an old (i.e., source) gNB-CU A 618A that, e.g., communicates with the old gNB-DU A 616A via an FI interface.
  • the old gNB e 602 also includes an old (i.e., source) gNB-CU e 618B that, e.g., communicates with the old gNB-DU B 616B via an FI interface.
  • Figure 5 illustrates a RRC reestablishment procedure in which a UE 620 sends an
  • RRCReestabHshmentRequest that is received by the new gNB-DU 610A within the new shared gNB-DU A / B 608.
  • the RRC Reestablishment procedure includes the following steps: • Step 1: The UE 620 sends an RRCReestabHshmentRequest to the new shared gNB-DU A / B 608. Within the new shared gNB-DU A / B 608, the
  • RRCReestabHshmentRequest ⁇ s more specifically received by the new shared gNB-DU A / B 608 and processed by the new shared gNB-DU A / B 608 -either in association with the new gNB-DU A 610A, which is a part of the new gNB A 600 that is associated with a first PLMN ID (PLM NA), or in association with the new gNB-DU B 610B, which is part of the new gNB e 602 that is associated with a second PLMN ID (PLM NB) .
  • PLMN ID PLMN ID
  • PLM NB PLMN ID
  • the RRCReestabHshmentRequest ⁇ s received by the new shared gNB-DU A / B 608 and processed by the new shared gNB-DU A / B 608 in association with the new gNB-DU A 610A, which is part of the new gNB A 600. Further, in this example, the RRCReestabHshmentRequest includes the following information:
  • UE 620 o Information that identifies the UE 620, which is referred to as a "UE
  • the UE-Identity is a C-RNTI of the UE 620 for a cell to which the UE 620 was connected prior to RRC reestablishment.
  • This cell is referred to herein as a "source cell” or “old cell” of the UE 620. o A source PCI of the source cell of the UE 620.
  • MAC-I short Message Authentication Code for Integrity
  • a reestablishmentCause that indicates a cause of the RRC reestablishment request.
  • Some example causes are reconfiguration failure, handover failure, or some other failure.
  • Step 2 The new shared gNB-DU A / B 608 (and in particular the new gNB-DU A 610A within the new shared gNB-DU A / B 608) sends an initial uplink RRC message to a (wrong) new gNB-CU A 612A, which is a gNB-CU that is part of the logical new gNB A 600 associated with PLMN A , over the FI interface between the new gNB-DU A 610A and the new gNB-CU A 612A.
  • the initial uplink RRC message includes new information (referred to herein as "shared new cell information") that provides information regarding which cell IDs are broadcast for other shared RANs.
  • the initial uplink RRC message includes "shared new cell information", which is information regarding other cells for other PLMNs that share the same physical resources (i.e., information regarding cells for other shared RANs).
  • This shared new cell information includes, in this example, the NG CGIs and/or PLMN IDs of the other cells that share the same physical resources.
  • This shared new cell information is desirable in order to enable a (correct) new gNB-CU B 612B (see step 10 discussed below) to behave as if it had received the initial uplink RRC message in step 2 with NR CGIB from the new shared gNB- DUA/B 608.
  • the initial uplink RRC message also includes, in this example, the C-RNTI of the UE 620 in the source cell and an RRC container comprising at least a portion of (but potentially all of) the
  • Step 3 The (wrong) new gNB-CU A 612A sends a request to a (wrong) old gNB- CUA 618A for a UE context of the UE 620.
  • This request includes information that identifies the UE 620 (C-RNTI in this example) as well as an RRC container comprising at least a portion of (but potentially all of) the
  • This information included in the request is desirable to prepare for a possible redirection of the request for the UE context of the UE 620 to the correct old gNB-CU (which in this example is old gNB-CU B 618B).
  • Step 4 The (wrong) old gNB-CU A 618A is unable to retrieve the UE context of the UE 620.
  • Step 5 Since the old gNB-CU A 618A was unable to retrieve the UE context of the UE 620, the old gNB-CU A 618A initiates a redirection of the UE context request to the appropriate old gNB-CU (which in this example is the old gNB-CU B 618B) by sending a redirect indication message to an old shared gNB-DU A / B 614 that allocated the C-RNTI of the UE 620 in the old cell. In this example, within the old gNB-DU A / B 614, the redirect indication message is received and processed by the old gNB-DU B .
  • the appropriate old gNB-CU which in this example is the old gNB-CU B 618B
  • This indication message of step 5 includes at least a portion of (but potentially all of) the RRCReestabHshmentRequest fro m step 1, at least a portion of (but potentially all of) the UE context request message from step 3, and the shared new cell information.
  • Step 6 The old gNB-DU A / B 614 identifies the correct old gNB-CU that holds the UE context of the UE 620 associated with the C-RNTI of the UE 620 in the old cell, e.g., based on a stored mapping between the C-RNTI and the correct old gNB-CU. Again, in this example, the correct old gNB-CU is the old gNB-CU B 618B.
  • Step 7 The old shared gNB-DU A / B 614 sends a redirect indication message to the correct old gNB-CU B 618B.
  • This indication message of step 7 includes at least a portion of (but potentially all of) the RRCReestabHshmentRequest fro m step 1, at least a portion of (but potentially all of) the UE context request message from step 3, and the shared new cell information.
  • Step 8 The correct old gNB-CU B 618B retrieves the UE context of the UE 620 and sends a redirection indication message including the UE context to the correct new gNB-CU B 612B.
  • the indication message of step 8 includes at least a portion of (but potentially all of) the UE context request message from step 3, and the shared new cell information.
  • Step 9 This step is only illustrated to indicate that, at this point, the redirection has ended up at the correct gNB-CU B 612B, as if the message of step 2 would have been sent to the correct gNB-CU B 612B.
  • Step 10 The correct new gNB-CU B 612B sends a RRC message transfer to the new gNB-DU A / B 608.
  • This message includes the C-RNTI of the UE 620 as a context reference.
  • indication that the UE context has been found can also be added to inform the new gNB-DU A / B 608 that a re-establishment procedure is being performed.
  • the RRC message transfer triggers transfer of the RRC reestablishment procedure from the new gNB-DU A 610A to the new gNB-DU B 610B.
  • Steps 11-13 The RRC reestablishment procedure is completed.
  • the proposed solution for redirection in CU-DU split can be also applied to a scenario where the same operator decides to configure multiple gNB-CUs and/or multiple gNB-DUs that share the same physical resource for any other reason.
  • the same approach is also applicable for other Radio Access Technologies (RATs) using the same or a similar architecture or functions (i.e., the embodiments described herein are not limited to 3GPP New Radio (NR)).
  • RATs Radio Access Technologies
  • a wireless network such as the example wireless network illustrated in Figure 7.
  • the wireless network of Figure 7 only depicts a network 706, network nodes 760 and 760B, and Wireless Devices (WDs) 710, 710B, and 710C.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or
  • wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards; Wireless Local Area Network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN Wireless Local Area Network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave
  • ZigBee ZigBee
  • the network 706 may comprise one or more backhaul networks, core networks, Internet Protocol (IP) networks, Public Switched Telephone Networks, IP networks, Public Switched Telephone Networks
  • PSTNs packet data networks
  • optical networks Wide Area Networks (WANs), Local Area Networks (LANs), WLANs
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • WANs Wide Area Networks
  • LANs Local Area Networks
  • WLANs wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • the network node 760 and the WD 710 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • network node refers to equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, Access Points (APs) (e.g., radio APs), Base Stations (BSs) (e.g., radio base stations, Node Bs, enhanced or evolved Node Bs (eNBs), and gNBs).
  • APs Access Points
  • BSs Base Stations
  • Node Bs Node Bs
  • eNBs enhanced or evolved Node Bs
  • gNBs gNode Bs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs Remote Radio Heads
  • Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS).
  • DAS Distributed Antenna System
  • network nodes include Multi-Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell/Multicast Coordination Entities (MCEs), core network nodes (e.g., Mobile Switching Centers (MSCs), Mobility Management Entities (MMEs)), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Center (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR Multi-Standard Radio
  • RNCs Radio Network Controllers
  • BSCs Base Transceiver Stations
  • MCEs Multi-Cell/Multicast Coordination Entities
  • core network nodes e.g., Mobile Switching Centers (MSCs
  • a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • the network node 760 includes processing circuitry 770, a device readable medium 780, an interface 790, auxiliary equipment 784, a power source 786, power circuitry 787, and an antenna 762.
  • the network node 760 illustrated in the example wireless network of Figure 7 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein.
  • a network node may comprise multiple different physical components that make up a single illustrated component (e.g., the device readable medium 780 may comprise multiple separate hard drives as well as multiple Random Access Memory (RAM) modules).
  • RAM Random Access Memory
  • the network node 760 may be composed of multiple physically separate components (e.g., a Node B component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 760 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple Node Bs.
  • each unique Node B and RNC pair may in some instances be considered a single separate network node.
  • the network node 760 may be configured to support multiple RATs.
  • the network node 760 may also include multiple sets of the various illustrated components for different wireless technologies integrated into the network node 760, such as, for example, GSM,
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • NR NR
  • WiFi Wireless Fidelity
  • Bluetooth wireless technologies may be integrated into the same or a different chip or set of chips and other components within the network node 760.
  • the processing circuitry 770 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by the processing circuitry 770 may include processing information obtained by the processing circuitry 770 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by the processing circuitry 770 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • the processing circuitry 770 may comprise a combination of one or more of a microprocessor, a controller, a microcontroller, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field
  • FPGA Programmable Gate Array
  • the processing circuitry 770 may execute instructions stored in the device readable medium 780 or in memory within the processing circuitry 770. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • the processing circuitry 770 may include a System on a Chip (SOC).
  • the processing circuitry 770 may include one or more of Radio Frequency (RF) transceiver circuitry 772 and baseband processing circuitry 774.
  • RF Radio Frequency
  • the RF transceiver circuitry 772 and the baseband processing circuitry 774 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of the RF transceiver circuitry 772 and the baseband processing circuitry 774 may be on the same chip or set of chips, boards, or units.
  • some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by the processing circuitry 770 executing instructions stored on the device readable medium 780 or memory within the processing circuitry 770. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 770 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, the processing circuitry 770 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry 770 alone or to other components of the network node 760, but are enjoyed by the network node 760 as a whole, and/or by end users and the wireless network generally.
  • the device readable medium 780 may comprise any form of volatile or non ⁇ volatile computer readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, Read Only Memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 770.
  • volatile or non ⁇ volatile computer readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, Read Only Memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device
  • the device readable medium 780 may store any suitable instructions; data or information, including a computer program; software; an application including one or more of logic, rules, code, tables, etc.; and/or other instructions capable of being executed by the processing circuitry 770 and utilized by the network node 760.
  • the device readable medium 780 may be used to store any calculations made by the processing circuitry 770 and/or any data received via the interface 790.
  • the processing circuitry 770 and the device readable medium 780 may be considered to be integrated.
  • the interface 790 is used in the wired or wireless communication of signaling and/or data between the network node 760, a network 706, and/or WDs 710. As illustrated, the interface 790 comprises port(s)/terminal(s) 794 to send and receive data, for example to and from the network 706 over a wired connection.
  • the interface 790 also includes radio front end circuitry 792 that may be coupled to, or in certain embodiments a part of, the antenna 762.
  • the radio front end circuitry 792 comprises filters 798 and amplifiers 796.
  • the radio front end circuitry 792 may be connected to the antenna 762 and the processing circuitry 770.
  • the radio front end circuitry 792 may be configured to condition signals communicated between the antenna 762 and the processing circuitry 770.
  • the radio front end circuitry 792 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • the radio front end circuitry 792 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 798 and/or the amplifiers 796.
  • the radio signal may then be transmitted via the antenna 762.
  • the antenna 762 may collect radio signals which are then converted into digital data by the radio front end circuitry 792.
  • the digital data may be passed to the processing circuitry 770.
  • the interface 790 may comprise different components and/or different combinations of components.
  • the network node 760 may not include separate radio front end circuitry 792; instead, the processing circuitry 770 may comprise radio front end circuitry and may be connected to the antenna 762 without separate radio front end circuitry 792.
  • the processing circuitry 770 may comprise radio front end circuitry and may be connected to the antenna 762 without separate radio front end circuitry 792.
  • all or some of the RF transceiver circuitry 772 may be considered a part of the interface 790.
  • the interface 790 may include the one or more ports or terminals 794, the radio front end circuitry 792, and the RF transceiver circuitry 772 as part of a radio unit (not shown), and the interface 790 may communicate with the baseband processing circuitry 774, which is part of a digital unit (not shown).
  • the antenna 762 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 762 may be coupled to the radio front end circuitry 792 and may be any type of antenna capable of
  • the antenna 762 may comprise one or more omni-directional, sector, or panel antennas operable to transmit/receive radio signals between, for example, 2 gigahertz (GFIz) and 66 GFIz.
  • GFIz gigahertz
  • An omni-directional antenna may be used to transmit/receive radio signals in any direction
  • a sector antenna may be used to transmit receive radio signals from devices within a particular area
  • a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line.
  • MIMO Multiple Input Multiple Output
  • the antenna 762 may be separate from the network node 760 and may be connectable to the network node 760 through an interface or port.
  • the antenna 762, the interface 790, and/or the processing circuitry 770 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data, and/or signals may be received from a WD, another network node, and/or any other network equipment. Similarly, the antenna 762, the interface 790, and/or the processing circuitry 770 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data, and/or signals may be transmitted to a WD, another network node, and/or any other network equipment.
  • the power circuitry 787 may comprise, or be coupled to, power management circuitry and is configured to supply the components of the network node 760 with power for performing the functionality described herein.
  • the power circuitry 787 may receive power from the power source 786.
  • the power source 786 and/or the power circuitry 787 may be configured to provide power to the various components of the network node 760 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 786 may either be included in, or be external to, the power circuitry 787 and/or the network node 760.
  • the network node 760 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to the power circuitry 787.
  • an external power source e.g., an electricity outlet
  • the power source 786 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, the power circuitry 787.
  • the battery may provide backup power should the external power source fail.
  • Other types of power sources, such as photovoltaic devices, may also be used.
  • the network node 760 may include additional components beyond those shown in Figure 7 that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 760 may include user interface equipment to allow input of information into the network node 760 and to allow output of information from the network node 760. This may allow a user to perform
  • WD refers to a device capable, configured, arranged, and/or operable to communicate wirelessly with network nodes and/or other WDs. Unless otherwise noted, the term WD may be used interchangeably herein with UE.
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a
  • a WD examples include, but are not limited to, a smart phone, a mobile phone, a cell phone, a Voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a Personal Digital Assistant (PDA), a wireless camera, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), a smart device, a wireless Customer Premise Equipment (CPE), a vehicle mounted wireless terminal device, etc.
  • a WD may support Device-to-Device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), Vehicle-to-Everything (V2X), and may in this case be referred to as a D2D communication device.
  • D2D Device-to-Device
  • V2V Vehicle-to-Vehicle
  • V2I Vehicle-to-Infrastructure
  • V2X Vehicle-to-Everything
  • a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such
  • the WD may in this case be a Machine-to-Machine (M2M) device, which may in a 3GPP context be referred to as a Machine-Type Communication (MTC) device.
  • M2M Machine-to-Machine
  • MTC Machine-Type Communication
  • the WD may be a UE implementing the 3GPP Narrowband IoT (NB-IoT) standard.
  • NB-IoT 3GPP Narrowband IoT
  • Such machines or devices are sensors, metering devices such as power meters, industrial machinery, home or personal appliances (e.g., refrigerators, televisions, etc.), or personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal.
  • a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • a WD 710 includes an antenna 711, an interface 714, processing circuitry 720, a device readable medium 730, user interface equipment 732, auxiliary equipment 734, a power source 736, and power circuitry 737.
  • the WD 710 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by the WD 710, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within the WD 710.
  • the antenna 711 may include one or more antennas or antenna arrays configured to send and/or receive wireless signals and is connected to the interface 714.
  • the antenna 711 may be separate from the WD 710 and be connectable to the WD 710 through an interface or port.
  • the antenna 711, the interface 714, and/or the processing circuitry 720 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data, and/or signals may be received from a network node and/or another WD.
  • radio front end circuitry and/or the antenna 711 may be considered an interface.
  • the interface 714 comprises radio front end circuitry 712 and the antenna 711.
  • the radio front end circuitry 712 comprises one or more filters 718 and amplifiers 716.
  • the radio front end circuitry 712 is connected to the antenna 711 and the processing circuitry 720 and is configured to condition signals communicated between the antenna 711 and the processing circuitry 720.
  • the radio front end circuitry 712 may be coupled to or be a part of the antenna 711.
  • the WD 710 may not include separate radio front end circuitry 712; rather, the processing circuitry 720 may comprise radio front end circuitry and may be connected to the antenna 711.
  • some or all of RF transceiver circuitry 722 may be considered a part of the interface 714.
  • the radio front end circuitry 712 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • the radio front end circuitry 712 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 718 and/or the amplifiers 716.
  • the radio signal may then be transmitted via the antenna 711.
  • the antenna 711 may collect radio signals which are then converted into digital data by the radio front end circuitry 712.
  • the digital data may be passed to the processing circuitry 720.
  • the interface 714 may comprise different components and/or different combinations of components.
  • the processing circuitry 720 may comprise a combination of one or more of a microprocessor, a controller, a microcontroller, a CPU, a DSP, an ASIC, a FPGA, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 710 components, such as the device readable medium 730, WD 710 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein.
  • the processing circuitry 720 may execute instructions stored in the device readable medium 730 or in memory within the processing circuitry 720 to provide the functionality disclosed herein.
  • the processing circuitry 720 includes one or more of the RF transceiver circuitry 722, baseband processing circuitry 724, and application processing circuitry 726.
  • the processing circuitry 720 may comprise different components and/or different combinations of components.
  • the processing circuitry 720 of the WD 710 may comprise a SOC.
  • the RF transceiver circuitry 722, the baseband processing circuitry 724, and the application processing circuitry 726 may be on separate chips or sets of chips.
  • part or all of the baseband processing circuitry 724 and the application processing circuitry 726 may be combined into one chip or set of chips, and the RF transceiver circuitry 722 may be on a separate chip or set of chips.
  • part or all of the RF transceiver circuitry 722 and the baseband processing circuitry 724 may be on the same chip or set of chips, and the application processing circuitry 726 may be on a separate chip or set of chips.
  • part or all of the RF transceiver circuitry 722, the baseband processing circuitry 724, and the application processing circuitry 726 may be combined in the same chip or set of chips.
  • the RF transceiver circuitry 722 may be a part of the interface 714.
  • the RF transceiver circuitry 722 may condition RF signals for the processing circuitry 720.
  • some or all of the functionality described herein as being performed by a WD may be provided by the processing circuitry 720 executing instructions stored on the device readable medium 730, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 720 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, the processing circuitry 720 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry 720 alone or to other components of the WD 710, but are enjoyed by the WD 710 as a whole, and/or by end users and the wireless network generally.
  • the processing circuitry 720 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by the processing circuitry 720, may include processing information obtained by the processing circuitry 720 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by the WD 710, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by the processing circuitry 720 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by the WD 710, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • the device readable medium 730 may be operable to store a computer program; software; an application including one or more of logic, rules, code, tables, etc.; and/or other instructions capable of being executed by the processing circuitry 720.
  • the device readable medium 730 may include computer memory (e.g., RAM or ROM), mass storage media (e.g., a hard disk), removable storage media (e.g., a CD or a DVD), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 720.
  • the processing circuitry 720 may include computer memory (e.g., RAM or ROM), mass storage media (e.g., a hard disk), removable storage media (e.g., a CD or a DVD), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions
  • processing circuitry 720 and the device readable medium 730 may be considered to be integrated.
  • the user interface equipment 732 may provide components that allow for a human user to interact with the WD 710. Such interaction may be of many forms, such as visual, audial, tactile, etc.
  • the user interface equipment 732 may be operable to produce output to the user and to allow the user to provide input to the WD 710.
  • the type of interaction may vary depending on the type of user interface equipment 732 installed in the WD 710. For example, if the WD 710 is a smart phone, the interaction may be via a touch screen; if the WD 710 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • the user interface equipment 732 may include input interfaces, devices and circuits, and output interfaces, devices and circuits.
  • the user interface equipment 732 is configured to allow input of information into the WD 710, and is connected to the processing circuitry 720 to allow the processing circuitry 720 to process the input information.
  • the user interface equipment 732 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a Universal Serial Bus (USB) port, or other input circuitry.
  • the user interface equipment 732 is also configured to allow output of information from the WD 710 and to allow the processing circuitry 720 to output information from the WD 710.
  • the user interface equipment 732 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits of the user interface equipment 732, the WD 710 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • the auxiliary equipment 734 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications, etc. The inclusion and type of components of the auxiliary equipment 734 may vary depending on the embodiment and/or scenario.
  • the power source 736 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices, or power cells may also be used.
  • the WD 710 may further comprise the power circuitry 737 for delivering power from the power source 736 to the various parts of the WD 710 which need power from the power source 736 to carry out any functionality described or indicated herein.
  • the power circuitry 737 may in certain embodiments comprise power management circuitry.
  • the power circuitry 737 may additionally or alternatively be operable to receive power from an external power source, in which case the WD 710 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • the power circuitry 737 may also in certain embodiments be operable to deliver power from an external power source to the power source 736. This may be, for example, for the charging of the power source 736.
  • the power circuitry 737 may perform any formatting, converting, or other modification to the power from the power source 736 to make the power suitable for the respective components of the WD 710 to which power is supplied.
  • Figure 8 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • a UE 800 may be any UE identified by 3GPP, including a NB-IoT UE, a MTC UE, and/or an enhanced MTC (eMTC) UE.
  • the UE 800 as illustrated in Figure 8, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by 3GPP, such as 3GPP's GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP's GSM, UMTS, LTE, and/or 5G standards such as 3GPP's GSM, UMTS, LTE, and/or 5G standards.
  • the term WD and UE may be used interchangeable. Accordingly, although Figure 8 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • the UE 800 includes processing circuitry 801 that is operatively coupled to an input/output interface 805, an RF interface 809, a network connection interface 811, memory 815 including RAM 817, ROM 819, and a storage medium 821 or the like, a communication subsystem 831, a power source 813, and/or any other component, or any combination thereof.
  • the storage medium 821 includes an operating system 823, an application program 825, and data 827.
  • the storage medium 821 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 8, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 801 may be configured to process computer instructions and data.
  • the processing circuitry 801 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.);
  • the processing circuitry 801 may include two CPUs. Data may be information in a form suitable for use by a computer.
  • the input/output interface 805 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • the UE 800 may be configured to use an output device via the input/output interface 805.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from the UE 800.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • the UE 800 may be configured to use an input device via the input/output interface 805 to allow a user to capture information into the UE 800.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • the RF interface 809 may be configured to provide a
  • the network connection interface 811 may be configured to provide a communication interface to a network 843A.
  • the network 843A may encompass wired and/or wireless networks such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • the network 843A may comprise a WiFi network.
  • the network connection interface 811 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet,
  • the network connection interface 811 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like).
  • the transmitter and receiver functions may share circuit components, software, or firmware, or alternatively may be implemented separately.
  • the RAM 817 may be configured to interface via a bus 802 to the processing circuitry 801 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • the ROM 819 may be configured to provide computer instructions or data to the processing circuitry 801.
  • the ROM 819 may be configured to store invariant low-level system code or data for basic system functions such as basic Input and Output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • the Storage medium 821 may be configured to include memory such as RAM, ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • the storage medium 821 may be configured to include the operating system 823, the application program 825 such as a web browser application, a widget or gadget engine, or another application, and the data file 827.
  • the storage medium 821 may store, for use by the UE 800, any of a variety of various operating systems or combinations of operating systems.
  • the storage medium 821 may be configured to include a number of physical drive units, such as a Redundant Array of Independent Disks (RAID), a floppy disk drive, flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a High-Density Digital Versatile Disc (HD-DVD) optical disc drive, an internal hard disk drive, a Blu-Ray optical disc drive, a Holographic Digital Data Storage (HDDS) optical disc drive, an external mini-Dual In-Line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a Subscriber Identity Module (SIM) or a Removable User Identity (RUIM) module, other memory, or any combination thereof.
  • RAID Redundant Array of Independent Disks
  • HD-DVD High-Density Digital Versatile Disc
  • HDDS Holographic Digital Data Storage
  • DIMM Digital Data Storage
  • DIMM Synchro
  • the storage medium 821 may allow the UE 800 to access computer-executable instructions, application programs, or the like, stored on transitory or non-transitory memory media, to off-load data or to upload data.
  • An article of manufacture, such as one utilizing a communication system, may be tangibly embodied in the storage medium 821, which may comprise a device readable medium.
  • the processing circuitry 801 may be configured to communicate with a network 843B using the communication subsystem 831.
  • the network 843A and the network 843B may be the same network or networks or different network or networks.
  • the communication subsystem 831 may be configured to include one or more transceivers used to communicate with the network 843B.
  • the communication subsystem 831 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a RAN according to one or more communication protocols, such as IEEE 802.7, Code Division Multiple Access (CDMA), WCDMA, GSM, LTE, Universal Terrestrial RAN (UTRAN), WiMax, or the like.
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • UTRAN Universal Terrestrial RAN
  • Each transceiver may include a transmitter 833 and/or a receiver 835 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, the transmitter 833 and the receiver 835 of each transceiver may share circuit components, software, or firmware, or alternatively may be implemented separately.
  • the communication subsystem 831 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof.
  • the communication subsystem 831 may include cellular communication, WiFi communication, Bluetooth communication, and GPS communication.
  • the network 843B may encompass wired and/or wireless networks such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another like network, or any combination thereof.
  • the network 843B may be a cellular network, a WiFi network, and/or a near-field network.
  • a power source 813 may be configured to provide Alternating Current (AC) or Direct Current (DC) power to components of the UE 800.
  • the communication subsystem 831 may be configured to include any of the components described herein.
  • the processing circuitry 801 may be configured to communicate with any of such components over the bus 802.
  • any of such components may be represented by program instructions stored in memory that, when executed by the processing circuitry 801, perform the
  • any of such components may be partitioned between the processing circuitry 801 and the communication subsystem 831.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIG. 9 is a schematic block diagram illustrating a virtualization environment 900 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a WD, or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executing on one or more physical processing nodes in one or more networks).
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a WD, or any other type of communication device
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 900 hosted by one or more of hardware nodes 930. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node)
  • the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications 920 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • the applications 920 are run in the virtualization environment 900 which provides hardware 930 comprising processing circuitry 960 and memory 990.
  • the memory 990 contains instructions 995 executable by the processing circuitry 960 whereby the application 920 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • the virtualization environment 900 comprises general-purpose or special- purpose network hardware devices 930 comprising a set of one or more processors or processing circuitry 960, which may be Commercial Off-the-Shelf (COTS) processors, dedicated ASICs, or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device 930 may comprise memory 990-1 which may be non-persistent memory for temporarily storing instructions 995 or software executed by the processing circuitry 960.
  • Each hardware device 930 may comprise one or more Network Interface Controllers (NICs) 970, also known as network interface cards, which include a physical network interface 980.
  • NICs Network Interface Controllers
  • Each hardware device 930 may also include non-transitory, persistent, machine-readable storage media 990-2 having stored therein software 995 and/or instructions executable by the processing circuitry 960.
  • the software 995 may include any type of software including software for instantiating one or more virtualization layers 950 (also referred to as hypervisors), software to execute virtual machines 940, as well as software allowing it to execute functions, features, and/or benefits described in relation with some embodiments described herein.
  • the virtual machines 940 comprise virtual processing, virtual memory, virtual networking or interface, and virtual storage, and may be run by a corresponding virtualization layer 950 or hypervisor.
  • Different embodiments of the instance of virtual appliance 920 may be implemented on one or more of the virtual machines 940, and the implementations may be made in different ways.
  • the processing circuitry 960 executes the software 995 to instantiate the hypervisor or virtualization layer 950, which may sometimes be referred to as a Virtual Machine Monitor (VMM).
  • the virtualization layer 950 may present a virtual operating platform that appears like networking hardware to the virtual machine 940.
  • the hardware 930 may be a standalone network node with generic or specific components.
  • the hardware 930 may comprise an antenna 9225 and may implement some functions via virtualization.
  • the hardware 930 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via a Management and Orchestration (MANO) 9100, which, among others, oversees lifecycle management of the applications 920.
  • MANO Management and Orchestration
  • NFV Network Function Virtualization
  • NFV Network Function Virtualization
  • the virtual machine 940 may be a software
  • VNE Virtual Network Element
  • VNF Virtual Network Function
  • one or more radio units 9200 that each include one or more transmitters 9220 and one or more receivers 9210 may be coupled to the one or more antennas 9225.
  • the radio units 9200 may communicate directly with the hardware nodes 930 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be effected with the use of a control system 9230, which may alternatively be used for communication between the hardware nodes 930 and the radio unit 9200.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include DSPs, special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as ROM, RAM, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • the term unit may have conventional meaning in the field of electronics, electrical devices, and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • Embodiment 1 A method performed by a first distributed unit (gNB-DU A / E s) of a first base station (gNB A ) associated with a first PLMN (PLMN A ) or a first network slice (Slice A ) wherein the first base station (gNB A ) shares physical layer and/or MAC layer resources with a second base station (gNB fi ) associated with a second PLMN (PLMNB) or a second network slice (Slice B ), the method comprising: receiving (Fig.
  • step 1) from a UE, a connection reestablishment request comprising an identity of the UE in a source cell to which the UE was connected prior to sending the connection reestablishment request and an identity of the source cell; and sending (Fig. 5, step 2) an initial message to a first central unit (new gNB-CU A ) of the first base station (gNB A ), the initial message comprising information regarding a second cell served by the second base station (gNB e ) using the shared physical layer and/or MAC layer resources.
  • a first central unit new gNB-CU A
  • the initial message comprising information regarding a second cell served by the second base station (gNB e ) using the shared physical layer and/or MAC layer resources.
  • Embodiment 2 The method of embodiment 1 wherein the connection reestablishment request is a RRC Reestablishment Request.
  • Embodiment 3 The method of embodiment 2 wherein the information regarding the second cell served by the second base station (gNB e ) using the shared physical layer and/or MAC layer resources comprises a Cell Group Identifier, CGI, of the second cell and/or a PLMN ID of the second PLMN (PLMNB) associated with the second cell.
  • CGI Cell Group Identifier
  • Embodiment 4 A method performed by a first central unit (old gNB-CU A ) of a first base station (gNB A ) associated with a first PLMN (PLMN A ) or a first network slice (Slice A ) for a connection reestablishment procedure for a UE, wherein the first base station (gNB A ) shares physical layer and/or MAC layer resources with a second base station 3 ⁇ 4NBB) associated with a second PLMN (PLMNB) or a second network slice (Slices), the method comprising: receiving (Fig.
  • step 3 from a second central unit (new gNB-CU A ), a request to retrieve a UE context of the UE, the request comprising an identity of the UE in a source cell to which the UE was connected prior to connection reestablishment; determining (Fig. 5, step 4) that the UE context of the UE cannot be found by the first central unit (old gNB-CU A ) of the first base station (gNB A ); and upon determining that the UE context of the UE cannot be found, sending (Fig. 5, step 5) a message to a distributed unit (old gNB-DU A / B ) that allocated the identity of the UE in the source cell to initiate redirection of the request to retrieve the UE context of the UE to a correct central unit.
  • a distributed unit old gNB-DU A / B
  • Embodiment 5 The method of embodiment 4 wherein the request to retrieve the UE context of the UE further comprises: at least a portion of a connection
  • Embodiment 6 The method of embodiment 4 or 5 wherein the message sent to the distributed unit (old gNB-DU A / B ) comprises: the identity of the UE in the source cell; at least a portion of a connection reestablishment request message sent by the UE to initiate the connection reestablishment procedure; at least a portion of the request to retrieve the UE context of the UE; and/or shared cell information.
  • Embodiment 7 The method of embodiment 5 or 6 wherein the shared cell information comprises a Cell Group Identifier, CGI, of another cell and/or a PLMN ID of the second PLMN associated with the other cell.
  • CGI Cell Group Identifier
  • Embodiment 8 A method performed by a first distributed unit (old gNB- DU A / B ) of a first base station (gNB e ) associated with a first PLMN (PLMNB) or a first network slice (Slice B ) for a connection reestablishment procedure for a UE, wherein the first base station (gNB e ) shares physical layer and/or MAC layer resources with a second base station (gNB A ) associated with a second PLMN (PLMN A ) or a second network slice (SliceA), the method comprising: receiving (Fig.
  • step 5 from a central unit (old gNB- CU A ) of the second base station (gNB A ), a message to initiate redirection of a request to retrieve a UE context of the UE to a correct central unit, the message comprising an identity of the UE in a source cell to which the UE was connected prior to connection reestablishment; identifying (Fig. 5, step 6) a correct central unit (old gNB-CU E s) of the first base station (gNB B ) from which to retrieve the UE context of the UE based on the identity of the UE in the source cell; and sending (Fig.
  • step 7 to the correct central unit (old gNB-CU B ) of the first base station (gNB B ), a message that redirects the request to retrieve the UE context of the UE to the correct central unit (old gNB-CU B ) of the first base station (gNB B ).
  • Embodiment 9 A method performed by a first central unit (old gNB-CU B ) of a first base station (gNB B ) associated with a first PLMN (PLMN B ) or a first network slice (Slice B ) for a connection reestablishment procedure for a UE, wherein the first base station (gNB B ) shares physical layer and/or MAC layer resources with a second base station (gNB A ) associated with a second PLMN (PLMN A ) or a second network slice (Slice A ), the method comprising: receiving (Fig.
  • step 7 from a distributed unit (old gNB-DU A / B ) of the first base station (gNB B ), a message that redirects a request to retrieve a UE context of the UE to the first central unit (old gNB-CU B ) of the first base station (gNB B ); upon receiving the message, retrieving the UE context of the UE; and sending (Fig. 5, step 8) the UE context of the UE to a central unit (new gNB-CU B ) associated with a correct distributed unit (new gNB-DU A / B ) for connection
  • Embodiment 10 A method performed by a distributed unit (new gNB-DU A / B ) of a first base station (gNB B ) associated with a first PLMN (PLMN B ) or a first network slice (Slice B ) for a connection reestablishment procedure for a UE, wherein the first base station (gNB B ) shares physical layer and/or MAC layer resources with a second base station (gNB A ) associated with a second PLMN (PLMN A ) or a second network slice (Slice A ), the method comprising: receiving (Fig.
  • step 10 from a central unit (new gNB-CU B ) of the first base station (gNB B ), a message that transfers the connection reestablishment procedure for the UE to the distributed unit (new gNB-DU A / B ) of the first base station (gNB B ); and completing (Fig. 5, steps 11-13) the connection
  • Embodiment 11 A node implementing a central unit or a distributed unit of a base station, the node comprising: a network interface; and processing circuitry associated with the network interface, the processing circuitry configured to cause the node to perform the method of any one of embodiments 1 to 10.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes et des procédés de rétablissement de connexion dans un système de communication cellulaire qui utilise une division unité centralisée (CU)/unité distribuée (DU). Dans un mode de réalisation, l'invention concerne un procédé mis en œuvre par une unité distribuée partagée pour un rétablissement de connexion pour un équipement d'utilisateur (EU). L'unité distribuée partagée comprend des unités distribuées de première et seconde stations de base cibles associées à des premier et second réseaux mobiles terrestres publics (RMTP) ou des première et seconde tranches de réseau, respectivement, les première et seconde stations de base cibles partageant des ressources. Le procédé consiste à recevoir une requête de rétablissement de connexion comprenant une identité de l'EU dans une cellule source et une identité de la cellule source et envoyer un message à une unité centrale de la première station de base cible comprenant les identités de l'EU et de la cellule source, et des informations concernant une cellule desservie par la seconde station de base cible à l'aide des ressources partagées.
PCT/IB2019/059739 2018-11-13 2019-11-13 Mécanisme de redirection pour supporter le partage/découpe de réseau avec division uc-ud pour le rétablissement WO2020100053A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862760658P 2018-11-13 2018-11-13
US62/760,658 2018-11-13

Publications (1)

Publication Number Publication Date
WO2020100053A1 true WO2020100053A1 (fr) 2020-05-22

Family

ID=68696474

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2019/059739 WO2020100053A1 (fr) 2018-11-13 2019-11-13 Mécanisme de redirection pour supporter le partage/découpe de réseau avec division uc-ud pour le rétablissement

Country Status (1)

Country Link
WO (1) WO2020100053A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112654056A (zh) * 2020-12-07 2021-04-13 京信通信系统(中国)有限公司 共享小区管理的方法、分布单元、集中单元和介质
WO2022021351A1 (fr) * 2020-07-31 2022-02-03 Lenovo (Beijing) Limited Procédé et appareil de rétablissement dans un système de communication sans fil
US20220408326A1 (en) * 2021-06-17 2022-12-22 Qualcomm Incorporated Enhanced reestablishment procedure in integrated access and backhaul nodes
US11871271B2 (en) 2021-05-17 2024-01-09 Cisco Technology, Inc. Dynamic switching for user equipment between unique cell and shared cell operating modes based on application traffic
US11882611B2 (en) 2021-05-17 2024-01-23 Cisco Technology, Inc. Dual-connectivity support for user equipment in a hybrid cell virtualized radio access network architecture
US11950218B2 (en) 2021-05-14 2024-04-02 Cisco Technology, Inc. Auto-configuration of hybrid cells supporting shared cell and unique cell operating modes for user equipment in virtualized radio access network architectures
US12004025B2 (en) 2021-05-14 2024-06-04 Cisco Technology, Inc. Supporting handovers in hybrid cell configuration environments

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON ET AL: "RAN sharing with multiple Cell ID broadcast", vol. RAN WG3, no. Spokane, WA, U.S.; 20181112 - 20181116, 11 November 2018 (2018-11-11), XP051558612, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN3/Docs/R3%2D186859%2Ezip> [retrieved on 20181111] *
ERICSSON: "Response paper to R3-185596 and R3-185739", vol. RAN WG3, no. Chengdu, P.R. China; 20181008 - 20181012, 4 October 2018 (2018-10-04), XP051529315, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG3%5FIu/TSGR3%5F101bis/Docs/R3%2D186053%2Ezip> [retrieved on 20181004] *
ERICSSON: "Response paper to R3-185845", vol. RAN WG3, no. Chengdu, P.R. China; 20181008 - 20181012, 4 October 2018 (2018-10-04), XP051529318, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG3%5FIu/TSGR3%5F101bis/Docs/R3%2D186056%2Ezip> [retrieved on 20181004] *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022021351A1 (fr) * 2020-07-31 2022-02-03 Lenovo (Beijing) Limited Procédé et appareil de rétablissement dans un système de communication sans fil
CN112654056A (zh) * 2020-12-07 2021-04-13 京信通信系统(中国)有限公司 共享小区管理的方法、分布单元、集中单元和介质
CN112654056B (zh) * 2020-12-07 2024-01-23 京信网络系统股份有限公司 共享小区管理的方法、分布单元、集中单元和介质
US11950218B2 (en) 2021-05-14 2024-04-02 Cisco Technology, Inc. Auto-configuration of hybrid cells supporting shared cell and unique cell operating modes for user equipment in virtualized radio access network architectures
US12004025B2 (en) 2021-05-14 2024-06-04 Cisco Technology, Inc. Supporting handovers in hybrid cell configuration environments
US11871271B2 (en) 2021-05-17 2024-01-09 Cisco Technology, Inc. Dynamic switching for user equipment between unique cell and shared cell operating modes based on application traffic
US11882611B2 (en) 2021-05-17 2024-01-23 Cisco Technology, Inc. Dual-connectivity support for user equipment in a hybrid cell virtualized radio access network architecture
US20220408326A1 (en) * 2021-06-17 2022-12-22 Qualcomm Incorporated Enhanced reestablishment procedure in integrated access and backhaul nodes
US11689975B2 (en) * 2021-06-17 2023-06-27 Qualcomm Incorporated Enhanced reestablishment procedure in integrated access and backhaul nodes

Similar Documents

Publication Publication Date Title
US11671952B2 (en) Frequency or radio access technology (RAT) selection based on slice availability
US11064405B2 (en) Delta configuration in split CU-DU RAN architecture
JP7218362B2 (ja) Ranインタフェースを介した通知制御
US11595853B2 (en) Redirection mechanism to support network sharing/slicing with CU-DU split
US20230328827A1 (en) Slicing of Network Resources for Dual Connectivity using NR
WO2020100053A1 (fr) Mécanisme de redirection pour supporter le partage/découpe de réseau avec division uc-ud pour le rétablissement
JP7307816B2 (ja) 2ステップ競合フリーランダムアクセス
WO2019054923A1 (fr) Procédé, nœud de réseau, et ue, pour gérer des mesures rrm sur une porteuse comprenant une pluralité de blocs de séquence de synchronisation
WO2020030676A1 (fr) Transfert inter-système des systèmes à connectivité simple/double vers des systèmes à connectivité double
EP4014532A1 (fr) Mise à jour d&#39;une pci dans une architecture divisée du-cu
EP4052532A1 (fr) Configuration conditionnelle dans un fonctionnement à connectivités multiples
WO2019159136A1 (fr) Procédé de transfert de technologie d&#39;accès inter-radio
EP3864927B1 (fr) Procédé et appareil utilisés dans la fiabilité de transmission
JP7407310B2 (ja) 複数のセルについての情報を記憶することを求める要求
WO2022031210A1 (fr) Demande d&#39;un changement de configuration pour un nœud de réseau d&#39;accès radio
WO2020139178A1 (fr) Appareils et procédés destinés à une double connectivité
US20230300634A1 (en) Reference signal beam configuration in a wireless communication network
EP4046418A1 (fr) Configuration et rapport d&#39;informations de position en association avec un mdt
US20210227382A1 (en) To Increase Security of Dual Connectivity
JP7439254B2 (ja) Srb3を介したオンデマンドシステム情報ブロックリクエスト
US11445474B2 (en) Mobile switching node and mobility management node to page terminal device
WO2021245604A1 (fr) Échec de transfert de nouvelle génération dû à des capacités d&#39;équipement utilisateur non prises en charge

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19809620

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19809620

Country of ref document: EP

Kind code of ref document: A1