A method to handle failure(s) during a ran node reconfiguration

Abstract

When the configuration parameters of a user equipment (UE) are to be modified, the current context and state may be stored, so that, on detection of a failure during reconfiguration, the network can c

Description

[0001] The example and non-limiting embodiments relate generally to resource reconfiguration and, more particularly, to failure handling. BACKGROUND

[0002] It is known, in response to resource reconfiguration failure, to release all resources allocated for a user equipment. SUMMARY

[0003] The following summary is merely intended to be illustrative. The summary is not intended to limit the scope of the claims .

[0004] In accordance with one aspect, an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: in response to a determination to modify one or more configuration parameters for a user equipment, determine one or more configuration identifiers for the one or more configuration parameters; store the one or more configuration identifiers; transmit a configuration change request, wherein the configuration change request comprises, at least, the one or more configuration identifiers; in response to a determination that the 1 configuration change request is successful, transmit an indication to release a previous configuration for the user equipment; and in response to a determination that at least one failure has occurred with respect to the configuration change request: release at least one resource requested with the configuration change request; and transmit at least one indication that the at least one resource requested with the configuration change request is released.

[0005] In accordance with one aspect, a method comprising: in response to a determination to modify one or more configuration parameters for a user equipment, determining, with a base station, one or more configuration identifiers for the one or more configuration parameters; storing the one or more configuration identifiers; transmitting a configuration change request, wherein the configuration change request comprises, at least, the one or more configuration identifiers; in response to a determination that the configuration change request is successful, transmitting an indication to release a previous configuration for the user equipment; and in response to a determination that at least one failure has occurred with respect to the configuration change request: releasing at least one resource requested with the configuration change request; and transmitting at least one indication that the at least one resource requested with the configuration change request is released.

[0006] In accordance with one aspect, an apparatus comprising means for: in response to a determination to modify one or more configuration parameters for a user equipment, determining one or more configuration identifiers for the one or more configuration parameters; storing the one or more configuration identifiers; transmitting a configuration change request, wherein the configuration change request comprises, at least, the one or more configuration identifiers; in response to a determination that the configuration change request is successful, transmitting an indication to release a previous configuration for the user equipment; and in response to a determination that at least one failure has occurred with respect to the configuration change request: releasing at least one resource requested with the configuration change request; and transmitting at least one indication that the at least one resource requested with the configuration change request is released.

[0007] In accordance with one aspect, a non-transitory computer-readable medium comprising program instructions stored thereon for performing at least the following: in response to a determination to modify one or more configuration parameters for a user equipment, determining one or more configuration identifiers for the one or more configuration parameters; causing storing of the one or more configuration identifiers; causing transmitting of a configuration change request, wherein the configuration change request comprises, at least, the one or more configuration identifiers; in response to a determination that the configuration change request is successful, causing transmitting of an indication to release a previous configuration for the user equipment; and in response to a determination that at least one failure has occurred with respect to the configuration change request: causing releasing of at least one resource requested with the configuration change request; and causing transmitting of at least one indication that the at least one resource requested with the configuration change request is released.

[0008] In accordance with one aspect, an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the apparatus; determine at least one of the one or more configuration parameters for which modification is not performed; and transmit an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[0009] In accordance with one aspect, a method comprising: receiving, with a user equipment, a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the user equipment; determining at least one of the one or more configuration parameters for which modification is not performed; and transmitting an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[0010] In accordance with one aspect, an apparatus comprising means for: receiving a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the apparatus; determining at least one of the one or more configuration parameters for which modification is not performed; and transmitting an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[0011] In accordance with one aspect, a non-transitory computer-readable medium comprising program instructions stored thereon for performing at least the following: causing receiving, with a user equipment, of a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the user equipment; determining at least one of the one or more configuration parameters for which modification is not performed; and causing transmitting of an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[0012] In accordance with one aspect, an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; store current configuration parameters for the user equipment; store the one or more configuration identifiers; transmit, to the user equipment, a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and receive at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[0013] In accordance with one aspect, a method comprising: receiving, with a base station, a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; storing current configuration parameters for the user equipment; storing the one or more configuration identifiers; transmitting, to the user equipment, a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and receiving at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[0014] In accordance with one aspect, an apparatus comprising means for: receiving a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; storing current configuration parameters for the user equipment; storing the one or more configuration identifiers; transmitting, to the user equipment, a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and receiving at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[0015] In accordance with one aspect, a non-transitory computer- readable medium comprising program instructions stored thereon for performing at least the following: causing receiving of a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; causing storing of current configuration parameters for the user equipment; causing storing of the one or more configuration identifiers; causing transmitting, to the user equipment, of a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and causing receiving of at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[0016] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The foregoing aspects and other features are explained in the following description, taken in connection with the accompanying drawings, wherein:

[0018] FIG. 1 is a block diagram of one possible and nonlimiting example system in which the example embodiments may be practiced;

[0019] FIG. 2 is a diagram illustrating features as described herein;

[0020] herein; FIG. 3 is a flowchart illustrating steps as described

[0021] herein; FIG. 4 is a diagram illustrating features as described 5

[0022] herein; FIG. 5 is a flowchart illustrating steps as described

[0023] herein; FIG. 6 is a flowchart illustrating steps as described 10

[0024] herein; FIG. 7 is a flowchart illustrating steps as described

[0025] herein; FIG. 8 is a flowchart illustrating steps as described

[0026] herein; FIG. and 9 is a flowchart illustrating steps as described 15

[0027] FIG. 10 is a flowchart illustrating steps as described herein. DETAILED DESCRIPTION OF EMBODIMENTS

[0028] The following abbreviations that may be found in the specification and / or the drawing figures are defined as follows: 20 3GPP third generation partnership project 5G fifth generation 5GC 5G core network AMF access and mobility management function CPU central processing unit 8 cRAN CU cloud radio access network central unit DU distributed unit eNB (or eNodeB) evolved Node B (e.g., an LTE base station) 5 EN-DC E-UTRA-NR dual connectivity en-gNB or En-gNB node providing NR user plane and control plane protocol terminations towards the UE, and acting as secondary node in EN-DC E-UTRA evolved universal terrestrial radio access, i.e., the LTE radio access 10 technology gNB (or gNodeB) base station for 5G / NR, i.e., a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC gNB-CU-CP base station central unit control plane 15 gNB-CU-UP base station central unit user plane gNB-DU base station distributed unit IE information element I / F interface LI layer 1 20 LTE long term evolution MAC medium access control MME mobility management entity ng or NG new generation ng-eNB or NG-eNB new generation eNB 25 ng-eNB-DU new generation base station distributed unit NR new radio NTWorNW network O-RAN open radio access network PDCP packet data convergence protocol 30 PHY physical layer RAN radio access network RF radio frequency RLC radio link control pnr IxJLW.' radio resource control 5 RRH remote radio head RS reference signal RU radio unit Rx receiver SCTP stream control transmission protocol 10 SDAP service data adaptation protocol SGW serving gateway SMF session management function SW software TNL transport network layer 15 Tx transmitter UE user equipment (e.g., a wireless, typically mobile device) UPF user plane function VNR virtualized network function 20

[0029] Turning to FIG. 1, this figure shows a block diagram of one possible and non-limiting example in which the examples may be practiced. A user equipment (UE) 110, radio access network (RAN) node 170, and network element (s) 190 are illustrated. In the example of FIG. 1, the user equipment (UE) 110 is in wireless 25 communication with a wireless network 100. A UE is a wireless device that can access the wireless network 100. The UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected through one or more buses 127. Each of the one or more transceivers 130 includes a receiver, Rx, 132 and a transmitter, Tx, 133. The one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like. A "circuit" may include dedicated hardware or hardware in association with software executable thereon. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. The UE 110 includes a module 140, comprising one of or both parts 140-1 and / or 140-2, which may be implemented in a number of ways. The module 140 may be implemented in hardware as module 140-1, such as being implemented as part of the one or more processors 120. The module 140-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the module 140 may be implemented as module 140-2, which is implemented as computer program code 123 and is executed by the one or more processors 120. For instance, the one or more memories 125 and the computer program code 123 may be configured to, with the one or more processors 120, cause the user equipment 110 to perform one or more of the operations as described herein. The UE 110 communicates with RAN node 170 via a wireless link 111.

