Patent Description:
3GPP allows two general architecture for <NUM> NR operation, namely Non-StandAlone (NSA) and StandAlone (SA). In NSA architecture, <NUM> is introduced as an overlay on top of <NUM> and utilizes connectivity towards the LTE core network using an LTE eNB as Master Node, while in the SA architecture the <NUM> core network is used and no assistance from an LTE Master Node is needed. NSA and SA are two cases of Multi-Radio Dual Connectivity (MR-DC). MR-DC is a generalization of Intra-E-UTRA Dual Connectivity (DC), where a multiple Rx/Tx capable UE may be configured to utilise resources provided by two different nodes connected via non-ideal backhaul, one providing NR access and the other one providing either E-UTRA access (NSA case) or NR access (SA case). One node acts as the MN and the other as the SN. The MN and SN are connected via a network interface and at least the MN is connected to the core network. In MR-DC, the MN is a radio access node providing the control plane connection to the core network. The SN does not have any control plane connection to the core network, but provides additional resources to the UE. Each of the MN and the SN may be a eNB (<NUM> radio access node) or a gNB (<NUM> radio access node).

<FIG> shows the EN-DC overall architecture (taken from 3GPP TS <NUM>) which corresponds to the NSA case. The eNBs act as MN having both a control plane and a user plane connection to the EPC (represented by MME/S-GW), while the gNBs act as SN having only a user plane connection to the EPC but not a control plane connection.

On the other hand, <FIG> shows a NG-RAN architecture (taken from 3GPP TS <NUM>) corresponding to the SA case. The EPC is replaced by 5GC, represented by AMF/UPF. Each of the gNBs and eNBs has a control and user plane connection to the 5GC.

A <NUM> cell at a gNB may be configured and operate in both NSA mode and SA mode simultaneously. That is, it may serve both as an NSA and a SA cell simultaneously.

A gNB may be split into a CU and one or more DUs. The interface between these two entities is called F1 (see <FIG>). In the DU, the lower layers of the protocol stack (e.g. PHY, MAC, RLC) are implemented, while in the CU, the upper layers of the protocol stack (e.g. PDCP) are implemented. The split may be implemented between other layers than between RLC and PDCP. As shown in <FIG>, the CU may be split again into a control part CU-CP and one or more user parts CU-UP. The control part CU-CP is connected to each of the user parts CU-UP by E1 interface. Each DU is connected to the CU-CP and to each of the CU-UPs. The DU owns the cell configuration.

A <NUM> cell can operate in one of the following modes:.

<NUM> cell configuration takes place at the DU node and is expected to be preconfigured via O&M prior to cell activation. This includes all the required System Information parameters, Access Control, Tracking Areas, PLMNs, etc. Within these parameters, it can be indicated whether the.

<NUM> cell is an NSA, SA, or SA+NSA cell. Likewise, the DU is in charge of informing the CU whenever a <NUM> cell is ready to be activated.

A gNB-CU may request cell deactivation from gNB-DU. In detail, the actions taken at gNB-DU on receiving a cell deactivation request from gNB-CU are.

The actions taken at gNB-CU on receiving a cell deactivation confirmation from gNB-DU are.

With respect to configuration and activation of cells, the work split between CU and DU is as follows:.

In detail, all of the cell configuration for lower protocol layers is dictated via preconfigured parameters via O&M in the DU. That is, the DU is in charge of indicating whether a cell is configured or not.

<CIT> discloses a method of providing two cell barring indications via system information for UE cell selection or reselection is proposed. A first indication is a "cellBarred" indication for EPC, which indicates wither UE is barred to access EPC core network, and a second indication is a "cellBarred5GS" indication for 5GC, which indicates whether UE is barred to access 5GC core network. For E-UTRAN cell connected to both EPC and 5GC, the two indications are determined on demand, based on network preference and congestion control. For E-UTRAN cell connected to 5GC only, the value of the "cellBarred" indication is always barred. For E-UTRAN cell connected to EPC only, the base station may omit the "cellBarred5GS" field, and the existence of "cellBarred5GS" can act as an indication whether the E-UTRAN connects to 5GC.

<NPL> discloses proposals relating to Cell Barred Info exchange over F1 as known in the art.

It is an object of the present invention to improve the prior art. Optional features are given in the dependent claims.

Further details, features, objects, and advantages are apparent from the following detailed description of the preferred embodiments of the present invention which is to be taken in conjunction with the appended drawings, wherein:.

