Nothing Special   »   [go: up one dir, main page]

EP4014532A1 - Mise à jour d'une pci dans une architecture divisée du-cu - Google Patents

Mise à jour d'une pci dans une architecture divisée du-cu

Info

Publication number
EP4014532A1
EP4014532A1 EP20761650.9A EP20761650A EP4014532A1 EP 4014532 A1 EP4014532 A1 EP 4014532A1 EP 20761650 A EP20761650 A EP 20761650A EP 4014532 A1 EP4014532 A1 EP 4014532A1
Authority
EP
European Patent Office
Prior art keywords
parameter
gnb
cell
base station
update
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
EP20761650.9A
Other languages
German (de)
English (en)
Inventor
Angelo Centonza
Ali PARICHEHREHTEROUJENI
Stefan Engström
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP4014532A1 publication Critical patent/EP4014532A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • Examples of this disclosure relate to updating a parameter of a cell, such as for example a Physical Cell Identifier (PCI) or random access configuration of the cell.
  • PCI Physical Cell Identifier
  • NG-RAN 5G radio access network
  • TS 38.401v15.5.0 e.g. available at http://www.3gpp.Org/ftp//Specs/archive/38_series/38.401/38401-f50.zip
  • Figure 1 shows an example of an overview of a 5G Radio Access Network (RAN) architecture with split RAN node.
  • RAN Radio Access Network
  • Next Generation (NG) architecture can be further described as follows:
  • the NG-RAN consists of a set of gNBs connected to the 5GC through the NG interface.
  • a gNB can support FDD mode, TDD mode or dual mode operation.
  • • gNBs can be interconnected through the Xn interface.
  • a gNB may consist of a gNB-CU (central unit) and one or more gNB-DUs (distributed units).
  • One gNB-DU is connected to only one gNB-CU. o
  • a gNB-DU may be connected to multiple gNB-CU by appropriate implementation.
  • NG, Xn and F1 are logical interfaces.
  • 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 i.e. the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL.
  • NG, Xn, F1 For each NG-RAN interface (NG, Xn, F1) the related TNL protocol and the functionality are specified.
  • the TNL provides services for user plane transport, signalling transport. If security protection for control plane and user plane data on TNL of NG-RAN interfaces has to be supported, NDS/IP (3GPP TS 33.401 [x] shall be applied).
  • a gNB may also be connected to an LTE eNB via the X2 interface.
  • Another architectural option is that where an LTE eNB connected to the Evolved Packet Core network is connected over the X2 interface with a so called en-gNB.
  • the latter is a gNB not connected directly to a CN and connected via X2 to an eNB for the sole purpose of performing dual connectivity.
  • the architecture in Figure 1 can be expanded by spitting the gNB-CU into two entities. So in the split architecture option, the RAN protocol stack functionality is separated in different parts.
  • the CU-CP central unit-control plane
  • the CU-UP central unit-user plane
  • the DU will handle the RLC, MAC and PHY layer of the protocol stack.
  • the DU can be separated units so that one DU handles the PHY parts separately compared to RLC and MAC layers that are handled in another DU.
  • Figure 2 shows an example of a RAN node split architecture. As shown in Figure 2, different units can handle different protocol stack functionalities, and there will be a need for inter-node communication between the DU, the CU-UP and the CU-CP. This is achieved via F1-C interface related to control plane signaling, via F1-U interface related to user plane signaling for communication between CU and DU and via E1 for communication between CU-UP and CU-CP.
  • the E1 interface is a logical interface. It supports the exchange of signalling information between the endpoints. From a logical standpoint, the E1 is a point-to-point interface between a gNB-CU-CP and a gNB-CU-UP. The E1 interface enables exchange of UE associated information and non-UE associated information. The E1 interface is a control interface and is not used for user data forwarding.
  • the split RAN architecture described above for the NG RAN is also replicated in E-UTRAN.
  • E-UTRAN a similar node structure to the NG RAN can be encountered, namely the E-UTRAN can be split into an eNB-DU and an eNB-CU, where the eNB-DU hosts the RLC/MAC/PFIY protocols and where the gNB-CU hosts the PDCP and RRC protocols.
  • a split eNB connects to other RAN nodes via the X2 interface and with the EPC CN system via the S1 interface.
  • Figure 3 shows an example of a split E-UTRAN architecture defined in 3GPP.
  • the current 3GPP specifications provide a basic mechanism for physical cell identifier (PCI) assignment and reconfiguration between the gNB-DU and gNB-CU by leveraging standardized signaling over F1 logical interface as shown in Figure 4, which shows an example of signaling between gNB-DU and gNB-CU-CP with possibility of reconfiguring PCI.
  • PCI physical cell identifier
  • the gNB-DU and its cells can be configured by DU OAM in the F1 pre-operational state.
  • Flence preconfiguration of the PCI may be decided by Operations, Administration and Maintenance (OAM) or by DU itself.
  • OFAM Operations, Administration and Maintenance
  • the gNB-DU may send an F1 SETUP REQUEST message to the gNB-CU including a list of cells that are pre-configured and ready to be activated as part of Served Cell Information information element (IE).
  • IE Served Cell Information information element
  • the gNB-CU may ensure the connectivity toward the core network via NG Setup or the gNB Configuration Update procedure towards 5GC.
  • gNB-CU via response message may indicate that gNB-DU need to reconfigure the PCI of some cells upon detection of PCI collision or confusion.
  • gNB-DU detects such request from gNB-CU- CP if a new PCI is configured beside the CGI as part of F1 Setup Response.
  • 38.473 (3GPP TS 38.473, Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP), 3GPP, V15.6.0, 2019-07), which is incorporated herein by reference:
  • the gNB-CU may include the Cells to be Activated List IE in the F1 SETUP RESPONSE message.
  • the Cells to be Activated List ⁇ E includes a list of cells that the gNB-CU requests the gNB-DU to activate.
  • the gNB-DU shall activate the cells included in the Cells to be Activated List IE and reconfigure the physical cell identity for cells for which the NR PCi IE is included.
  • the gNB-DU may initiate the gNB-DU Configuration Update procedure towards the gNB-CU and includes the cell(s) that are In-Service and/or the cell(s) that are Out-Of-Service.
  • the gNB-DU may also indicate cell(s) to be deleted, in which case the gNB-CU removes the corresponding cell(s) information.
  • the gNB-CU may send a gNB-DU Configuration update acknowledge message to the gNB-DU and indicate whether PCI of activated cells need to be reconfigured with new PCI.
  • the gNB-DU shall activate the cell indicated by NR CGI IE and reconfigure the physical cell identity for cells for which the NR PCI IE is included.
  • the gNB-CU may send a GNB-CU-CP CONFIGURATION UPDATE message to the gNB-DU that optionally includes a list of cells to be activated (e.g., in case that these cells were not activated using the F1 SETUP RESPONSE message), as well as the new PCI for the activated cell if required.
  • gNB-DU should apply the changes and reconfigure the cells requested to be reconfigured with new PCI. The following is an excerpt from 38.473:
  • the gNB-DU shall activate the cell indicated by NR CGI IE and reconfigure the physical cell identity for which the NR PCI IE is included.
  • the gNB-DU replies with a GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message that optionally includes a list of cells that failed to be activated.
  • the gNB-CU regards all Active cells as Out-Of-Service until the gNB-DU indicates that they are In-Service.
  • the gNB-DU is provisioned with PCIs for each supported cell.
  • the gNB-DU includes a PCI that was preconfigured at the gNB-DU.
  • the gNB-CU is able to re-assign a PCI to any given cell of a gNB-DU either at the time of cell activation, or while a cell is already in active state.
  • the change of PCI can be provided from the gNB-CU to the gNB-DU by means of including a new PCI for a specified gNB-DU cell in the F1 Setup Response message, or gNB-CU Configuration Update message or in the gNB-DU configuration Update Acknowledge message.
  • the criteria according to which the gNB-CU provisions the gNB-DU with a new PCI for a given cell are gNB-CU implementation specific and comprise the detection of issues such as PCI collision or PCI confusion.
  • PCI collision is defined as the case where one cell has a neighbour cell with the same PCI. This may lead to issues such as dropped connections.
  • PCI confusion is defined as the case where one cell has two or more neighbour cells, which have the same PCI. This may lead to failed handovers or dropped connections.
  • One aspect of the present disclosure provides a method in a base station central unit, CU, of updating a parameter of a cell associated with a base station distributed unit, DU.
  • the method comprises sending an instruction to the DU to cause the DU to update the parameter, and receiving a notification from the DU that the update of the parameter has been performed.
  • Another aspect of the present disclosure provides a method of updating a parameter of a cell associated with a base station distributed unit, DU.
  • the method comprises receiving an instruction to update the parameter, performing the update of the parameter, and sending a notification that the update of the parameter has been performed.
  • the apparatus comprises a processor and a memory.
  • the memory contains instructions executable by the processor such that the apparatus is operable to send an instruction to the DU to cause the DU to update the parameter, and receive a notification from the DU that the update of the parameter has been performed.
  • Another aspect of the present disclosure provides apparatus for updating a parameter of a cell associated with a base station distributed unit, DU.
  • the apparatus comprises a processor and a memory.
  • the memory contains instructions executable by the processor such that the apparatus is operable to receive an instruction to update the parameter, perform the update of the parameter, and send a notification that the update of the parameter has been performed.
  • Another aspect of the present disclosure provides apparatus in a base station central unit, CU, of updating a parameter of a cell associated with a base station distributed unit, DU.
  • the apparatus is configured to send an instruction to the DU to cause the DU to update the parameter, and receive a notification from the DU that the update of the parameter has been performed.
  • Another aspect of the present disclosure provides apparatus for updating a parameter of a cell associated with a base station distributed unit, DU.
  • the apparatus is configured to receive an instruction to update the parameter, perform the update of the parameter, and send a notification that the update of the parameter has been performed.
  • Figure 1 shows an example of an overview of a 5G RAN architecture with split RAN node
  • Figure 2 shows an example of a RAN node split architecture
  • Figure 3 shows an example of a split E-UTRAN architecture defined in 3GPP
  • Figure 4 shows an example of signaling between gNB-DU and gNB-CU-CP
  • Figure 5 is a flow chart of an example of a method in a base station central unit, CU, of updating a parameter of a cell associated with a base station distributed unit, DU;
  • Figure 6 is a flow chart of an example of a method of updating a parameter of a cell associated with a base station distributed unit, DU;
  • Figure 7 shows an example of communications between a gNB-CU-CP and gNB-DU in a method of updating a parameter of a cell associated with a base station distributed unit, DU;
  • Figure 8 shows an example of a wireless network in accordance with some embodiments
  • Figure 9 shows an example of a User Equipment in accordance with some embodiments.
  • Figure 10 shows an example of a virtualization environment in accordance with some embodiments
  • Figure 11 shows an example of a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments
  • Figure 12 shows an example of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments
  • Figure 13 shows examples of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments
  • Figure 14 shows examples of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments
  • Figure 15 shows examples of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments
  • Figure 16 shows examples of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments
  • Figure 17 shows an example of virtualization apparatus in accordance with some embodiments.
  • Figure 18 shows another example of virtualization apparatus in accordance with some embodiments.
  • Hardware implementation may include or encompass, without limitation, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g., digital or analogue) circuitry including but not limited to application specific integrated circuit(s) (ASIC) and/or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the gNB-CU may signal to the gNB-DU a change of PCI for a given cell when the cell is active and in service.
  • the gNB-DU may not be possible for the gNB-DU to change the PCI of the cell without disrupting served UE traffic.
  • a change of PCI might cause UEs to disconnect and reconnect again to their serving cell, resulting in performance degradation.
  • the gNB-DU took the liberty of not applying the PCI change upon reception of the new PCI from the gNB- CU, there would be a de-synchronization between gNB-DU and gNB-CU with respect to the PCI used by gNB-DU cells.
  • gNB-CU commands a change of PCI for Cell X, but gNB-DU does not apply the change immediately, then gNB- CU may believe that the change was applied and it might (for example) select the wrong handover target for a UE that reports the new PCI assigned by the gNB-CU to the gNB-DU.
  • the problem in some examples is therefore how to avoid changes of cell parameters configuration impacting the quality of service of served users.
  • a distributed unit such as for example a gNB-DU apply changes to cell parameters when the traffic conditions are most favourable, e.g. when traffic load is low, and to allow the gNB-DU to confirm to the gNB-CU when the change took place.
  • the latter allows the information between the PCI used per cell by the gNB-DU and the same information at the gNB-CU to be always in sync.
  • a specific distributed unit e.g. eNB-DU or gNB-DU
  • a specific central unit e.g. eNB-CU, eNB- CU-CP, gNB-CU or gNB-CU-CP
  • PCI physical cell identifier
  • the gNB-CU-CP may detect the need for a change in PCI for a cell served by one of its connected gNB-DUs.
  • the gNB-CU-CP may signal to the gNB-DU an indication that the PCI of a specific cell needs to be changed.
  • the gNB-CU-CP may signal also the new PCI to be assigned to the specific cell.
  • the request may include a set of possible PCIs so select from.
  • selection of the new PCI may be solely performed by the gNB-DU.
  • the gNB-CU-CP should not assume that the PCI of the specific cell was updated as soon as the procedure for sending to the gNB-DU the new PCI (or for flagging the need for a PCI change) is completed. Instead, the gNB- CU-CP should assume that the PCI of the specific cell has not been changed until the gNB-DU notifies the gNB- CU-CP of such change.
  • the gNB-DU After receiving the new PCI for the specific cell, the gNB-DU waits for the most effective time when a change of PCI can be applied to the cell. This may depend from factors such as the number of UEs connected to the cell, or the types of services served by the cell. When the gNB-DU considers that there is an optimal time to perform the PCI change, it will assign a new PCI to the cell and it will start transmitting this PCI over the air for the specific cell.
  • the gNB-DU after changing the PCI of the specific cell, signals the gNB-CU-CP with an indication that the PCI of the cell was updated. If the new PCI was provided by the gNB-CU-CP, the gNB-DU may only signal an indication that the PCI was changed successfully. If the new PCI was selected by the gNB-DU, the signaling may include the new PCI selected or allocated by the gNB-DU. After reception of the confirmation from the gNB-DU, the gNB-CU-CP can update the cell information stored for each connected gNB-DU with the new assigned PCI for the specific cell.
  • the gNB-CU-CP may signal neighbour RAN nodes with an indication that a change of PCI has occurred for the specific cell, so that neighbour RAN nodes can update their neighbour cell information and correctly perform mobility towards the cell with the new PCI.
  • the gNB-CU-CP and gNB-DU may also signal the updated PCI configuration to the OAM system.
  • the request for change of PCI may be received in the gNB-CU-CP from another network node, e.g. another gNB-CU-CP, another gNB-DU, an eNB, a radio network controller (RNC), a base station controller (BSC), another control node or from the OAM system.
  • the request can be received over an Xn, X2, NG, S1, F1 or other interface.
  • the request may include a suggested new PCI or a set of possible PCIs to select from. After receiving the request the method proceeds as in the first embodiment when the change is initiated by the gNB-CU-CP.
  • the request for change of PCI is received in the gNB-DU from another network node, e.g another gNB-CU-CP, another gNB-DU, an eNB, an RNC, a BSC, another control node or from the OAM system.
  • the request can be received over an F1 or other interface.
  • the method may proceed as in other embodiments when the request for change has been received in the gNB-DU.
  • a method of updating a parameter of a cell associated with a base station distributed unit, DU comprises sending an instruction to the DU to cause the DU to update the parameter, and receiving a notification from the DU that the update of the parameter has been performed.
  • a method of updating a parameter of a cell associated with a base station distributed unit, DU comprises sending an instruction to the DU to cause the DU to update the parameter, and determining that the update of the parameter has been performed if a notification that the update of the parameter has not been performed is not received from the DU in a predetermined time period.
  • a method of updating a parameter of a cell associated with a base station distributed unit, DU comprises receiving an instruction to update the parameter, performing the update of the parameter, and sending a notification that the update of the parameter has been performed.
  • a method of updating a parameter of a cell associated with a base station distributed unit, DU comprises receiving a request to update the parameter, and sending a notification that the update of the parameter has not been performed if the update of the parameter is not performed within a predetermined time period.
  • a distributed unit e.g. gNB-DU may perform reconfiguration of new assigned PCI in a favorable time with minimum impairment on the quality of experience of the camped/connected UEs.
  • methods may provide a full- awareness of the cell configuration (e.g., assigned PCI) of the cells belonging to the DUs controlled by a given central unit e.g. gNB-CU, improving the interoperating between gNB-DUs and gNB-CU-CP over F1 interface.
  • Figure 5 is a flow chart of an example of a method 500 in a base station central unit, CU, of updating a parameter of a cell associated with a base station distributed unit, DU.
  • the method 500 comprises, in step 502, sending an instruction to the DU to cause the DU to update the parameter.
  • the method 500 also comprises, in step 504, receiving a notification from the DU that the update of the parameter has been performed.
  • the method 500 comprises updating information stored for the cell based on the updated parameter after receiving the notification. Additionally or alternatively, method 500 comprises receiving an acknowledgement from the DU after sending the instruction to the DU.
  • method 500 comprises sending an acknowledgement to the DU after receiving the notification. Additionally or alternatively, method 500 comprises sending an updated parameter to the DU to cause the DU to update the parameter to the updated parameter. The method 500 may then comprise sending the updated parameter to the DU in the instruction.
  • the method 500 in some examples may comprise sending a plurality of parameters to the DU to cause the DU to update the parameter to one of the plurality of parameters.
  • the method 500 may comprise sending the plurality of parameters to the DU in the instruction.
  • method 500 comprises sending an indication to a core network that the parameter has been updated after receiving the notification.
  • the indication to the core network identifies the updated parameter.
  • the method 500 may in some examples comprise sending an indication to one or more neighbour network nodes that the parameter has been updated after receiving the notification.
  • the indication to the one or more neighbour network nodes may identify the updated parameter.
  • the one or more neighbour network nodes may comprise one or more neighbour base stations, base station distributed units, DUs, base station central units, CUs, eNB- CUs, eNB-CU-CPs, eNB-DUs, gNB-CUs, gNB-CU-CPs and/or gNB-DUs.
  • Sone examples of the method 500 may include receiving an indication of the updated parameter from the DU.
  • the method 500 may comprise receiving the indication of the updated parameter from the DU in the notification.
  • the method 500 may in some examples comprise determining a conflict between the parameter of the cell and the parameter of another cell before sending the instruction to the DU.
  • determining the conflict may comprise receiving an indication of the conflict from the DU.
  • the DU may comprise for example an eNB-DU or gNB-DU.
  • the method is performed in some examples by an eNB-CU, eNB-CU-CP, gNB-CU or gNB-CU-CP.
  • the method 500 may in some examples comprise, before sending the instruction to the DU, receiving an instruction from a network node to cause the DU to update the parameter.
  • the network node may comprise for example a base station central unit, CU, base station distributed unit, DU, eNB-CU, eNB-CU-CP, eNB-DU, gNB-CU, gNB-CU-CP, gNB-DU, radio network controller, base station controller or Operations, Administration and Maintenance (OAM) node.
  • the instruction from the network node indicates the updated parameter for the cell or a plurality of parameters for the cell.
  • the parameter of the cell may comprise for example a physical cell identifier, PCI, or random access configuration of the cell.
  • the cell associated with the DU comprises a cell served by the DU.
  • Figure 6 is a flow chart of an example of a method of updating a parameter of a cell associated with a base station distributed unit, DU.
  • the method 600 comprises, in step 602, receiving an instruction (e.g. from a base station CU) to update the parameter.
  • the method 600 also comprises, in step 604, performing the update of the parameter and, in step 606, sending a notification (e.g. to the base station CU) that the update of the parameter has been performed.
  • the method 600 comprises performing the update of the parameter at a time based on a status of the cell and/or one or more User Equipments, UEs, connected to the cell.
  • the status of the cell and/or the one or more UEs comprises a cell load status and/or a time window associated with random access resources or conditional handover.
  • the method 600 comprises sending an acknowledgement after receiving the instruction. Additionally or alternatively, the method 600 comprises receiving an acknowledgement after sending the notification.
  • the method 600 may in some examples comprise receiving the instruction from a network node.
  • the network node may comprise for example a base station central unit, CU, base station distributed unit, DU, eNB-CU, eNB-CU-CP, eNB-DU, gNB-CU, gNB-CU-CP, gNB-DU, radio network controller, base station controller or Operations, Administration and Maintenance (OAM) node.
  • the network node may comprise for example a CU, eNB-CU, eNB-CU-CP, gNB-CU or gNB-CU- CP associated with a node performing the method.
  • the method 600 may in some examples comprise sending the notification to the network node.
  • the method 600 may comprise for example receiving an updated parameter, and performing the update of the parameter comprises updating the parameter to the updated parameter (e.g. the parameter is updated to an updated value).
  • the method 600 may comprise receiving the updated parameter in the instruction.
  • the method 600 comprises receiving a plurality of parameters, and wherein performing the update of the parameter comprises updating the parameter to one of the plurality of parameters.
  • the method 600 may comprise receiving the plurality of parameters in the instruction.
  • the method 600 in some examples may comprise sending an indication to a core network that the parameter has been updated after performing the update.
  • the indication to the core network may identify the updated parameter.
  • the method 600 may comprise sending an indication to one or more neighbour network nodes that the parameter has been updated after performing the update.
  • the indication to the one or more neighbour network nodes may identify the updated parameter.
  • the one or more neighbour network nodes may comprise one or more neighbour base stations, base station distributed units, DUs, base station central units, CUs, eNB-CUs, eNB-CU-CPs, eNB-DUs, gNB-CUs, gNB-CU-CPs and/or gNB-DUs.
  • the method 600 in some examples comprises sending an indication of the updated parameter in the notification.
  • the method 600 comprises, before receiving the instruction, determining a conflict between the parameter of the cell and the parameter of another cell and sending an indication of the conflict to a central unit, CU, associated with the cell.
  • the method is performed in some examples by a distributed unit, DU, eNB-DU or gNB-DU.
  • the parameter of the cell may comprise for example a physical cell identifier, PCI or random access configuration of the cell.
  • the cell associated with the DU may comprise for example a cell served by the DU.
  • Methods described herein may apply to all RAN architectures that follow a split similar to that of the NG RAN and the E-UTRAN architecture. Without loss of generality, the description takes as an example the NG-RAN system and describes the methods with respect to a split gNB architecture. However, these methods are also valid for other similar systems such as for example the split eNB node in E-UTRAN.
  • At least some examples disclosed herein may comprise actions for two RAN entities (e.g., gNB-DU and gNB-CU- CP in DU/CU split architecture in NR terminology) wherein one node performs a first configuration of cell parameters (e.g., Physical Cell ID, PCI).
  • the other node e.g. gNB-CU-CP
  • a three-way split architecture for a RAN is considered, where for example (in the case of NR) the gNB-CU is further split into gNB-CU-CP and gNB-CU-UP.
  • a two-way split architecture is also possible, where the gNB-CU remains a single node.
  • Embodiments herein may be applied to both of these as well as other architectures, and what is herein referred to as the gNB-CU-CP would have to be replaced by the gNB-CU (or, as suggested above, a more general distributed unit, CU).
  • the following steps may be performed:
  • Step 1 gNB-CU-CP may either select/assign a new PCI for one or a subset of the cells, or signal to the gNB- DU the required actions to be taken for selecting/assigning a new PCI (or simply signal that a new PCI is needed).
  • Step 2 gNB-DU may consider some quality of service parameters (cell load and number of camped UEs if available) to find a suitable time for applying reconfiguration changes.
  • Step 3 gNB-CU-CP may assume the new configuration of the cell is applied (new PCI) only if gNB-DU acknowledges that the reconfiguration of cell (e.g., with new PCI) is done.
  • Figure 7 shows an example of communications between a gNB-CU-CP and gNB-DU in a method of updating a parameter of a cell associated with a base station distributed unit, DU (in this example, the gNB-DU).
  • Step 3 gNB-CU-CP may assume the new configuration (e.g., new PCI) of the cell is applied after a certain period of time (predetermined time) T, o Time T may be defined as absolute or relative time. o In case the gNB-DU is not able to apply the change after the signaled time T, gNB-DU should notify gNB-CU-CP of the fact that the change could not be applied.
  • the following steps may be performed:
  • gNB-DU may decide either to reconfigure the cell (e.g., with a new PCI), or it can postpone the reconfiguration of the new cell to a proper time. Decision on the proper time to apply the new PCI can be taken based on the load status or any other parameter concerning the quality of service requirement of the camped UEs. If gNB- DU postpones the reconfiguration of PCI, it may signal to the gNB-CU-CP that the reconfiguration of the cell with the new PCI is not applied and postponed. o gNB-DU may use a timer T to determine a certain time to apply the new configuration. o The gNB-DU may signal the timer to the gNB-CU-CP. o gNB-DU (in the context of LTE and NR) may use any signaling from DU to CU over F1 interface including but not limited to gNB-DU Configuration Update or gNB-CU-CP Configuration Update Acknowledge.
  • gNB-DU applied the reconfiguration of PCI
  • it may signal to the gNB-CU-CP the reconfiguration of the cell with the new PCI applied.
  • the gNB-CU-CP may signal to the gNB-DU that a change of PCI for a given cell is needed (as well as the new PCI to assign to the cell in some examples, or list of possible PCIs in some examples), and the gNB-CU-CP may signal a time T (or the time T is a predetermined or default time, which may not need to be signaled) after which the gNB- CU may assume that the change is applied. If the gNB-CU-CP does not receive an explicit acknowledgement from the gNB- DU that the change of PCI has occurred (e.g.
  • the gNB-CU will assume that the change of PCI has been performed by the gNB-DU.
  • the opposite behavior by the gNB-CU is also possible, namely that if the gNB-CU-CP does not receive an explicit acknowledgement from the gNB-DU about the actuated change of PCI (e.g. via gNB-DU configuration Update signaling over F1), the gNB-CU will assume that the change of PCI has not been performed by the gNB-DU.
  • the need for a change of PCI in a specific cell may be detected by another network node, e.g. another gNB-CU-CP, another gNB-DU, an eNB, an RNC, a BSC, another control node or an OAM system and signalled to the gNB-CU-CP.
  • another network node e.g. another gNB-CU-CP, another gNB-DU, an eNB, an RNC, a BSC, another control node or an OAM system and signalled to the gNB-CU-CP.
  • the gNB-CU-CP receives an indication from the other network node or OAM system.
  • the indication may either provide a new PCI for the specific cell or a set of PCIs to choose from for the specific cell or it may let the gNB-CU-CP or gNB-DU select a new PCI.
  • the embodiment from this point on may be similar to other examples, e.g. where the gNB-CU-CP signals the need for change to the gNB-DU.
  • the need for a change of PCI in a specific cell may be detected by another network node, e.g. another gNB-CU-CP, another gNB-DU, an eNB, an RNC, a BSC, another control node or an OAM system and signalled to the gNB-DU.
  • another network node e.g. another gNB-CU-CP, another gNB-DU, an eNB, an RNC, a BSC, another control node or an OAM system and signalled to the gNB-DU.
  • the gNB-DU receives an indication from the other network node or OAM system, similar to that described above from the gNB-CU-CP, indicating that a change of PCI is needed.
  • the indication from the OAM may either provide a new PCI for the specific cell or a set of PCIs to select from, or it may let the gNB-DU select a new PCI.
  • the embodiment from this point on may be similar to other examples, e.g. when the gNB-DU has received the request to change PCI.
  • the need to reconfigure the cell configuration at gNB-DU may be generalized to any parameter including those in the system information (e.g., SIB in the context of LTE and NR).
  • the gNB-DU may be required to apply changes to other cell parameters such as the random access configuration.
  • Random Access Resources may need to remain unchanged for a certain time window due to, e.g. the fact they are reserved for conditional handover purposes.
  • changing random access resources e.g., rootSequence Index
  • gNB-DU may postpone the reconfiguration of new RACH resources, or of any other cell parameters it is signaled to change, to the time that all RACH resources are released.
  • gNB-DU may decide to delay and signal the gNB-CU when reconfiguration is applied.
  • base station central unit CU
  • eNB-CU eNB-CU
  • eNB-CU-CP gNB-CU
  • gNB-CU-CP base station distributed unit
  • base station distributed unit DU, eNB-DU and gNB-DU are used interchangeably.
  • a wireless network such as the example wireless network illustrated in Figure 8.
  • the wireless network of Figure 8 only depicts network QQ106, network nodes QQ160 and QQ160b, and WDs QQ110, QQ110b, and QQ110c.
  • 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.
  • network node QQ160 and wireless device (WD) QQ110 are depicted with additional detail.
  • 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 procedures.
  • particular embodiments of the 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 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 and/or ZigBee standards.
  • Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node QQ160 and WD QQ110 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 connections in a wireless network.
  • 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 access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • 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 remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • 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 base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • 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.
  • network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162.
  • network node QQ160 illustrated in the example wireless network of Figure 8 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.
  • network node QQ160 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node QQ160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node QQ160 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 NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node QQ160 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ160.
  • Processing circuitry QQ170 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 processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 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 processing circuitry QQ170 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 circuitry QQ170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, 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 network node QQ160 components, such as device readable medium QQ180, network node QQ160 functionality.
  • processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry QQ170 may include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174.
  • radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units
  • processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170.
  • some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium QQ180 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, random access memory (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 processing circuitry GO170.
  • volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (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
  • Device readable medium GO180 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 processing circuitry QQ170 and, utilized by network node QQ160.
  • Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190.
  • processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.
  • Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162.
  • antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192.
  • the digital data may be passed to processing circuitry QQ170.
  • the interface may comprise different components and/or different combinations of components.
  • network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190.
  • interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).
  • Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GFIz and 66 GFIz.
  • 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.
  • the use of more than one antenna may be referred to as MIMO.
  • antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.
  • Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 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 wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 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 wireless device, another network node and/or any other network equipment.
  • Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160.
  • network node QQ160 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 power circuitry QQ187.
  • power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. 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.
  • network node QQ160 may include additional components beyond those shown in Figure 8 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.
  • network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term WD may be used interchangeably herein with user equipment (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 predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD 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 cameras, 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, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle-mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • PDA personal digital assistant
  • a wireless cameras 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, a laptop-embedded equipment (LEE), a laptop-mounted equipment (L
  • 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 monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard.
  • NB-loT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) 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. Furthermore, 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.
  • wireless device QQ110 includes antenna QQ111, interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137.
  • WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, 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 WD QQ110.
  • Antenna QQ111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114.
  • antenna QQ111 may be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port.
  • Antenna QQ111, interface QQ114, and/or processing circuitry QQ120 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 antenna QQ111 may be considered an interface.
  • interface QQ114 comprises radio front end circuitry QQ112 and antenna QQ111.
  • Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116.
  • Radio front end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111 and processing circuitry QQ120.
  • Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ111.
  • WD QQ110 may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ111.
  • Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ118 and/or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120.
  • the interface may comprise different components and/or different combinations of components.
  • Processing circuitry QQ120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, 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 QQ110 components, such as device readable medium QQ130, WD QQ110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein.
  • processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.
  • processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry QQ120 of WD QQ110 may comprise a SOC.
  • RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips.
  • RF transceiver circuitry QQ122 may be a part of interface QQ114.
  • RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.
  • processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer-readable storage medium.
  • some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry QQ120 can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry QQ120 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 processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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 processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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.
  • Device readable medium QQ130 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 processing circuitry QQ120.
  • Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., 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 processing circuitry QQ120.
  • processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated.
  • User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 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).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ 132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110.
  • User interface equipment QQ132 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 user interface equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment QQ134 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 auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.
  • Power source QQ136 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.
  • WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any functionality described or indicated herein.
  • Power circuitry QQ137 may in certain embodiments comprise power management circuitry.
  • Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 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.
  • Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.
  • Figure 9 illustrates one embodiment of a UE (or terminal device) 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).
  • UE QQ200 may be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE QQ200 is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • the term WD and UE may be used interchangeable. Accordingly, although Figure 9 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231 , power source QQ233, and/or any other component, or any combination thereof.
  • Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in Figure 9, 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.
  • processing circuitry QQ201 may be configured to process computer instructions and data.
  • Processing circuitry QQ201 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.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry QQ201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE QQ200 may be configured to use an output device via input/output interface QQ205.
  • 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 UE QQ200.
  • 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.
  • UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200.
  • 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.
  • RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a.
  • Network QQ243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network QQ243a may comprise a Wi-Fi network.
  • Network connection interface QQ211 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, TCP/IP, SONET, ATM, or the like.
  • Network connection interface QQ211 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.
  • RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 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.
  • ROM QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201.
  • ROM QQ219 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 nonvolatile memory.
  • Storage medium QQ221 may be configured to include memory such as RAM, ROM, programmable readonly memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and datafile QQ227.
  • Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/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 external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • smartcard memory such as a subscriber identity module or a
  • Storage medium QQ221 may allow UE QQ200 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 storage medium QQ221, which may comprise a device readable medium.
  • processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231.
  • Network QQ243a and network QQ243b may be the same network or networks or different network or networks.
  • Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b.
  • communication subsystem QQ231 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 radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem QQ231 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.
  • communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.
  • communication subsystem QQ231 may be configured to include any of the components described herein.
  • processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231.
  • 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 10 is a schematic block diagram illustrating a virtualization environment QQ300 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 wireless device 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 wireless device 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 QQ300 hosted by one or more of hardware nodes QQ330. 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 functions may be implemented by one or more applications QQ320 (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.
  • Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390.
  • Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment QQ300 comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360.
  • Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360.
  • Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines QQ340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.
  • processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM).
  • Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.
  • hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.
  • CPE customer premise equipment
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines QQ340, and that part of hardware QQ330 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225.
  • Radio units QQ3200 may communicate directly with hardware nodes QQ330 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.
  • a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411, such as a radio access network, and core network QQ414.
  • Access network QQ411 comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c.
  • Each base station QQ412a, QQ412b, QQ412c is connectable to core network QQ414 over a wired or wireless connection QQ415.
  • a first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c.
  • a second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491, QQ492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412.
  • Telecommunication network QQ410 is itself connected to host computer QQ430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer QQ430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network QQ420.
  • Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 11 as a whole enables connectivity between the connected UEs QQ491, QQ492 and host computer QQ430.
  • the connectivity may be described as an over-the-top (OTT) connection QQ450.
  • Host computer QQ430 and the connected UEs QQ491, QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ411, core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications.
  • base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491.
  • base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491 towards the host computer QQ430.
  • host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500.
  • Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities.
  • processing circuitry QQ518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer QQ510 further comprises software QQ511, which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518.
  • Software QQ511 includes host application QQ512.
  • Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.
  • Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530.
  • Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in Figure 12) served by base station QQ520.
  • Communication interface QQ526 may be configured to facilitate connection GO560 to host computer QQ510.
  • Connection qq560 may be direct or it may pass through a core network (not shown in Figure 12) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station QQ520 further has software QQ521 stored internally or accessible via an external connection.
  • Communication system QQ500 further includes UE QQ530 already referred to. Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE QQ530 further comprises software QQ531 , which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532.
  • Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510.
  • an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510.
  • client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data.
  • OTT connection QQ550 may transfer both the request data and the user data.
  • Client application QQ532 may interact with the user to generate the user data that it provides.
  • host computer QQ510, base station QQ520 and UE QQ530 illustrated in Figure 12 may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412c and one of UEs QQ491, QQ492 of Figure 11, respectively.
  • the inner workings of these entities may be as shown in Figure 12 and independently, the surrounding network topology may be that of Figure 11.
  • OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection QQ570 between UE QQ530 and base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection QQ550 may be implemented in software QQ511 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both.
  • sensors may be deployed in or in association with communication devices through which OTT connection QQ550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software QQ511 , QQ531 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection QQ550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer QQ510’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software QQ511 and QQ531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.
  • FIG. 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section.
  • the host computer provides user data.
  • substep QQ611 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application.
  • step QQ620 the host computer initiates a transmission carrying the user data to the UE.
  • step QQ630 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step QQ640 the UE executes a client application associated with the host application executed by the host computer.
  • FIG 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step QQ730 (which may be optional), the UE receives the user data carried in the transmission.
  • FIG. 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section.
  • step QQ810 (which may be optional) the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data.
  • substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application.
  • substep QQ811 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step QQ930 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • Figure 17 illustrates a schematic block diagram of an apparatus WWOO in a wireless network (for example, the wireless network shown in Figure 8).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device QQ110 or network node QQ160 shown in Figure 8).
  • Apparatus WWOO is operable to carry out the example method described with reference to Figure 500 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 500 is not necessarily carried out solely by apparatus WWOO. At least some operations of the method can be performed by one or more other entities.
  • Apparatus may be for example apparatus in a base station central unit, CU, of updating a parameter of a cell associated with a base station distributed unit, DU.
  • Virtual Apparatus WWOO may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (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 read-only memory (ROM), random-access memory, 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, in several embodiments.
  • apparatus WWOO includes Sending Unit WW02 configured to send an instruction to the DU to cause the DU to update the parameter, and Receiving Unit WW04 configured to receive a notification from the DU that the update of the parameter has been performed.
  • Figure 18 illustrates a schematic block diagram of an apparatus WW10 in a wireless network (for example, the wireless network shown in Figure 8).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device QQ110 or network node QQ160 shown in Figure 8).
  • Apparatus WW10 is operable to carry out the example method described with reference to Figure 600 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 600 is not necessarily carried out solely by apparatus WW10. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus WW10 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (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 read-only memory (ROM), random-access memory, 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, in several embodiments.
  • the processing circuitry may be used to cause Receiving Unit WW12, Performing Unit WW14, Sending Unit WW16 and any other suitable units of apparatus WW10 to perform corresponding functions according one or more embodiments of the present disclosure.
  • apparatus WW10 includes Receiving Unit WW12 configured to receive an instruction to update the parameter, Performing Unit WW14 configured to perform the update of the parameter, and Sending Unit WW16 configured to send a notification that the update of the parameter has been performed.
  • 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.
  • a method of updating a parameter of a cell associated with a base station distributed unit, DU comprising: sending an instruction to the DU to cause the DU to update the parameter; and receiving a notification from the DU that the update of the parameter has been performed.
  • the one or more neighbour network nodes comprise one or more neighbour base stations, base station distributed units, DUs, base station central units, CUs, eNB-CUs, eNB-CU- CPs, eNB-DUs, gNB-CUs, gNB-CU-CPs and/or gNB-DUs.
  • determining the conflict comprises receiving an indication of the conflict from the DU.
  • the network node comprises a base station central unit, CU, base station distributed unit, DU, eNB-CU, eNB-CU-CP, eNB-DU, gNB-CU, gNB-CU-CP, gNB-DU, radio network controller, base station controller or Operations, Administration and Maintenance (OAM) node.
  • the network node comprises a base station central unit, CU, base station distributed unit, DU, eNB-CU, eNB-CU-CP, eNB-DU, gNB-CU, gNB-CU-CP, gNB-DU, radio network controller, base station controller or Operations, Administration and Maintenance (OAM) node.
  • OAM Operations, Administration and Maintenance
  • a method of updating a parameter of a cell associated with a base station distributed unit, DU comprising: sending an instruction to the DU to cause the DU to update the parameter; and determining that the update of the parameter has been performed if a notification that the update of the parameter has not been performed is not received from the DU in a predetermined time period.
  • the one or more neighbour network nodes comprise one or more neighbour base stations, base station distributed units, DUs, base station central units, CUs, eNB-CUs, eNB-CU- CPs, eNB-DUs, gNB-CUs, gNB-CU-CPs and/or gNB-DUs.
  • determining the conflict comprises receiving an indication of the conflict from the DU.
  • the network node comprises a base station central unit, CU, base station distributed unit, DU, eNB-CU, eNB-CU-CP, eNB-DU, gNB-CU, gNB-CU-CP, gNB-DU, radio network controller, base station controller or Operations, Administration and Maintenance (OAM) node.
  • DU base station central unit
  • eNB-CU base station distributed unit
  • eNB-CU-CP eNB-DU
  • gNB-CU gNB-CU-CP
  • gNB-DU radio network controller
  • base station controller or Operations, Administration and Maintenance (OAM) node.
  • OFAM Operations, Administration and Maintenance
  • a method of updating a parameter of a cell associated with a base station distributed unit, DU comprising: receiving an instruction to update the parameter; performing the update of the parameter; and sending a notification that the update of the parameter has been performed.
  • the method of embodiment 50 comprising performing the update of the parameter at a time based on a status of the cell and/or one or more User Equipments, UEs, connected to the cell.
  • the network node comprises a base station central unit, CU, base station distributed unit, DU, eNB-CU, eNB-CU-CP, eNB-DU, gNB-CU, gNB-CU-CP, gNB-DU, radio network controller, base station controller or Operations, Administration and Maintenance (OAM) node.
  • the network node comprises a base station central unit, CU, base station distributed unit, DU, eNB-CU, eNB-CU-CP, eNB-DU, gNB-CU, gNB-CU-CP, gNB-DU, radio network controller, base station controller or Operations, Administration and Maintenance (OAM) node.
  • OAM Operations, Administration and Maintenance
  • the network node comprises a CU, eNB-CU, eNB-CU-CP, gNB-CU or gNB-CU-CP associated with a node performing the method.
  • the method of embodiment 61 comprising receiving the plurality of parameters in the instruction.
  • the method of any of embodiments 50 to 62 comprising sending an indication to a core network that the parameter has been updated after performing the update.
  • the method of embodiment 63 wherein the indication to the core network identifies the updated parameter.
  • the method of any of embodiments 50 to 64 comprising sending an indication to one or more neighbour network nodes that the parameter has been updated after performing the update.
  • the method of embodiment 65 wherein the indication to the one or more neighbour network nodes identifies the updated parameter.
  • the one or more neighbour network nodes comprise one or more neighbour base stations, base station distributed units, DUs, base station central units, CUs, eNB-CUs, eNB-CU- CPs, eNB-DUs, gNB-CUs, gNB-CU-CPs and/or gNB-DUs.
  • the method of any of embodiments 50 to 67 comprising sending an indication of the updated parameter in the notification.
  • the method of any of embodiments 50 to 68 comprising, before receiving the instruction, determining a conflict between the parameter of the cell and the parameter of another cell and sending an indication of the conflict to a central unit, CU, associated with the cell.
  • the one or more neighbour network nodes comprise one or more neighbour base stations, base station distributed units, DUs, base station central units, CUs, eNB-CUs, eNB-CU- CPs, eNB-DUs, gNB-CUs, gNB-CU-CPs and/or gNB-DUs.
  • the network node comprises a base station central unit, CU, base station distributed unit, DU, eNB-CU, eNB-CU-CP, eNB-DU, gNB-CU, gNB-CU-CP, gNB-DU, radio network controller, base station controller or Operations, Administration and Maintenance (OAM) node.
  • DU base station central unit
  • eNB-CU base station distributed unit
  • eNB-CU-CP eNB-DU
  • gNB-CU gNB-CU-CP
  • gNB-DU radio network controller
  • base station controller or Operations, Administration and Maintenance (OAM) node.
  • OFAM Operations, Administration and Maintenance
  • the network node comprises a CU, eNB-CU, eNB-CU-CP, gNB-CU or gNB-CU-CP associated with a node performing the method.
  • - power supply circuitry configured to supply power to the base station.
  • a communication system including a host computer comprising:
  • UE user equipment
  • the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the previous embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • the host computer initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments. 103.
  • the method of the previous embodiment further comprising, at the base station, transmitting the user data.
  • a user equipment configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • UE user equipment
  • the communication system of the previous embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH enhanced Physical Downlink Control Channel
  • GERAN GSM EDGE Radio Access Network gNB Base station in NR GNSS Global Navigation Satellite System

Landscapes

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

Abstract

Dans un exemple, un procédé selon la présente invention, réalisé dans une unité centrale, CU, d'une station de base, consiste à mettre à jour un paramètre d'une cellule associée à une unité distribuée, DU, de la station de base. Le procédé comprend l'envoi d'une instruction à la DU pour amener la DU à mettre à jour le paramètre, et la réception, depuis la DU, d'une notification qui indique que la mise à jour du paramètre a été effectuée.
EP20761650.9A 2019-08-16 2020-08-14 Mise à jour d'une pci dans une architecture divisée du-cu Withdrawn EP4014532A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962887763P 2019-08-16 2019-08-16
PCT/SE2020/050787 WO2021034254A1 (fr) 2019-08-16 2020-08-14 Mise à jour d'une pci dans une architecture divisée du-cu

Publications (1)

Publication Number Publication Date
EP4014532A1 true EP4014532A1 (fr) 2022-06-22

Family

ID=72240465

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20761650.9A Withdrawn EP4014532A1 (fr) 2019-08-16 2020-08-14 Mise à jour d'une pci dans une architecture divisée du-cu

Country Status (2)

Country Link
EP (1) EP4014532A1 (fr)
WO (1) WO2021034254A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111432415B (zh) * 2019-01-09 2022-05-17 华为技术有限公司 通信方法和装置
JP2023536912A (ja) * 2020-08-06 2023-08-30 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 無線アクセスネットワークノードに対する設定変更の要求
WO2022234540A1 (fr) * 2021-05-06 2022-11-10 Telefonaktiebolaget Lm Ericsson (Publ) Impacts d'interface et d'architecture de mobilité centrée l1/l2
CN114513803B (zh) * 2022-02-25 2024-03-22 成都中科微信息技术研究院有限公司 一种提升基站cu和du之间小区管理状态一致性的方法及系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107360557B (zh) * 2017-06-15 2020-03-24 电信科学技术研究院 一种系统消息通知、发送方法及装置
US12041528B2 (en) * 2018-01-11 2024-07-16 Comcast Cable Communications, Llc Connection failure reporting

Also Published As

Publication number Publication date
WO2021034254A1 (fr) 2021-02-25

Similar Documents

Publication Publication Date Title
US11838810B2 (en) Report NSA/SA NR indicator
US11265801B2 (en) Information exchange for initial user equipment access
EP3808129B1 (fr) Détermination de périodicité de ssb/rmsi pour noeud iab
EP3791621B1 (fr) Temporisateur de rapport de mesure
EP3791682B1 (fr) Sélection d'id de cellule dans des scénarios à multiples id de cellule
WO2021034254A1 (fr) Mise à jour d'une pci dans une architecture divisée du-cu
WO2021044375A1 (fr) Signalisation de capacité à connectivité multiple pour nœuds multiservices
US20230199521A1 (en) Management of frequency bands selection and measurement configurations
US20210044999A1 (en) Minimization of Driving Test Measurements
US20230199481A1 (en) Request to Store Information for a Plurality of Cells
WO2019215707A1 (fr) Message d'accès aléatoire segmenté
EP3928574B1 (fr) Orientation de stratégie de planification de plan utilisateur d'un ran
US12047909B2 (en) Methods and apparatus for controlling a mode of operation of a wireless device
US20220015038A1 (en) Mobile Terminated Early Data Transmission Reachability for RAN Context
EP4039053B1 (fr) Aspects de signalisation de groupe pour une connectivité double nr-nr (nr-dc) et une reconfiguration
US11882457B2 (en) Baseband processing capability handling in split deployment
WO2022214844A1 (fr) Changement de nœud maître en nœud b évolué (enb) avec transfert direct de nœud sn

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20220207

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20230612

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20231024