[0030] The RAN node 170 in this example is a base station that provides access by wireless devices such as the UE 110 to the wireless network 100. The RAN node 170 may be, for example, a base station for 5G, also called New Radio (NR). In 5G, the RAN node 170 may be a NG-RAN node, which is defined as either a gNB or a ng-eNB. A gNB is a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to a 5GC (such as, for example, the network element (s) 11 190) . The ng-eNB is a node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. The NG-RAN node may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) 196 and distributed unit(s) (DUs) (gNB-DUs), of which DU 195 is shown. Note that the DU may include or be coupled to and control a radio unit (RU). The gNB-CU is a logical node hosting RRC, service data adaptation protocol (SDAP) and packet data convergence protocol (PDCP) protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the Fl interface connected with the gNB-DU. The Fl interface is illustrated as reference 198, although reference 198 also illustrates a link between remote elements of the RAN node 170 and centralized elements of the RAN node 170, such as between the gNB-CU 196 and the gNB-DU 195. The gNB-DU is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU. One gNB-CU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface 198 connected with the gNB-CU. Note that the DU 195 is considered to include the transceiver 160, e.g., as part of a RU, but some examples of this may have the transceiver 160 as part of a separate RU, e.g., under control of and connected to the DU 195. The RAN node 170 may also be an eNB (evolved NodeB) base station, for LTE (long term evolution), or any other suitable base station, access point, access node, or node .

[0031] The RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N / W I / F(s)) 161, and one or more transceivers 160 interconnected through one or more buses 157. Each of the one or more transceivers 160 includes a receiver, Rx, 162 and a transmitter, Tx, 163. The one or more transceivers 160 are connected to one or more antennas 158 . The one or more memories 155 include computer program code 153. The CU 196 may include the processor(s) 152, memories 155, and network interfaces 161. Note that the DU 195 may also contain its own memory / memories and processor (s), and / or other hardware, but these are not shown.

[0032] The RAN node 170 includes a module 150, comprising one of or both parts 150-1 and / or 150-2, which may be implemented in a number of ways. The module 150 may be implemented in hardware as module 150-1, such as being implemented as part of the one or more processors 152. The module 150-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the module 150 may be implemented as module 150-2, which is implemented as computer program code 153 and is executed by the one or more processors 152. For instance, the one or more memories 155 and the computer program code 153 are configured to, with the one or more processors 152, cause the RAN node 170 to perform one or more of the operations as described herein. Note that the functionality of the module 150 may be distributed, such as being distributed between the DU 195 and the CU 196, or be implemented solely in the DU 195.

[0033] The one or more network interfaces 161 communicate over a network such as via the links 176 and 131. Two or more gNBs 170 may communicate using, e.g., link 176. The link 176 may be wired or wireless or both and may implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interface for other standards.

[0034] The one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like. For example, the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for gNB implementation for 5G, with the other elements of the RAN node 170 possibly being physically in a different location from the RRH / DU, and the one or more buses 157 could be implemented in part as, for example, fiber optic cable or other suitable network connection to connect the other elements (e.g., a central unit (CU) , gNB-CU) of the RAN node 170 to the RRH / DU 195. Reference 198 also indicates those suitable network link (s) .

[0035] It is noted that description herein indicates that "cells" perform functions, but it should be clear that equipment which forms the cell will perform the functions. The cell makes up part of a base station. That is, there can be multiple cells per base station. For example, there could be three cells for a single carrier frequency and associated bandwidth, each cell covering one-third of a 360 degree area so that the single base station's coverage area covers an approximate oval or circle. Furthermore, each cell can correspond to a single carrier and a base station may use multiple carriers. So if there are three 120 degree cells per carrier and two carriers, then the base station has a total of 6 cells.

[0036] The wireless network 100 may include a network element or elements 190 that may include core network functionality, and which provides connectivity via a link or links 181 with a further network, such as a telephone network and / or a data communications network (e.g., the Internet). Such core network functionality for 5G may include access and mobility management function(s) (AMF(s)) and / or user plane functions (UPF(s)) and / or session management function(s) (SMF(s)). Such core network functionality for LTE may include MME (Mobility Management Entity) / SGW (Serving Gateway) functionality. These are merely illustrative functions that may be supported by the network element(s) 190, and note that both 5G and LTE functions might be supported. The RAN node 170 is coupled via a link 131 to a network element 190. The link 131 may be implemented as, e.g., an NG interface for 5G, or an SI interface for LTE, or other suitable interface for other standards. The network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N / W I / F(s)) 180, interconnected through one or more buses 185. The one or more memories 171 include computer program code 173. The one or more memories 171 and the computer program code 173 are configured to, with the one or more processors 175, cause the network element 190 to perform one or more operations.

[0037] The wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as either external, combining many networks, or parts of networks, into a virtual unit, or internal, providing networklike functionality to software containers on a single system. For example, a network may be deployed in a tele cloud, with virtualized network functions (VNF) running on, for example, data center servers. For example, network core functions and / or radio access network(s) (e.g. CloudRAN, O-RAN, edge cloud) may be virtualized. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors 152 or 175 and memories 155 and 171, and also such virtualized entities create technical effects.

[0038] It may also be noted that operations of example embodiments of the present disclosure may be carried out by a plurality of cooperating devices (e.g. cRAN).

[0039] The computer readable memories 125, 155, and 171 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The computer readable memories 125, 155, and 171 may be means for performing storage functions. The processors 120, 152, and 175 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multicore processor architecture, as non-limiting examples. The processors 120, 152, and 175 may be means for performing functions, such as controlling the UE 110, RAN node 170, and other functions as described herein.

[0040] In general, the various example embodiments of the user equipment 110 can include, but are not limited to, cellular telephones such as smart phones, tablets, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances permitting wireless Internet access and browsing, tablets with wireless communication capabilities, as well as portable units or terminals that incorporate combinations of such functions.

[0041] Having thus introduced one suitable but non-limiting technical context for the practice of the example embodiments of the present disclosure, example embodiments will now be described with greater specificity.

[0042] Features as described herein may generally relate to resilience handling in a separated RAN node. A separated RAN node may consist of at least one base station centralized unit in the control plane (gNB-CU-CP) , one or more base station centralized units in the user plane (gNB-CU-UP), and one or more base station distributed units (gNB-DU). Separated architecture may or may not be part of a cloud. An example of the overall architecture for separation of gNB-CU-CP (210) and gNB-CU-UP (220) is shown in FIG. 2 .

[0043] A gNB may consist of a gNB-CU-CP (210), multiple gNB-CU-UPs (220) and multiple gNB-DUs (230). The gNB-CU-CP (210) may be connected to the gNB-DU (230) through the Fl-C interface. The gNB-CU-UP (220) may be connected to the gNB-DU (230) through the Fl-U interface. The gNB-CU-UP (220) may be connected to the gNB-CU-CP (210) through the El interface. One gNB-DU (230) may be connected to only one gNB-CU-CP (210) . One gNB-CU-UP (220) may be connected to only one gNB-CU-CP (210). For resiliency, a gNB-DU (230) and / or a gNB-CU-UP (220) may be connected to multiple gNB-CU-CPs (210) by appropriate implementation.

[0044] One gNB-DU (230) may be connected to multiple gNB-CU-UPs (220) under the control of the same gNB-CU-CP (210) . One gNB-CU-UP (220) may be connected to multiple DUs under the control of the same gNB-CU-CP (210). The connectivity between a gNB-CU-UP (220) and a gNB-DU (230) may be established by the gNB-CU-CP (210) using bearer context management functions.

[0045] Referring now to FIG. 3, illustrated is a 5G RAN node configuration example of a UE initial access procedure involving El and Fl with 3GPP defined architecture. In a typical RAN node implementation, internal architecture may be needed to achieve optimal resource usage and scalability. As an example, computing resources for common resource handling scales differently, and may need to be more centralized, like cell specific component (s), whereas UE state handling may be more UE specific. Interface handling may still bring another aspect to the internal architecture complexity.

[0046] At 302, the UE may transmit, to the gNB-DU, a RRCSetupRequest message. At 304, the gNB-DU may transmit, to the gNB-CU-CP, an initial UL RRC message transfer. At 306, the gNB-CU-CP may transmit, to the gNB-DU, a DL RRC message transfer. At 308, the gNB-DU may transmit, to the UE, an RRCSetup message. At 310, the UE may transmit, to the gNB-DU, a RRCSetupComplete message. At 312, the gNB-DU may transmit, to the gNB-CU-CP, a UL RRC message transfer. At 314, the gNB-CU-CP may transmit, to an access and mobility management function (AMF), an initial UE message. At 316, the AMF may transmit, to the gNB-CU-CP, an initial context setup request. At 318, the gNB-CU-CP may transmit, to the gNB-CU-UP, a bearer context setup request. At 320, the gNB-CU-UP may transmit, to the gNB-CU-CP, a bearer context setup response. At 322, the gNB-CU-CP may transmit, to a gNB-DU, a UE context setup request. At 324, the gNB-DU may transmit, to the UE, a SecurityModeCommand message. At 32 6, the gNB-DU may transmit, to the gNB-CU-CP, a UE context setup response. At 328, the gNB-CU-CP may transmit, to the gNB-CU-UP, a bearer context modification request. At 330, the gNB-CU-UP may transmit, to the gNB-CU-CP, a bearer context modification response. At 334, the gNB-DU may transmit, to the gNB-CU-CP, a UL RRC message transfer. At 336, the gNB-CU-CP may transmit, to the gNB-DU, a DL RRC message transfer. At 338, the gNB-DU may transmit, to the UE, a RRCReconfiguration message. At 340, the UE may transmit, to the gNB-DU, a RRCReconfigurationComplete message. At 342, the gNB-DU may transmit, to the gNB-CU-CP, a UL RRC message transfer. At 344, the gNB-CU-CP may transmit, to the AMF, an initial context setup response.