Herein below, certain embodiments of the present invention are described in detail with reference to the accompanying drawings, wherein the features of the embodiments can be freely combined with each other unless otherwise described. However, it is to be expressly understood that the description of certain embodiments is given by way of example only, and that it is by no way intended to be understood as limiting the invention to the disclosed details.

In the procedures for cell handling specified in the existing 3GPP specifications, there is no explicit distinction on whether a cell is NSA, SA, or both NSA+SA. This incurs problems in some scenarios, e.g., when there is an issue encountered towards only one of the core networks (e.g., a <NUM> core network issue, such as an AMF going for a re-start or becoming unreachable), leading to some downtime with SA service in the cell(s) served by the AMF. Thus, given that there are no separate procedures based on operation mode, changes to the cell (e.g., deactivation or reconfiguration) cannot be triggered for an individual operation mode (technology basis). That is, there are also no means for a CU to inform a DU (who owns the cell configuration) to carry out any changes (e.g.: Stop providing SA service temporarily in the cells) with respect to a specific mode of operation (i.e. applicable only to SA or NSA).

In other words, with the current framework, there are neither means for the CU to be involved in the <NUM> cell configuration nor any way for the CU to request DU to change the <NUM> cell configuration. As a consequence, if the CU encounters an issue involving only one of the technologies (e.g., connectivity to <NUM> core has problems) or would benefit from reducing the number of UEs of a particular mode in accessing the cell (e.g., for load balancing or congestion reasons), it is unable to indicate it, or request such change from the DU. Thus, any changes CU triggers (e.g., deactivation of a cell) will affect both modes (SA and NSA) of the cell and, naturally, impacts all kinds of UEs served by the cell. This is not a desired condition since the issue could be possibly associated to e.g. the <NUM> core (AMF) only and, thus, should impact UEs experiencing SA service only but not UEs experiencing NSA service.

Of course, a corresponding consideration may be made if there is a <NUM> only issue (e.g. connectivity to EPC lost, MME down etc.). As another option, the issue may be in the CU itself (a malfunctioning) affecting only one of the operation modes but not the other one.

The problem may be understood better with the help of the following example scenario:.

Some example embodiments of this invention introduce a signalling mechanism between CU and DU to resolve the aforementioned issues.

, some example embodiments of the invention provide a mechanism to enable the CU to notify the DU of an issue associated with (only) one of the modes of cell operation. For example, CU may request de-configuration of the particular mode of cell operation. In the above example scenario, one of the following actions may be performed:.

Each of these measures to reduce access to the affected operation modes may be permanent or temporary (i.e. a suspension). If the measure is temporary, the respective instruction to DU may comprise a timer. When the timer is elapsed, the DU re-instantiates the previous operation mode / barring status without involvement of the CU. If the measure is permanent, the previous operation mode / barring status may be re-instantiated by a corresponding instruction from the CU. In the time until the re-instantiation, the CU may attempt to remove the issue (or wait that the issue is removed).

This approach may be backwards compatible and may also keep whole final authority at DU in regard to configuration of <NUM> cell parameters, as in the existing framework. This is achieved because CU indicates and notify issues, so that the DU can change the configuration and report it via a subsequent message to the CU (e.g., once it has removed one of the modes of operation, such as changing the cell configuration from NSA+SA to SA only).

The CU may request/indicate the change in configuration based on different scenarios, such as:.

Once the GNB-CU CONFIGURATION UPDATE is supplemented with de-configuration of one of the modes in a SA+NSA cell, the actions taken at gNB-DU may be as follows (different to deactivation command received as in prior art):.

The actions taken at gNB-DU on receiving a cell reconfiguration request from gNB-CU are :.

The actions taken at gNB-CU on receiving a cell deactivation confirmation from gNB-DU may be:.

In contrast to the prior art, gNB-CU does not inform any eNB on the updated served cell information. This ensures NSA service continuity in the cell.

The actions taken at gNB-CU on receiving a cell deactivation confirmation from gNB-DU are :.

In contrast to the prior art, gNB-CU does not inform any gNB on the updated served cell information. This ensures SA service continuity in the cell.

Hereinafter, some example embodiments of the invention are described at greater detail.

Some options to implement some example embodiments of the invention are as follows:.

In case existing procedures are reused (e.g. according to Option <NUM>), only IE introduction is needed.

Similarly, the same procedure initiated from CU can be used to indicate that the issue has been resolved and let DU bring the earlier configuration back (e.g., connectivity to AMF was restored).