[0047] In FIG. 3, illustrated is a basic call setup scenario with the 3GPP defined external messages. When, to the FIG. 3 type of scenario, steps and hops are added that are needed by the internal architecture, the final number of messages and different states in UE configuration handling may be multiple times higher than the illustrated messages. This needs a lot of CPU processing and adds latency to the scenario.

[0048] When a RAN node is implemented by using cloudified resources, the optimal CPU resource handling is a fundamental part of the functionality. The functionalities may include scalability of the computing resources. At any time during the signaling scenario of FIG. 3, there may happen scaling in and / or out of functionality that may change the entity that handles the messaging endpoint(s). Other cases when the signaling endpoint may change may include different fault and resiliency scenarios where the task of the signaling computing unit may be assigned to another computing unit.

[0049] Implementing an ultra-reliable RAN node in this kind of system is very complex. Basically, to get the system highly reliable, the system should bookkeep the signaling scenario state for every step (i.e. store the step to a database), including internal steps as well, for example in a RAN node internal database. This may lead to complex implementation and increase the possibility of software (SW) faults, leading to various problems. Also, CPU usage and latency may be increased, leading to low performance of a cloudified RAN node.

[0050] Current NG RAN procedures do not include a way to cancel a started configuration change. If during the UE configuration change, in the NG RAN node, a failure occurs (e.g. RRC reconfiguration unsuccessful) or the task of the NG RAN node is assigned to another computing unit from which the NG RAN node is not able to continue the scenario / procedure, a simple way to proceed is to release the UE and all resources allocated for the UE. In other words, a procedure (e.g. a step of a signaling scenario) may only be canceled when the response is received with new resource modification and / or release (e.g. the requesting side may not be able to release the requested resources unless it receives a response). Alternatively, all UE resources may be released with a reset procedure.

[0051] 3GPP protocol supports idempotent resending of the same message. But, in dynamic situations, it is possible that concurrently proceeding parallel procedure(s) intercept the prior procedure so it may be required to perform a different configuration than the original one. Retransmission might happen too late, as the fault may cause reset of the repeating entity. Accordingly, the need for the idempotent retry / resending may be lost unless the state is stored to a database so that it can continue after recovery. In many cases, continuation of the procedure does not make sense, for example: handover to seconds old measurement report or usage of old DU activation; in case DU has already detected no UEs coming to target channel and might have been started release procedure; if after recovery the requestor starts to repeat the original command, it would only work if all remaining processes in the message chain would understand that this is just an old, repeated message, and all so-far configured entities would still await the resource usage, which may not be realistic in a real system; etc.

[0052] Network element failure does not happen often, but applies typically when there are many simultaneous UEs, and at least some of them are in a configuration change state. Since it is currently not possible to go back and cancel the started configuration change, those UEs would need to perform release.

[0053] In an example embodiment, the network may return the UE configuration state to a previous configuration and cancel the ongoing configuration change if a failure happens during the configuration change in the gNB. A technical effect of example embodiments of the present disclosure may be to prevent repeating of all signaling messages with a complete set of parameters. In an example embodiment, the network may keep the UE context and state in case of failure (i.e. keep the information in memory). A technical effect of example embodiments of the present disclosure may be to implement resilience by bookkeeping fewer steps and configuration history during the configuration change phase.

[0054] In the present disclosure, the term "keep" is used to refer to storage of information, for example in memory.

[0055] Referring now to FIG. 4, illustrated is an example about the configuration process in the gNB due to UE input. In the example of FIG. 4, the UE input (1) may trigger multiple configuration steps in the gNB (e.g. DU, CU-CP, CU-UP).

[0056] When the gNB is implemented to support scalability, it may need multiple internal components to allow efficient performance and scalability. Many of these components may need to store configuration (s) for the UE. This may complicate resiliency scenarios, as a component failure may happen any time during the ongoing scenario in any component. If, for example, message 18 is lost due to a failure, according to an example embodiment of the present disclosure, the gNB may internally cancel the procedure and keep the UE's previous state instead of releasing the UE completely.

[0057] In an example embodiment, a new RAN configuration identifier may be used for all needed procedures. The RAN configuration identifier may identify a group of parameters that are under modification. One configuration change may include one or more RAN configuration identifiers, or all configuration changes may be released / mapped to the one RAN configuration identifier. In other words, one identifier may include one or 22 more parameter changes (e.g. a group of configuration change requests). Parameter changes may be grouped under a same identifier if, for example, errors for the group may be handled together, and / or errors for different groups may be handled separately.

[0058] In an example embodiment a first configuration ID may be associated with a first group of parameters, a second configuration ID may be associated with a second group of parameters, etc. In an example embodiment, the first group of parameters may be mandatory or essential or prioritized parameters. If the first group of parameters are not applied, then the old configuration may be used, and the new configuration may be released completely (e.g. failure scenario, see, e.g., FIG. 6) . In an example embodiment, the second group of parameters may be optional or non-essential or good-to-have parameters. If the second group of parameters are not applied, but the first group of parameters are applied by the UE, then the new configuration, with the first group of parameters, may be used, while part of the old configuration may be used instead of the second group of parameters, which may not be used (partial failure scenario, see, e.g., FIG. 7).

[0059] In a further example embodiment, the first group of parameters may be related to DU configuration parameters (e.g. related to MAC layer parameters, RLC layer, etc.), and the second group of parameters may be related to CU-UP configuration parameters (e.g. a list of DRBs, PDU Session Resources, QoS parameters, etc.). If, for example, the first group of parameters are not or cannot be applied by the UE, then the old configuration may be used, and the new configuration may be released completely. Alternatively, the new configuration may be reconfigured. If at the same time the second group of parameters is applied by the UE, then the new configuration may be confirmed and used, and the newly reconfigured first group of parameters adapted thereto. This way only one out of two groups of parameters may need to be reconfigured, which may have the technical effect of saving signaling effort and time, and / or reducing the risk of the UE loosing connection. Furthermore, implementation may be quicker, for example if DU parameters are applied by the UE, the UE may already start handover, even if at the same time the CU-UP parameters couldn't, and are not, applied, and may need reconfiguration, and then may subsequently perform data transmission with the newly configured and applied CU-UP parameters. This way, less signaling may be required, for example compared to a situation where there is a requirement to perform re-establishment with a high amount of signaling in case only a portion of the overall parameters couldn't be applied (e.g. failure).

[0060] For a reconfiguration of resources, a bearer context modification procedure might be used, for example:

[0061] - The gNB-CU-CP may initiate the procedure by sending the BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP.

[0062] - If the gNB-CU-UP succeeds to modify the bearer context, it may reply to the gNB-CU-CP with the BEARER CONTEXT MODIFICATION RESPONSE message.

[0063] - If the DL UP Parameters IE is contained in the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may configure the corresponding information.

[0064] - If the QoS Flow Mapping Indication IE is contained in the QoS Flow QoS Parameters List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP may, if supported, replace any previously received value, and may take it into account that only the uplink or downlink QoS flow is mapped to the DRB.

[0065] It may be noted that while multiple actions may be triggered at the same time, the actions may have different results due to the needs of each action and the applicability by the UE (e.g. CU-UP application, but DU reconfiguration; CU-UP and DU reconfiguration; DU application, but CU-UP reconfiguration; etc.).

[0066] While the present disclosure refers to a "RAN configuration identifier," this is not limiting; a configuration ID may not be limited to RAN. The configuration ID may also be valid in the core network direction.

[0067] When, for example, the gNB-CU-CP starts configuration modification, it may allocate a RAN configuration identifier, store the identifier to a database, and add the identifier to a configuration change request towards the gNB-DU, and also for the gNB-CU-UP. Both the gNB-DU and the gNB-CU-UP may map the newly allocated resources to the RAN configuration change identifier (s), and keep the old configuration just in case the new procedure fails in a later step. If there happens a failure during the configuration change, the gNB-CU-CP may cancel the configuration change with / using the RAN configuration identifier, instead of releasing all of the UE configuration.

[0068] Referring now to FIG. 4, illustrated is an example of information element (IE) mapping with a RAN configuration ID IE successful scenario. The UE configuration modification may be triggered due to, for example, a measurement result, PDU session addition / modification, UE capability change(s), an internal trigger (e.g. scalability), etc. The measurement result may trigger simultaneously multiple actions like intra DU handover, or carrier aggregation addition, etc. It may be noted that while multiple actions may be triggered at the same time, the actions may have different results due to the needs of each action (e.g. DU reconfiguration, CU-UP and DU reconfiguration, etc.). In other words, some configuration changes may be successful, while other configuration changes may be unsuccessful.

[0069] The gNB-CU-CP may allocate a RAN configuration identifier for each triggered configuration change, and may store the ID (e.g. a mapping between the ID and the (requested) configuration change) to the RAN internal database, for example for resilience purposes and / or to start the modification phase. The granularity of the RAN configuration identifier may be decided by the gNB-CU-CP; the gNB-CU-CP may use one identifier or allocate multiple identifiers for different sets of parameters / requested configuration changes.

[0070] At 502, the UE may transmit, to a gNB-CU-CP, a measurement result. At 504, the gNB-CU-CP may determine to trigger a UE configuration modification. At 506, the gNB-CU-CP may send a BEARER CONTEXT SETUP REQUEST message containing, for example, a request for SDAP and PDCP configuration (e.g. a request for a configuration including at least one modified configuration parameter) to the gNB-CU-UP. For example, the request may include one or more lEs mapped with one or more RAN configuration IDs. The gNB-CU-CP may map these configurations with the new RAN configuration ID. At 508, the gNB-CU-UP may map the newly allocated resources with the RAN configuration ID and keep the mapping. The gNB-CU-UP may also keep the old configuration, in case the request was for modification, and respond with a BEARER CONTEXT SETUP RESPONSE message. At 510-512, a Fl UE context setup / modification procedure may be performed to setup and / or modify the gNB-DU configuration. The gNB-DU may map these configurations with the new RAN configuration ID, and may also keep the old configuration.

[0071] At 514, the gNB-CU-CP may send, to the gNB-CU-UP, a BEARER CONTEXT MODIFICATION REQUEST message containing the DL transport network layer (TNL) address information for Fl-U or Xn-U, and PDCP status. At 516, the gNB-DU may transmit, to the gNB-CU-UP, uplink user data. At 518, the gNB-CU-UP may respond with a BEARER CONTEXT MODIFICATION RESPONSE message. The gNB-CU-CP may know / determine that the UE configuration is ready to be sent to the UE, and that once the message is sent to the UE, canceling is no longer possible. The gNb-CU-CP may mark / store the state to the database (e.g. the UE configuration and the RAN configuration IDs) . At 520, the gNB-CU-UP may transmit, to the gNB-DU, downlink user data. At 522, the gNB-CU-CP may determine a change to the UE configuration.

[0072] The UE may be configured with the RRC reconfiguration. At 524, the gNB-CU-CP may transmit, to the gNB-DU, a DL RRC message transfer. At 52 6, the gNB-DU may transmit, to the UE, an RRCReconfiguration message. At 528, the UE may transmit, to the gNB-DU, an RRCReconfigurationComplete message. At 530, the gNB-DU may transmit, to the gNB-CU-CP, a UL RRC message transfer.

[0073] At 532, the gNB-CU-CP may send a UE CONTEXT MODIFICATION REQUEST message to release the previous configuration and let the gNB-DU know that the new configuration is now valid (i.e. no failure has occurred). For example, the request may include at least one IE configured to indicate that a previous configuration is to be released, as the configuration associated with the RAN configuration ID has been implemented. At 534, the gNB-CU-CP may send a BEARER CONTEXT MODIFICATION REQUEST message to release the previous configuration and let the gNB-CU-UP know that the new configuration is now valid. The previous configuration may be removed from the database and / or from memory, while the new configuration may be kept in memory. For example, the request may include at least one IE configured to indicate that a previous configuration is to be released, as the configuration associated with the RAN configuration ID has been implemented. The UE and the network may continue successfully with the new configuration.

[0074] Referring now to FIG. 6, illustrated is an example of IE mapping with RAN configuration ID with failure. A UE configuration modification may be triggered due to, for example, a measurement result, PDU session addition / modification, UE capability change(s), an internal trigger (e.g. scalability), etc. This may trigger intra DU handover, carrier aggregation addition, etc. The gNB-CU-CP may allocate a RAN configuration identifier for each triggered configuration change, and may store the ID to the BAN internal database, for example, for resilience purposes and to start the modification phase.

[0075] At 605, the UE may transmit, to a gNB-CU-CP, a measurement result. At 610, the gNB-CU-CP may determine that a UE configuration modification has been triggered, for example based on the measurement result. At 615, the gNB-CU-CP may send a BEARER CONTEXT SETUP REQUEST message containing, for example, SDAP and PDCP configuration to the gNB-CU-UP. For example, the request may include IE(s) mapped with one or more RAN configuration IDs. The gNB-CU-CP may map these configurations (e.g. configuration parameters to be modified) with the new RAN configuration ID(s). At 620, the gNB-CU-UP may map the newly allocated resources with the RAN configuration ID and may keep / store the new mapping. The gNB-CU-UP may also keep / store the old configuration in case the request was for modification, and may respond with a BEARER CONTEXT SETUP RESPONSE message. At 625, a Fl UE context setup / modification procedure may be performed to setup and / or modify the gNB-DU configuration. For example, the request may include IE(s) mapped with one or more RAN configuration IDs. The gNB-DU may map new conf iguration (s) with the RAN configuration ID(s), and may also keep the old configuration.

[0076] At 630, failure may happen in the gNB-CU-CP. After recovery, the gNB-CU-CP may read, from the database, the ongoing configuration changes and may release requested resources (i.e. the resources for the ongoing configuration changes that have failed).

[0077] At 635, the gNB-DU resource release with UE CONTEXT MODIFICATION REQUEST may be transmitted, and may include new IE(s) that identify failed configuration(s). For example, the request may include IE(s) for releasing all or part of the configuration mapped to the RAN configuration ID(s). The gNB-DU may continue with the old configuration. At 640, the gNB-CU-UP resource release with BEARER CONTEXT MODIFICATION REQUEST may be transmitted, and may include new IE(s) that identify the failed configuration. For example, the request may include IE(s) for releasing all or part of the configuration mapped to the RAN configuration ID(s). At 645, the UE and the network may continue with the old configuration .

[0078] Referring now to FIG. 7, illustrated is an example of IE mapping with RAN configuration ID(s) in a partially successful (or partial failure) scenario. The UE configuration modification may be triggered due to, for example, a measurement result, PDU session addi tion / modification, UE capability change(s), an internal trigger (e.g. scalability), etc. This may trigger intra DU handover, carrier aggregation addition, etc. The gNB-CU-CP may allocate a RAN configuration identifier for each triggered configuration change, and may store the ID to the RAN internal database, for example for resilience purposes and / or to start the modification phase.

[0079] At 702, the UE may transmit, to the gNB-CU-CP, a measurement result. At 704, the gNB-CU-CP may determine a trigger or UE configuration modification, for example based on the measurement result. At 706, the gNB-CU-CP may send a BEARER CONTEXT SETUP REQUEST message containing, for example, SDAP and PDCP configuration to the gNB-CU-UP. For example, the request may include IE(s) mapped with RAN configuration ID(s). The gNB-CU-CP may map these configurations with the new RAN configuration ID. At 708, the gNB-CU-UP may map the newly allocated resources with the RAN configuration ID and may keep / store the mapping. The gNB-CU-UP may also keep the old / previous configuration in case the request was for modification, and may respond with a BEARER CONTEXT SETUP RESPONSE message.

[0080] At 710, 712, the Fl UE context setup / modi f ication procedure may be performed to setup and / or modify the gNB-DU configuration. For example, gNB-CU-CP may transmit, to the gNB-DU, a request including IE(s) mapped with RAN configuration ID(s). The gNB-DU may map these configurations with the new RAN configuration ID, and may also keep the old configuration. At 714, the gNB-CU-CP may send a BEARER CONTEXT MODIFICATION REQUEST message containing the DL TNL address information for Fl-U or Xn-U, and PDCP status. At 716, the gNB-DU may transmit, to the gNB-CU-UP, uplink user data. At 718, the gNB-CU-UP may respond with a BEARER CONTEXT MODIFICATION RESPONSE message. The gNB-CU-CP may know / determine that the UE configuration is ready to be sent to the UE, and that once the message is sent to the UE, canceling is no longer possible. The gNb-CU-CP may mark / store the state to the database. At 720, the gNB-CU-CP may determine a UE configuration change. At 722, gNB-CU-UP may transmit, to the gNB-DU, downlink user data.

[0081] At 724, the gNB-CU-CP may transmit, to the gNB-DU, a DL message transfer that includes RRC reconfiguration. At 726, the RRC reconfiguration message that includes modified configuration mapped with new RAN configuration identifier may be transmitted from the gNB-DU to the UE. For example, the message may include IE(s) mapped with RAN configuration ID(s) . At 728, the UE may transmit, to the gNB-DU, the RRC reconfiguration complete message that includes the failed configuration mapped with the new RAN configuration identifier. For example, the message may include IE(s) indicating failed RAN configuration ID(s). At 730, the gNB-DU may transmit, to the gNB-CU-CP, a UL message transfer that includes RRC reconfiguration complete. For example, the UL transfer message may include IE(s) indicating failed RAN configuration ID(s).