The proposed new procedure names and names of lEs stated below are just non-binding examples.

For Option <NUM>, a new procedure "Cell Modification Required" may be introduced. It may be described e.g. in 3GPP TS <NUM>, chapter <NUM>. The purpose of the Cell Modification Required is to request a modification in the cell configuration at gNB-DU. The procedure uses non UE-associated signalling. <FIG> shows a message flow of successful operation. The F1AP CELL MODIFICATION REQUIRED message is initiated by the gNB-CU indicating whether a change in cell configuration is required. <FIG> shows an example of an parameter definition of the new command.

The message may be a Class <NUM> message or a Class <NUM> message, although a class <NUM> message is preferred. In 3GPP terms, a Class <NUM> procedure is one in which there are both a request and a response following the request. The procedure is not considered to be complete without the response message (e.g., F1 SETUP REQUEST + F1 SETUP RESPONSE messages constitute a Class <NUM> procedure).

In contrast, a Class <NUM> procedure is determined by a single message and it may/or may not trigger additional actions at the receiver. According to some example embodiments using a class <NUM> procedure, the CU sends the "CELL MODIFICATION REQUIRED" message. Then it is up to the DU to trigger the changes. The DU may inform the CU on the changes by an additional procedure (e.g. DU CONFIGURATION UPDATE). This way, a minimum response time is not imposed on the DU to trigger the action (usually Class <NUM> procedures have an expiration time in which the requesting end expects the response to be received).

However, in some example embodiments, a Class <NUM> procedure may be used instead. It may look like the following example:.

The procedure may also comprise the following message:.

For Option <NUM>, the purpose of the existing gNB-CU Configuration Update command may be described as follows: The purpose of the gNB-CU Configuration Update procedure is to update application level configuration data needed for the gNB-DU and gNB-CU to interoperate correctly on the F1 interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non-UE associated signalling.

A message flow for successful operation is shown in <FIG>. In detail, the gNB-CU initiates the procedure by sending a GNB-CU CONFIGURATION UPDATE message including the appropriate updated configuration data to the gNB-DU. The gNB-DU responds with a GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If an information element is not included in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall interpret that the corresponding configuration data is not changed and shall continue to operate the F1-C interface with the existing related configuration data.

The updated configuration data shall be stored in the respective node and used as long as there is an operational TNL association or until any further update is performed.

If Cells to be Activated List Item IE is contained in the GNB-CU CONFIGURATION UPDATE message, 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.

If Cells to be Deactivated List Item IE is contained in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall deactivate the cell indicated by NR CGI IE.

If Cells to be Activated List Item IE is contained in the GNB-CU CONFIGURATION UPDATE message and the indicated cells are already activated, the gNB-DU shall update the cell information received in Cells to be Activated List Item IE.

If the gNB-CU System Information IE is contained in the gNB-CU CONFIGURATION UPDATE message, the gNB-DU shall include the Dedicated SI Delivery Needed UE List IE in the GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message for UEs that are unable to receive system information from broadcast.

If Dedicated SI Delivery Needed UE List IE is contained in the GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-CU should take it into account when informing the UE of the updated system information via the dedicated RRC message.

If the gNB-CU TNL Association To Add List IE is contained in the gNB-CU CONFIGURATION UPDATE message, the gNB-DU shall, if supported, use it to establish the TNL association(s) with the gNB-CU. The gNB-DU shall report to the gNB-CU, in the gNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, the successful establishment of the TNL association(s) with the gNB-CU as follows:.

If the GNB-CU CONFIGURATION UPDATE message includes gNB-CU TNL Association To Remove List IE, and the Endpoint IP address IE and the Port Number IE for both TNL endpoints of the TNL association(s) are included in the gNB-CU TNL Association To Remove List IE, the gNB-DU shall, if supported, initiate removal of the TNL association(s) indicated by both received TNL endpoints towards the gNB-CU. If the Endpoint IP address IE, or the Endpoint IP address IE and the Port Number IE for one or both of the TN L endpoints is included in the gNB-CU TNL Association To Remove List IE, the gNB-DU shall, if supported, initiate removal of the TNL association(s) indicated by the received endpoint IP address(es).

If the gNB-CU TNL Association To Update List IE is contained in the gNB-CU CONFIGURATION UPDATE message the gNB-DU shall, if supported, overwrite the previously stored information for the related TNL Association(s).