[0082] In an alternative example embodiment, the gNB-CU-CP may determine that one or more of the requested changes, included in the modified configuration, may / will fail. This detection may occur before the gNB-CU-CP receives an indication of failed configuration ID(s), and / or before the UE determines failure of the requested changes. Based on such detection, the gNB-CU-CP may release the (new) configuration associated with the failed configuration ID(s), for example before receiving a response from the UE .

[0083] At 732, the gNB-CU-CP may send a UE CONTEXT MODIFICATION REQUEST message to release the previous configuration and the failed configuration, and let the gNB-DU know which part(s) of the configuration is now valid. For example, the message may include IE(s) indicating release of the previous configuration for RAN configuration ID(s), and / or IE(s) indicating release of failed RAN configuration IDs. At 734, the gNB-CU-CP may send a BEARER CONTEXT MODIFICATION REQUEST message to release the previous configuration and the failed configuration, and let the gNB-CU-UP know which part(s) of the configuration is now valid. For example, the message may include IE(s) indicating release of the previous configuration for RAN configuration ID(s), and / or IE(s) indicating release of failed RAN configuration IDs. At 736, the UE and the network may continue successfully with the partial new configuration .

[0084] In an alternative example embodiment, the gNB-CU-CP may cause partial release of failed configuration ID(s) for: the UE to which the modification request was transmitted, at least one different UE, or both. For example, in some failures the same UE that is detected to behave in a faulty way may not have responded yet. So, the CU-CP may request a change from the DU, and when the DU does not respond fast enough, the CU-CP may cancel the request with the configuration ID(s).

[0085] A partial failure / success scenario, for example as in FIG. 7, may occur where the UE is unable to adapt one parameter (e.g. parameter modification failure), and the UE fails only a portion of the modification request. Additionally or alternatively, from the perspective of the UE, it may appear that a modification request has failed in its entirety, whereas from the perspective of the network, the failure at the UE is only a portion of a larger modi fication / reconfiguration.

[0086] A person of ordinary skill in the art will understand that one, some, or all of the steps in FIGs. 5-7 may be performed concurrently with each other, or may be performed in a different order .

[0087] In an alternative example embodiment, the RAN configuration identifier may be used to reject some request(s) from gNB-DU and / or from gNB-CU-UP. If the gNB-CU-CP requests multiple configuration changes and has mapped them under different RAN configuration IDs, the gNB DU may be able to make partial configuration changes, and may indicate partial success.

[0088] In an alternative example embodiment, the UE may use the RAN configuration identifier to reject some configuration changes. If the gNB requests multiple configuration changes and has mapped them under different RAN configuration IDs, the UE may be able to make partial configuration changes, and may indicate partial success and / or partial failure.

[0089] In an alternative example embodiment, after internal cancelation, the gNB may immediately trigger the configuration change for different gNB nodes again to get the UE configured with the wanted configuration. For example, if the CU-CP starts a configuration request for one DU, and that takes more time than expected, the request may be canceled, and another started for another DU.

[0090] NG-RAN may also consist of a set of ng-eNBs, an ng-eNB may consist of an ng-eNB-CU-CP, one or more ng-eNB-CU-UP(s) , and one or more ng-eNB-DU(s). An ng-eNB-CU-CP and an ng-eNB-CU-UP may be connected via the El interface. An ng-eNB-DU may be connected to an ng-eNB-CU-CP via the Wl-C interface, and to an ng-eNB-CU-UP via the Wl-U interface. Example embodiments of the present disclosure may also apply to ng-eNB and its corresponding El and W1 interfaces, if not explicitly specified otherwise.

[0091] FIG. 8 illustrates the potential steps of an example method 800. The example method 800 may include: in response to a determination to modify one or more configuration parameters for a user equipment, determining one or more configuration identifiers for the one or more configuration parameters; store the one or more configuration identifiers, 810; transmitting a configuration change request, wherein the configuration change request comprises, at least, the one or more configuration identifiers, 820; in response to a determination that the configuration change request is successful, transmitting an indication to release a previous configuration for the user equipment, 830; and in response to a determination that at least one failure has occurred with respect to the configuration change request: releasing at least one resource requested with the configuration change request; and transmitting at least one indication that the at least one resource requested with the configuration change request is released, 840. The example method 800 may be performed, for example, with a base station, gNB, eNB, network node, gNB-CU-CP, etc.

[0092] FIG. 9 illustrates the potential steps of an example method 900. The example method 900 may include: receiving a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers allocated determined for one or more configuration parameters for modification for the apparatus, 910; determining at least one of the one or more configuration parameters for which modification is not performed, 920; and transmitting an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed, 930. The example method 900 may be performed, for example, with a UE.

[0093] FIG. 10 illustrates the potential steps of an example method 1000. The example method 1000 may include: receiving a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment, 1010; storing current configuration parameters for the user equipment, 1020; storing the one or more configuration identifiers, 1030; transmitting, to the user equipment, a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request, 1040; and receiving at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request, 1050. The example method 1000 may be performed, for example, with a base station, gNB, eNB, network node, gNB-DU, etc.

[0094] In accordance with one example embodiment, an apparatus may comprise: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: in response to a determination to modify one or more configuration parameters for a user equipment, determine one or more configuration identifiers for the one or more configuration parameters; store the one or more configuration identifiers; transmit a configuration change request, wherein the configuration change request may comprise, at least, the one or more configuration identifiers; in response to a determination that the configuration change request is successful, transmit an indication to release a previous configuration for the user equipment; and in response to a determination that at least one failure has occurred with respect to the configuration change request: release at least one resource requested with the configuration change request; and transmit at least one indication that the at least one resource requested with the configuration change request is released.

[0095] A respective one of the one or more configuration identifiers may be associated with a respective one of one or more configuration parameters .

[0096] A respective one of the one or more configuration identifiers may be associated with a plurality of configuration parameters of the one or more configuration parameters.

[0097] The configuration change request may be transmitted to at least one of: a distributed unit of a base station, or a user plane centralized unit of the base station.

[0098] The indication to release the previous configuration may be transmitted to at least one of: a distributed unit of a base station, or a user plane centralized unit of the base station.

[0099] The at least one indication may be transmitted to at least one of: a distributed unit of a base station, or a user plane centralized unit of the base station.

[00100] Storing the one or more configuration identifiers may comprises the example apparatus being further configured to: store a mapping between the one or more configuration identifiers and the one or more configuration parameters in a radio access network internal database.

[00101] The example apparatus may be further configured to: receive an indication of at least one configuration identifier of the one or more configuration identifiers for which the at least one failure has occurred; and determine that the at least one failure has occurred with respect to the configuration change request based, at least partially, on the received indication of the at least one configuration identifier.

[00102] The example apparatus may be further configured to: receive an indication that the at least one failure has occurred with respect to the configuration change request, comprising at least one of the one or more configuration identifiers associated with the at least one failure; determine at least one of the one or more configuration parameters that is successful based, at least partially, on the received indication; and transmit an indication to release at least one previous configuration based, at least partially, on the at least one configuration parameter determined to be successful.

[00103] The example apparatus may be further configured to: detect that the at least one failure has occurred with respect to the configuration change request; determine at least one of the one or more configuration parameters that is successful based, at least partially, on the at least one detected failure; and transmit an indication to release at least one previous configuration based, at least partially, on the at least one configuration parameter determined to be successful.

[00104] The one or more configuration parameters may comprise a first set of configuration parameters and a second set of configuration parameters, wherein the first set of configuration parameters may comprise one or more mandatory configuration parameters, wherein the second set of configuration parameters may comprise one or more optional configuration parameters, wherein the example apparatus may be further configured to one of: release all resources requested with the configuration change request in response to a failure with respect to the first set of configuration parameters; or release only resources associated with the second set of configuration parameters in response to a failure with respect to the second set of configuration parameters.

[00105] In accordance with one aspect, an example method may be provided comprising: in response to a determination to modify one or more configuration parameters for a user equipment, determining, with a base station, one or more configuration identifiers for the one or more configuration parameters; storing the one or more configuration identifiers; transmitting a configuration change request, wherein the configuration change request may comprise, at least, the one or more configuration identifiers; in response to a determination that the configuration change request is successful, transmitting an indication to release a previous configuration for the user equipment; and in response to a determination that at least one failure has occurred with respect to the configuration change request: releasing at least one resource requested with the configuration change request; and transmitting at least one indication that the at least one resource requested with the configuration change request is released.

[00106] A respective one of the one or more configuration identifiers may be associated with a respective one of one or more configuration parameters .

[00107] A respective one of the one or more configuration identifiers may be associated with a plurality of configuration parameters of the one or more configuration parameters.

[00108] The configuration change request may be transmitted to at least one of: a distributed unit of a base station, or a user plane centralized unit of the base station.

[00109] The indication to release the previous configuration may be transmitted to at least one of: a distributed unit of a base station, or a user plane centralized unit of the base station.

[00110] The at least one indication may be transmitted to at least one of: a distributed unit of a base station, or a user plane centralized unit of the base station.