If the TNL Association usage IE is included in the gNB-CU TNL Association To Add List IE or the gNB-CU TNL Association To Update List IE, the gNB-DU node shall, if supported, use it as described in TS <NUM> [<NUM>].

For NG-RAN, the gNB-CU shall include the gNB-CU System Information IE in the GNB-CU CONFIGURATION UPDATE message. The SIB type to Be Updated List IE shall contain the full list of SIBs to be broadcast.

If Protected E-UTRA Resources List IE is contained in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall protect the corresponding resource of the cells indicated by E-UTRA Cells List IE for spectrum sharing between E-UTRA and NR.

If the GNB-CU CONFIGURATION UPDATE message contains the Protected E-UTRA Resource Indication IE, the receiving gNB-DU should forward it to lower layers and use it for cell-level resource coordination. The gNB-DU shall consider the received Protected E-UTRA Resource Indication IE when expressing its desired resource allocation during gNB-DU Resource Coordination procedure. The gNB-DU shall consider the received Protected E-UTRA Resource Indication IE content valid until reception of a new update of the IE for the same gNB-DU.

If Available PLMN List IE, and optionally also Extended Available PLMN List IE, is contained in GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall overwrite the whole available PLMN list and update the corresponding system information.

If Cells Failed to be Activated Item IE is contained in the GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-CU shall consider that the indicated cells are out-of-service as defined in TS <NUM> [<NUM>].

If Cell Modification Required List IE is contained in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall, if supported, trigger modifications to the cells indicated by NR-CGI IE, to suspend or re-activate a mode of cell operation.

The last clause hereinabove (Cell Modification Required List) describes the modification compared to the existing gNB-CU Configuration Update command (see 3GPP <NUM>).

A message flow for unsuccessful operation according to Option <NUM> is shown in <FIG>.

If the gNB-DU cannot accept the update, it shall respond with a GNB-CU CONFIGURATION UPDATE FAILURE message and appropriate cause value.

If the GNB-CU CONFIGURATION UPDATE FAILURE message includes the Time To Wait IE, the gNB-CU shall wait at least for the indicated time before reinitiating the GNB-CU CONFIGURATION UPDATE message towards the same gNB-DU.

<FIG> shows the parameters of the gNB-CU configuration update command according to some example embodiments of the invention. <FIG> is split into <FIG>, and the newly introduced parameter Cell modification Required List is depicted in <FIG>. This message is sent by the gNB-CU to transfer updated information associated to an F1-C interface instance. If F1-C signalling transport is shared among several F1-C interface instances, this message may transfer updated information associated to several F1-C interface instances. The table of <FIG> is based on 3GPP TS <NUM>.

<FIG> shows an apparatus according to an embodiment of the invention. The apparatus may be a CU (e.g. gNB-CU) or an element thereof. <FIG> shows a method according to an embodiment of the invention. The apparatus according to <FIG> may perform the method of <FIG> but is not limited to this method. The method of <FIG> may be performed by the apparatus of <FIG> but is not limited to being performed by this apparatus.

The apparatus comprises means for detecting <NUM> and means for instructing <NUM>. The means for detecting <NUM> and means for instructing <NUM> may be a detecting means and instructing means, respectively. The means for detecting <NUM> and means for instructing <NUM> may be a detector and instructor, respectively. The means for detecting <NUM> and means for instructing <NUM> may be a detecting processor and instructing processor, respectively.

The means for detecting <NUM> detects if an issue impacts a first operation mode of a cell and the issue does not impact a second operation mode of the cell (S10). The second operation mode is different to the first operation mode. For example, the first operation mode may be SA and the second operation mode may be NSA, or the first operation mode may be NSA and the second operation mode may be SA. In general, an operation mode may be characterized by its connectivity to a core network of a certain technology such as <NUM> (core network = EPC) or <NUM> (core network = 5GC).

If the issue impacts the first operation mode and does not impact the second operation mode (S10 = "yes"), the means for instructing <NUM> instructs a distributed unit serving the cell to reduce an access to the cell operating in the first operation mode without reducing the access to the cell operating in the second operation mode (S20). For example, the instructing may comprise de-configuring the first mode, barring the first mode, or adapting an access control parameter to the first mode.

<FIG> shows an apparatus according to an embodiment of the invention. The apparatus may be a DU (e.g. gNB-DU) or an element thereof. <FIG> shows a method according to an embodiment of the invention. The apparatus according to <FIG> may perform the method of <FIG> but is not limited to this method. The method of <FIG> may be performed by the apparatus of <FIG> but is not limited to being performed by this apparatus.