[00111] The storing of the one or more configuration identifiers may comprise: storing a mapping between the one or more configuration identifiers and the one or more configuration parameters in a radio access network internal database.

[00112] The example method may further comprise: receiving an indication of at least one configuration identifier of the one or more configuration identifiers for which the at least one failure has occurred; and determining that the at least one failure has occurred with respect to the configuration change request based, at least partially, on the received indication of the at least one configuration identifier.

[00113] The example method may further comprise: receiving an indication that the at least one failure has occurred with respect to the configuration change request, comprising at least one of the one or more configuration identifiers associated with the at least one failure; determining at least one of the one or more configuration parameters that is successful based, at least partially, on the received indication; and transmitting an indication to release at least one previous configuration based, at least partially, on the at least one configuration parameter determined to be successful.

[00114] The example method may further comprise: detecting that the at least one failure has occurred with respect to the configuration change request; determining at least one of the one or more configuration parameters that is successful based, at least partially, on the at least one detected failure; and transmitting an indication to release at least one previous configuration based, at least partially, on the at least one configuration parameter determined to be successful.

[00115] The one or more configuration parameters may comprise a first set of configuration parameters and a second set of configuration parameters, wherein the first set of configuration parameters may comprise one or more mandatory configuration parameters, wherein the second set of configuration parameters may comprise one or more optional configuration parameters, and the example method may further comprise one of: releasing all resources requested with the configuration change request in response to a failure with respect to the first set of configuration parameters; or releasing only resources associated with the second set of configuration parameters in response to a failure with respect to the second set of configuration parameters .

[00116] In accordance with one example embodiment, an apparatus may comprise: circuitry configured to perform: in response to a determination to modify one or more configuration parameters for a user equipment, determining one or more configuration identifiers for the one or more configuration parameters; circuitry configured to perform: storing the one or more configuration identifiers; circuitry configured to perform: transmitting a configuration change request, wherein the configuration change request may comprise, at least, the one or more configuration identifiers; circuitry configured to perform: in response to a determination that the configuration change request is successful, transmitting an indication to release a previous configuration for the user equipment; and circuitry configured to perform: in response to a determination that at least one failure has occurred with respect to the configuration change request: releasing at least one resource requested with the configuration change request; and transmitting at least one indication that the at least one resource requested with the configuration change request is released.

[00117] In accordance with one example embodiment, an apparatus may comprise: processing circuitry; memory circuitry including computer program code, the memory circuitry and the computer program code configured to, with the processing circuitry, enable the apparatus to: in response to a determination to modify one or more configuration parameters for a user equipment, determine one or more configuration identifiers for the one or more configuration parameters; store the one or more configuration identifiers; transmit a configuration change request, wherein the configuration change request may comprise, at least, the one or more configuration identifiers; in response to a determination that the configuration change request is successful, transmit an indication to release a previous configuration for the user equipment; and in response to a determination that at least one failure has occurred with respect to the configuration change request: release at least one resource requested with the configuration change request; and transmit at least one indication that the at least one resource requested with the configuration change request is released.