The apparatus comprises means for monitoring <NUM> and means for reducing <NUM>. The means for monitoring <NUM> and means for reducing <NUM> may be a monitoring means and reducing means, respectively. The means for monitoring <NUM> and means for reducing <NUM> may be a monitor and reducer, respectively. The means for monitoring <NUM> and means for reducing <NUM> may be a monitoring processor and reducing processor, respectively.

The means for monitoring <NUM> monitors if a distributed unit serving a cell receives an instruction (S110). The instruction instructs the distributed unit to reduce an access to the cell operating in a first operation mode without reducing an access to the cell operating in a second operation mode. The second operation mode is different from the first operation mode. For example, the first operation mode may be SA and the second operation mode may be NSA, or the first operation mode may be NSA and the second operation mode may be SA. In general, an operation mode may be characterized by its connectivity to a core network of a certain technology such as <NUM> (core network = EPC) or <NUM> (core network = 5GC).

If the instruction is received (S110 = yes), the means for reducing <NUM> reduces the access to the cell operating in the first operation mode without reducing the access to the cell operating in the second operation mode (S120). For example, the reducing may comprise de-configuring the first mode, barring the first mode, or adapting an access control parameter to the first mode.

<FIG> shows an apparatus according to an embodiment of the invention. The apparatus comprises at least one processor <NUM>, at least one memory <NUM> including computer program code, and the at least one processor <NUM>, with the at least one memory <NUM> and the computer program code, being arranged to cause the apparatus to at least perform at least one of the methods according to <FIG> and related description.

Some example embodiments are described with respect to two modes of operation of the cell, namely NSA and SA. However, the invention is not limited to these two modes. In some example embodiments, the cell may operate in more than two modes or in two modes different from NSA and SA. For example, in an upcoming <NUM>th generation network, a cell may operate simultaneously in a <NUM> mode, a <NUM> mode, and a <NUM> mode, or in any two of these three operation modes. In general, an operation mode may be defined as a mode of operation having connectivity to at least a certain core network.

The instruction to reduce the access to the cell operating in one operation mode but not to the cell operating in another operating mode may be given explicitly or implicitly. In the implicit case, the CU may just inform the DU that the issue is with the one operation mode only and the DU may interpret this information as a corresponding instruction.

Names of network elements, network functions, protocols, and methods are based on current standards. In other versions or other technologies, the names of these network elements and/or network functions and/or protocols and/or methods may be different, as long as they provide a corresponding functionality.

If not otherwise stated or otherwise made clear from the context, the statement that two entities are different means that they perform different functions. It does not necessarily mean that they are based on different hardware. That is, each of the entities described in the present description may be based on a different hardware, or some or all of the entities may be based on the same hardware. It does not necessarily mean that they are based on different software. That is, each of the entities described in the present description may be based on different software, or some or all of the entities may be based on the same software.

According to the above description, it should thus be apparent that example embodiments of the present invention provide, for example, a CU, or a component thereof, an apparatus embodying the same, a method for controlling and/or operating the same, and computer program(s) controlling and/or operating the same as well as mediums carrying such computer program(s) and forming computer program product(s). According to the above description, it should thus be apparent that example embodiments of the present invention provide, for example, a DU, or a component thereof, an apparatus embodying the same, a method for controlling and/or operating the same, and computer program(s) controlling and/or operating the same as well as mediums carrying such computer program(s) and forming computer program product(s).

Implementations of any of the above described blocks, apparatuses, systems, techniques or methods include, as non-limiting examples, implementations as hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof. Each of the entities described in the present description may be embodied in the cloud.

Claim 1:
Apparatus, comprising
means for detecting (<NUM>) configured to detect if an issue impacts a first operation mode of a cell and the issue does not impact a second operation mode of the cell different to the first operation mode;
means for instructing (<NUM>) configured to instruct a distributed unit serving the cell to reduce an access to the cell operating in the first operation mode without reducing the access to the cell operating in the second operation mode if the issue impacts the first operation mode and does not impact the second operation mode, wherein the means for instructing is configured to instruct the distributed unit that the first operation mode of the cell is to be de-configured and the second operation mode of the cell is not to be de-configured; and characterised by
means for informing configured to inform a first peer node involved in the operation of the cell in the first operation mode of the cell that the first operation mode of the cell is de-configured without informing any second peer node involved in the operation of the cell in the second operation mode of the cell that the second operation mode of the cell was de-configured.