[00118] As used in this application, the term "circuitry" or "means" may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable) : (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor (s) with software (including digital signal processor (s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit(s) and or processor (s), such as a microprocessor (s) or a portion of a microprocessor(s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation." This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[00119] In accordance with one example embodiment, an apparatus may comprise means for: in response to a determination to modify one or more configuration parameters for a user equipment, determining one or more configuration identifiers for the one or more configuration parameters; storing the one or more configuration identifiers; transmitting a configuration change request, wherein the configuration change request may comprise, at least, the one or more configuration identifiers; in response to a determination that the configuration change request is successful, transmitting an indication to release a previous configuration for the user equipment; and in response to a determination that at least one failure has occurred with respect to the configuration change request: releasing at least one resource requested with the configuration change request; and transmitting at least one indication that the at least one resource requested with the configuration change request is released.

[00120] A respective one of the one or more configuration identifiers may be associated with a respective one of one or more configuration parameters .

[00121] A respective one of the one or more configuration identifiers may be associated with a plurality of configuration parameters of the one or more configuration parameters.

[00122] The configuration change request may be transmitted to at least one of: a distributed unit of a base station, or a user plane centralized unit of the base station.

[00123] The indication to release the previous configuration may be transmitted to at least one of: a distributed unit of a base station, or a user plane centralized unit of the base station.

[00124] The at least one indication may be transmitted to at least one of: a distributed unit of a base station, or a user plane centralized unit of the base station.

[00125] The means configured for storing the one or more configuration identifiers may comprise means configured for: storing a mapping between the one or more configuration identifiers and the one or more configuration parameters in a radio access network internal database.

[00126] The means may be further configured for: receiving an indication of at least one configuration identifier of the one or more configuration identifiers for which the at least one failure has occurred; and determining that the at least one failure has occurred with respect to the configuration change request based, at least partially, on the received indication of the at least one configuration identifier.

[00127] The means may be further configured for: receiving an indication that the at least one failure has occurred with respect to the configuration change request, comprising at least one of the one or more configuration identifiers associated with the at least one failure; determining at least one of the one or more configuration parameters that is successful based, at least partially, on the received indication; and transmitting an indication to release at least one previous configuration based, at least partially, on the at least one configuration parameter determined to be successful.

[00128] The means may be further configured for: detecting that the at least one failure has occurred with respect to the configuration change request; determining at least one of the one or more configuration parameters that is successful based, at least partially, on the at least one detected failure; and transmitting an indication to release at least one previous configuration based, at least partially, on the at least one configuration parameter determined to be successful.

[00129] The one or more configuration parameters may comprise a first set of configuration parameters and a second set of configuration parameters, wherein the first set of configuration parameters may comprise one or more mandatory configuration parameters, wherein the second set of configuration parameters may comprise one or more optional configuration parameters, wherein the means may be further configured for one of: releasing all resources requested with the configuration change request in response to a failure with respect to the first set of configuration parameters; or releasing only resources associated with the second set of configuration parameters in response to a failure with respect to the second set of configuration parameters.

[00130] A processor, memory, and / or example algorithms (which may be encoded as instructions, program, or code) may be provided as example means for providing or causing performance of operation.

[00131] In accordance with one example embodiment, a non-transitory computer-readable medium comprising instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: in response to a determination to modify one or more configuration parameters for a user equipment, determine one or more configuration identifiers for the one or more configuration parameters; cause storing of the one or more configuration identifiers; cause transmitting of a configuration change request, wherein the configuration change request may comprise, at least, the one or more configuration identifiers; in response to a determination that the configuration change request is successful, cause transmitting of an indication to release a previous configuration for the user equipment; and in response to a determination that at least one failure has occurred with respect to the configuration change request: cause releasing of at least one resource requested with the configuration change request; and cause transmitting of at least one indication that the at least released.

[00132] In accordance with one example embodiment, a non-transitory computer-readable medium comprising program instructions stored thereon for performing at least the following: in response to a determination to modify one or more configuration parameters for a user equipment, determining one or more configuration identifiers for the one or more configuration parameters; causing storing of the one or more configuration identifiers; causing transmitting of a configuration change request, wherein the configuration change request may comprise, at least, the one or more configuration identifiers; in response to a determination that the configuration change request is successful, causing transmitting of an indication to release a previous configuration for the user equipment; and in response to a determination that at least one failure has occurred with respect to the configuration change request: causing releasing of at least one resource requested with the configuration change request; and causing transmitting of at least one indication that the at least one resource requested with the configuration change request is released.

[00133] In accordance with another example embodiment, a non-transitory program storage device readable by a machine may be provided, tangibly embodying instructions executable by the machine for performing operations, the operations comprising: in response to a determination to modify one or more configuration parameters for a user equipment, determining one or more configuration identifiers for the one or more configuration parameters; causing storing of the one or more configuration identifiers; causing transmitting of a configuration change request, wherein the configuration change request may comprise, at least, the one or more configuration identifiers; in response to a determination that the configuration change request is successful, causing transmitting of an indication to release a previous configuration for the user equipment; and in response to a determination that at least one failure has occurred with respect to the configuration change request: causing releasing of at least one resource requested with the configuration change request; and causing transmitting of at least one indication that the at least one resource requested with the configuration change request is released.

[00134] In accordance with another example embodiment, a non-transitory computer-readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: in response to a determination to modify one or more configuration parameters for a user equipment, determining one or more configuration identifiers for the one or more configuration parameters; causing storing of the one or more configuration identifiers; causing transmitting of a configuration change request, wherein the configuration change request may comprise, at least, the one or more configuration identifiers; in response to a determination that the configuration change request is successful, causing transmitting of an indication to release a previous configuration for the user equipment; and in response to a determination that at least one failure has occurred with respect to the configuration change request: causing releasing of at least one resource requested with the configuration change request; and causing transmitting of at least one indication that the at least released.

[00135] A computer implemented system comprising: at least one processor and at least one non-transitory memory storing instructions that, when executed by the at least one processor, cause the system at least to perform: in response to a determination to modify one or more configuration parameters for a user equipment, determining one or more configuration identifiers for the one or more configuration parameters; causing storing of the one or more configuration identifiers; causing transmitting of a configuration change request, wherein the configuration change request may comprise, at least, the one or more configuration identifiers; in response to a determination that the configuration change request is successful, causing transmitting of an indication to release a previous configuration for the user equipment; and in response to a determination that at least one failure has occurred with respect to the configuration change request: causing releasing of at least one resource requested with the configuration change request; and causing transmitting of at least one indication that the at least one resource requested with the configuration change request is released.

[00136] A computer implemented system comprising: means for in response to a determination to modify one or more configuration parameters for a user equipment, determining one or more configuration identifiers for the one or more configuration parameters; means for causing storing of the one or more configuration identifiers; means for causing transmitting of a configuration change request, wherein the configuration change request may comprise, at least, the one or more configuration identifiers; means for in response to a determination that the configuration change request is successful, causing transmitting of an indication to release a previous configuration for the user equipment; and means for in response to a determination that at least one failure has occurred with respect to the configuration change request: causing releasing of at least one resource requested with the configuration change request; and causing transmitting of at least one indication that the at least one resource requested with the configuration change request is released.

[00137] In accordance with one example embodiment, an apparatus may comprise: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the apparatus; determine at least one of the one or more configuration parameters for which modification is not performed; and transmit an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[00138] A respective one of the one or more configuration identifiers may be associated with a respective one of one or more configuration parameters .

[00139] A respective one of the one or more configuration identifiers may be associated with a plurality of configuration parameters of the one or more configuration parameters.

[00140] The received configuration change request may comprise a radio resource control reconfiguration request received from a base station, wherein the indication of the at least one configuration identifier may be transmitted to the base station.

[00141] Determining the at least one configuration parameter for which modification is not performed may comprise the example apparatus being further configured to: determine that at least one failure has occurred with respect to modification of the at least one configuration parameter.

[00142] Determining the at least one configuration parameter for which modification is not performed may comprise the example apparatus being further configured to: determine to reject modification of the at least one configuration parameter.

[00143] The example apparatus may be further configured to: determine that modification of a configuration parameter of the one or more configuration parameters is successful, wherein the transmitted indication of the at least one configuration identifier may not comprise an indication of a configuration identifier associated with the configuration parameter.

[00144] In accordance with one aspect, an example method may be provided comprising: receiving, with a user equipment, a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the user equipment; determining at least one of the one or more configuration parameters for which modification is not performed; and transmitting an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[00145] A respective one of the one or more configuration identifiers may be associated with a respective one of one or more configuration parameters .

[00146] A respective one of the one or more configuration identifiers may be associated with a plurality of configuration parameters of the one or more configuration parameters.

[00147] The received configuration change request may comprise a radio resource control reconfiguration request received from a base station, wherein the indication of the at least one configuration identifier may be transmitted to the base station.

[00148] The determining of the at least one configuration parameter for which modification is not performed may comprise: determining that at least one failure has occurred with respect to modification of the at least one configuration parameter.

[00149] The determining of the at least one configuration parameter for which modification is not performed may comprise: determining to reject modification of the at least one configuration parameter.

[00150] The example method may further comprise: determining that modification of a configuration parameter of the one or more configuration parameters is successful, wherein the transmitted indication of the at least one configuration identifier may not comprise an indication of a configuration identifier associated with the configuration parameter.

[00151] In accordance with one example embodiment, an apparatus may comprise: circuitry configured to perform: receiving, with a user equipment, a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the user equipment; circuitry configured to perform: determining at least one of the one or more configuration parameters for which modification is not performed; and circuitry configured to perform: transmitting an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[00152] In accordance with one example embodiment, an apparatus may comprise: processing circuitry; memory circuitry including computer program code, the memory circuitry and the computer program code configured to, with the processing circuitry, enable the apparatus to: receive a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the apparatus; determine at least one of the one or more configuration parameters for which modification is not performed; and transmit an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[00153] In accordance with one example embodiment, an apparatus may comprise means for: receiving a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the apparatus; determining at least one of the one or more configuration parameters for which modification is not performed; and transmitting an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[00154] A respective one of the one or more configuration identifiers may be associated with a respective one of one or more configuration parameters .

[00155] A respective one of the one or more configuration identifiers may be associated with a plurality of configuration parameters of the one or more configuration parameters.

[00156] The received configuration change request may comprise a radio resource control reconfiguration request received from a base station, wherein the indication of the at least one configuration identifier may be transmitted to the base station.

[00157] The means configured for determining the at least one configuration parameter for which modification is not performed may comprise means configured for: determining that at least one failure has occurred with respect to modification of the at least one configuration parameter.

[00158] The means configured for determining the at least one configuration parameter for which modification is not performed may comprise means configured for: determining to reject modification of the at least one configuration parameter.

[00159] The means may be further configured for: determining that modification of a configuration parameter of the one or more configuration parameters is successful, wherein the transmitted indication of the at least one configuration identifier may not comprise an indication of a configuration identifier associated with the configuration parameter.

[00160] In accordance with one example embodiment, a non-transitory computer-readable medium comprising instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: cause receiving, with a user equipment, of a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the user equipment; determine at least one of the one or more configuration parameters for which modification is not performed; and cause transmitting of an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[00161] In accordance with one example embodiment, a non-transitory computer-readable medium comprising program instructions stored thereon for performing at least the following: causing receiving, with a user equipment, of a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the user equipment; determining at least one of the one or more configuration parameters for which modification is not performed; and causing transmitting of an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[00162] In accordance with another example embodiment, a non-transitory program storage device readable by a machine may be provided, tangibly embodying instructions executable by the machine for performing operations, the operations comprising: causing receiving, with a user equipment, of a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the user equipment; determining at least one of the one or more configuration parameters for which modification is not performed; and causing transmitting of an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[00163] In accordance with another example embodiment, a non-transitory computer-readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: causing receiving, with a user equipment, of a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the user equipment; determining at least one of the one or more configuration parameters for which modification is not performed; and causing transmitting of an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[00164] A computer implemented system comprising: at least one processor and at least one non-transitory memory storing instructions that, when executed by the at least one processor, cause the system at least to perform: causing receiving, with a user equipment, of a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the user equipment; determining at least one of the one or more configuration parameters for which modification is not performed; and causing transmitting of an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[00165] A computer implemented system comprising: means for causing receiving, with a user equipment, of a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the user equipment; means for determining at least one of the one or more configuration parameters for which modification is not performed; and means for causing transmitting of an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

[00166] In accordance with one example embodiment, an apparatus may comprise: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; store current configuration parameters for the user equipment; store the one or more configuration identifiers; transmit, to the user equipment, a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and receive at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[00167] In accordance with one aspect, an example method may be provided comprising: receiving, with a base station, a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; storing current configuration parameters for the user equipment; storing the one or more configuration identifiers; transmitting, to the user equipment, a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and receiving at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[00168] In accordance with one example embodiment, an apparatus may comprise: circuitry configured to perform: receiving a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; circuitry configured to perform: storing current configuration parameters for the user equipment; circuitry configured to perform: storing the one or more configuration identifiers; circuitry configured to perform: transmitting, to the user equipment, a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and circuitry configured to perform: receiving at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[00169] In accordance with one example embodiment, an apparatus may comprise: processing circuitry; memory circuitry including computer program code, the memory circuitry and the computer program code configured to, with the processing circuitry, enable the apparatus to: receive a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; store current configuration parameters for the user equipment; store the one or more configuration identifiers; transmit, to the user equipment, a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and receive at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[00170] In accordance with one example embodiment, an apparatus may comprise means for: receiving a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; storing current configuration parameters for the user equipment; storing the one or more configuration identifiers; transmitting, to the user equipment, a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and receiving at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[00171] In accordance with one example embodiment, a non-transitory computer-readable medium comprising instructions stored thereon which, when executed with at least one processor, cause the at least one processor to: cause receiving of a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; cause storing of current configuration parameters for the user equipment; cause storing of the one or more configuration identifiers; cause transmitting, to the user equipment, of a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and cause receiving of at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[00172] In accordance with one example embodiment, a non-transitory computer-readable medium comprising program instructions stored thereon for performing at least the following: causing receiving of a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; causing storing of current configuration parameters for the user equipment; causing storing of the one or more configuration identifiers; causing transmitting, to the user equipment, of a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and causing receiving of at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[00173] In accordance with another example embodiment, a non-transitory program storage device readable by a machine may be provided, tangibly embodying instructions executable by the machine for performing operations, the operations comprising: causing receiving of a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; causing storing of current configuration parameters for the user equipment; causing storing of the one or more configuration identifiers; causing transmitting, to the user equipment, of a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and causing receiving of at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[00174] In accordance with another example embodiment, a non-transitory computer-readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: causing receiving of a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; causing storing of current configuration parameters for the user equipment; causing storing of the one or more configuration identifiers; causing transmitting, to the user equipment, of a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and causing receiving of at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[00175] A computer implemented system comprising: at least one processor and at least one non-transitory memory storing instructions that, when executed by the at least one processor, cause the system at least to perform: causing receiving of a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; causing storing of current configuration parameters for the user equipment; causing storing of the one or more configuration identifiers; causing transmitting, to the user equipment, of a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and causing receiving of at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[00176] A computer implemented system comprising: means for causing receiving of a configuration change request, wherein the configuration change request may comprise, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment; means for causing storing of current configuration parameters for the user equipment; means for causing storing of the one or more configuration identifiers; means for causing transmitting, to the user equipment, of a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; and means for causing receiving of at least one of: an indication to release the stored current configuration parameters, or an indication to release at least one resource requested with the configuration change request.

[00177] The term "non-transitory," as used herein, is a limitation of the medium itself (i.e. tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[00178] It should be understood that the foregoing description is only illustrative. Various alternatives and modifications can be devised by those skilled in the art. For example, features recited in the various dependent claims could be combined with each other 5 in any suitable combination (s) . In addition, features from different embodiments described above could be selectively combined into a new embodiment. Accordingly, the description is intended to embrace all such alternatives, modification and variances which fall within the scope of the appended claims.

Claims

What is claimed is:

1. An apparatus comprising means for:in response to a determination to modify one or more configuration parameters for a user equipment, determining one or more configuration identifiers for the one or more configuration parameters;storing the one or more configuration identifiers;transmitting a configuration change request, wherein the configuration change request comprises, at least, the one or more configuration identifiers;in response to a determination that the configuration change request is successful, transmitting an indication to release a previous configuration for the user equipment; andin response to a determination that at least one failure has occurred with respect to the configuration change request:releasing at least one resource requested with the configuration change request; andtransmitting at least one indication that the at least one resource requested with the configuration change request is released.

2. The apparatus of claim 1, wherein a respective one of the one or more configuration identifiers is associated with a respective one of one or more configuration parameters.

3. The apparatus of claim 1, wherein a respective one of the one or more configuration identifiers is associated with a plurality of configuration parameters of the one or more configuration parameters.

4. The apparatus of any of claims 1 through 3, wherein the configuration change request is transmitted to at least one of :a distributed unit of a base station, ora user plane centralized unit of the base station.

5. The apparatus of any of claims 1 through 4, wherein the indication to release the previous configuration is transmitted to at least one of:a distributed unit of a base station, ora user plane centralized unit of the base station.

6. The apparatus of any of claims 1 through 5, wherein the at least one indication is transmitted to at least one of:a distributed unit of a base station, ora user plane centralized unit of the base station.

7. The apparatus of any of claims 1 through 6, wherein the means configured for storing the one or more configuration identifiers comprises means configured for:storing a mapping between the one or more configuration identifiers and the one or more configuration parameters in a radio access network internal database.

8. The apparatus of any of claims 1 through 7, wherein the means are further configured for:receiving an indication of at least one configuration identifier of the one or more configuration identifiers for which the at least one failure has occurred; anddetermining that the at least one failure has occurred with respect to the configuration change request based, at least partially, on the received indication of the at least one configuration identifier.

9. The apparatus of any of claims 1 through 8, wherein the means are further configured for:receiving an indication that the at least one failure has occurred with respect to the configuration change request, comprising at least one of the one or more configuration identifiers associated with the at least one failure;determining at least one of the one or more configuration parameters that is successful based, at least partially, on the received indication; andtransmitting an indication to release at least one previous configuration based, at least partially, on the at least one configuration parameter determined to be successful.

10. The apparatus of any of claims 1 through 8, wherein the means are further configured for:detecting that the at least one failure has occurred with respect to the configuration change request;determining at least one of the one or more configuration parameters that is successful based, at least partially, on the at least one detected failure; andtransmitting an indication to release at least one previous configuration based, at least partially, on the at least one configuration parameter determined to be successful.

11. The apparatus of any of claims 1 through 10, wherein the one or more configuration parameters comprise a first set of configuration parameters and a second set of configuration parameters, wherein the first set of configuration parameters comprises one or more mandatory configuration parameters, wherein the second set of configuration parameters comprises one or more optional configuration parameters, wherein the means are further configured for one of:releasing all resources requested with the configuration change request in response to a failure with respect to the first set of configuration parameters; orreleasing only resources associated with the second set of configuration parameters in response to a failure with respect to the second set of configuration parameters .

12. An apparatus comprising:at least one processor; andat least one non-transitory memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:in response to a determination to modify one or more configuration parameters for a user equipment, determine one or more configuration identifiers for the one or more configuration parameters;store the one or more configuration identifiers;transmit a configuration change request, wherein the configuration change request comprises, at least, the one or more configuration identifiers;in response to a determination that the configuration change request is successful, transmit an indication to release a previous configuration for the user equipment; andin response to a determination that at least one failure has occurred with respect to the configuration change request:release at least one resource requested with the configuration change request; andtransmit at least one indication that the at least one resource requested with the configuration change request is released.

13. A method comprising:in response to a determination to modify one or more configuration parameters for a user equipment, determining, with a base station, one or more configuration identifiers for the one or more configuration parameters;storing the one or more configuration identifiers;transmitting a configuration change request, wherein the configuration change request comprises, at least, the one or more configuration identifiers;in response to a determination that the configuration change request is successful, transmitting an indication to release a previous configuration for the user equipment; andin response to a determination that at least one failure has occurred with respect to the configuration change request:releasing at least one resource requested with the configuration change request; andtransmitting at least one indication that the at least one resource requested with the configuration change request is released.

14. A non-transitory computer-readable medium comprising program instructions stored thereon for performing at least the following:in response to a determination to modify one or more configuration parameters for a user equipment, determining one or more configuration identifiers for the one or more configuration parameters;causing storing of the one or more configuration identifiers;causing transmitting of a configuration change request, wherein the configuration change request comprises, at least, the one or more configuration identifiers;in response to a determination that the configuration change request is successful, causing transmitting of an indication to release a previous configuration for the user equipment; andin response to a determination that at least one failure has occurred with respect to the configuration change request:causing releasing of at least one resource requested with the configuration change request; andcausing transmitting of at least one indication that the at least one resource requested with the configuration change request is released.

15. An apparatus comprising means for:receiving a configuration change request, wherein the configuration change request comprises, at least, one ormore configuration identifiers determined for one or more configuration parameters for modification for the apparatus;determining at least one of the one or more configuration parameters for which modification is not performed; and transmitting an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

16. The apparatus of claim 15, wherein a respective one of the one or more configuration identifiers is associated with a respective one of one or more configuration parameters.

17. The apparatus of claim 15, wherein a respective one of the one or more configuration identifiers is associated with a plurality of configuration parameters of the one or more configuration parameters.

18. The apparatus of any of claims 15 through 17, wherein the received configuration change request comprises a radio resource control reconfiguration request received from a base station, wherein the indication of the at least one configuration identifier is transmitted to the base station.

19. The apparatus of any of claims 15 through 18, wherein the means configured for determining the at least one configuration parameter for which modification is not performed comprises means configured for:determining that at least one failure has occurred withrespect to modification of the at least oneconfiguration parameter.

20. The apparatus of any of claims 15 through 18, wherein the means configured for determining the at least one configuration parameter for which modification is not performed comprises means configured for:determining to reject modification of the at least oneconfiguration parameter.

21. The apparatus of any of claims 15 through 20, wherein the means are further configured for:determining that modification of a configuration parameter of the one or more configuration parameters is successful, wherein the transmitted indication of the at least one configuration identifier does not comprise an indication of a configuration identifier associated with the configuration parameter.

22. An apparatus comprising:at least one processor; andat least one non-transitory memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:receive a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers determinedfor one or more configuration parameters for modification for the apparatus;determine at least one of the one or more configuration parameters for which modification is not performed; andtransmit an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

23. A method comprising:receiving, with a user equipment, a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the user equipment;determining at least one of the one or more configuration parameters for which modification is not performed; andtransmitting an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

24. A non-transitory computer-readable medium comprising program instructions stored thereon for performing at least the following:causing receiving, with a user eguipment, of a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers determined for one or more configuration parameters for modification for the user equipment;determining at least one of the one or more configuration parameters for which modification is not performed; andcausing transmitting of an indication of at least one configuration identifier, of the one or more configuration identifiers, associated with the at least one configuration parameter for which modification is not performed.

25. An apparatus comprising means for:receiving a configuration change request, wherein the configuration change request comprises, at least, one or more configuration identifiers for one or more configuration parameters to be modified for a user equipment;storing current configuration parameters for the user equipment;storing the one or more configuration identifiers;transmitting, to the user equipment, a request to modify the one or more configuration parameters based, at least partially, on the received configuration change request; andreceiving at least one of:an indication to release thestored currentconfiguration parameters, oran indication to release at least one resourcerequested with theconfiguration change request.77

Images