Generating a complete L1 / L2 trigger mobility candidate cell configuration

Abstract

A method performed by a user device (UE) for an L1 / L2 triggered mobility (LTM) cell switch procedure, including receiving an LTM reference configuration and an LTM candidate cell configuration. The method further includes combining the LTM reference configuration and the LTM candidate cell configuration to obtain the complete LTM candidate cell configuration of the LTM candidate cell. The method further includes receiving an LTM cell switch command from a source network node, the LTM cell switch command including at least an instruction for the LTM candidate cell configuration. The method further includes applying the complete LTM candidate cell configuration of the instructed LTM candidate cell configuration and sending uplink signaling to confirm completion of the LTM cell switch procedure.

Description

[Technical Field]

[0001] This disclosure relates generally to communications, and more specifically to communication methods and related devices and nodes that support wireless communications. [Background technology]

[0002] Release 18 of the Third Generation Partnership Project (3GPP) agreed on a work item known as Further NR Mobility Extensions. This work item includes a technical area titled L1 / L2-based Inter-cell Mobility. According to the Work Item Description (WID)[1], when a UE moves from the coverage area of ​​one cell to another, a serving cell change must be performed at some point. Currently, serving cell changes are triggered by L3 measurements and RRC signaling, which is triggered by PCell and PSCell changes and, where applicable, by reconfiguration with synchronization for SCell release and addition. In either case, it involves a complete L2 (and L1) reset, resulting in longer latency, greater overhead, and longer downtime than beam switch mobility. The goal of L1 / L2-based Inter-cell Mobility is to enable serving cell changes via L1 / L2 signaling to reduce latency, overhead, and downtime.

[0003] Referring to the further NR mobility extensions in 3GPP Release 18, one of the objectives of this work is to define mechanisms and procedures for L1 / L2-based inter-cell mobility to reduce mobility latency. [Overview of the project] [Means for solving the problem]

[0004] Several embodiments disclosed herein are directed toward methods performed by user equipment (UE) for L1 / L2 triggered mobility (LTM) cell switch procedures. The method includes receiving an LTM reference configuration and an LTM candidate cell configuration. The method further includes combining the LTM reference configuration and the LTM candidate cell configuration to obtain the complete LTM candidate cell configuration of the LTM candidate cell. The method further includes receiving an LTM cell switch command from a source network node. The LTM cell switch command includes at least an instruction for the LTM candidate cell configuration. The method further includes applying the complete LTM candidate cell configuration of the instructed LTM candidate cell configuration and sending uplink signaling to confirm completion of the LTM cell switch procedure.

[0005] Several other embodiments are directed towards a method performed by a source network node to initiate an L1 / L2 triggered mobility (LTM) cell switch procedure at a user equipment (UE). The method includes sending an LTM reference configuration and an LTM candidate cell configuration to the UE, and sending an LTM cell switch command to the UE to initiate the LTM cell switch procedure. The LTM cell switch command includes instructions for the LTM candidate cell configuration.

[0006] Several other embodiments are directed toward a method performed by a target network node for an L1 / L2 triggered mobility (LTM) cell switch procedure. The method includes initiating the configuration of an LTM candidate cell configuration at a user device (UE) via another network node. The method further includes receiving signaling from the UE indicating that the LTM cell switch procedure has completed successfully and that the UE has begun operating with the target network node according to the LTM candidate cell configuration.

[0007] Certain embodiments may offer one or more of the following technical advantages. The proposed embodiments may allow the UE to determine when and how to generate the complete LTM candidate cell configuration to be used when the LTM cell switch procedure is triggered by the receipt of an LTM cell switch command. Even if the LTM cell switch command includes instructions for an LTM candidate cell configuration, if the UE has also previously received an LTM reference configuration, the UE should combine the LTM reference configuration and the LTM candidate cell configuration to generate the complete LTM candidate cell configuration, and therefore the UE cannot use the LTM candidate cell configuration directly. Thus, upon receiving an LTM cell switch command that includes instructions for an LTM candidate cell configuration, the UE should use the complete LTM candidate cell configuration generated from the LTM reference configuration and the LTM candidate cell configuration during the LTM cell switch procedure. This would ensure that the LTM cell switch procedure does not fail due to an incorrect LTM candidate cell configuration applied (or used) by the UE.

[0008] The UEs and network nodes, as well as other methods performed by the corresponding UEs and networks, will become apparent to those skilled in the art by examining the following drawings and detailed description. All such additional methods and the corresponding UEs and network nodes are included in this description, within the scope of the subject matter of the invention, and intended to be protected by the appended claims. Furthermore, all embodiments disclosed herein are intended to be implemented individually or in any way and / or in any combination. [Brief explanation of the drawing]

[0009] The accompanying drawings are included to provide a further understanding of this disclosure, are incorporated into and constitute part of this application, and illustrate certain non-limiting embodiments of the concept of the present invention. In the drawings: [Figure 1] A diagram showing a system structure including entities related to several embodiments of the concept of the present invention. [Figure 2]A diagram illustrating flowcharts of the operation of the UE and related methods according to several embodiments. [Figure 3] A diagram illustrating flowcharts of the operation by source network nodes and related methods according to several embodiments. [Figure 4] A diagram illustrating flowcharts of the operation by a target network node and related methods according to several embodiments. [Figure 5] Figure 5.3.5.1-1 from 3GPP TS 38.331 V17.4.0(2023-03) shows that the RRC reconstruction was successful. [Figure 6] Figure 5.3.5.1-2 from 3GPP TS 38.331 V17.4.0(2023-03) shows that RRC reconstruction failed. [Figure 7] A diagram showing an example of a communication system according to several embodiments. [Figure 8] A diagram showing a UE (Unified Element) according to several embodiments of the concept of the present invention. [Figure 9] A diagram showing network nodes according to several embodiments. [Figure 10] A block diagram of a host that may be an embodiment of the host shown in Figure 7 according to several embodiments. [Figure 11] A block diagram showing a virtualization environment in which functions implemented by several embodiments can be virtualized. [Figure 12] A communication diagram of a host communicating with a UE via a network node over a partial wireless connection, according to several embodiments. [Modes for carrying out the invention]

[0010] Some of the embodiments envisioned herein will be described in more detail with reference to the accompanying drawings. These embodiments are provided as examples to help those skilled in the art understand the scope of the subject matter and illustrate examples of embodiments of the concept of the present invention. However, the concept of the present invention can be embodied in various forms and should not be construed as being limited to the embodiments described herein. Rather, these embodiments are provided to make this disclosure thorough and complete and to fully convey the scope of the concept of the present invention to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components of one embodiment may implicitly be present / used in another embodiment.

[0011] In addition to the above description, configuration and maintenance of multiple candidate cells [RAN2, RAN3] are defined to enable rapid application of candidate cell configurations. Furthermore, a dynamic switching mechanism between candidate serving cells (including SpCell and SCell) [RAN2, RAN1] is defined for potential application scenarios based on L1 / L2 signaling. Furthermore, L1 extensions for inter-cell beam management, including L1 measurement and reporting, and beam indication [RAN1, RAN2] are defined. Note that early involvement of RAN2 is necessary, including the possibility of further clarifying its interaction with the aforementioned statements. Furthermore, timing advance management [RAN1, RAN2] is defined. Furthermore, CU-DU interface signaling [RAN3] is defined to support L1 / L2 mobility as needed.

[0012] It should also be noted that any extensions specific to frequency range 2 (FR2), if any, are not excluded.

[0013] It should also be noted that the L1 / L2-based inter-cell mobility procedure is applicable to the following scenarios: standalone, CA and NR-DC cases with serving cell changes within a single CG; in-DU cases and inter-CU cases (applicable to standalone and CA: no new RAN interface is assumed); both in-frequency and inter-frequency; both frequency range 1 (FR1) and FR2; and source and target cells may be synchronous or asynchronous.

[0014] 3GPP has initiated discussions on solutions for L1 / L2-based inter-cell mobility (often also called LTM, L1 / L2 triggered mobility, or lower-layer triggered mobility).

[0015] The basic principle of L1 / L2 Triggered Mobility (LTM) is that the UE is pre-configured by the network with an RRC configuration for each LTM candidate cell, often also known as an LTM candidate cell configuration. Such an LTM candidate cell configuration can be one or more IEs / fields / parameters, such as an RRCReconfiguration message (e.g., delta signaling associated with a reference configuration or the UE's current configuration) or CellGroupConfig. The UE performs L1 measurements on these LTM candidate cells (e.g., CSI measurements such as SS-RSRP, L1 RSRP per SSB, etc.) and sends the corresponding L1 measurement reports to the network (e.g., PUCCH and / or PUSCH). The network then triggers an LTM cell switch to one of these LTM candidate cells in the UE by sending an LTM cell switch command (e.g., MAC CE) to the UE, after which the UE connects to the specific LTM candidate cell and switches to the RRC configuration of that LTM candidate cell.

[0016] Currently, certain challenges exist. Many details of L1 / L2-based inter-cell mobility procedures remain undefined in 3GPP. This also applies to the details of the so-called LTM cell switch procedure. RAN2 has so far concluded that if LTM is configured, the UE will receive at least an LTM candidate cell configuration from the network. Furthermore, when LTM is running, the UE receives an LTM cell switch command in the form of a MAC control element (MAC CE), triggering the LTM cell switch procedure. This command also contains the information necessary for the UE to perform the cell switch, including instructions for the LTM candidate cell configuration.

[0017] Certain aspects and embodiments of this disclosure may provide solutions to these or other problems. In this regard, RAN2 also agrees that during LTM configuration, the UE may receive an LTM reference configuration and an LTM candidate cell configuration. In this case, in order to obtain a complete LTM candidate cell configuration, the UE should apply the LTM candidate cell configuration on top of the LTM reference configuration.

[0018] One of the issues that remains unresolved is how the UE should actually generate the complete LTM candidate cell configuration. It is unclear what action the UE should take when it needs to apply the LTM candidate cell configuration on top of the LTM reference configuration.

[0019] To address the above challenges, various embodiments of this disclosure are directed to methods and corresponding operations for a user device (UE) to perform an LTM cell switch procedure. The methods and operations include receiving at least one LTM reference configuration and at least one LTM candidate cell configuration, and further combining the LTM reference configuration and the LTM candidate cell configuration to obtain the complete LTM candidate cell configuration of the LTM candidate cell. The methods and operations further include receiving an LTM cell switch command (e.g., MAC CE) from a source network node that includes instructions for an LTM candidate cell configuration, applying (or initiating use of, switching) the complete LTM candidate cell configuration of the instructed LTM candidate cell configuration, and in response, sending uplink signaling to confirm the completion of the LTM cell switch procedure.

[0020] In some embodiments, the UE first processes the received LTM reference configuration and then applies the received LTM candidate cell configuration on top of the output of the processing to generate a complete LTM candidate cell configuration.

[0021] In some embodiments, the UE generates a complete LTM candidate cell configuration, processes the LTM reference configuration and the LTM candidate cell configuration simultaneously (e.g., concurrent processing), and performs operations such as ADDITION, INTERSECT, SUBTRACTION, DIVISION to combine the LTM reference configuration and the LTM candidate cell configuration.

[0022] In some embodiments, the UE generates a complete LTM candidate cell configuration upon receiving the LTM reference configuration and the LTM candidate cell configuration. For example, the UE generates a complete LTM candidate cell configuration during the LTM configuration.

[0023] In some embodiments, the UE generates a complete LTM candidate cell configuration when the LTM cell switch procedure is triggered by receiving an LTM cell switch command that includes instructions on which LTM candidate cell configuration to use.

[0024] Certain embodiments may offer one or more of the following technical advantages. The proposed embodiments allow the UE to determine when and how to generate the complete LTM candidate cell configuration to be used when the LTM cell switch procedure is triggered by the receipt of an LTM cell switch command. Even if the LTM cell switch command includes instructions for an LTM candidate cell configuration, if the UE has also previously received an LTM reference configuration, the UE should combine the LTM reference configuration and the LTM candidate cell configuration to generate the complete LTM candidate cell configuration, and therefore the UE cannot use the LTM candidate cell configuration directly. Thus, upon receiving an LTM cell switch command that includes instructions for an LTM candidate cell configuration, the UE should use the complete LTM candidate cell configuration generated from the LTM reference configuration and the LTM candidate cell configuration during the LTM cell switch procedure. This would ensure that the LTM cell switch procedure does not fail due to an incorrect LTM candidate cell configuration applied (or used) by the UE.

[0025] Some embodiments of the concept of the present invention will be described in more detail with reference to the accompanying drawings. These embodiments are provided as examples to help those skilled in the art understand the scope of the subject matter. Additional information may also be found in the appendix documentation.

[0026] This disclosure refers to the term “L1 / L2 base cell mobility” as used in 3GPP work item descriptions, but it is used interchangeably with the terms L1 / L2 mobility, L1 mobility, L1-based mobility, L1 / L2 centric cell mobility, L1 / L2 cell mobility, L1 / L2 triggered mobility, lower-layer triggered mobility, or LTM. The basic principle is that the UE receives lower-layer signaling from the network indicating a change (or switch or activation) of its service cell (e.g., a change of PCell from a source to a target PCell), and lower-layer signaling is a message / signaling of a lower-layer protocol, which may also be referred to as an L1 / L2 cell mobility execution command or an LTM cell switch command. A change in a serving cell (e.g., a change in PCell) may also lead to a change in an Scell ​​in the same cell group, for example, if a command is triggered to cause the UE to change to a different cell group configuration of the same type (e.g., a different MCG configuration). Before the UE receives an LTM cell switch command, the UE is configured by the network with one or more LTM candidate cell configurations (e.g., receiving an RRC reconfiguration message containing at least one LTM candidate cell configuration). The LTM candidate cell configuration may include parameters in the IE CellGroupConfig of the LTM candidate cell, and / or the embedded RRC reconfiguration of the LTM candidate cell.

[0027] The term LTM cell switch procedure refers to the process by which a UE uses L1 / L2 triggered mobility (LTM) to switch (or change) a cell from a source cell to a target cell (which may be referred to here as an LTM candidate cell or adjacent cell). In the context of L1 / L2 triggered mobility (LTM), an LTM cell switch procedure may also often be known as an L1 / L2 base cell-to-cell mobility execution, an LTM execution, a dynamic switch, an LTM switch, an (LTM) cell switch, an (LTM) serving cell change, or an (LTM) cell change. In the context of some embodiments, switching to an LTM candidate cell configuration involves the UE considering that the LTM candidate cell will become its new special cell (SpCell), for example, a PCell if LTM is configured for a master cell group (MCG), and / or a PSCell if LTM is configured for a secondary cell group (SCG), or changing that SpCell from the current PCell to an LTM candidate cell.

[0028] Even when the term "switching or changing a cell" is used, it may include switching or changing the entire cell group configuration, which includes changes to SpCells (e.g., changes to PCells or PSCells) and changes to SCells in a cell group (e.g., adding, changing, and / or releasing one or more SCells).

[0029] This text refers to an LTM candidate cell, which is a cell configured for a UE when L1 / L2 trigger mobility is configured. In other words, it is a cell to which a UE can move in the LTM cell switch procedure upon receiving an LTM cell switch command. Such a cell may also be called a candidate cell, candidate, mobility candidate, non-serving cell, additional cell, target candidate cell, target candidate, etc. An LTM candidate cell is a cell to which a UE can perform measurements (e.g., CSI measurements), as a result of which the UE reports these measurements, and the network can make informed decisions about which beam (e.g., TCI status) and / or cell to switch the UE to. An LTM candidate cell may be a candidate to become a target PCell or PSCell, or a SCell in a cell group (e.g., an MCG SCell or SCG SCell).

[0030] This text refers to at least one LTM candidate cell configuration and that the UE receives at least one LTM candidate cell configuration. This is often also referred to as the LTM candidate cell configuration and may be an RRC configuration, such as one encapsulated in an RRC reconfiguration message received when the UE configures L1 / L2 trigger mobility. The LTM candidate cell configuration includes a configuration that the UE needs to initiate when performing an LTM cell switch procedure to its LTM candidate cell, for example, when it receives an LTM cell switch command to its LTM candidate cell, it becomes the target cell and the current (new) SpCell or SCell in the service frequency. The LTM candidate cell configuration includes parameters for a serving cell (or multiple serving cells such as a cell group) and includes a group of one or more parameters such as an RRCReconfiguration message, IE CellGroupConfig, or IE SpCellConfig (or IE SCellConfig for a secondary cell). An LTM candidate cell configuration may include, in one example, one or more of the following: i) a PCell configuration and one or more SCell configurations for a master cell group (MCG). i) PSCell configurations and one or more SCell configurations of a secondary cell group (SCG). When referring to LTM candidate cell configurations, the terms (LTM) candidate configuration, LTM configuration, (LTM) candidate target cell configuration, and (LTM) target candidate (cell) configuration may be used interchangeably.

[0031] The actual LTM candidate cell configuration and the exact content and / or structure of this IE and / or embedded message may be referred to as the candidate configuration RRC model, or simply the RRC model. An LTM candidate cell configuration includes the configurations that the UE must act upon when it performs (executes) L1 / L2 base cell mobility to an LTM candidate cell (which will be the target cell and the current (new) PCell, or SCell within the serving frequency) upon receiving lower layer signaling (MAC CE) indicating L1 / L2 base cell mobility to an LTM candidate cell configuration indicated by a candidate configuration identifier, identity, or index (often also called a candidate configuration ID). A UE may consist of multiple LTM candidate cell configurations, and a candidate DU (C-DU) generates and transmits multiple configurations to the CU. The actual LTM candidate cell configuration that the UE receives during LTM configuration may be delta signaling applied on top of a reference configuration, and as a result, the actual configuration that the UE uses for the LTM candidate cell at LTM cell switch is a combination of the LTM candidate cell configuration and a reference configuration (e.g., individually signaled from the network to the UE). The combination of the LTM candidate cell configuration and the reference configuration used by the UE may also be called the complete LTM candidate cell configuration. In the context of the disclosed embodiments, unless otherwise specified, this complete LTM candidate cell configuration may also be considered as the LTM candidate cell configuration.

[0032] The term "beam" can refer to the spatial direction in which a signal is transmitted (e.g., by a network node) or received (e.g., by a UE), or to a spatial filter applied to the transmitted or received signal. Therefore, transmitting a signal on a different beam can refer to transmitting a signal in a different spatial direction. When the text refers to "selected beam," it can refer to a beam index and / or a reference signal (RS) index or identifier such as a synchronous signal block (SSB) index or a CSI-RS resource identifier. Therefore, selecting a beam can refer to selecting an SSB associated with an SSB index, or selecting a beam can refer to selecting a CSI-RS associated with a CSI-RS resource identifier.

[0033] Terminology in texts Apply X to Y This is an action in which the UE first applies a configuration common to all configured LTM candidate cells (e.g., an LTM reference configuration), and then applies a second configuration (e.g., an LTM candidate cell configuration) as the difference of this first configuration.

[0034] The text also refers to the complete LTM candidate cell configuration, which is the configuration obtained by combining the first configuration (e.g., the LTM reference configuration) and the second configuration (e.g., the LTM candidate cell configuration). The complete LTM candidate cell configuration is the final configuration that the UE should apply and use when performing the LTM cell switch procedure to the LTM target candidate cell. Note that the LTM reference configuration or LTM candidate cell configuration may not be sufficient for the UE to operate on the LTM target candidate cell.

[0035] The text also refers to partially complete LTM candidate cell configurations. These can be intermediate configurations of what will ultimately become a complete LTM candidate cell configuration. For example, it may contain only the LTM reference configuration, a subset of protocol entities, and ASN.1 structures / fields / information elements for each layer of the protocol stack (e.g., MAC, RLC, PDCP, RRC entities) that will ultimately be included in a complete LTM candidate cell configuration. In some cases, a partially complete LTM candidate cell configuration may contain protocol entities and ASN.1 structures / fields / information elements for each layer of the protocol stack (e.g., MAC, RLC, PDCP, RRC entities) that exist but are empty (e.g., not configured), do not exist, or exist but are partially configured.

[0036] Figure 1 shows a system structure including entities related to several embodiments. The user device (UE) 101 is a wireless terminal such as a cellular smartphone, and may be connected to the source network node 102 via a wireless interface 104, or it may be connected to the target network node 103 to which the UE 101 is connected via a wireless interface 105.

[0037] In the context of mobility procedures such as the UE's LTM cell switch procedure, the source network node 102, often also referred to as a serving network node, controls the source cell 109 (often called a serving cell or special cell (SpCell)). The target network node 103 controls the target cell 110 (often called an adjacent cell, candidate cell, or LTM candidate cell). Each of the source network node 102 and target network node 103 can be, for example, a base station such as a gNB, or a distributed unit often called a gNB-DU or DU in the case of a distributed CU / DU (central unit / distributed unit) RAN architecture. Therefore, the source network node 1002 corresponds to the source DU (S-DU), often known as a serving DU, and the target network node 103 corresponds to the target DU (T-DU) (often also called an adjacent DU or candidate DU (C-DU)). Both the source network node 102 and target network node 103 are connected to a third network node 106, often referred to as a serving network node. The source network node and the target network node can be the same network node. In some scenarios, the source network node 102 and the target network node 103 can be connected to different third network nodes 106.

[0038] Furthermore, the third network node 106 may be a central unit (CU) often referred to as a serving CU known as gNB-CU, CU, gNB-CU-CP, or gNB-CU-UP in the case of a distributed CU / DU RAN architecture, or a core network node such as a user plane function (UPF) or access and mobility management function (AMF).

[0039] A user equipment (UE) method for performing an LTM cell switch procedure includes receiving an LTM reference configuration and an LTM candidate cell configuration. Multiple LTM reference configurations and multiple LTM candidate cell configurations may be received and used to obtain a complete LTM candidate cell configuration. For brevity, the term "LTM reference configuration" may include multiple LTM reference configurations. Similarly, the term "LTM candidate cell configuration" may include multiple LTM candidate cell configurations. The method further combines the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for an LTM candidate cell, and further receives an LTM cell switch command (e.g., MAC CE) from a source network node containing instructions for an LTM candidate cell configuration, applies (or initiates use of, switches) the complete LTM candidate cell configuration of the instructed LTM candidate cell configuration, and in response sends uplink signaling to confirm completion of the LTM cell switch procedure. Note that the steps of applying a complete LTM candidate cell configuration and / or sending uplink signaling may be optional steps for the most extensive embodiment relating to the operation and method of the UE.

[0040] Figure 2 shows a flowchart illustrating the operation by the UE and related methods according to several embodiments of the concept of the invention.

[0041] An example embodiment includes a method performed by a UE for an LTM cell switch procedure based on the above. The method includes receiving an LTM reference configuration and an LTM candidate cell configuration 200. The method also includes combining the LTM reference configuration and the LTM candidate cell configuration to obtain the complete LTM candidate cell configuration of the LTM candidate cell 202. The method includes receiving an LTM cell switch command from a source network node 204, the LTM cell switch command including instructions for at least an LTM candidate cell configuration. The method also includes applying the complete LTM candidate cell configuration of the instructed LTM candidate cell configuration 206. The method also includes sending an uplink signaling to confirm the completion of the LTM cell switch procedure 208.

[0042] In some embodiments, upon receiving the LTM reference configuration and LTM candidate cell configuration from the source network node, the UE generates a complete LTM candidate cell configuration.

[0043] In an example embodiment, combining an LTM reference configuration and an LTM candidate cell configuration to obtain a complete LTM candidate cell configuration based on the above includes receiving an LTM reference configuration and one of at least one LTM candidate cell configurations from a source network node, and generating a complete LTM candidate cell configuration in response to the said reception after a previous reception of the other of the LTM reference configuration and at least one LTM candidate cell configuration from the source network node.

[0044] In one example, the UE generates a complete LTM candidate cell configuration when it receives one. This means that the UE does not process the LTM reference configuration until it receives one (receiving the LTM candidate cell configuration triggers the generation of the complete LTM candidate cell configuration).

[0045] In one example, the UE first processes and stores the LTM reference configuration in memory (regardless of whether it has received at least one LTM candidate cell configuration), and when it receives an LTM candidate cell configuration, it begins the process of generating a complete LTM candidate cell configuration. Here, when the UE first processes and stores the LTM reference configuration, it creates a kind of "template" that is common to all received LTM candidate cell configurations.

[0046] In some embodiments, the UE generates a complete LTM candidate cell configuration upon receiving an LTM cell switch command from a source network node.

[0047] In one embodiment, combining the LTM reference configuration and the LTM candidate cell configuration to obtain the complete LTM candidate cell configuration of the LTM candidate cell based on the above includes generating the complete LTM candidate cell configuration in response to receiving an LTM cell switch command from a source network node.

[0048] In one example, the UE only begins processing and combining the LTM reference configuration and the LTM candidate cell configuration to generate a complete LTM candidate cell configuration when it receives an LTM cell switch command from the source node.

[0049] In one example, when a UE receives an LTM reference configuration (regardless of whether at least one LTM candidate cell configuration has been received), it first processes it and stores it in memory, but only processes the LTM candidate cell configurations to generate a complete LTM candidate cell configuration when an LTM cell switch command is received from the source node.

[0050] In some embodiments, the UE generates a complete LTM candidate cell configuration by applying the LTM candidate cell configuration on top of the LTM reference configuration according to one or more of the following:

[0051] Firstly, the UE can generate a complete LTM candidate cell configuration by performing a set of actions common to both the LTM reference configuration and the LTM candidate cell configuration. As an example, the UE performs the actions specified in 3GPP TS 38.331 V17.4.0(2023-03), section 5.3.5.3 only once. In this example, the UE's actions differ when processing both the LTM reference configuration and the LTM candidate cell configuration. This can be achieved, for example, by clarifying the UE actions that apply when processing an LTM reference configuration and when processing an LTM candidate cell configuration in 3GPP TS 38.331 V17.4.0(2023-03), section 5.3.5.3.

[0052] Secondly, the UE can generate a complete LTM candidate cell configuration by performing separate sets of actions on the LTM reference configuration and the LTM candidate cell configuration. For example, the set of actions performed on the LTM reference configuration may differ from another set of actions performed on the LTM candidate cell configuration. One example of this is the UE performing actions independently on the LTM reference configuration and the LTM candidate cell configuration, as specified in 3GPP TS 38.331 V17.4.0(2023-03), section 5.3.5.3.

[0053] Thirdly, the UE can generate a complete LTM candidate cell configuration by performing a set of actions, where it is up to the UE implementation to determine how to process and combine the LTM reference configuration and the LTM candidate cell configuration to generate the complete LTM candidate cell configuration.

[0054] Fourth, the UE may generate a complete LTM candidate cell configuration by performing a set of actions on the LTM reference configuration and / or LTM candidate cell configuration in accordance with rules or guidelines that define the processing of ASN.1 structures / fields / information elements in the LTM reference configuration and LTM candidate cell configuration.

[0055] For example, a rule or guideline may specify whether to use the values ​​of the ASN.1 structure / field / information element in the LTM reference configuration or the values ​​of the corresponding ASN.1 structure / field / information element in the LTM candidate cell configuration.

[0056] For example, a rule or guideline may stipulate the use of operations on the values ​​of ASN.1 structures / fields / information elements in an LTM reference configuration and / or on the values ​​of corresponding ASN.1 structures / fields / information elements in an LTM candidate cell configuration. For example, the operations may be ADDITION, INTERSECT, SUBTRACTION, DIVISION, MULTIPLICATION, LOGICAL AND, LOGICAL OR, LOGICAL XOR, CONCATENATION, REPLACEMENT, etc.

[0057] For example, rules or guidelines may specify how to handle certain types of ASN.1 structures / fields / information elements in LTM reference configurations and LTM candidate cell configurations. For example, the type could be one of SEQUENCE, SetupRelease, ToAddModList, ToReleaseList, lists, ENUMERATED, CHOICE, OCTET STRING, INTEGER, BOOLEAN, or BIT STRING. For example, how to handle them might involve adding, concatenating, joining, deleting, or replacing individual substructures, subfields / element parts of ASN.1 structures / fields / information elements in LTM reference configurations, and individual element parts of corresponding ASN.1 structures / fields / information elements in LTM candidate cell configurations. For example, this might occur if these individual substructures, subfields / element parts of ASN.1 structures / fields / information elements are part of a list. For example, the order in which processing is performed could be the sequence in which specific operations are carried out that involve both the ASN.1 structure / field / information element of the LTM reference configuration and the corresponding ASN.1 structure / field / information element of the LTM candidate cell configuration.

[0058] For example, rules or guidelines may specify how to handle certain values ​​of ASN.1 structures / fields / information elements in LTM reference configurations and LTM candidate cell configurations.

[0059] For example, rules or guidelines may specify how to handle the presence of ASN.1 structures / fields / information elements in LTM reference configurations and LTM candidate cell configurations. For instance, presence can be absent / present, optional, or conditional. For example, how to handle cases where an optional ASN.1 structure / field / information element is absent in the LTM reference configuration but a corresponding ASN.1 structure / field / information element is present in the LTM candidate cell configuration, or vice versa. For example, how to handle cases where a conditional ASN.1 structure / field / information element is absent in the LTM reference configuration but a corresponding ASN.1 structure / field / information element is present in the LTM candidate cell configuration, or vice versa.

[0060] For example, rules or guidelines may specify how to handle specific Need codes for ASN.1 structures / fields / information elements in LTM reference configurations and LTM candidate cell configurations. For instance, Need codes could be specified (S), maintained (M), no action (N), or released (R). For example, how to handle cases where an ASN.1 structure / field / information element with a particular Need code does not exist in the LTM reference configuration, but the corresponding ASN.1 structure / field / information element exists in the LTM candidate cell configuration, or vice versa.

[0061] For example, rules or guidelines may specify how to handle the conditions of ASN.1 structures / fields / information elements in LTM reference configurations and LTM candidate cell configurations.

[0062] For example, rules or guidelines may specify how to handle extensions to ASN.1 structures / fields / information elements in LTM reference configurations and LTM candidate cell configurations.

[0063] In the embodiment example, combining an LTM reference configuration and an LTM candidate cell configuration to obtain a complete LTM candidate cell configuration based on the above includes applying the LTM candidate cell configuration on top of the LTM reference configuration in accordance with one or more of the following: performing a set of actions common to the LTM reference configuration and the LTM candidate cell configuration; performing a separate set of actions on the LTM reference configuration and the LTM candidate cell configuration; and performing a set of actions on the LTM reference configuration and / or LTM candidate cell configuration in accordance with rules or guidelines that define the processing of ASN.1 structures, fields, or information elements of the LTM reference configuration and the LTM candidate cell configuration.

[0064] In the above-described embodiment, performing a set of actions on the LTM reference configuration and LTM candidate cell configuration in accordance with rules or guidelines defining the processing of the ASN.1 structure, fields, or information elements of the LTM reference configuration and LTM candidate cell configuration includes determining from the rules or guidelines at least one of the following: the operation to use for the value of the ASN.1 structure, fields, or information elements of the LTM reference configuration and / or LTM candidate cell configuration; the type of the ASN.1 structure, fields, or information elements of the LTM reference configuration and / or LTM candidate cell configuration. Operations used based on the P, the order in which operations are performed on the ASN.1 structure, fields, or information element values ​​of the LTM reference configuration and / or LTM candidate cell configuration, operations used based on the ASN.1 structure, fields, or information element values ​​of the LTM reference configuration and / or LTM candidate cell configuration, operations used based on the existence of the ASN.1 structure, fields, or information element of the LTM reference configuration and / or LTM candidate cell configuration, and operations used based on the need code of the ASN.1 structure, fields, or information element of the LTM reference configuration and / or LTM candidate cell configuration.

[0065] In some embodiments, upon receiving an LTM reference configuration and an LTM candidate cell configuration, the UE prepares a partially complete LTM candidate cell configuration, and upon receiving an LTM cell switch command, the UE generates a complete LTM candidate cell configuration.

[0066] In the embodiments described above, the method further includes preparing a portion of the complete LTM candidate cell configuration based on the reception of an LTM reference configuration and an LTM candidate cell configuration. The method further includes preparing a complete LTM candidate cell configuration based on the portion in response to the reception of an LTM cell switch command.

[0067] In one example, when the UE receives an LTM reference configuration and an LTM candidate cell configuration, the UE processes only the LTM reference configuration and prepares a placeholder for the configuration that will be completed when it receives an LTM cell switch command, which will also process the LTM candidate cell configuration.

[0068] In one possible scenario, when the UE processes the LTM reference configuration, it might create (build, create, configure, and set the contents of) the initial configurations, protocol entities, and ASN.1 structures / fields / information elements for each layer of the protocol stack (e.g., MAC, RLC, PDCP, RRC entities), and then the final configurations of these configurations, protocol entities, and ASN.1 structures / fields / information elements are only obtained when processing the LTM candidate cell configuration (e.g., when an LTM cell switch command is received).

[0069] In one possible scenario, the UE might handle both the LTM reference configuration and the LTM candidate cell configuration by creating the configurations, protocol entities, and ASN.1 structure / field / information elements for each layer of the protocol stack (e.g., MAC, RLC, PDCP, RRC entities) that would be used when executing the LTM cell switch procedure. However, these configurations, protocol entities, and ASN.1 structure / field / information are only applied (or used, or configured) when the LTM cell switch command is received.

[0070] In some embodiments, the generation of a complete LTM candidate cell configuration by the UE is left to the UE implementation. Even when this is left to the UE implementation, several high-level principles can be specified, such as the UE applying an LTM reference configuration on top of the LTM candidate cell configuration. Instructions that can be incorporated into the specifications include whether the UE should generate a complete LTM candidate cell configuration upon receiving the LTM reference configuration and the LTM candidate cell configuration, or upon receiving an LTM cell switch command.

[0071] In some embodiments, the UE receives both the LTM reference configuration and the LTM candidate cell configuration, but considers the LTM candidate cell configuration to be the complete LTM candidate cell configuration. In this case, the UE does not process (or apply) the received LTM reference configuration, meaning that the LTM candidate cell configuration contains all the configurations necessary to operate on the target LTM candidate cell when the LTM cell switch procedure is initiated.

[0072] In the embodiment example, combining the LTM reference configuration and the LTM candidate cell configuration to obtain the complete LTM candidate cell configuration of the LTM candidate cell based on the above includes defining the LTM candidate cell configuration as the complete LTM candidate cell configuration.

[0073] In one example, the indication that an LTM candidate cell configuration is a complete LTM candidate cell configuration is received by the source network node within the LTM cell switch command.

[0074] In one example, the indication that an LTM candidate cell configuration is a complete LTM candidate cell configuration is received by the source network node as part of a message (e.g., an RRCReconfiguration message) that includes the LTM reference configuration and one or more LTM candidate cell configurations.

[0075] In one example, the indication that an LTM candidate cell configuration is a complete LTM candidate cell configuration is received within the LTM candidate cell configuration itself.

[0076] In one example, the indication that an LTM candidate cell configuration is a complete LTM candidate cell configuration is implicit based on the presence or absence of an LTM reference configuration. For example, if an LTM reference configuration exists, a complete LTM candidate cell configuration should be generated by applying the LTM candidate cell configuration on top of the LTM reference configuration, but if an LTM reference configuration does not exist, the LTM candidate cell configuration is a complete LTM candidate cell configuration. Here, "non-existent" or "existent" may mean that the ASN.1 field / structure / information element is "empty" (if non-existent) or contains some information (if present).

[0077] In some embodiments, when an LTM cell switch procedure is executed upon receiving an LTM cell switch command that includes instructions for an LTM candidate cell configuration, the UE performs one or more of the following actions before applying the corresponding complete LTM candidate cell configuration related to the instructed LTM candidate cell configuration:

[0078] Firstly, if timers, counters, or any other configurations need to be maintained in continuity at the target source node specified in the LTM cell switch command, the UE copies such configurations from the current UE configuration to the complete LTM candidate cell configuration. An example is the handling of timers and counters. If these timers and counters should not be stopped when the LTM cell switch procedure is executed, the UE takes a snapshot of these timers and counters and continues to use their current values ​​at the target source node where the LTM cell switch procedure was executed. For example, if timer 1 = 5 seconds and counter 1 = 10 at the start of the LTM cell switch procedure, after the LTM cell switch procedure is executed, the UE will have initial values ​​of timer 1 = 5 seconds and counter 1 = 10 when it starts operating at the target source cell where the LTM cell switch procedure was executed. Note that in this case, the initial value of the timers may be greater than 5 seconds, taking into account the time it takes for the UE to switch from the source network node to the target network node (since the timers are still operating during this period). An example is the handling of the PDCP and SDAP layers. One of the prerequisites for LTM is that PDCP and SDAP are not released during LTM. In such cases, the UE can simply copy and paste the configurations related to such entities from the current UE configuration to the complete LTM candidate cell configuration before performing the LTM cell switch procedure.

[0079] Secondly, the UE clears all dedicated configurations from the current UE configuration. These are configurations received from the source network node via dedicated signaling.

[0080] Thirdly, the UE clears all common configurations from the current UE configuration. These are configurations received from the source network node via system information (broadcast).

[0081] An example embodiment, based on the above, further includes, after receiving an LTM cell switch command 204 and before applying the complete LTM candidate cell configuration 206, copying timers, counters, and / or configurations from the current UE configuration to the complete LTM candidate cell configuration; clearing dedicated configurations previously received from source network nodes in the current UE configuration via dedicated signaling; clearing common configurations previously received from source network nodes in the current UE configuration via system information; and performing an L2 reset.

[0082] In some embodiments, if the LTM cell switch procedure is performed by receiving an LTM cell switch command which includes instructions for an LTM candidate cell configuration, the UE performs one or more of the following actions before applying the corresponding complete LTM candidate cell configuration associated with the instructed LTM candidate cell configuration:

[0083] Fourth, the UE performs an L2 reset. Here, the L2 reset may imply a MAC reset, RLC re-establishment, PDCP recovery, or any combination thereof.

[0084] Fifth, if a dedicated configuration does not exist within the complete LTM candidate cell configuration, the UE applies a default configuration. An example is the MAC entity. If the UE needs to reset the MAC entity when performing the LTM cell switch procedure, but the complete LTM candidate cell configuration does not provide a MAC configuration, the UE applies the MAC default configuration specified in 3GPP TS 38.331 V17.4.0 (2023-03).

[0085] Sixth, the UE applies the complete LTM candidate cell configuration to the target cell. For example, the UE begins using any resources that were added or modified as a result of applying the complete LTM candidate cell configuration. For example, the UE stops using any resources that were freed as a result of applying the complete LTM candidate cell configuration.

[0086] Seventh, the UE sends UL signaling to the target network node to confirm that the LTM cell switch procedure has been successfully completed.

[0087] An example embodiment, based on the above, includes, after receiving an LTM cell switch command 204 and before applying the complete LTM candidate cell configuration 206, applying a default configuration if no dedicated configuration exists in the complete LTM candidate cell configuration, applying the complete LTM candidate cell configuration to the target cell, and sending uplink signaling to the target network node to confirm the completion of the LTM cell switch procedure.

[0088] The following embodiments relating to the methods performed by the source network node (source DU) are described herein.

[0089] In various embodiments, a method is described at a source network node (source DU), such as a source gNB, source DU, or source CU, for initiating an LTM cell switch procedure at a UE, the method comprising transmitting at least one LTM reference configuration and at least one LTM candidate cell configuration. Multiple LTM reference configurations and multiple LTM candidate cell configurations may be transmitted. For brevity, the term "LTM reference configuration" may include multiple LTM reference configurations. Similarly, the term "LTM candidate cell configuration" may include multiple LTM candidate cell configurations. The method further comprises transmitting an LTM cell switch command (e.g., MAC CE) for initiating an LTM cell switch procedure, which includes instructions for the LTM candidate cell configurations.

[0090] Figure 3 shows a flowchart illustrating the operation by a source network node and related methods according to several embodiments of the concept of the present invention.

[0091] An example embodiment is a method performed by a source network node to initiate an LTM cell switch procedure at the UE based on the above. The method includes sending an LTM reference configuration and an LTM candidate cell configuration to the UE 300. The method also includes sending an LTM cell switch command to the UE 302 to initiate an LTM cell switch procedure. The LTM cell switch command includes instructions for the LTM candidate cell configuration.

[0092] In some embodiments, a message sent to the UE containing the LTM candidate cell configuration includes an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.

[0093] In one example embodiment, based on the above, the LTM candidate cell configuration sent to the UE includes an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.

[0094] In one example, the instruction for the UE to consider an LTM candidate cell configuration as a complete LTM candidate cell configuration is explicit.

[0095] In one example, the instruction for the UE to consider an LTM candidate cell configuration as a complete LTM candidate cell configuration is implicit, indicating to the UE that the submitted LTM reference configuration should not be considered in generating the complete LTM candidate cell configuration related to the LTM candidate cell configuration.

[0096] In one example, the message sent to the UE regarding the LTM candidate cell configuration is RRCReconfiguration.

[0097] In some embodiments, an indication that the LTM candidate cell configuration is a complete LTM candidate cell configuration is sent to the UE in a message that is not the same as the message to which the LTM candidate cell configuration is sent.

[0098] In one embodiment, based on the above, an instruction to whether the LTM candidate cell configuration is a complete LTM candidate cell configuration is sent to the UE in a message that is not the same as the message to which the LTM candidate cell configuration is sent.

[0099] In one example, this message could be a MAC CE, L1 signaling, or RRC message.

[0100] The following embodiments relating to the methods performed by the target network node (target DU) are described herein.

[0101] Various embodiments describe a scenario in which a target network node (Target DU), such as a Target gNB, Target DU, or Target CU, configures an LTM candidate cell configuration at the UE (e.g., via a third network node or source network node), and further receives signaling from the UE indicating that the LTM cell switching procedure has been successfully completed and the UE has started operating at the target network node according to the received LTM candidate cell configuration.

[0102] Figure 4 shows a flowchart illustrating the operation by a target network node and related methods according to several embodiments of the concept of the present invention.

[0103] In some embodiments, based on the above, the method is performed by the target network node for an L1 / L2 triggered mobility (LTM) cell switch procedure. The method includes initiating the configuration of an LTM candidate cell configuration at a user device (UE) via another network node 400. The method also includes receiving a signaling from the UE indicating that the LTM cell switch procedure has been successfully completed and that the UE has started working with the target network node according to the LTM candidate cell configuration 402.

[0104] In some embodiments, the LTM candidate cell configuration includes an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.

[0105] In the embodiment example, based on the above, the LTM candidate cell configuration includes an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.

[0106] In one example, the instruction for the UE to consider an LTM candidate cell configuration as a complete LTM candidate cell configuration is explicit.

[0107] In one example, the instruction for the UE to consider an LTM candidate cell configuration as a complete LTM candidate cell configuration is implicit, indicating to the UE that the submitted LTM reference configuration should not be considered in generating the complete LTM candidate cell configuration related to the LTM candidate cell configuration.

[0108] Further embodiments are described in the context of operational implementations that may be used in 3GPP TS 38.331 Rel-18 V17.4.0(2023-03). Several embodiments that have been added to the current 3GPP TS 38.331 Rel-18 V17.4.0(2023-03) are indicated by underlining.

[0109] Next, we will explain RRC reconstruction.

[0110] Figure 5 shows the corresponding Figure 5.3.5.1-1 from 3GPP TS 38.331 V17.4.0 (2023-03), illustrating the case where RRC reconstruction is successful.

[0111] Figure 6 shows the corresponding Figure 5.3.5.1-2 from 3GPP TS 38.331 V17.4.0 (2023-03), illustrating the case where RRC reconstruction fails.

[0112] The purpose of this procedure is to modify RRC connections, such as establishing / modifying / releasing RB / BH RLC channels / Uu relay RLC channels / PC5 relay RLC channels, performing reconfigurations with synchronization, setting / modifying / releasing measurements, adding / modifying / releasing SCells and cell groups, adding / modifying / releasing conditional handover configurations, adding / modifying / releasing conditional PSCell modification or conditional PSCell addition configurations, and adding / modifying LTM candidate cells. As part of the procedure, NAS-specific information may be transferred from the network to the UE. RRC reconfiguration for performing reconfiguration with synchronization includes, but is not limited to, the following cases: - Synchronized reconfiguration and security key refresh, including RA to Pcell / PSCell, MAC reset, security refresh, and re-establishment of RLC and PDCP triggered by explicit L2 indicators; - Reconfiguration with synchronization without security key refresh, including RA to Pcell / PSCell, MAC reset, RLC re-establishment, and PDCP data recovery (in the case of AM DRB or AM MRB) triggered by an explicit L2 indicator. - Reconfiguration and security key refresh with synchronization for DAPS, including RA to target Pcell and establishment of target MAC, and, - For non-DAPS bearers: Security refresh and re-establishment of RLC and PDCP triggered by an explicit L2 indicator; - For DAPS bearers: Establish RLC for the target Pcell, refresh security, and reconfigure PDCP to add encryption, integrity protection, and ROHC functions to the target Pcell; - For SRB: Refresh the security of the target Pcell and establish RLC and PDCP; - Reconfiguration with synchronization for DAPS without security key refresh, including RA to target Pcell and establishment of target MAC; and - For non-DAPS bearers: RLC re-establishment and PDCP data recovery triggered by an explicit L2 indicator (for AM DRB or AM MRB). - For DAPS bearers: Reconfiguration of PDCP to add RLC establishment for target Pcell, encryption function, integrity protection function, and ROHC function for target Pcell; - For SRB: Establish RLC and PDCP of the target Pcell. - Reconfiguration with synchronization for switching from direct to indirect paths, without involvement of the target side's RA and without PDCP re-establishment / PDCP data recovery (in the case of AM DRB) triggered by an explicit L2 indicator. In (NG)EN-DC and NR-DC, SRB3 can be used for measurement configuration and reporting, (re)configuration and reporting of UE assistance for power saving, (re)configuration and reporting of IAB node IP addresses, (re)configuration of MAC, RLC, BAP, physical layer, RLF timers and constants of SCG configuration, reconfiguration of PDCP of DRB associated with S-KgNB or SRB3, reconfiguration of SDAP of DRB associated with S-KgNB in ​​NGEN-DC and NR-DC, adding / modifying / releasing conditional PSCell change configurations when MN involvement is not required for (re)configuration, and sending RRC messages between MN and UE during fast MCG link recovery. In (NG)EN-DC and NR-DC, unless RRCReconfiguration is received within DLInformationTransferMRDC, RRCReconfiguration received via SRB3 includes only measConfig, radioBearerConfig, conditionalReconfiguration, bap-Config, iab-IP-AddressConfigurationList, otherConfig, and / or secondaryCellGroup. 5.3.5.2 Start The network may initiate the RRC reconfiguration procedure for UEs with RRC_CONNECTED. The network applies the procedure as follows: - RB establishment (except SRB1 established during RRC connection establishment) is performed only if AS security is activated; - Establishing a BH RLC channel for IAB is only performed if AS security is activated; - The establishment of Uu relay RLC channels and PC5 relay RLC channels (other than SL-RLC0 and SL-RLC1) for L2 U2N relay UEs is performed only when AS security is activated, and the establishment of PC5 relay RLC channels (other than SL-RLC0 and SL-RLC1) for L2 U2N remote UEs is performed only when AS security is activated; - The addition of secondary cell groups and SCells is only performed when AS security is activated; -reconfigurationWithSync is included in secondaryCellGroup only if at least one RLC bearer or BH RLC channel is configured in the SCG; -reconfigurationWithSync is included in masterCellGroup only if AS security is activated and SRB2 has at least one DRB or multicast MRB, or in the case of IAB, SRB2 is configured and not suspended; - The conditionalReconfiguration of CPC is only included if at least one RLC bearer is configured in SCG; -The conditional reconfiguration of the CHO or CPA is only included if AS security is activated and SRB2 is configured with at least one DRB or multicast MRB, or in the case of IAB, SRB2 is configured and not suspended. -LTM's ltm-CandidateConfig is only included if AS security is activated, SRB2 is configured with at least one DRB, and it is not suspended. Editor's note: Whether to apply ltm-CandidateConfig to MBS or IAB depends on FFS. 5.3.5.3 Receiving RRCReconfiguration via UE When a UE receives an RRCReconfiguration or performs a conditional reconfiguration (CHO, CPA, or CPC), it must perform the following actions: 1>If RRCReconfiguration is applied due to a conditional reconfiguration being performed during cell selection while timer T311 was running, as defined in 5.3.7.3: 2> If present, delete all entries in MCG and SCG VarConditionalReconfig; 1>If RRCReconfiguration includes daps-SourceRelease: 2> Reset the source MAC and release the source MAC configuration; 2>Regarding each DAPS bearer: 3> Release the RLC entity and the associated logical channels of the source SpCell as specified in TS 38.322[4], section 5.1.3; 3> Reconfigure the PDCP entity to release the DAPS as specified in TS 38.323[5]; 2>Regarding each SRB: 3> Release the PDCP entity of the source SpCell; 3> Release the RLC entity and the associated logical channels of the source SpCell as specified in TS 38.322[4], section 5.1.3; 2> Release the physical channel configuration of the source SpCell; 2> Key used in source SpCell (K gNB key, K RRCenc key, K RRCint key, K Upint Key, and K Upenc Discard the key if one exists; 1>If RRCReconfiguration is received via another RAT (i.e., inter-RAT handover to NR): 2>When RRCReconfiguration does not include fullConfig and the UE is connected to 5GC (i.e., delta signaling during handover within 5GC): 3> Reuse the source RAT SDAP and PDCP configuration if available (i.e., the current SDAP / PDCP configuration of all RBs from the source E-UTRA RAT before receiving the inter-RAT HO RRCReconfiguration message); 1>Otherwise: 2>If RRCReconfiguration includes fullConfig: 3> Perform the full configuration procedure as specified in 5.3.5.11; 1>If RRCReconfiguration includes masterCellGroup: 2> Perform the cell group configuration of the received masterCellGroup according to 5.3.5.5; 1>If RRCReconfiguration includes masterKeyUpdate: Perform the AS security key update procedure as specified in 2>5.3.5.7; 1>If RRCReconfiguration includes sk-Counter: 2> Perform the security key update procedure as specified in 5.3.5.7; 1>If RRCReconfiguration includes secondaryCellGroup: 2> Perform the SCG cell group configuration according to 5.3.5.5; 1>If RRCReconfiguration includes mrdc-SecondaryCellGroupConfig: 2> If mrdc-SecondaryCellGroupConfig is set to setup: 3> If mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd: Perform MR-DC release as specified in section 4>5.3.5.10; 3>If the received mrdc-SecondaryCellGroup is set to nr-SCG: 4> For the RRCReconfiguration message included in nr-SCG, perform RRC reconfiguration according to section 5.3.5.3; 3>If the received mrdc-SecondaryCellGroup is set to eutra-SCG: 4>For the RRCConnectionReconfiguration message included in eutra-SCG, perform RRC connection reconfiguration as specified in TS 36.331

[10] , section 5.3.5.3; 2> Otherwise (mrdc-SecondaryCellGroupConfig is set to release): Perform MR-DC release as specified in Section 3>5.3.5.10; 1>If the RRCReconfiguration Message includes radioBearerConfig: 2> Perform the wireless bearer configuration according to 5.3.5.6; 1>If the RRCReconfiguration Message includes radioBearerConfig2: 2> Perform the wireless bearer configuration according to 5.3.5.6; 1>If the RRCReconfiguration message contains measConfig: Perform the measurement configuration procedure as specified in 2>5.5.2; 1>If the RRCReconfiguration message contains dedicatedNAS-MessageList: 2> Transfer each element of the dedicatedNAS-MessageList to the upper layer in the same order in which it is listed; 1>If the RRCReconfiguration Message includes dedicatedSIB1-Delivery: 2>Execute the action upon receiving SIB1 as specified in 5.2.2.4.2; Note 0: If this RRCReconfiguration is associated with an MCG and includes reconfigurationWithSync in spCellConfig and dedicatedSIB1-Delivery, the UE will initiate a request to obtain the required SIB (if necessary) in accordance with Section 5.2.2.3.5 only after the random access procedure to the target SpCell is complete. 1>If RRCReconfiguration MessagededicatedSystemInformationDelivery is included: 2>Execute the action upon receiving system information as specified in 5.2.2.4; 1>If the RRCReconfiguration message contains dedicatedPosSysInfoDelivery: 2> Perform the action upon receiving posSIB(s) as specified in Section 5.2.2.4.16; 1>If the RRCReconfiguration Message includes otherConfig: 2> Perform the other configuration steps as specified in 5.3.5.9; 1>If the RRCReconfiguration Message includes bap-Config: 2> Perform the BAP configuration procedure as specified in 5.3.5.12; 1>If the RRCReconfiguration Message includes iab-IP-AddressConfigurationList: 2>If iab-IP-AddressToReleaseList is included: Release the IP address as specified in 3>5.3.5.12a.1.1; 2>If iab-IP-AddressToAddModList is included: 3> Perform IAB IP address addition / update as specified in 5.3.5.12a.1.2; 1>If RRCReconfiguration MessageconditionalReconfiguration is included: 2> Perform a conditional reconfiguration as specified in 5.3.5.13; 1>If the RRCReconfiguration message contains needForGapsConfigNR: 2>If needForGapsConfigNR is set to setup: 3> It is assumed that it is configured to provide measurement gap requirement information for the NR target band; 2>Otherwise: 3> It is considered that the system is not configured to provide measurement gap requirement information for the NR target band; 1>If the RRCReconfiguration message contains needForGapNCSG-ConfigNR: 2>If needForGapNCSG-ConfigNR is set to setup: 3> It is assumed that it is configured to provide measurement gap and NCSG requirement information for the NR target band; 2>Otherwise: 3> It is considered not configured to provide measurement gap and NCSG requirement information for the NR target band; 1>If the RRCReconfiguration message contains needForGapNCSG-ConfigEUTRA: 2>If needForGapNCSG-ConfigEUTRA is set to setup: 3> It is assumed that the system is configured to provide measurement gap and NCSG requirement information for the E-UTRA target band; 2>Otherwise: 3> It is considered that the system is not configured to provide measurement gap and NCSG requirement information for the E-UTRA target band; 1>If the RRCReconfiguration Message contains sl-ConfigDedicatedNR: 2> Perform the side-link-specific configuration procedure as specified in 5.3.5.14; Note 0a: If sl-ConfigDedicatedNR is received embedded within an E-UTRA RRCConnectionReconfiguration message, the UE does not construct an NR RRCReconfigurationComplete message for the received sl-ConfigDedicatedNR. 1>If the RRCReconfiguration Message contains sl-L2RelayUE-Config: Perform the L2 U2N relay UE configuration procedure as specified in 2>5.3.5.15; 1>If the RRCReconfiguration message contains sl-L2RemoteUE-Config: 2> Perform the L2 U2N remote UE configuration procedure as specified in 5.3.5.16; 1>If the RRCReconfiguration Message includes dedicatedPagingDelivery: 2>Execute the Paging message reception procedure as specified in 5.3.2.3; 1>If the RRCReconfiguration Message includes sl-ConfigDedicatedEUTRA-Info: 2>Perform the relevant procedures for V2X sidelink communication in accordance with TS 36.331

[10] , sections 5.3.10 and 5.5.2; 1>If the RRCReconfiguration Message contains ul-GapFR2-Config: Perform the FR2 UL gap configuration procedure as specified in 2>5.3.5.13c; 1>If the RRCReconfiguration Message includes musim-GapConfig: Perform the MUSIM gap configuration procedure as specified in 2>5.3.5.9a; 1>If the RRCReconfiguration Message includes appLayerMeasConfig: Perform the application layer measurement configuration procedure as specified in 2>5.3.5.13d; 1>If the RRCReconfiguration message contains ue-TxTEG-RequestUL-TDOA-Config: 2>If ue-TxTEG-RequestUL-TDOA-Config is set to setup: 3>Execute the UE positioning assistance information procedure as specified in 5.7.14; 2>Otherwise: 3> Release the configuration of UE positioning assistance information; 1>If the RRCReconfiguration message contains ltm-CandidateConfig: Perform the LTM configuration procedure as specified in 2>5.3.5.x; 1>Set the contents of the RRCReconfigurationComplete message as follows: Note X: If this procedure is initiated by generating a complete LTM candidate cell configuration, the UE should generate only one RRCReconfigurationComplete after the generation of the complete LTM candidate cell configuration is complete. 2>If RRCReconfiguration includes a masterCellGroup that contains reportUplinkTxDirectCurrent: 3>Include an uplinkTxDirectCurrentList in each MCG serving cell that has UL; 3> If present, include the uplinkDirectCurrentBWP-SUL for each MCG serving cell in which a SUL carrier is configured in the uplinkTxDirectCurrentList; 2>If RRCReconfiguration includes a masterCellGroup containing reportUplinkTxDirectCurrentTwoCarrier: 3>Include a list of uplinkTxDC locations for the in-band uplink carrier aggregation configured within the MCG in uplinkTxDirectCurrentTwoCarrierList; 2>If RRCReconfiguration includes a masterCellGroup that contains reportUplinkTxDirectCurrentMoreCarrier: 3>Include a list of uplinkTxDC locations for the in-band uplink carrier aggregation configured within the MCG in uplinkTxDirectCurrentMoreCarrierList; 2>If RRCReconfiguration contains a secondaryCellGroup that includes reportUplinkTxDirectCurrent: 3>Include an uplinkTxDirectCurrentList in each SCG serving cell that has UL; 3> If present, include the uplinkDirectCurrentBWP-SUL for each SCG serving cell in which a SUL carrier is configured in the uplinkTxDirectCurrentList; 2>If RRCReconfiguration contains a secondaryCellGroup that includes reportUplinkTxDirectCurrentTwoCarrier: 3>Include a list of uplinkTxDC locations for in-band uplink carrier aggregations configured within the SCG in uplinkTxDirectCurrentTwoCarrierList; 2>If RRCReconfiguration contains a secondaryCellGroup that includes reportUplinkTxDirectCurrentMoreCarrier: 3>Include a list of uplinkTxDC locations for in-band uplink carrier aggregations configured within the SCG in uplinkTxDirectCurrentMoreCarrierList; Note 0b: The UE does not expect to receive reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier in both masterCellGroup and secondaryCellGroup. The network consists of at most one of reportUplinkTxDirectCurrent, reportUplinkTxDirectCurrentTwoCarrier, or reportUplinkTxDirectCurrentMoreCarrier in a single RRC message. 2>If the RRCReconfiguration message contains mrdc-SecondaryCellGroupConfig where mrdc-SecondaryCellGroup is set to eutra-SCG: 3>Include the E-UTRA RRCConnectionReconfigurationComplete message in eutra-SCG-Response in accordance with TS 36.331

[10] , section 5.3.5.3; 2>If the RRCReconfiguration message contains mrdc-SecondaryCellGroupConfig where mrdc-SecondaryCellGroup is set to nr-SCG: 3>Include the SCG RRCReconfigurationComplete message in nr-SCG-Response; 3> If a conditional reconfiguration is performed and the RRCReconfiguration message is applied, and the RRCReconfiguration message does not include reconfigurationWithSync in masterCellGroup: 4>Include the condReconfigId of the selected cell in selectedCondRRCReconfig for conditional reconfiguration execution; 2> If RRCReconfiguration includes reconfigurationWithSync in MCG's spCellConfig: 3>If the UE has log measurement data available for NR, and the RPLMN is included in the plmn-IdentityList stored in VarLogMeasReport: 4>Include logMeasAvailable in the RRCReconfigurationComplete message; 4>If the Bluetooth measurement results are included in the log measurement data available to the NR held by the UE: 5>Include logMeasAvailableBT in the RRCReconfigurationComplete message; 4>If the WLAN measurement results are included in the log measurement data available to NR that the UE has: 5>Include logMeasAvailableWLAN in the RRCReconfigurationComplete message; 3>If VarLogMeasReport contains sigLoggedMeasType: 4>When the T330 timer is running and the log measurement configuration is for NR: 5> Set sigLogMeasConfigAvailable to true in the RRCReconfigurationComplete message; 4>Otherwise: 5>If the UE has log measurement data available to NR: 6> Set sigLogMeasConfigAvailable to false in the RRCReconfigurationComplete message; 3>If the UE has connection establishment failure or connection reopening failure information available in VarConnEstFailReport or VarConnEstFailReportList, and the RPLMN is equal to the plmn-Identity stored in at least one entry in VarConnEstFailReport or VarConnEstFailReportList: 4>Include connEstFailInfoAvailable in the RRCReconfigurationComplete message; 3>If the UE has available radio link failure or handover failure information in the VarRLF-Report, and the RPLMN is included in the plmn-IdentityList stored in the VarRLF-Report; or 3>If the UE has radio link failure or handover failure information available in the VarRLF-Report of TS 36.331

[10] , and the UE is compatible with cross-RAT RLF reporting, and the RPLMN is included in the plmn-IdentityList stored in the VarRLF-Report of TS 36.331

[10] : 4>Include rlf-InfoAvailable in the RRCReconfigurationComplete message; 3>If successHO-Config was configured when the UE connected to the source Pcell; and, As defined in 3>5.3.7.3, if RRCReconfiguration is applied due to a conditional reconfiguration being performed during cell selection while timer T311 was running: 4>If the random access procedure triggered for reconfigurationWithSync of spCellConfig in MCG completes successfully, perform the action for determining the success of the handover, as specified in Section 5.7.10.6; 3>If the UE has available handover success information in the VarSuccessHO-Report, and the RPLMN is included in the plmn-IdentityList stored in the VarSuccessHO-Report: 4>Include successHO-InfoAvailable in the RRCReconfigurationComplete message; 2> If an RRCReconfiguration message is received via SRB1 but is not within mrdc-SecondaryCellGroup, E-UTRA RRCConnectionReconfiguration, or E-UTRA RRCConnectionResume: 3>If the UE is configured to provide measurement gap requirement information for the NR target band: 4> If the RRCReconfiguration message contains needForGapsConfigNR; or 4>If the NeedForGapsInfoNR information has changed compared to when UE last reported this information: 5>Include NeedForGapsInfoNR and configure its contents as follows: 6>Set the gap requirement information for in-frequency measurements for each NR serving cell, including intraFreq-needForGap; 6>If requestedTargetBandFilterNR is configured: 7> For each supported NR band included in requestedTargetBandFilterNR, include an entry in interFreq-needForGap and set the gap requirement information for that band; 6>Otherwise: 7>Include an entry in interFreq-needForGap and configure the gap requirement information corresponding to each supported NR band; 3>If the UE is configured to provide measurement gap and NCSG requirement information for the NR target band: 4> If the RRCReconfiguration message contains needForGapNCSG-ConfigNR; or 4>needForGapNCSG-InfoNR information has changed compared to when UE last reported this information: 5>Include needForGapNCSG-InfoNR and configure its contents as follows: 6> Set the in-frequency measurement gap and NCSG requirement information for each NR serving cell, including intraFreq-needForNCSG; 6>If requestedTargetBandFilterNCSG-NR is configured: 7>For each supported NR band included in requestedTargetBandFilterNCSG-NR, include an entry in interFreq-needForNCSG and set the NCSG requirement information for that band; 6>Otherwise: 7> For each supported NR band, include an entry in interFreq-needForNCSG and configure the corresponding NCSG requirement information; 3>If the UE is configured to provide measurement gap and NCSG requirement information for the E-UTRA target band: 4> If the RRCReconfiguration message includes needForGapNCSG-ConfigEUTRA; or 4>needForGapNCSG-InfoEUTRA information has changed compared to when UE last reported this information: 5>Include NeedForGapNCSG-InfoEUTRA and configure its contents as follows: 6> If requestedTargetBandFilterNCSG-EUTRA is configured, include an entry in needForNCSG-EUTRA for each supported E-UTRA band included in requestedTargetBandFilterNCSG-EUTRA and configure the NCSG requirement information for that band; otherwise, include an entry in needForNCSG-EUTRA for each supported E-UTRA band and configure the corresponding NCSG requirement information; 2> If this procedure is initiated by generating a complete LTM candidate cell configuration: 3>Finish the procedure; 1>If the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (the UE is in (NG)EN-DC): 2> If an RRCReconfiguration message is received via E-UTRA SRB1 as specified in TS 36.331

[10] ; or 2>If an RRCReconfiguration message is received via the E-UTRA RRC message RRCConnectionReconfiguration within MobilityFromNRCommand (Handover from NR Standalone to (NG)EN-DC); 3>When RRCReconfiguration is applied by a conditional reconfiguration execution of a CPC configured via conditionalReconfiguration included in nr-SecondaryCellGroupConfig as defined in TS 36.331

[10] : 4> Submit the RRCReconfigurationComplete message via E-UTRA MCG embedded in the E-UTRA RRC message ULInformationTransferMRDC, as specified in TS 36.331

[10] , section 5.6.2a. 3> If the E-UTRA RRCConnectionResume message contains an RRCReconfiguration message: 4> Submit the RRCReconfigurationComplete message embedded in the E-UTRA RRC message RRCConnectionResumeComplete, as specified in TS 36.331

[10] , section 5.3.3.4a; 3>Otherwise: 4> Submit the RRCReconfigurationComplete embedded in the E-UTRA RRC message RRCConnectionReconfigurationComplete via E-UTRA, as specified in TS 36.331

[10] , section 5.3.5.3 / 5.3.5.4 / 5.4.2.3; 3> If the E-UTRA message (RRCConnectionReconfiguration or RRCConnectionResume) containing the RRCReconfiguration message does not include scg-State: Perform SCG activation as specified in 4>5.3.5.13a; 4>If reconfigurationWithSync is included in the spCellConfig of SCG: 5>Initiate a random access procedure on the PSCell as specified in TS 38.321[3]; 4> If the SCG was deactivated before receiving the E-UTRA RRC message containing the RRCReconfiguration message: 5> If bfd-and-RLM was not set to true before receiving an E-UTRA RRCConnectionReconfiguration or RRCConnectionResume message containing an RRCReconfiguration message, or if a lower layer indicates that a random access procedure is required for SCG activation: 6>Initiate a random access procedure on the SpCell as specified in TS 38.321[3]; 5> Otherwise, end the procedure; 4> Otherwise, end the procedure; 3>Otherwise: Perform SCG deactivation as specified in 4>5.3.5.13b; 4>Finish the procedure; 2>DLInformationTransferIf an RRCReconfiguration message is received within nr-SecondaryCellGroupConfig of an RRCConnectionReconfiguration message received via SRB3 in MRDC: 3> Submit the RRCReconfigurationComplete embedded in the E-UTRA RRC message RRCConnectionReconfigurationComplete via E-UTRA, as specified in TS 36.331

[10] , section 5.3.5.3 / 5.3.5.4; 3>If scg-State is not included in RRCConnectionReconfiguration: 4>If reconfigurationWithSync is included in the spCellConfig of SCG: 5>Initiate a random access procedure on the SpCell as specified in TS 38.321[3]; 4> Otherwise, end the procedure; 3>Otherwise: Perform SCG deactivation as specified in 4>5.3.5.13b; 4>Finish the procedure; Note 1: The order in which the UE sends the RRCConnectionReconfigurationComplete message and executes random access procedures toward the SCG is left to the UE implementation. 2> If not (RRCReconfiguration was received via SRB3) but not within DLInformationTransferMRDC: 3> To send using the new configuration, submit the RRCReconfigurationComplete message to the lower layer via SRB3; Note 2: In (NG)EN-DC and NR-DC, if an RRCReconfiguration is received via SRB1 or within DLInformationTransferMRDC via SRB3, random access is triggered by the RRC layer itself because there are not necessarily other UL transmissions. If an RRCReconfiguration is received via SRB3 but not within DLInformationTransferMRDC, random access is triggered by the MAC layer upon arrival of RRCReconfigurationComplete. 1>Instead, if the RRCReconfiguration message is received via SRB1 in nr-SCG within mrdc-SecondaryCellGroup (if the UE in NR-DC, mrdc-SecondaryCellGroup, receives it via RRCReconfiguration or RRCResume through SRB1): 2>When RRCReconfiguration is applied by a conditional reconfiguration execution of a CPC configured via conditionalReconfiguration included in nr-SCG within mrdc-SecondaryCellGroup: As specified in Section 3>5.7.2a.3, submit the RRCReconfigurationComplete message embedded in the NR RRC message ULInformationTransferMRDC via the NR MCG. 2> If the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message does not include scg-State: Perform SCG activation as specified in 3>5.3.5.13a; 3>If reconfigurationWithSync is included in nr-SCG's spCellConfig: 4>Initiate a random access procedure on the PSCell as specified in TS 38.321[3]; 3> If the SCG was deactivated before receiving an NR RRC message containing an RRCReconfiguration message: 4> If bfd-and-RLM was not configured to true before receiving an RRCReconfiguration or RRCResume message containing an RRCReconfiguration message; or 4> If the lower layer indicates that a random access procedure is required for SCG activation: 5>Initiate a random access procedure on the PSCell as specified in TS 38.321[3]; 4> Otherwise, end the procedure; 3> Otherwise, end the procedure; 2>Other cases 3> Perform SCG deactivation as specified in 5.3.5.13b; 3>Finish the procedure; Note 2a: The order in which the UE sends the RRCReconfigurationComplete message and executes random access procedures toward the SCG is left to the UE implementation. 1> Instead, if the RRCReconfiguration message is received via SRB3 (UE is in NR-DC): 2>If the RRCReconfiguration message is received within DLInformationTransferMRDC: 3> If the RRCReconfiguration message is received within nr-SCG in mrdc-SecondaryCellGroup (NR SCG RRC reconfiguration): 4>If the RRCReconfiguration message contains an RRCReconfiguration message and does not include scg-State: 5>If reconfigurationWithSync is included in nr-SCG's spCellConfig: 6>Initiate a random access procedure on the PSCell as specified in TS 38.321[3]; 5>Otherwise: 6>Finish the procedure; 4>Otherwise: Perform SCG deactivation as specified in 5>5.3.5.13b; 5>Finish the procedure; 3>Otherwise: 4>If RRCReconfiguration does not include mrdc-SecondaryCellGroupConfig: 5>If RRCReconfiguration includes scg-State: Perform SCG deactivation as specified in 6>5.3.5.13b; 4> To send using the new configuration, submit the RRCReconfigurationComplete message to the lower layer via SRB1; 2>Otherwise: 3> If this procedure is initiated by the processing of an ltm-Candidate received within ltm-CandidateConfig; As specified in 4>5.3.5.x.5, submit the RRCReconfigurationComplete message to the lower layer via SRB3 only when performing the LTM cell switch procedure, in order to send it using the new configuration; 3>Otherwise: 4 >Submit the RRCReconfigurationComplete message to the lower layer via SRB3 in order to send using the new configuration; 1>Otherwise (if RRCReconfiguration is received via SRB1): 2>UE is within NR-DC, and; 2>If RRCReconfiguration does not include mrdc-SecondaryCellGroupConfig: 3>If RRCReconfiguration includes scg-State: Perform SCG deactivation as specified in 4>5.3.5.13b; 3>Otherwise: Perform SCG activation without an SN message, as specified in 4>5.3.5.13b1; 2>If reconfigurationWithSync is included in the spCellConfig of MCG: 3>If ta-Report is configured with the value enabled and the UE supports TA reporting: 4> Indicates the start of TA reporting to lower layers; 2> If this procedure is initiated by the processing of an ltm-Candidate received within ltm-CandidateConfig; As specified in 3>5.3.5.x.5, when performing the LTM cell switch procedure, submit the RRCReconfigurationComplete message to the lower layer via SRB1 to send using the new configuration; 2>Otherwise: 3> To send using the new configuration, submit the RRCReconfigurationComplete message to the lower layer via SRB1; 2> If this is the first RRCReconfiguration message after the successful completion of the RRC re-establishment procedure: 3> Restart the suspended IAB-MT SRB2, SRB4, DRB, multicast MRB, BH RLC channels, and the L2 U2N relay UE Uu relay RLC channel; 1> If the spCellConfig of the MCG or SCG includes reconfigurationWithSync and the MAC of the NR cell group successfully completes the random access procedure triggered above; or 1>If the reconfigurationWithSync in the MCG's spCellConfig includes sl-PathSwitchConfig and the RRCReconfigurationComplete message is successfully sent (i.e., a PC5 RLC acknowledgment is received from the target L2 U2N relay UE): 2> If operating, stop timer T304 for that cell group; 2>If sl-PathSwitchConfig is included in reconfigurationWithSync: 3> Stop Timer T420; 3> Release all wireless resources, including RLC entities and MAC configurations on the source side; 3> Reset the MAC used in the source cell; Note 2b: PDCP and SDAP configured by the source before the path switch and reconfigured and reused by the target when delta signaling is used are not released as part of this procedure. 2> If running, stop the timer T310 of the source SpCell; 2> Apply the CSI reporting configuration, scheduling request configuration, and sounding RS configuration to any part where the UE does not need to know the SFN of each target SpCell; 2> If there are parts of the measurement and wireless resource configuration where the UE needs to know the SFN of each target SpCell (e.g., measurement gap, periodic CQI reporting, scheduling request configuration, sounding RS configuration), then obtain and apply the SFN of that target SpCell; 2> For each DRB configured as a DAPS bearer, request an uplink data switch to the PDCP entity as specified in TS 38.323[5]; 2>If reconfigurationWithSync is included in the spCellConfig of MCG: 3>If T390 is running: 4> Stop timer T390 for all access categories; Perform the action as specified in 4>5.3.14.4; 3>If the T350 is working: 4> Stop Timer T350; 3> RRCReconfiguration does not include dedicatedSIB1-Delivery, and 3>If the active downlink BWP indicated by firstActiveDownlinkBWP-Id of the MCG target SpCell has a common search space composed of searchSpaceSIB1: 4> Obtain the SIB1 scheduled for the target SpCell of the MCG as specified in TS 38.213

[13] ; 4>When SIB1 is obtained, perform the action specified in section 5.2.2.4.2; 2>If reconfigurationWithSync is included in the spCellConfig of MCG: or 2>If reconfigurationWithSync is included in spCellConfig of SCG, and CPA or CPC is configured: 3> If present, delete all entries in MCG and SCG VarConditionalReconfig; 3> Delete all entries in VarConditionalReconfiguration, if any, as specified in TS 36.331

[10] , section 5.3.5.9.6; 3> If configured, each measId in MCG measConfig, and if configured, each measId in SCG measConfig, if the associated reportConfig has the reportType set in condTriggerConfig: 4> For the associated reportConfigId: 5> Remove the entry with the matching reportConfigId from reportConfigList in VarMeasConfig; 4> If the associated measObjectId is only associated with a reportConfig where reportType is set to condTriggerConfig: 5> Remove the entry with the matching measObjectId from the measObjectList in VarMeasConfig; 4> Remove the matching measId entry from measIdList in VarMeasConfig; 2>If reconfigurationWithSync is included in masterCellGroup or secondaryCellGroup: 3> If the UE has started sending UEAssistanceInformation messages to the corresponding cell group in the past 1 second, and the UE is still configured to provide the corresponding UE assistance information to the corresponding cell group; or 3> If a conditional reconfiguration run applies the RRCReconfiguration message, and the UE is configured to provide UE assistance information for the corresponding cell group, and the UE is configured to do so in accordance with Section 5.7.4.2, and has therefore initiated sending the UEAssistanceInformation message for the corresponding cell group: 4> In order to provide the relevant UE assistance information, initiate sending of UEAssistanceInformation messages to the corresponding cell group in accordance with Section 5.7.4.3; 4> Start or restart the MUSIM prohibit timer (if any) associated with the corresponding UE assistance information for which a timer value has been set in the corresponding configuration value, or exit without responding to the timer; 3> If the target Pcell provides SIB12 and the UE starts sending a SidelinkUEInformationNR message indicating a change in NR sidelink communication / discovery-related parameters associated with the target Pcell (i.e., a change in sl-RxInterestedFreqList or sl-TxResourceReqList) within the second immediately preceding the UE receiving an RRCReconfiguration message containing reconfigurationWithSync in the MCG's spCellConfig; or 3>If a conditional reconfiguration execution applies the RRCReconfiguration message, the UE is responsive to NR sidelink communication / discovery, SIB12 is provided by the target Pcell, and the UE was configured to do so in accordance with 5.8.3.2, and therefore initiated sending the SidelinkUEInformationNR message: Instruct the sending of SidelinkUEInformationNR messages according to 4>5.8.3.3; 2>If reconfigurationWithSync is included in masterCellGroup: 3> Application layer measurement is configured, and an application layer measurement report container has been received from a higher layer, but the message has not been successfully sent or at least one segment of the message has not been acknowledged by a lower layer: 4> Resubmit the MeasurementReportAppLayer message or all segments of the MeasurementReportAppLayer message to the lower layer for transmission via SRB4; 2>If reconfigurationWithSync is included in masterCellGroup and the target cell is providing SIB21: 3>If the UE started sending an MBSInterestIndication message in the second immediately preceding the receipt of this RRCReconfiguration message; or 3> If a conditional reconfiguration execution applies an RRCReconfiguration message, and the UE starts sending MBSInterestIndication messages after receiving this RRCReconfiguration message: Initiate sending of MBSInterestIndication messages according to section 4>5.9.4; 2>Finish the procedure. Note 3: The UE is required to acquire the broadcast SIB1 only if it can acquire it without interrupting the reception of unicast or MBS multicast data; in other words, broadcast and unicast / MBS multicast beams are quasi-coexistent. Note 4: The UE sets the contents of UEAssistanceInformation according to the latest configuration (i.e., the configuration after applying the RRCReconfiguration message) and the latest UE preferences. The UE may include a lot of information in UEAssistanceInformation in addition to the relevant UE assistance information, as per 5.7.4.2. Therefore, the contents of a UEAssistanceInformation message may not be the same as the contents of a previous UEAssistanceInformation message. 5.3.5.5 Cell Group Configuration 5.3.5.5.1 General The network configures a master cell group (MCG) and zero or one secondary cell group (SCG) in the UE. In (NG)EN-DC, the MCG is configured as specified in TS 36.331

[10] , and in NE-DC, the SCG is configured as specified in TS 36.331

[10] . The network provides cell group configuration parameters in CellGroupConfig IE. The UE performs the following actions based on the received CellGroupConfig IE: 1>If CellGroupConfig contains spCellConfig with reconfigurationWithSync: and 1>If this procedure is not initiated by generating a complete LTM candidate cell configuration: Perform a reconfiguration with synchronization according to 2>5.3.5.5.2; 2> Restart all suspended radio bearers except the SRB in the source cell group, restart SCG transmission for all radio bearers, restart the BH RLC channel of the IAB-MT if suspended, and restart SCG transmission for the BH RLC channel; Note: If the SCG is deactivated, reactivating SCG transmission on all radio bearers does not imply that PDCP PDUs can be transmitted or received on SCG RLC bearers. 1> When CellGroupConfig includes rlc - BearerToReleaseList or rlc - BearerToReleaseListExt: 2> Execute RLC bearer release as specified in 5.3.5.5.3; 1> When CellGroupConfig includes rlc - BearerToAddModList: 2> Execute RLC bearer addition / modification as specified in 5.3.5.5.4; 1> When CellGroupConfig includes mac - CellGroupConfig: 2> Configure the MAC entity of this cell group as specified in 5.3.5.5.5; 1> When CellGroupConfig includes sCellToReleaseList: 2> Execute SCell release as specified in 5.3.5.5.8; 1> When CellGroupConfig includes spCellConfig: 2> Configure SpCell as specified in 5.3.5.5.7; 1> When CellGroupConfig includes sCellToAddModList: 2> Execute SCell addition / modification as specified in 5.3.5.5.9; 1> When CellGroupConfig includes bh - RLC - ChannelToReleaseList: 2> Execute BH RLC channel release as specified in 5.3.5.5.10; 1> When CellGroupConfig includes bh - RLC - ChannelToAddModList: 2> Execute BH RLC channel addition / modification as specified in 5.3.5.5.11; 1> When CellGroupConfig includes uu - RelayRLC - ChannelToReleaseList: 2> Perform Uu relay RLC channel release as specified in 5.3.5.5.12; 1>If CellGroupConfig contains uu-RelayRLC-ChannelToAddModList: 2> Perform the Uu relay RLC channel addition / modification as specified in 5.3.5.5.13; 5.3.5.5.3 RLC Bearer Release The UE must do the following: 1> For each logicalChannelIdentity / LogicalChannelIdentityExt value contained in rlc-BearerToReleaseList / rlc-BearerToReleaseListExt, which is part of the current UE configuration within the same cell group, (release LCH); or For each logicalChannelIdentity value released as a result of SCG release according to 1>5.3.5.4: 2> Release the RLC entity as specified in section 5.1.3 of TS 38.322[4]; 2> Release the corresponding logical channel. 5.3.5.5.4 Addition / Modification of RLC Bearer For each RLC-BearerConfig received in IE via rlc-BearerToAddModList, the UE must perform the following: 1>If the current configuration of the UE includes an RLC bearer with an received logicalChannelIdentity / LogicalChannelIdentityExt within the same cell group: Note X: This case does not apply if this procedure was initiated by generating an LTM candidate cell configuration. 2> If the RLC bearer is associated with the DAPS bearer, or 2> If any DAPS bearer is configured and the RLC bearer is associated with the SRB: 3> Reconfigure the RLC entities of the target cell group according to the received rlc-Config; 3> Reconfigure the logical channels of the target cell group according to the received mac-LogicalChannelConfig; 2>Otherwise: 3>reestablish if RLC is received: 4> Re-establish the RLC entity as specified in TS 38.322[4]; 3> Reconfigure the RLC entities according to the received rlc-Config; 3> Reconfigure the logical channel according to the received mac-LogicalChannelConfig; 3>If you receive a servedMBS-RadioBearer: 4> Associate this logical channel with the PDCP entity identified by servedMBS-RadioBearer; Note 1: In the case of DRB and SRB, the network does not reassociate an already configured logical channel with another radio bearer. Therefore, servedRadioBearer does not exist in this case. In the case of MRB, the network does not reassociate an already configured logical channel with a DRB, SRB, or another MRB (i.e., an MRB of another PDCP entity). Therefore, multicastRLC-BearerConfig does not exist in this case. Note 2: In a DAPS handover, when the UE receives instructions for the successful completion of random access from a lower layer to a target cell, as specified in TS 38.321[3], it may perform re-establishment of the RLC entity of the RLC bearer associated with the non-DAPS bearer (if reestablishRLC is configured). 1> No, unless the logical channels with a given logicalChannelIdentity / LogicalChannelIdentityExt are configured within the same cell group, including when the full configuration option is used: 2>If servedRadioBearer associates a logical channel with an SRB and rlc-Config is not included: 3> For the corresponding SRB, establish the RLC entity according to the default configuration defined in 9.2; 2>Otherwise: 3> Establish an RLC entity according to the received rlc-Config; 2>When servedRadioBearer associates a logical channel with an SRB and mac-LogicalChannelConfig is not included: 3>For the corresponding SRB, configure this MAC entity together with the logical channel according to the default configuration defined in 9.2; 2>Otherwise: 3>Configure this MAC entity together with the logical channel according to the received mac-LogicalChannelConfig; 2>Associate this logical channel with the PDCP entity identified by servedRadioBearer or servedMBS-RadioBearer; 5.3.5.5.5 MAC entity configuration The UE shall perform the following: 1>If the SCG MAC is not part of the current UE configuration (i.e., SCG establishment): 2>Create an SCG MAC entity; 1>If any DAPS bearer is configured: 2 Reconfigure the MAC main configuration of the target cell group according to the received mac-CellGroupConfig, excluding tag-ToReleaseList and tag-ToAddModList; 1> If this procedure is initiated by generating a complete LTM candidate cell configuration: 2> Create MAC entities for LTM candidate cell configurations that need to generate a complete configuration excluding tag-ToReleaseList and tag-ToAddModList; 1>Otherwise: 2>Reconfigure the MAC main configuration of the cell group according to the received mac-CellGroupConfig excluding tag-ToReleaseList and tag-ToAddModList; 1>If the received mac-CellGroupConfig includes tag-ToReleaseList: 2>For each TAG-Id value included in tag-ToReleaseList that is part of the current UE configuration: 3>Release the TAG indicated by the TAG-Id; 1>If the received mac-CellGroupConfig includes tag-ToAddModList: 2> For each tag-Id value included in tag-ToAddModList that is not part of the current UE configuration (adding a TAG): 3> Add a TAG corresponding to the tag-Id according to the received timeAlignmentTimer; 2> For each tag-Id value included in tag-ToAddModList, which is part of the current UE configuration (TAG modification): 3> Reconstruct the TAG corresponding to the tag-Id according to the received timeAlignmentTimer. 5.3.5.5.6 RLF Timer and Constant Configuration The UE must do the following: 1>If the received rlf-TimersAndConstants is set to release: 2> If any DAPS bearer is configured: 3>Use the values ​​of timers T301, T310, T311 and constants N310, N311 of the target cell group as they are included in the ue-TimersAndConstants received in SIB1; 2>Otherwise: 3>Use the values ​​of timers T301, T310, T311 and constants N310, N311 as they are included in the ue-TimersAndConstants received in SIB1; 1>Otherwise: 2> If any DAPS bearer is configured: 3> Configure the timer and constant values ​​for the target cell group according to the received rlf-TimersAndConstants; 2>Otherwise: 3> Reconfigure the timer and constant values ​​according to the received rlf-TimersAndConstants; 3> If this procedure is not initiated by generating a complete LTM candidate cell configuration: 4> If in operation, stop timer T310 for this cell group; 4> If in operation, stop timer T312 for this cell group; 4> Reset counters N310 and N311. 5.3.5.5.7 SpCell Configuration The UE must do the following: 1>If the UE is operating as an L2 U2N remote UE: 2>If SpCellConfig includes rlf-TimersAndConstants set in setup: 3> Use the value of timer T311 as received in rlf-TimersAndConstants; 2> If rlf-TimersAndConstants is not configured for this cell group, or if it contains rlf-TimersAndConstants with SpCellConfig set to release: 3> Use the value of timer T311 so that it is included in ue-TimersAndConstants received in SIB1; 1>Otherwise 2> If SpCellConfig includes rlf-TimersAndConstants: Configure the RLF timer and constants for this cell group as specified in 3>5.3.5.5.6; 2> If rlf-TimersAndConstants is not configured for this cell group: 3> If any DAPS bearer is configured: 4>Use the values ​​of timers T301, T310, T311 and constants N310, N311 of the target cell group as they are included in the ue-TimersAndConstants received in SIB1; 3>Other cases 4>Use the values ​​of timers T301, T310, T311 and constants N310, N311 as they are included in the ue-TimersAndConstants received in SIB1; 2> If SpCellConfig includes spCellConfigDedicated: 3> Configure the SpCell according to spCellConfigDedicated; 3>If spCellConfigDedicated contains firstActiveUplinkBWP-Id, the bandwidth portion indicated therein will be considered the active uplink bandwidth portion; 3>If spCellConfigDedicated contains firstActiveDownlinkBWP-Id: 4> If the RRCReconfiguration message included in the NR or E-UTRA RRC message indicating that SCG is deactivated contains SpCellConfig: 5>The bandwidth portion indicated by firstActiveDownlinkBWP-Id shall be considered as the bandwidth portion for radio link monitoring, beam fault detection, and measurement; 4>Otherwise: 5>The bandwidth portion indicated by firstActiveDownlinkBWP-Id is considered the active downlink bandwidth portion; 3> Any of the reference signals used for wireless link monitoring has been reconfigured by the received spCellConfigDedicated: and 1>If this procedure is not initiated by generating a complete LTM candidate cell configuration: 4> If running, stop the timer T310 of the corresponding SpCell; 4> If running, stop the timer T312 of the corresponding SpCell; 4> Reset counters N310 and N311. 1> If SpCellConfig includes lowMobilityEvaluationConnected: 2>UE may perform a low mobility criterion assessment on this cell group as specified in 5.7.13.1; 1> If SpCellConfig includes goodServingCellEvaluationRLM: 2>UE may perform an assessment of the good serving cell quality criteria for this SpCell, as specified in 5.7.13.2; 1> If SpCellConfig includes goodServingCellEvaluationBFD: 2>UE may perform a good serving cell quality assessment on this serving cell, as specified in 5.7.13.2; 5.3.5.5.8 SCell release The UE must do the following: 1> If release is triggered by receiving sCellToReleaseList: 2>For each sCellIndex value included in sCellToReleaseList: 3>If the current UE configuration contains an SCell with the value sCellIndex: 4> Release SCell. Editor's note: FFS determines whether releasing SCells based on LTM candidate cell configurations is a valid approach. 5.3.5.5.9 SCell additions / corrections The UE must do the following: 1> For each sCellIndex value included in sCellToAddModList that is not part of the current UE configuration (SCell addition): 2> Add SCells corresponding to sCellIndex according to sCellConfigCommon and sCellConfigDedicated; 2>sCellState is included: 3> Configure the lower layer to treat the SCell as being in an activated state; 2>Otherwise: 3> Configure the lower layer to treat the SCell as being in an inactive state; 2>For each measId included in the measIdList within VarMeasConfig: 3> SCell is not applicable to the relevant measurement; and, 3> If the relevant SCell is included in the cellsTriggeredList defined within this measId's VarMeasReportList: 3> If this procedure is not initiated by generating a complete LTM candidate cell configuration: 4> Remove the corresponding SCell from the cellsTriggeredList defined within the VarMeasReportList for this measId; 2>If SCellConfig includes goodServingCellEvaluationBFD: 3>UE may perform a good serving cell quality assessment on this serving cell, as specified in 5.7.13.2; 1> For each sCellIndex value included in sCellToAddModList, which is part of the current UE configuration (SCell modification): Note X: This case does not apply if this procedure was initiated by generating an LTM candidate cell configuration. 2> Modify the SCell configuration according to sCellConfigDedicated; 2>sCellState is included: 3> Configure the lower layer to treat the SCell as being in an activated state; 2>Otherwise: 3> Configure the lower layer to treat the SCell as being in an inactive state; 2>If SCellConfig includes goodServingCellEvaluationBFD: 3>UE may perform a good serving cell quality assessment on this serving cell, as specified in 5.7.13.2; 5.3.5.6 Wireless Bearer Configuration 5.3.5.6.1 General The UE must perform the following actions based on the received RadioBearerConfig IE: 1>If RadioBearerConfig includes srb3-ToRelease or srb4-ToRelease: 2> Perform SRB release as specified in 5.3.5.6.2; 1>If RadioBearerConfig includes srb-ToAddModList, or if any DAPS bearer is configured: 2> Perform SRB addition or reconfiguration as specified in 5.3.5.6.3; 1>If RadioBearerConfig includes drb-ToReleaseList: 2> Perform DRB release as specified in 5.3.5.6.4; 1>If RadioBearerConfig includes drb-ToAddModList: 2> Perform DRB addition or reconfiguration as specified in 5.3.5.6.5; 1>If RadioBearerConfig includes mrb-ToReleaseList: 2> Perform multicast MRB release as specified in 5.3.5.6.6; 1>If RadioBearerConfig includes mrb-ToAddModList: 2> Perform multicast MRB addition or reconfiguration as specified in 5.3.5.6.7; 1>If this procedure is not initiated by generating a complete LTM candidate cell configuration: 2> As specified in TS 37.324

[24] , section 5.1.2, release all SDAP entities that do not have associated DRBs, if any, and indicate to the upper layer the release of user plane resources for PDU sessions associated with the released SDAP entities; 1> As specified in TS 37.324

[24] , section 5.1.2, release all SDAP entities that do not have associated multicast MRBs and indicate to the upper layer the release of user plane resources for these MBS multicast sessions. 5.3.5.6.2 SRB release The UE must do the following: 1>If srb3-ToRelease is included: 2> Release the PDCP entity and srb-Identity of SRB3; 1>If srb4-ToRelease is included 2> Release the PDCP entity and srb-Identity of SRB4. 5.3.5.6.3 SRB addition / modification The UE must do the following: 1> If any DAPS bearer is configured for each SRB: 2> Establish a PDCP entity for the target cell group with the same configuration as the PDCP entity for the source cell group, as specified in TS 38.323[5]; 2>If you receive a masterKeyUpdate: 3>Configure the PDCP entity using a security algorithm according to securityConfig and apply the keys (K gNB ) associated with the master key (K RRCenc and K RRCint ); 2>Otherwise: 3>Configure the PDCP entity of the target cell group with the same security configuration as the PDCP entity of the source cell group, with continuity of state variables as specified in TS 38.323 [5]; 1>For each srb-Identity value included in srb-ToAddModList that is not part of the current UE configuration (for the establishment of an SRB or the reconfiguration from E-UTRA PDCP to NR PDCP): 2>Establish a PDCP entity; 2>If AS security is activated: 3>If the target RAT of the handover is E-UTRA / 5GC; or 3>If the UE is connected to E-UTRA / 5GC: 4>If the UE is compatible with E-UTRA / 5GC but not with NGEN-DC: 5>Configure the PDCP entity with the keys (K RRCenc and K RRCint ) configured / derived as specified in TS 36.331

[10] and a security algorithm; 4>Otherwise (i.e., if the UE is compatible with NGEN-DC): 5>Configure the PDCP entity with a security algorithm according to securityConfig and apply the keys (K eNB ) associated with the master key (K gNB ) or the keys (K RRCenc and K RRCint ) associated with the secondary key (S-K 3>Otherwise (i.e., if the UE is connected to NR or if the UE is connected to E-UTRA / EPC): 4> Configure the PDCP entity with a security algorithm that conforms to securityConfig, and if applicable, use the master key (K) as shown in keyToUse. eNB / K gNB ) or secondary key (SK gNB ) Key associated with (K RRCenc and K RRCint ) apply; 2>If the current UE configuration configured by E-UTRA in TS 36.331

[10] includes an SRB identified by the same srb-Identity value: 3> Associate the E-UTRA RLC entity and DCCH of this SRB with the NR PDCP entity; 3> Release the E-UTRA PDCP entity of this SRB; 2>If pdcp-Config is included: 3> Configure the PDCP entity according to the received pdcp-Config; 2>Otherwise: 3> For the corresponding SRB, configure the PDCP entity according to the default configuration defined in 9.2.1; 1>If any DAPS bearer is configured for each srb-Identity value included in srb-ToAddModList, which is part of the current UE configuration: 2>If pdcp-Config is included: 3> Reconfigure the PDCP entities of the target cell group according to the received pdcp-Config; 1> Otherwise, for each srb-Identity value included in srb-ToAddModList, which is part of the current UE configuration: Note X: This case does not apply if this procedure was initiated by generating an LTM candidate cell configuration. 2>Establish PDCP if it is set up: 3> If the handover target RAT is E-UTRA / 5GC; or 3>If UE is connected to E-UTRA / 5GC: 4>If UE supports E-UTRA / 5GC but not NGEN-DC: 5> K configured / derived as specified in TS 36.331

[10] RRCint The PDCP entity must be configured to apply the key and integrity protection algorithm; that is, the integrity protection configuration must be applied to all subsequent messages sent and received by the UE, including the message used to indicate the successful completion of the procedure; 5> K configured / derived as specified in TS 36.331

[10] RRCenc The PDCP entity must be configured to apply the key and encryption algorithm; that is, the encryption configuration must be applied to all subsequent messages sent and received by the UE, including the message used to indicate the successful completion of the procedure; 4>Otherwise (i.e., if UE supports NGEN-DC): 5> As shown in keyToUse, integrity protection algorithm and master key (K eNB ) or secondary key (SK gNB ) associated with K RRCint The PDCP entity must be configured to apply the key; that is, the integrity protection configuration must be applied to all subsequent messages sent and received by the UE, including the message used to indicate the successful completion of the procedure. 5> As shown in keyToUse, the encryption algorithm and master key (K eNB ) or secondary key (SK gNB ) associated with K RRCenc The PDCP entity must be configured to apply the key; that is, the encryption configuration must be applied to all subsequent messages sent and received by the UE, including the message used to indicate the successful completion of the procedure. 3>Otherwise (i.e., if the UE is connected to the NR, or if the UE is in the EN-DC): 4> As shown in keyToUse, integrity protection algorithm and master key (K eNB / K gNB ) or secondary key (SK gNB ) and K RRCintThe PDCP entity must be configured to apply the key; that is, the integrity protection configuration must be applied to all subsequent messages sent and received by the UE, including the message used to indicate the successful completion of the procedure. 4> As shown in keyToUse, the encryption algorithm and master key (K eNB / K gNB ) or secondary key (SK gNB ) associated with K RRCenc The PDCP entity must be configured to apply the key; that is, the encryption configuration must be applied to all subsequent messages sent and received by the UE, including the message used to indicate the successful completion of the procedure. 3> Re-establish the PDCP entity of this SRB as specified in TS 38.323[5]; 2> If discardOnPDCP is set: 3> Trigger the PDCP entity to perform SDU destruction as specified in TS 38.323[5]; 2>If pdcp-Config is included: 3> Reconfigure the PDCP entity according to the received pdcp-Config; 5.3.5.6.4 DRB Release The UE must do the following: 1> For each drb-Identity value included in drb-ToReleaseList, which is part of the current UE configuration; or For each drb-Identity value released as a result of a full configuration according to 1>5.3.5.11: 2> Release the PDCP entity and drb-Identity; 2>If an SDAP entity associated with this DRB is configured: 3> Indicates the release of the DRB to the SDAP entity associated with this DRB (TS 37.324

[24] , Section 5.3.3); 2>If DRB is associated with eps-BearerIdentity: 3> If a new bearer has not been added to either an NR or E-UTRA with the same eps-BearerIdentity: 4> The DRB is released, and the eps-BearerIdentity of the released DRB is shown to the upper layer. Note 1: If drb-ToReleaseList contains any drb-Identity value that is not part of the current UE configuration, the UE will not consider the message an error. Note 2: Whether the RLC and MAC entities associated with this PDCP entity are reset or released is determined by CellGroupConfig. 5.3.5.6.5 DRB additions / corrections The UE must do the following: 1> For each drb-Identity value included in drb-ToAddModList that is not part of the current UE configuration (including DRB establishment when the full configuration option is used): 2>If this procedure is not initiated by generating a complete LTM candidate cell configuration: 3> Establish a PDCP entity and configure it according to the received pdcp-Config; 2> If the PDCP entity of this DRB is not configured as cipheringDisabled: 3> If the handover target RAT is E-UTRA / 5GC; or 3>If UE is connected to E-UTRA / 5GC: 4>If UE supports E-UTRA / 5GC but not NGEN-DC: 5> K configured / derived as specified in TS 36.331

[10] UPenc The PDCP entity is constructed using keys and encryption algorithms; 4>Otherwise (i.e., if UE supports NGEN-DC): 5> Configure the PDCP entity with an encryption algorithm according to securityConfig, and if applicable, use the master key (K) as shown in keyToUse. eNB ) or secondary key (SK gNB ) Key associated with (K UPenc ) apply; 3>Otherwise (i.e., if the UE is connected to NR, or if the UE is connected to E-UTRA / EPC): 4> Configure the PDCP entity with an encryption algorithm according to securityConfig, and the master key (K eNB / K gNB ) or secondary key (SK gNB / SK eNB ) associated with K UPenc Apply the key; 2> If the PDCP entity of this DRB is configured with integrityProtection: 3> Configure the PDCP entity with an integrity protection algorithm according to securityConfig, and set the master (K) as shown in keyToUse. eNB / K gNB ) or secondary key (SK gNB ) associated with K UPint Apply the key; 2>If sdap-Config is included: 3> If there is no SDAP entity with the received pdu-Session: 4>Establish an SDAP entity as specified in TS 37.324

[24] , section 5.1.1; 4> If no SDAP entity with the received pdu-Session existed before receiving this reconfiguration: 5> The establishment of user plane resources for the pdu-Session is shown to the upper layer; 3> Configure the SDAP entity according to the received sdap-Config as specified in TS 37.324

[24] , and associate the DRB with the SDAP entity; 3> For each QFI value added to mappedQoS-FlowsToAdd, if that QFI value was previously configured, release that QFI value from the old DRB; 2>If DRB is associated with eps-BearerIdentity: 3> If the DRB was configured with the same eps-BearerIdentity by either NR or E-UTRA before receiving this reconstruction: 4> Associate the established DRB with the corresponding eps-BearerIdentity; 3>Otherwise: 4> Establish the DRB and display the eps-BearerIdentity of the established DRB in the upper layer; 1> For each drb-Identity value included in drb-ToAddModList, which is part of the current UE configuration and configured as a DAPS bearer: Note X: This case does not apply if this procedure was initiated by generating an LTM candidate cell configuration. 2> Reconfigure the PDCP entity to configure the DAPS with encryption, integrity protection, and ROHC functions for the target cell group, as specified in TS 38.323[5], and configure it according to the received pdcp-Config; 2>If you receive a masterKeyUpdate: 3> If the encryption function of the target cell group PDCP entity is not configured as cipheringDisabled: 4> Configure the encryption functionality of the target cell group PDCP entity with an encryption algorithm according to securityConfig, and set the master key (K gNB ) associated with K UPenc The key must be applied, i.e., the encryption configuration must be applied to all subsequent PDCP PDUs received from and sent to the target cell group by the UE; 3> If the integrity protection function of the target cell group PDCP entity is configured as integrityProtection: 4> Configure the integrity protection function of the target cell group PDCP entity with an integrity protection algorithm according to securityConfig, and set the master key (K) as shown in keyToUse. gNB ) associated with K UPint Apply the key; 2>Otherwise: 3> Configure the encryption and integrity protection functions of the target cell group PDCP entity with the same security configuration as the source cell group PDCP entity; 2>sdap-Config is included and instructions for successful completion of random access from lower layers to target cells are received as specified in [3]: 3> Reconfigure the SDAP entity according to the received sdap-Config, as specified in TS 37.324

[24] ; 3> For each QFI value added to mappedQoS-FlowsToAdd, if that QFI value was previously configured, release that QFI value from the old DRB; 1> For each drb-Identity value included in drb-ToAddModList, which is part of the current UE configuration and is not configured as a DAPS bearer: 2>Establish PDCP if it is set up: 3> If the handover target RAT is E-UTRA / 5GC; or 3>If UE is connected to E-UTRA / 5GC: 4>If UE supports E-UTRA / 5GC but not NGEN-DC: 5> If the PDCP entity of this DRB is not configured as cipheringDisabled: 6>K constructed / derived as specified in TS 36.331

[10] , section 5.4.2.3 UPenc The PDCP entity must be configured with a key and encryption algorithm; that is, the encryption configuration must be applied to all subsequent PDCP PDUs sent and received by the UE; 4>Otherwise (i.e., if UE supports NGEN-DC): 5> If the PDCP entity of this DRB is not configured as cipheringDisabled: 6> As shown in keyToUse, the encryption algorithm and master key (K eNB ) or secondary key (SKgNB ) associated with K UPenc The PDCP entity must be configured with a key; that is, the encryption configuration must be applied to all subsequent PDCP PDUs sent and received by the UE. 3> In other cases (i.e., when the UE is connected to NR, or when the UE is connected to E-UTRA / EPC) (in the case of EN-DC or EN-DC compatible): 4>If the PDCP entity of this DRB is not configured as cipheringDisabled: 5> As shown in keyToUse, the encryption algorithm and master key (K eNB / K gNB ) or secondary key (SK gNB / SK eNB ) associated with K UPenc The PDCP entity must be configured with a key; that is, the encryption configuration must be applied to all subsequent PDCP PDUs sent and received by the UE. 4>If the PDCP entity of this DRB is configured with integrityProtection: 5> Configure the PDCP entity with an integrity protection algorithm according to securityConfig, and set the master key (K) as shown in keyToUse. eNB / K gNB ) or secondary key (SK gNB ) associated with K UPint Apply the key; 3>If pdcp-Config includes drb-ContinueROHC: 4> Indicates that drb-ContinueROHC is configured in the lower layer; 3>If pdcp-Config includes drb-ContinueEHC-DL: 4> Indicates that drb-ContinueEHC-DL is configured in the lower layer; 3>If pdcp-Config includes drb-ContinueEHC-UL: 4> Indicates that drb-ContinueEHC-UL is configured in the lower layer; 3>If pdcp-Config includes drb-ContinueUDC: 4> Indicates that drb-ContinueUDC is configured in the lower layer; 3> Re-establish the PDCP entity of this DRB as specified in TS 38.323[5], section 5.1.2; 2> If recoverPDCP is configured: 3> Trigger the PDCP entity of this DRB to perform data recovery, as specified in TS 38.323[5]; 2>If pdcp-Config is included: 3> Reconfigure the PDCP entity according to the received pdcp-Config; 2>If sdap-Config is included: 3> Reconfigure the SDAP entity according to the received sdap-Config, as specified in TS37.324

[24] ; 3> For each QFI value added to mappedQoS-FlowsToAdd, if that QFI value was previously configured, release that QFI value from the old DRB; Note 1: Invalid Note 2: When determining whether a drb-Identity value is part of the current UE configuration, the UE does not distinguish which RadioBearerConfig and DRB-ToAddModList the DRB was originally configured in. To reassociate a DRB with a different key (KeNB to S-KgNB, KgNB to S-KeNB, KgNB to S-KgNB, or vice versa), the network provides the drb-Identity value to the (target) drb-ToAddModList and sets the reestablishPDCP flag. The network does not list drb-Identity in the (source) drb-ToReleaseList. Note 3: When setting the reestablishPDCP flag on a wireless bearer, ensure that the network does not distribute old PDCP PDUs to re-established PDCP entities. This is done, for example, by triggering a reconfiguration with synchronization of the cell group hosting the old RLC entity, or by releasing the old RLC entity. Note 4: In this specification, unless otherwise specified, UE configurations refer to parameters configured by NR RRC. Note 5: Encryption and integrity protection can be enabled or disabled for the DRB. Enabling / disabling encryption or integrity protection can only be changed by releasing or adding a DRB. Note 6: During a DAPS handover, when the UE receives instructions for the successful completion of random access from the lower layer to the target cell, as specified in TS 38.321[3], it may perform a PDCP entity re-establishment (if reestablishPDCP is configured) or PDCP data recovery (if recoverPDCP is configured) for non-DAPS bearers. In this case, the UE suspends data transmission and reception for all non-DAPS bearers in the source MCG during the DAPS handover. 5.3.5.x LTM Configuration and Execution 5.3.5.x.1 General The UE must perform the following actions based on the received LTM-CandidateConfig IE. 1>If it exists, store the received ltm-ReferenceConfiguration in VarLTM-Config; 1>If LTM-CandidateConfig contains ltm-CandidateToReleaseList: 2> Perform LTM candidate cell release as specified in 5.3.5.x.2; 1>If LTM-CandidateConfig includes ltm-CandidateResetL2-List: 2> Add the received ltm-CandidateResetL2-List to VarLTM-Config; 1>If LTM-CandidateConfig includes ltm-CandidateToAddModList: 2> Perform LTM candidate cell addition or reconfiguration as specified in 5.3.5.x.3; 1> Perform the action to generate a complete LTM configuration as specified in 5.3.5.x.4; Note X: Whether the generation of the complete LTM configuration is delayed until the LTM cell switch is executed depends on the UE implementation. Editor's Note: FFS determines whether the UE performs compliance checks on reference and LTM candidate cell configurations when receiving LTM cell switch executions. Editor's note: For information on whether RACH is required for LTM candidate cells and how to do so, see FFS. Editor's Note: For information on how UE should establish TA for LTM candidate cells, see FFS. 5.3.5.x.2 LTM Candidate Cell Release The UE must do the following: 1>For each ltm-CandidateId in ltm-CandidateToReleaseList: 2>If the current VarLTM-Config contains the ltm-Candidate of the given ltm-CandidateId: 3> Release ltm-Candidate from VarLTM-Config; 5.3.5.x.3 Added / Modified LTM candidate cells The UE must do the following: 1>For each ltm-CandidateId in ltm-CandidateToAddModList: 2>If the current VarLTM-Config contains the ltm-Candidate of the given ltm-CandidateId: 3> Modify the ltm-Candidate in VarLTM-Config according to the received ltm-Candidate; 2>Otherwise: 3> Add the received ltm-Candidate to VarLTM-Config; 5.3.5.x.4 Generating UE LTM Configuration The purpose of this procedure is for the UE to generate a complete LTM candidate cell configuration and save and apply it only when it receives an LTM cell switch instruction at a lower layer. The current UE configuration is not modified while the complete LTM candidate cell configuration is being generated. The UE must do the following: 1>For each ltm-Candidate in ltm-CandidateConfigList within VarLTM-Config; 2>Store the ltm-CandidateId contained in ltm-Candidate in VarLTM-UE-Config; 2>If ltm-Candidate includes ltm-ConfigComplete: Following the actions described in Section 3>5.3.5.3, generate the complete LTM candidate cell configuration of the received ltm-Candidate and store it in ue-LTM-Config within VarLTM-UE-Config. 2>Otherwise: Following the actions described in section 3>5.3.5.3, a complete LTM candidate cell configuration is generated by applying ltm-Candidate on top of referenceConfiguration and stored in ue-LTM-Config within VarLTM-UE-Config. Editor's note: FFS asks whether ltm-ConfigComplete is required to indicate to the UE that the LTM candidate cell configuration within ltm-Candidate is a full configuration. Editor's Note: FFS will need to know whether UE will need to rely on the full configuration procedure when generating a complete LTM candidate cell configuration, or whether a new procedure will be created for LTM. 5.3.5.x.5 LTM Cell Switch Execution In response to instructions from lower layers that the LTM cell switch procedure has been triggered, the UE must perform the following: 1> Unlock / clear all current dedicated wireless configurations except for the following: 2>When the LTM cell switch is triggered by the MCG: -MCG C-RNTI; - AS security configuration associated with the master key; 2> Instead, if the LTM cell switch is triggered by the SCG: -SCG C-RNTI; - AS security configuration associated with secondary keys; -SRB1 / SRB2 configuration and DRB configuration configured by radioBearerConfig or radioBearerConfig2; Editor's note: FFS is required to retain the wireless bearer when running LTM cell switches. -UE variables VarLTM-Config and VarLTM-UE-Config. 1> Unlock / clear all current shared wireless configurations; 1> For timers T310, T311, and constants N310, N311, use the default values ​​specified in 9.2.3; 1> Except as follows, the default L1 parameter values ​​are applied as specified in the corresponding physical layer specification: -Parameters for which values ​​are provided in SIB1; 1> Apply the value of newUE-Identity as the C-RNTI for this cell group, according to the LTM candidate cell configuration associated with the LTM candidate cell configuration identifier, as received by the lower layer; 1> Configure the lower layer according to the received spCellConfigCommon, based on the LTM candidate cell configuration indicated by the lower layer; 1> Configure the lower layer according to the received rach-ConfigDedicated, based on the LTM candidate cell configuration indicated by the lower layer; 1>Apply the default MAC cell group configuration as specified in 9.2.2; 1> Configure the PDCP entity of the LTM candidate cell configuration indicated by the lower layer with the same security configuration as the source cell group's PDCP entity, with the continuation of state variables as specified in TS 38.323[5]; 1> If running, stop the timer T310 of the corresponding SpCell; 1> If this procedure is performed on MCG: 2> If Timer T316 is running; 3> Stop timer T316; 1> If running, stop timer T312 of the corresponding SpCell; 1> Apply the specified BCCH configuration defined in 9.1.1.1 to the target SpCell; 1>If applicable, retrieve the MIB of the target SpCell as shown in the LTM candidate cell configuration shown by the lower layer, scheduled as specified in TS 38.213

[13] ; 1> Apply the LTM configuration to the UE-LTM-Config in VarLTM-UE-Config, which is associated with the LTM candidate cell configuration identifier as received by the lower layer. 1> Submit the RRCReconfigurationComplete message to the lower layer in order to send using the new configuration. Editor's Note: FFS should determine whether the sending of the RRCReconfigurationComplete message should be triggered in this section or in section 5.3.5.3 (i.e., the UE receiving the RRCReconfiguration). Editor's note: For example, FFS should specify whether further actions of the UE are required for interaction with subsequent LTM cell switches or lower layers. Editor's note: For UE actions based on ltm-CandidateNoResetL2-List (in the case of no L2 reset), use FFS. Editor's note: For information on whether RACH is required for LTM candidate cells and how to do so, see FFS. Editor's Note: FFS is responsible for how to handle TAs (and cases where the UE does not have a TA) in source cells during LTM cell switching (when RACH is not performed) and whether this should be specified in RRC or MAC. Editor's note: For monitoring timers on LTM cell switches, use FFS. Editor's Note: FFS explains how to provide UL grants to the UE if RACH is not performed during LTM cell switching. 6.2 RRC Message 6.2.2 Message Definition -RRCReconfiguration The RRCReconfiguration message is a command for correcting an RRC connection. It can convey information about measurement configuration, mobility control, radio resource configuration (including RB, MAC main configuration, and physical channel configuration), and AS security configuration. Signaling radio bearer: SRB1 or SRB3 RLC-SAP:AM Logical Channel: DCCH Direction: from network to UE RRCReconfiguration message -- ASN1START -- TAG-RRCRECONFIGURATION-START RRCReconfiguration ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReconfiguration RRCReconfiguration-IEs, criticalExtensionsFuture SEQUENCE {}, } } RRCReconfiguration-Ies ::= SEQUENCE { radioBearerConfig RadioBearerConfig OPTIONAL, -- Need M secondaryCellGroup OCTET STRING (CONTAINING CellGroupConfig) OPTIONAL, -- Cond SCG measConfig MeasConfig OPTIONAL, -- Need M lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCReconfiguration-v1530-Ies OPTIONAL } RRCReconfiguration-v1530-Ies ::= SEQUENCE { masterCellGroup OCTET STRING (CONTAINING CellGroupConfig) OPTIONAL, -- Need M fullConfig ENUMERATED {true} OPTIONAL, -- Cond FullConfig dedicatedNAS-MessageList SEQUENCE (SIZE(1..maxDRB)) OF DedicatedNAS-Message OPTIONAL, -- Cond nonHO masterKeyUpdate MasterKeyUpdate OPTIONAL, -- Cond MasterKeyChange dedicatedSIB1-Delivery OCTET STRING (CONTAINING SIB1) OPTIONAL, -- Need N dedicatedSystemInformationDelivery OCTET STRING (CONTAINING SystemInformation) OPTIONAL, -- Need N otherConfig OtherConfig OPTIONAL, -- Need M nonCriticalExtension RRCReconfiguration-v1540-Ies OPTIONAL } RRCReconfiguration-v1540-Ies ::= SEQUENCE { otherConfig-v1540 OtherConfig-v1540 OPTIONAL, -- Need M nonCriticalExtension RRCReconfiguration-v1560-Ies OPTIONAL } RRCReconfiguration-v1560-Ies ::= SEQUENCE { mrdc-SecondaryCellGroupConfig SetupRelease { MRDC-SecondaryCellGroupConfig} OPTIONAL, -- Need M radioBearerConfig2 OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, -- Need M sk-Counter SK-Counter OPTIONAL, -- Need N nonCriticalExtension RRCReconfiguration-v1610-Ies OPTIONAL } RRCReconfiguration-v1610-Ies ::= SEQUENCE { otherConfig-v1610 OtherConfig-v1610 OPTIONAL, -- Need M bap-Config-r16 SetupRelease { BAP-Config-r16} OPTIONAL, -- Need M iab-IP-AddressConfigurationList-r16 IAB-IP-AddressConfigurationList-r16 OPTIONAL, -- Need M conditionalReconfiguration-r16 ConditionalReconfiguration-r16 OPTIONAL, -- Need M daps-SourceRelease-r16 ENUMERATED{true} OPTIONAL, -- Need N t316-r16 SetupRelease {T316-r16} OPTIONAL, -- Need M needForGapsConfigNR-r16 SetupRelease {NeedForGapsConfigNR-r16} OPTIONAL, -- Need M onDemandSIB-Request-r16 SetupRelease { OnDemandSIB-Request-r16} OPTIONAL, -- Need M dedicatedPosSysInfoDelivery-r16 OCTET STRING (CONTAINING PosSystemInformation-r16-Ies) OPTIONAL, -- Need N sl-ConfigDedicatedNR-r16 SetupRelease {SL-ConfigDedicatedNR-r16} OPTIONAL, -- Need M sl-ConfigDedicatedEUTRA-Info-r16 SetupRelease {SL-ConfigDedicatedEUTRA-Info-r16} OPTIONAL, -- Need M targetCellSMTC-SCG-r16 SSB-MTC OPTIONAL, -- Need S nonCriticalExtension RRCReconfiguration-v1700-Ies OPTIONAL } RRCReconfiguration-v1700-Ies ::= SEQUENCE { otherConfig-v1700 OtherConfig-v1700 OPTIONAL, -- Need M sl-L2RelayUE-Config-r17 SetupRelease { SL-L2RelayUE-Config-r17} OPTIONAL, -- Need M sl-L2RemoteUE-Config-r17 SetupRelease { SL-L2RemoteUE-Config-r17} OPTIONAL, -- Need M dedicatedPagingDelivery-r17 OCTET STRING (CONTAINING Paging) OPTIONAL, -- Cond PagingRelay needForGapNCSG-ConfigNR-r17 SetupRelease {NeedForGapNCSG-ConfigNR-r17} OPTIONAL, -- Need M needForGapNCSG-ConfigEUTRA-r17 SetupRelease {NeedForGapNCSG-ConfigEUTRA-r17} OPTIONAL, -- Need M musim-GapConfig-r17 SetupRelease {MUSIM-GapConfig-r17} OPTIONAL, -- Need M ul-GapFR2-Config-r17 SetupRelease { UL-GapFR2-Config-r17} OPTIONAL, -- Need M scg-State-r17 ENUMERATED { deactivated} OPTIONAL, -- Need N appLayerMeasConfig-r17 AppLayerMeasConfig-r17 OPTIONAL, -- Need M ue-TxTEG-RequestUL-TDOA-Config-r17 SetupRelease {UE-TxTEG-RequestUL-TDOA-Config-r17} OPTIONAL, -- Need M nonCriticalExtension RRCReconfiguration-v18xy OPTIONAL } RRCReconfiguration-v18xy-Ies ::= SEQUENCE { ltm-CandidateConfig-r18 SetupRelease {LTM-CandidateConfig-r18} OPTIONAL, -- Need M nonCriticalExtension SEQUENCE {} OPTIONAL } MRDC-SecondaryCellGroupConfig ::= SEQUENCE { mrdc-ReleaseAndAdd ENUMERATED {true} OPTIONAL, -- Need N mrdc-SecondaryCellGroup CHOICE { nr-SCG OCTET STRING (CONTAINING RRCReconfiguration), eutra-SCG OCTET STRING } } BAP-Config-r16 ::= SEQUENCE { bap-Address-r16 BIT STRING (SIZE (10)) OPTIONAL, -- Need M defaultUL-BAP-RoutingID-r16 BAP-RoutingID-r16 OPTIONAL, -- Need M defaultUL-BH-RLC-Channel-r16 BH-RLC-ChannelID-r16 OPTIONAL, -- Need M flowControlFeedbackType-r16 ENUMERATED {perBH-RLC-Channel, perRoutingID, both} OPTIONAL, -- Need R ... } MasterKeyUpdate ::= SEQUENCE { keySetChangeIndicator BOOLEAN, nextHopChainingCount NextHopChainingCount, nas-Container OCTET STRING OPTIONAL, -- Cond securityNASC ... } OnDemandSIB-Request-r16 ::= SEQUENCE { onDemandSIB-RequestProhibitTimer-r16 ENUMERATED {s0, s0dot5, s1, s2, s5, s10, s20, s30} } T316-r16 ::= ENUMERATED {ms50, ms100, ms200, ms300, ms400, ms500, ms600, ms1000, ms1500, ms2000} IAB-IP-AddressConfigurationList-r16 ::= SEQUENCE { iab-IP-AddressToAddModList-r16 SEQUENCE (SIZE(1..maxIAB-IP-Address-r16)) OF IAB-IP-AddressConfiguration-r16 OPTIONAL, -- Need N iab-IP-AddressToReleaseList-r16 SEQUENCE (SIZE(1..maxIAB-IP-Address-r16)) OF IAB-IP-AddressIndex-r16 OPTIONAL, -- Need N ... } IAB-IP-AddressConfiguration-r16 ::= SEQUENCE { iab-IP-AddressIndex-r16 IAB-IP-AddressIndex-r16, iab-IP-Address-r16 IAB-IP-Address-r16 OPTIONAL, -- Need M iab-IP-Usage-r16 IAB-IP-Usage-r16 OPTIONAL, -- Need M iab-donor-DU-BAP-Address-r16 BIT STRING (SIZE(10)) OPTIONAL, -- Need M ... } SL-ConfigDedicatedEUTRA-Info-r16 ::= SEQUENCE { sl-ConfigDedicatedEUTRA-r16 OCTET STRING OPTIONAL, -- Need M sl-TimeOffsetEUTRA-List-r16 SEQUENCE (SIZE (8)) OF SL-TimeOffsetEUTRA-r16 OPTIONAL -- Need M } SL-TimeOffsetEUTRA-r16 ::= ENUMERATED {ms0, ms0dot25, ms0dot5, ms0dot625, ms0dot75, ms1, ms1dot25, ms1dot5, ms1dot75, ms2, ms2dot5, ms3, ms4, ms5, ms6, ms8, ms10, ms20} UE-TxTEG-RequestUL-TDOA-Config-r17 ::= CHOICE { oneShot-r17 NULL, periodicReporting-r17 ENUMERATED { ms160, ms320, ms1280, ms2560, ms61440, ms81920, ms368640, ms737280} } -- TAG-RRCRECONFIGURATION-STOP -- ASN1STOP

[0113] [Table 1] <00015​​​​​​​​ [Table 3]

[0116] [Table 4]

[0117] [Table 5]

[0118] [Table 6]

[0119] [Table 7]

[0120] [Table 8]

[0121] [Table 9]

[0122] 6.3 RRC Information Element 6.3.2 Wireless Resource Control Information Elements -LTM-CandidateConfig IE LTM-CandidateConfig is used to provide LTM candidate cell configurations. LTM-CandidateConfig information element -- ASN1START -- TAG-LTM-CANDIDATECONFIG-START LTM-CandidateConfig-r18 ::= SEQUENCE { lte-ReferenceConfiguration-r18 OCTET STRING (CONTAINING RRCReconfiguration), OPTIONAL, -- Cond FirstLTM-Candidate ltm-CandidateToReleaseList-r18 LTM-CandidateToReleaseList-r18 OPTIONAL, -- Need N ltm-CandidateToAddModList-r18 LTM-CandidateToAddModList-r18 OPTIONAL, -- Need N ltm-CandidateResetL2-List-r18 SetupRelease { LTM-CandidateResetL2-List-r18} OPTIONAL -- Need M ... } LTM-CandidateToReleaseList-r18 ::= SEQUENCE (SIZE (1..maxNrofCellsLTM-r18)) OF LTM-CandidateId-r18 OPTIONAL -- Need N LTM-CandidateToAddModList-r18 ::= SEQUENCE (SIZE (1..maxNrofCellsLTM-r18)) OF LTM-Candidate-r18 LTM-Candidate-r18 ::= SEQUENCE { ltm-CandidateId-r18 LTM-CandidateId-r18, ltm-Config-r18 OCTET STRING (CONTAINING RRCReconfiguration), ltm-ConfigComplete-r18 ENUMERATED {true} OPTIONAL -- Need R ... } LTM-CandidateResetL2-List-r18 ::= SEQUENCE (SIZE (1..maxNrofCellsLTM-r18)) OF LTM-CandidateId-r18 Editor's Note: Whether LTM-CandidateNoResetL2-List should include separate reset flags for MAC, RLC, and PDCP recovery is FFS. -- TAG-LTM-CANDIDATECONFIG-STOP -- ASN1STOP

[0123] [Table 10]

[0124] [Table 11]

[0125] 6.4 RRC Multiplicity and Type Constraints - Definition of multiplicity and type constraints -- ASN1START -- TAG-MULTIPLICITY-AND-TYPE-CONSTRAINT-DEFINITIONS-START maxAdditionalRACH-r17 INTEGER ::= 256 -- Maximum number of additional RACH configurations. maxAI-DCI-PayloadSize-r16 INTEGER ::= 128 --Maximum size of the DCI payload scrambled with ai-RNTI maxAI-DCI-PayloadSize-1-r16 INTEGER ::= 127 --Maximum size of the DCI payload scrambled with ai-RNTI minus 1 maxBandComb INTEGER ::= 65536 -- Maximum number of DL band combinations maxBandsUTRA-FDD-r16 INTEGER ::= 64 -- Maximum number of bands listed in UTRA-FDD UE caps maxBH-RLC-ChannelID-r16 INTEGER ::= 65536 -- Maximum value of BH RLC Channel ID maxBT-IdReport-r16 INTEGER ::= 32 -- Maximum number of Bluetooth IDs to report maxBT-Name-r16 INTEGER ::= 4 -- Maximum number of Bluetooth name maxCAG-Cell-r16 INTEGER ::= 16 -- Maximum number of NR CAG cell ranges in SIB3, SIB4 maxTwoPUCCH-Grp-ConfigList-r16 INTEGER ::= 32 -- Maximum number of supported configuration(s) of {primary PUCCH group -- config, secondary PUCCH group config} maxTwoPUCCH-Grp-ConfigList-r17 INTEGER ::= 16 -- Maximum number of supported configuration(s) of {primary PUCCH group -- config, secondary PUCCH group config} for PUCCH cell switching maxCBR-Config-r16 INTEGER ::= 8 -- Maximum number of CBR range configurations for sidelink communication -- congestion control maxCBR-Config-1-r16 INTEGER ::= 7 -- Maximum number of CBR range configurations for sidelink communication -- congestion control minus 1 maxCBR-Level-r16 INTEGER ::= 16 -- Maximum number of CBR levels maxCBR-Level-1-r16 INTEGER ::= 15 -- Maximum number of CBR levels minus 1 maxCellExcluded INTEGER ::= 16 -- Maximum number of NR exclude-listed cell ranges in SIB3, SIB4 maxCellGroupings-r16 INTEGER ::= 32 -- Maximum number of cell groupings for NR-DC maxCellHistory-r16 INTEGER ::= 16 -- Maximum number of visited PCells reported maxPSCellHistory-r17 INTEGER ::= 16 -- Maximum number of visited PSCells across all reported PCells maxCellInter INTEGER ::= 16 -- Maximum number of inter-Freq cells listed in SIB4 maxCellIntra INTEGER ::= 16 -- Maximum number of intra-Freq cells listed in SIB3 maxCellMeasEUTRA INTEGER ::= 32 -- Maximum number of cells in E-UTRAN maxCellMeasIdle-r16 INTEGER ::= 8 -- Maximum number of cells per carrier for idle / inactive measurements maxCellMeasUTRA-FDD-r16 INTEGER ::= 32 -- Maximum number of cells in FDD UTRAN maxCellNTN-r17 INTEGER ::= 4 -- Maximum number of NTN neighbour cells for which assistance information is -- provided maxCarrierTypePairList-r16 INTEGER ::= 16 -- Maximum number of supported carrier type pair of (carrier type on which -- CSI measurement is performed, carrier type on which CSI reporting is -- performed) for CSI reporting cross PUCCH group maxCellAllowed INTEGER ::= 16 -- Maximum number of NR allow-listed cell ranges in SIB3, SIB4 maxEARFCN INTEGER ::= 262143 -- Maximum value of E-UTRA carrier frequency maxEUTRA-CellExcluded INTEGER ::= 16 -- Maximum number of E-UTRA exclude-listed physical cell identity ranges -- in SIB5 maxEUTRA-NS-Pmax INTEGER ::= 8 -- Maximum number of NS and P-Max values per band maxFeatureCombPreamblesPerRACHResource-r17 INTEGER ::= 256 -- Maximum number of feature combination preambles. maxLogMeasReport-r16 INTEGER ::= 520 -- Maximum number of entries for logged measurements maxMultiBands INTEGER ::= 8 -- Maximum number of additional frequency bands that a cell belongs to maxNARFCN INTEGER ::= 3279165 -- Maximum value of NR carrier frequency maxNR-NS-Pmax INTEGER ::= 8 -- Maximum number of NS and P-Max values per band maxFreqIdle-r16 INTEGER ::= 8 -- Maximum number of carrier frequencies for idle / inactive measurements maxNrofServingCells INTEGER ::= 32 -- Max number of serving cells (SpCells + SCells) maxNrofServingCells-1 INTEGER ::= 31 -- Max number of serving cells (SpCells + SCells) minus 1 maxNrofAggregatedCellsPerCellGroup INTEGER ::= 16 maxNrofAggregatedCellsPerCellGroupMinus4-r16 INTEGER ::= 12 maxNrofDUCells-r16 INTEGER ::= 512 -- Max number of cells configured on the collocated IAB-DU maxNrofAppLayerMeas-r17 INTEGER ::= 16 -- Max number of simultaneous application layer measurements maxNrofAppLayerMeas-1-r17 INTEGER ::= 15 -- Max number of simultaneous application layer measurements minus 1 maxNrofAvailabilityCombinationsPerSet-r16 INTEGER ::= 512 -- Max number of AvailabilityCombinationId used in the DCI format 2_5 maxNrofAvailabilityCombinationsPerSet-1-r16 INTEGER ::= 511 -- Max number of AvailabilityCombinationId used in the DCI format 2_5 minus 1 maxNrofIABResourceConfig-r17 INTEGER ::= 65536 -- Max number of IAB-ResourceConfigID used in MAC CE maxNrofIABResourceConfig-1-r17 INTEGER ::= 65535 -- Max number of IAB-ResourceConfigID used in MAC CE minus 1 maxNrofSCellActRS-r17 INTEGER ::= 255 -- Max number of RS configurations per SCell for SCell activation maxNrofSCells INTEGER ::= 31 -- Max number of secondary serving cells per cell group maxNrofCellMeas INTEGER ::= 32 -- Maximum number of entries in each of the cell lists in a measurement object maxNrofCRS-IM-InterfCell-r17 INTEGER ::= 8 -- Maximum number of LTE interference cells for CRS-IM per UE maxNrofRelayMeas-r17 INTEGER ::= 32 -- Maximum number of L2 U2N Relay UEs to measure for each measurement object -- on sidelink frequency maxNrofCG-SL-r16 INTEGER ::= 8 -- Max number of sidelink configured grant maxNrofCG-SL-1-r16 INTEGER ::= 7 -- Max number of sidelink configured grant minus 1 maxSL-GC-BC-DRX-QoS-r17 INTEGER ::= 16 -- Max number of sidelink DRX configurations for NR -- sidelink groupcast / broadcast communication maxNrofSL-RxInfoSet-r17 INTEGER ::= 4 -- Max number of sidelink DRX configuration sets in sidelink DRX assistant -- information maxNrofSS-BlocksToAverage INTEGER ::= 16 -- Max number for the (max) number of SS blocks to average to determine cell measurement maxNrofCondCells-r16 INTEGER ::= 8 -- Max number of conditional candidate SpCells maxNrofCondCells-1-r17 INTEGER ::= 7 -- Max number of conditional candidate SpCells minus 1 maxNrofCSI-RS-ResourcesToAverage INTEGER ::= 16 -- Max number for the (max) number of CSI-RS to average to determine cell measurement maxNrofDL-Allocations INTEGER ::= 16 -- Maximum number of PDSCH time domain resource allocations maxNrofDL-AllocationsExt-r17 INTEGER ::= 64 -- Maximum number of PDSCH time domain resource allocations for multi-PDSCH -- scheduling maxNrofPDU-Sessions-r17 INTEGER ::= 256 -- Maximum number of PDU Sessions maxNrofSR-ConfigPerCellGroup INTEGER ::= 8 -- Maximum number of SR configurations per cell group maxLCG-ID INTEGER ::= 7 -- Maximum value of LCG ID maxLCG-ID-IAB-r17 INTEGER ::= 255 -- Maximum value of LCG ID for IAB-MT maxLC-ID INTEGER ::= 32 -- Maximum value of Logical Channel ID maxLC-ID-Iab-r16 INTEGER ::= 65855 -- Maximum value of BH Logical Channel ID extension maxLTE-CRS-Patterns-r16 INTEGER ::= 3 -- Maximum number of additional LTE CRS rate matching patterns maxNrofTAGs INTEGER ::= 4 -- Maximum number of Timing Advance Groups maxNrofTAGs-1 INTEGER ::= 3 -- Maximum number of Timing Advance Groups minus 1 maxNrofBWPs INTEGER ::= 4 -- Maximum number of BWPs per serving cell maxNrofCombIDC INTEGER ::= 128 -- Maximum number of reported MR-DC combinations for IDC maxNrofSymbols-1 INTEGER ::= 13 -- Maximum index identifying a symbol within a slot (14 symbols, indexed from 0..13) maxNrofSlots INTEGER ::= 320 -- Maximum number of slots in a 10 ms period maxNrofSlots-1 INTEGER ::= 319 -- Maximum number of slots in a 10 ms period minus 1 maxNrofPhysicalResourceBlocks INTEGER ::= 275 -- Maximum number of PRBs maxNrofPhysicalResourceBlocks-1 INTEGER ::= 274 -- Maximum number of PRBs minus 1 maxNrofPhysicalResourceBlocksPlus1 INTEGER ::= 276 -- Maximum number of PRBs plus 1 maxNrofControlResourceSets INTEGER ::= 12 -- Max number of CoReSets configurable on a serving cell maxNrofControlResourceSets-1 INTEGER ::= 11 -- Max number of CoReSets configurable on a serving cell minus 1 maxNrofControlResourceSets-1-r16 INTEGER ::= 15 -- Max number of CoReSets configurable on a serving cell extended in minus 1 maxNrofCoresetPools-r16 INTEGER ::= 2 -- Maximum number of CORESET pools maxCoReSetDuration INTEGER ::= 3 -- Max number of OFDM symbols in a control resource set maxNrofSearchSpaces-1 INTEGER ::= 39 -- Max number of Search Spaces minus 1 maxNrofSearchSpacesLinks-1-r17 INTEGER ::= 39 -- Max number of Search Space links minus 1 maxNrofBFDResourcePerSet-r17 INTEGER ::= 64 -- Max number of reference signal in one BFD set maxSFI-DCI-PayloadSize INTEGER ::= 128 -- Max number payload of a DCI scrambled with SFI-RNTI maxSFI-DCI-PayloadSize-1 INTEGER ::= 127 -- Max number payload of a DCI scrambled with SFI-RNTI minus 1 maxIAB-IP-Address-r16 INTEGER ::= 32 -- Max number of assigned IP addresses maxINT-DCI-PayloadSize INTEGER ::= 126 -- Max number payload of a DCI scrambled with INT-RNTI maxINT-DCI-PayloadSize-1 INTEGER ::= 125 -- Max number payload of a DCI scrambled with INT-RNTI minus 1 maxNrofRateMatchPatterns INTEGER ::= 4 -- Max number of rate matching patterns that may be configured maxNrofRateMatchPatterns-1 INTEGER ::= 3 -- Max number of rate matching patterns that may be configured minus 1 maxNrofRateMatchPatternsPerGroup INTEGER ::= 8 -- Max number of rate matching patterns that may be configured in one group maxNrofCSI-ReportConfigurations INTEGER ::= 48 -- Maximum number of report configurations maxNrofCSI-ReportConfigurations-1 INTEGER ::= 47 -- Maximum number of report configurations minus 1 maxNrofCSI-ResourceConfigurations INTEGER ::= 112 -- Maximum number of resource configurations maxNrofCSI-ResourceConfigurations-1 INTEGER ::= 111 -- Maximum number of resource configurations minus 1 maxNrofAP-CSI-RS-ResourcesPerSet INTEGER ::= 16 maxNrOfCSI-AperiodicTriggers INTEGER ::= 128 -- Maximum number of triggers for aperiodic CSI reporting maxNrofReportConfigPerAperiodicTrigger INTEGER ::= 16 -- Maximum number of report configurations per trigger state for aperiodic reporting maxNrofNZP-CSI-RS-Resources INTEGER ::= 192 -- Maximum number of Non-Zero-Power (NZP) CSI-RS resources maxNrofNZP-CSI-RS-Resources-1 INTEGER ::= 191 -- Maximum number of Non-Zero-Power (NZP) CSI-RS resources minus 1 maxNrofNZP-CSI-RS-ResourcesPerSet INTEGER ::= 64 -- Maximum number of NZP CSI-RS resources per resource set maxNrofNZP-CSI-RS-ResourceSets INTEGER ::= 64 -- Maximum number of NZP CSI-RS resource sets per cell maxNrofNZP-CSI-RS-ResourceSets-1 INTEGER ::= 63 -- Maximum number of NZP CSI-RS resource sets per cell minus 1 maxNrofNZP-CSI-RS-ResourceSetsPerConfig INTEGER ::= 16 -- Maximum number of resource sets per resource configuration maxNrofNZP-CSI-RS-ResourcesPerConfig INTEGER ::= 128 -- Maximum number of resources per resource configuration maxNrofZP-CSI-RS-Resources INTEGER ::= 32 -- Maximum number of Zero-Power (ZP) CSI-RS resources maxNrofZP-CSI-RS-Resources-1 INTEGER ::= 31 -- Maximum number of Zero-Power (ZP) CSI-RS resources minus 1 maxNrofZP-CSI-RS-ResourceSets-1 INTEGER ::= 15 maxNrofZP-CSI-RS-ResourcesPerSet INTEGER ::= 16 maxNrofZP-CSI-RS-ResourceSets INTEGER ::= 16 maxNrofCSI-IM-Resources INTEGER ::= 32 -- Maximum number of CSI-IM resources maxNrofCSI-IM-Resources-1 INTEGER ::= 31 -- Maximum number of CSI-IM resources minus 1 maxNrofCSI-IM-ResourcesPerSet INTEGER ::= 8 -- Maximum number of CSI-IM resources per set maxNrofCSI-IM-ResourceSets INTEGER ::= 64 -- Maximum number of NZP CSI-IM resource sets per cell maxNrofCSI-IM-ResourceSets-1 INTEGER ::= 63 -- Maximum number of NZP CSI-IM resource sets per cell minus 1 maxNrofCSI-IM-ResourceSetsPerConfig INTEGER ::= 16 -- Maximum number of CSI IM resource sets per resource configuration maxNrofCSI-SSB-ResourcePerSet INTEGER ::= 64 -- Maximum number of SSB resources in a resource set maxNrofCSI-SSB-ResourceSets INTEGER ::= 64 -- Maximum number of CSI SSB resource sets per cell maxNrofCSI-SSB-ResourceSets-1 INTEGER ::= 63 -- Maximum number of CSI SSB resource sets per cell minus 1 maxNrofCSI-SSB-ResourceSetsPerConfig INTEGER ::= 1 -- Maximum number of CSI SSB resource sets per resource configuration maxNrofCSI-SSB-ResourceSetsPerConfigExt INTEGER ::= 2 -- Maximum number of CSI SSB resource sets per resource configuration -- extended maxNrofFailureDetectionResources INTEGER ::= 10 -- Maximum number of failure detection resources maxNrofFailureDetectionResources-1 INTEGER ::= 9 -- Maximum number of failure detection resources minus 1 maxNrofFailureDetectionResources-1-r17 INTEGER ::= 63 -- Maximum number of the enhanced failure detection resources minus 1 maxNrofFreqSL-r16 INTEGER ::= 8 -- Maximum number of carrier frequency for NR sidelink communication maxNrofSL-BWPs-r16 INTEGER ::= 4 -- Maximum number of BWP for NR sidelink communication maxFreqSL-EUTRA-r16 INTEGER ::= 8 -- Maximum number of EUTRA anchor carrier frequency for NR sidelink communication maxNrofSL-MeasId-r16 INTEGER ::= 64 -- Maximum number of sidelink measurement identity (RSRP) per destination maxNrofSL-ObjectId-r16 INTEGER ::= 64 -- Maximum number of sidelink measurement objects (RSRP) per destination maxNrofSL-ReportConfigId-r16 INTEGER ::= 64 -- Maximum number of sidelink measurement reporting configuration(RSRP) per destination maxNrofSL-PoolToMeasureNR-r16 INTEGER ::= 8 -- Maximum number of resource pool for NR sidelink measurement to measure for -- each measurement object (for CBR) maxFreqSL-NR-r16 INTEGER ::= 8 -- Maximum number of NR anchor carrier frequency for NR sidelink communication maxNrofSL-QFIs-r16 INTEGER ::= 2048 -- Maximum number of QoS flow for NR sidelink communication per UE maxNrofSL-QFIsPerDest-r16 INTEGER ::= 64 -- Maximum number of QoS flow per destination for NR sidelink communication maxNrofObjectId INTEGER ::= 64 -- Maximum number of measurement objects maxNrofPageRec INTEGER ::= 32 -- Maximum number of page records maxNrofPCI-Ranges INTEGER ::= 8 -- Maximum number of PCI ranges maxPLMN INTEGER ::= 12 -- Maximum number of PLMNs broadcast and reported by UE at establishment maxTAC-r17 INTEGER ::= 12 -- Maximum number of Tracking Area Codes to which a cell belongs to maxNrofCSI-RS-ResourcesRRM INTEGER ::= 96 -- Maximum number of CSI-RS resources per cell for an RRM measurement object maxNrofCSI-RS-ResourcesRRM-1 INTEGER ::= 95 -- Maximum number of CSI-RS resources per cell for an RRM measurement object -- minus 1. maxNrofMeasId INTEGER ::= 64 -- Maximum number of configured measurements maxNrofQuantityConfig INTEGER ::= 2 -- Maximum number of quantity configurations maxNrofCSI-RS-CellsRRM INTEGER ::= 96 -- Maximum number of cells with CSI-RS resources for an RRM measurement object maxNrofSL-Dest-r16 INTEGER ::= 32 -- Maximum number of destination for NR sidelink communication and discovery maxNrofSL-Dest-1-r16 INTEGER ::= 31 -- Highest index of destination for NR sidelink communication and discovery maxNrofSLRB-r16 INTEGER ::= 512 -- Maximum number of radio bearer for NR sidelink communication per UE maxSL-LCID-r16 INTEGER ::= 512 -- Maximum number of RLC bearer for NR sidelink communication per UE maxSL-SyncConfig-r16 INTEGER ::= 16 -- Maximum number of sidelink Sync configurations maxNrofRXPool-r16 INTEGER ::= 16 -- Maximum number of Rx resource pool for NR sidelink communication and -- discovery maxNrofTXPool-r16 INTEGER ::= 8 -- Maximum number of Tx resource pool for NR sidelink communication and -- discovery maxNrofPoolID-r16 INTEGER ::= 16 -- Maximum index of resource pool for NR sidelink communication and -- discovery maxNrofSRS-PathlossReferenceRS-r16 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for SRS power control. maxNrofSRS-PathlossReferenceRS-1-r16 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for SRS power control -- minus 1. maxNrofSRS-ResourceSets INTEGER ::= 16 -- Maximum number of SRS resource sets in a BWP. maxNrofSRS-ResourceSets-1 INTEGER ::= 15 -- Maximum number of SRS resource sets in a BWP minus 1. maxNrofSRS-PosResourceSets-r16 INTEGER ::= 16 -- Maximum number of SRS Positioning resource sets in a BWP. maxNrofSRS-PosResourceSets-1-r16 INTEGER ::= 15 -- Maximum number of SRS Positioning resource sets in a BWP minus 1. maxNrofSRS-Resources INTEGER ::= 64 -- Maximum number of SRS resources. maxNrofSRS-Resources-1 INTEGER ::= 63 -- Maximum number of SRS resources minus 1. maxNrofSRS-PosResources-r16 INTEGER ::= 64 -- Maximum number of SRS Positioning resources. maxNrofSRS-PosResources-1-r16 INTEGER ::= 63 -- Maximum number of SRS Positioning resources minus 1. maxNrofSRS-ResourcesPerSet INTEGER ::= 16 -- Maximum number of SRS resources in an SRS resource set maxNrofSRS-TriggerStates-1 INTEGER ::= 3 -- Maximum number of SRS trigger states minus 1, i.e., the largest code point. maxNrofSRS-TriggerStates-2 INTEGER ::= 2 -- Maximum number of SRS trigger states minus 2. maxRAT-CapabilityContainers INTEGER ::= 8 -- Maximum number of interworking RAT containers (incl NR and MRDC) maxSimultaneousBands INTEGER ::= 32 -- Maximum number of simultaneously aggregated bands maxULTxSwitchingBandPairs INTEGER ::= 32 -- Maximum number of band pairs supporting dynamic UL Tx switching in a band -- combination. maxNrofSlotFormatCombinationsPerSet INTEGER ::= 512 -- Maximum number of Slot Format Combinations in a SF-Set. maxNrofSlotFormatCombinationsPerSet-1 INTEGER ::= 511 -- Maximum number of Slot Format Combinations in a SF-Set minus 1. maxNrofTrafficPattern-r16 INTEGER ::= 8 -- Maximum number of Traffic Pattern for NR sidelink communication. maxNrofPUCCH-Resources INTEGER ::= 128 maxNrofPUCCH-Resources-1 INTEGER ::= 127 maxNrofPUCCH-ResourceSets INTEGER ::= 4 -- Maximum number of PUCCH Resource Sets maxNrofPUCCH-ResourceSets-1 INTEGER ::= 3 -- Maximum number of PUCCH Resource Sets minus 1. maxNrofPUCCH-ResourcesPerSet INTEGER ::= 32 -- Maximum number of PUCCH Resources per PUCCH-ResourceSet maxNrofPUCCH-P0-PerSet INTEGER ::= 8 -- Maximum number of P0-pucch present in a p0-pucch set maxNrofPUCCH-PathlossReferenceRSs INTEGER ::= 4 -- Maximum number of RSs used as pathloss reference for PUCCH power control. maxNrofPUCCH-PathlossReferenceRSs-1 INTEGER ::= 3 -- Maximum number of RSs used as pathloss reference for PUCCH power control -- minus 1. maxNrofPUCCH-PathlossReferenceRSs-r16 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for PUCCH power control -- extended. maxNrofPUCCH-PathlossReferenceRSs-1-r16 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for PUCCH power control -- minus 1 extended. maxNrofPUCCH-PathlossReferenceRSs-1-r17 INTEGER ::= 7 -- Maximum number of RSs used as pathloss reference for PUCCH power control -- minus 1. maxNrofPUCCH-PathlossReferenceRSsDiff-r16 INTEGER ::= 60 -- Difference between the extended maximum and the non-extended maximum maxNrofPUCCH-ResourceGroups-r16 INTEGER ::= 4 -- Maximum number of PUCCH resources groups. maxNrofPUCCH-ResourcesPerGroup-r16 INTEGER ::= 128 -- Maximum number of PUCCH resources in a PUCCH group. maxNrofPowerControlSetInfos-r17 INTEGER ::= 8 -- Maximum number of PUCCH power control set infos maxNrofMultiplePUSCHs-r16 INTEGER ::= 8 -- Maximum number of multiple PUSCHs in PUSCH TDRA list maxNrofP0-PUSCH-AlphaSets INTEGER ::= 30 -- Maximum number of P0-pusch-alpha-sets (see TS 38.213

[13] , clause 7.1) maxNrofP0-PUSCH-AlphaSets-1 INTEGER ::= 29 -- Maximum number of P0-pusch-alpha-sets minus 1 (see TS 38.213

[13] , clause 7.1) maxNrofPUSCH-PathlossReferenceRSs INTEGER ::= 4 -- Maximum number of RSs used as pathloss reference for PUSCH power control. maxNrofPUSCH-PathlossReferenceRSs-1 INTEGER ::= 3 -- Maximum number of RSs used as pathloss reference for PUSCH power control -- minus 1. maxNrofPUSCH-PathlossReferenceRSs-r16 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for PUSCH power control -- extended maxNrofPUSCH-PathlossReferenceRSs-1-r16 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for PUSCH power control -- extended minus 1 maxNrofPUSCH-PathlossReferenceRSsDiff-r16 INTEGER ::= 60 -- Difference between maxNrofPUSCH-PathlossReferenceRSs-r16 and -- maxNrofPUSCH-PathlossReferenceRSs maxNrofPathlossReferenceRSs-r17 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for PUSCH, PUCCH, SRS -- power control for unified TCI state operation maxNrofPathlossReferenceRSs-1-r17 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for PUSCH, PUCCH, SRS -- power control for unified TCI state operation minus 1 maxNrofNAICS-Entries INTEGER ::= 8 -- Maximum number of supported NAICS capability set maxBands INTEGER ::= 1024 -- Maximum number of supported bands in UE capability. maxBandsMRDC INTEGER ::= 1280 maxBandsEUTRA INTEGER ::= 256 maxCellReport INTEGER ::= 8 maxDRB INTEGER ::= 29 -- Maximum number of DRBs (that can be added in DRB-ToAddModList). maxFreq INTEGER ::= 8 -- Max number of frequencies. maxFreqLayers INTEGER ::= 4 -- Max number of frequency layers. maxFreqPlus1 INTEGER ::= 9 -- Max number of frequencies for Slicing. maxFreqIDC-r16 INTEGER ::= 128 -- Max number of frequencies for IDC indication. maxCombIDC-r16 INTEGER ::= 128 -- Max number of reported UL CA for IDC indication. maxFreqIDC-MRDC INTEGER ::= 32 -- Maximum number of candidate NR frequencies for MR-DC IDC indication maxNrofCandidateBeams INTEGER ::= 16 -- Max number of PRACH-ResourceDedicatedBFR in BFR config. maxNrofCandidateBeams-r16 INTEGER ::= 64 -- Max number of candidate beam resources in BFR config. maxNrofCandidateBeamsExt-r16 INTEGER ::= 48 -- Max number of PRACH-ResourceDedicatedBFR in the CandidateBeamRSListExt maxNrofPCIsPerSMTC INTEGER ::= 64 -- Maximum number of PCIs per SMTC. maxNrofQFIs INTEGER ::= 64 maxNrofResourceAvailabilityPerCombination-r16 INTEGER ::= 256 maxNrOfSemiPersistentPUSCH-Triggers INTEGER ::= 64 -- Maximum number of triggers for semi persistent reporting on PUSCH maxNrofSR-Resources INTEGER ::= 8 -- Maximum number of SR resources per BWP in a cell. maxNrofSlotFormatsPerCombination INTEGER ::= 256 maxNrofSpatialRelationInfos INTEGER ::= 8 maxNrofSpatialRelationInfos-plus-1 INTEGER ::= 9 maxNrofSpatialRelationInfos-r16 INTEGER ::= 64 maxNrofSpatialRelationInfosDiff-r16 INTEGER ::= 56 -- Difference between maxNrofSpatialRelationInfos-r16 and maxNrofSpatialRelationInfos maxNrofIndexesToReport INTEGER ::= 32 maxNrofIndexesToReport2 INTEGER ::= 64 maxNrofSSBs-r16 INTEGER ::= 64 -- Maximum number of SSB resources in a resource set. maxNrofSSBs-1 INTEGER ::= 63 -- Maximum number of SSB resources in a resource set minus 1. maxNrofS-NSSAI INTEGER ::= 8 -- Maximum number of S-NSSAI. maxNrofTCI-StatesPDCCH INTEGER ::= 64 maxNrofTCI-States INTEGER ::= 128 -- Maximum number of TCI states. maxNrofTCI-States-1 INTEGER ::= 127 -- Maximum number of TCI states minus 1. maxUL-TCI-r17 INTEGER ::= 64 -- Maximum number of TCI states. maxUL-TCI-1-r17 INTEGER ::= 63 -- Maximum number of TCI states minus 1. maxNrofAdditionalPCI-r17 INTEGER ::= 7 -- Maximum number of additional PCI maxMPE-Resources-r17 INTEGER ::= 64 -- Maximum number of pooled MPE resources maxNrofUL-Allocations INTEGER ::= 16 -- Maximum number of PUSCH time domain resource allocations. maxQFI INTEGER ::= 63 maxRA-CSIRS-Resources INTEGER ::= 96 maxRA-OccasionsPerCSIRS INTEGER ::= 64 -- Maximum number of RA occasions for one CSI-RS maxRA-Occasions-1 INTEGER ::= 511 -- Maximum number of RA occasions in the system maxRA-SSB-Resources INTEGER ::= 64 maxSCSs INTEGER ::= 5 maxSecondaryCellGroups INTEGER ::= 3 maxNrofServingCellsEUTRA INTEGER ::= 32 maxMBSFN-Allocations INTEGER ::= 8 maxNrofMultiBands INTEGER ::= 8 maxCellSFTD INTEGER ::= 3 -- Maximum number of cells for SFTD reporting maxReportConfigId INTEGER ::= 64 maxNrofCodebooks INTEGER ::= 16 -- Maximum number of codebooks supported by the UE maxNrofCSI-RS-ResourcesExt-r16 INTEGER ::= 16 -- Maximum number of codebook resources supported by the UE for eType2 / Codebook combo maxNrofCSI-RS-ResourcesExt-r17 INTEGER ::= 8 -- Maximum number of codebook resources for fetype2R1 and fetype2R2 maxNrofCSI-RS-Resources INTEGER ::= 7 -- Maximum number of codebook resources supported by the UE maxNrofCSI-RS-ResourcesAlt-r16 INTEGER ::= 512 -- Maximum number of alternative codebook resources supported by the UE maxNrofCSI-RS-ResourcesAlt-1-r16 INTEGER ::= 511 -- Maximum number of alternative codebook resources supported by the UE minus 1 maxNrofSRI-PUSCH-Mappings INTEGER ::= 16 maxNrofSRI-PUSCH-Mappings-1 INTEGER ::= 15 maxSIB INTEGER::= 32 -- Maximum number of SIBs maxSI-Message INTEGER::= 32 -- Maximum number of SI messages maxSIB-MessagePlus1-r17 INTEGER::= 33 -- Maximum number of SIB messages plus 1 maxPO-perPF INTEGER ::= 4 -- Maximum number of paging occasion per paging frame maxPEI-perPF-r17 INTEGER ::= 4 -- Maximum number of PEI occasion per paging frame maxAccessCat-1 INTEGER ::= 63 -- Maximum number of Access Categories minus 1 maxBarringInfoSet INTEGER ::= 8 -- Maximum number of access control parameter sets maxCellEUTRA INTEGER ::= 8 -- Maximum number of E-UTRA cells in SIB list maxEUTRA-Carrier INTEGER ::= 8 -- Maximum number of E-UTRA carriers in SIB list maxPLMNIdentities INTEGER ::= 8 -- Maximum number of PLMN identities in RAN area configurations maxDownlinkFeatureSets INTEGER ::= 1024 -- (for NR DL) Total number of FeatureSets (size of the pool) maxUplinkFeatureSets INTEGER ::= 1024 -- (for NR UL) Total number of FeatureSets (size of the pool) maxEUTRA-DL-FeatureSets INTEGER ::= 256 -- (for E-UTRA) Total number of FeatureSets (size of the pool) maxEUTRA-UL-FeatureSets INTEGER ::= 256 -- (for E-UTRA) Total number of FeatureSets (size of the pool) maxFeatureSetsPerBand INTEGER ::= 128 -- (for NR) The number of feature sets associated with one band. maxPerCC-FeatureSets INTEGER ::= 1024 -- (for NR) Total number of CC-specific FeatureSets (size of the pool) maxFeatureSetCombinations INTEGER ::= 1024 -- (for MR-DC / NR)Total number of Feature set combinations (size of the pool) maxInterRAT-RSTD-Freq INTEGER ::= 3 maxGIN-r17 INTEGER ::= 24 -- Maximum number of broadcast GINs maxHRNN-Len-r16 INTEGER ::= 48 -- Maximum length of HRNNs maxNPN-r16 INTEGER ::= 12 -- Maximum number of NPNs broadcast and reported by UE at establishment maxNrOfMinSchedulingOffsetValues-r16 INTEGER ::= 2 -- Maximum number of min. scheduling offset (K0 / K2) configurations maxK0-SchedulingOffset-r16 INTEGER ::= 16 -- Maximum number of slots configured as min. scheduling offset (K0) maxK2-SchedulingOffset-r16 INTEGER ::= 16 -- Maximum number of slots configured as min. scheduling offset (K2) maxK0-SchedulingOffset-r17 INTEGER ::= 64 -- Maximum number of slots configured as min. scheduling offset (K0) maxK2-SchedulingOffset-r17 INTEGER ::= 64 -- Maximum number of slots configured as min. scheduling offset (K2) maxDCI-2-6-Size-r16 INTEGER ::= 140 -- Maximum size of DCI format 2-6 maxDCI-2-7-Size-r17 INTEGER ::= 43 -- Maximum size of DCI format 2-7 maxDCI-2-6-Size-1-r16 INTEGER ::= 139 -- Maximum DCI format 2-6 size minus 1 maxNrofUL-Allocations-r16 INTEGER ::= 64 -- Maximum number of PUSCH time domain resource allocations maxNrofP0-PUSCH-Set-r16 INTEGER ::= 2 -- Maximum number of P0 PUSCH set(s) maxOnDemandSIB-r16 INTEGER ::= 8 -- Maximum number of SIB(s) that can be requested on-demand maxOnDemandPosSIB-r16 INTEGER ::= 32 -- Maximum number of posSIB(s) that can be requested on-demand maxCI-DCI-PayloadSize-r16 INTEGER ::= 126 -- Maximum number of the DCI size for CI maxCI-DCI-PayloadSize-1-r16 INTEGER ::= 125 -- Maximum number of the DCI size for CI minus 1 maxUu-RelayRLC-ChannelID-r17 INTEGER ::= 32 -- Maximum value of Uu Relay RLC channel ID maxWLAN-Id-Report-r16 INTEGER ::= 32 -- Maximum number of WLAN IDs to report maxWLAN-Name-r16 INTEGER ::= 4 -- Maximum number of WLAN name maxRAReport-r16 INTEGER ::= 8 -- Maximum number of RA procedures information to be included in the RA report maxTxConfig-r16 INTEGER ::= 64 -- Maximum number of sidelink transmission parameters configurations maxTxConfig-1-r16 INTEGER ::= 63 -- Maximum number of sidelink transmission parameters configurations minus 1 maxPSSCH-TxConfig-r16 INTEGER ::= 16 -- Maximum number of PSSCH TX configurations maxNrofCLI-RSSI-Resources-r16 INTEGER ::= 64 -- Maximum number of CLI-RSSI resources for UE maxNrofCLI-RSSI-Resources-1-r16 INTEGER ::= 63 -- Maximum number of CLI-RSSI resources for UE minus 1 maxNrofCLI-SRS-Resources-r16 INTEGER ::= 32 -- Maximum number of SRS resources for CLI measurement for UE maxCLI-Report-r16 INTEGER ::= 8 maxNrofCC-Group-r17 INTEGER ::= 16 -- Maximum number of CC groups for DC location report maxNrofConfiguredGrantConfig-r16 INTEGER ::= 12 -- Maximum number of configured grant configurations per BWP maxNrofConfiguredGrantConfig-1-r16 INTEGER ::= 11 -- Maximum number of configured grant configurations per BWP minus 1 maxNrofCG-Type2DeactivationState INTEGER ::= 16 -- Maximum number of deactivation state for type 2 configured grants per BWP maxNrofConfiguredGrantConfigMAC-1-r16 INTEGER ::= 31 -- Maximum number of configured grant configurations per MAC entity minus 1 maxNrofSPS-Config-r16 INTEGER ::= 8 -- Maximum number of SPS configurations per BWP maxNrofSPS-Config-1-r16 INTEGER ::= 7 -- Maximum number of SPS configurations per BWP minus 1 maxNrofSPS-DeactivationState INTEGER ::= 16 -- Maximum number of deactivation state for SPS per BWP maxNrofPPW-Config-r17 INTEGER ::= 4 -- Maximum number of Preconfigured PRS processing windows per DL BWP maxNrofPPW-ID-1-r17 INTEGER ::= 15 -- Maximum number of Preconfigured PRS processing windows minus 1 maxNrOfTxTEGReport-r17 INTEGER ::= 256 -- Maximum number of UE Tx Timing Error Group Report maxNrOfTxTEG-ID-1-r17 INTEGER ::= 7 -- Maximum number of UE Tx Timing Error Group ID minus 1 maxNrofDormancyGroups INTEGER ::= 5 -- maxNrofPagingSubgroups-r17 INTEGER ::= 8 -- Maximum number of paging subgroups per paging occasion maxNrofPUCCH-ResourceGroups-1-r16 INTEGER ::= 3 -- maxNrofReqComDC-Location-r17 INTEGER ::= 128 -- Maximum number of requested carriers / BWPs combinations for DC location -- report maxNrofServingCellsTCI-r16 INTEGER ::= 32 -- Maximum number of serving cells in simultaneousTCI-UpdateList maxNrofTxDC-TwoCarrier-r16 INTEGER ::= 64 -- Maximum number of UL Tx DC locations reported by the UE for 2CC uplink CA maxNrofRB-SetGroups-r17 INTEGER ::= 8 -- Maximum number of RB set groups maxNrofRB-Sets-r17 INTEGER ::= 8 -- Maximum number of RB sets maxNrofEnhType3HARQ-ACK-r17 INTEGER ::= 8 -- Maximum number of enhanced type 3 HARQ-ACK codebook maxNrofEnhType3HARQ-ACK-1-r17 INTEGER ::= 7 -- Maximum number of enhanced type 3 HARQ-ACK codebook minus 1 maxNrofPRS-ResourcesPerSet-r17 INTEGER ::= 64 -- Maximum number of PRS resources for one set maxNrofPRS-ResourcesPerSet-1-r17 INTEGER ::= 63 -- Maximum number of PRS resources for one set minus 1 maxNrofPRS-ResourceOffsetValue-1-r17 INTEGER ::= 511 maxNrofGapId-r17 INTEGER ::= 8 -- Maximum number of measurement gap ID is FFS maxNrofPreConfigPosGapId-r17 INTEGER ::= 16 -- Maximum number of preconfigured positioning measurement gap maxNrOfGapPri-r17 INTEGER ::= 16 -- Maximum number of gap priority level maxCEFReport-r17 INTEGER ::= 4 -- Maximum number of CEF reports by the UE maxNrofMultiplePDSCHs-r17 INTEGER ::= 8 -- Maximum number of PDSCHs in PDSCH TDRA list maxSliceInfo-r17 INTEGER ::= 8 -- Maximum number of NSAGs maxCellSlice-r17 INTEGER ::= 16 -- Maximum number of cells supporting the NSAG maxNrofTRS-ResourceSets-r17 INTEGER ::= 64 -- Maximum number of TRS resource sets maxNrofSearchSpaceGroups-1-r17 INTEGER ::= 2 -- Maximum number of search space groups minus 1 maxNrofRemoteUE-r17 INTEGER ::= 32 -- Maximum number of connected L2 U2N Remote UEs maxDCI-4-2-Size-r17 INTEGER ::= 140 -- Maximum size of DCI format 4-2 maxFreqMBS-r17 INTEGER ::= 16 -- Maximum number of MBS frequencies reported in MBSInterestIndication maxNrofDRX-ConfigPTM-r17 INTEGER ::= 64 -- Max number of DRX configuration for PTM provided in MBS broadcast in a -- cell maxNrofDRX-ConfigPTM-1-r17 INTEGER ::= 63 -- Max number of DRX configuration for PTM provided in MBS broadcast in a -- cell minus 1 maxNrofMBS-ServiceListPerUE-r17 INTEGER ::= 16 -- Maximum number of services which the UE can include in the MBS interest -- indication maxNrofMBS-Session-r17 INTEGER ::= 1024 -- Maximum number of MBS sessions provided in MBS broadcast in a cell maxNrofMTCH-SSB-MappingWindow-r17 INTEGER ::= 16 -- Maximum number of MTCH to SSB beam mapping pattern maxNrofMTCH-SSB-MappingWindow-1-r17 INTEGER ::= 15 -- Maximum number of MTCH to SSB beam mapping pattern minus 1 maxNrofMRB-Broadcast-r17 INTEGER ::= 4 -- Maximum number of broadcast MRBs configured for one MBS broadcast service maxNrofPageGroup-r17 INTEGER ::= 32 -- Maximum number of paging groups in a paging message maxNrofPDSCH-ConfigPTM-r17 INTEGER ::= 16 -- Maximum number of PDSCH configuration groups for PTM maxNrofPDSCH-ConfigPTM-1-r17 INTEGER ::= 15 -- Maximum number of PDSCH configuration groups for PTM minus 1 maxG-RNTI-r17 INTEGER ::= 16 -- Maximum number of G-RNTI that can be configured for a UE. maxG-RNTI-1-r17 INTEGER ::= 15 -- Maximum number of G-RNTI that can be configured for a UE minus 1. maxG-CS-RNTI-r17 INTEGER ::= 8 -- Maximum number of G-CS-RNTI that can be configured for a UE. maxG-CS-RNTI-1-r17 INTEGER ::= 7 -- Maximum number of G-CS-RNTI that can be configured for a UE minus 1. maxMRB-r17 INTEGER ::= 32 -- Maximum number of multicast MRBs (that can be added in MRB-ToAddModLIst) maxFSAI-MBS-r17 INTEGER ::= 64 -- Maximum number of MBS frequency selection area identities maxNeighCellMBS-r17 INTEGER ::= 8 -- Maximum number of MBS broadcast neighbour cells maxNrofPdcch-BlindDetectionMixed-1-r16 INTEGER ::= 7 -- Maximum number of combinations of mixed Rel-16 and Rel-15 PDCCH -- monitoring capabilities minus 1 maxNrofPdcch-BlindDetection-r17 INTEGER ::= 16 -- Maximum number of combinations of PDCCH blind detection monitoring Program performance maxNrofCellsLTM-r18 INTEGER ::= 99999 -- Maximum number of LTM candidate cells -- TAG-MULTIPLICITY-AND-TYPE-CONSTRAINT-DEFINITIONS-STOP -- ASN1STOP Editor's note: maxK0-SchedulingOffset and maxK0-SchedulingOffset require verification using RAN1. 7.4 UE Variables -VarLTM-Config IE VarLTM-Config is used to store reference configurations and LTM candidate cell configurations. VarLTM-Config UE Variables -- ASN1START -- TAG-VARLTM-CONFIG-START VarLTM-Config-r18-IEs ::= SEQUENCE { ltm-ReferenceConfiguration-r18 OCTET STRING (CONTAINING RRCReconfiguration), ltm-CandidateList-r18 LTM-CandidateList-r18 ltm-CandidateResetL2-List-r18 LTM-CandidateResetL2-List-r18 } LTM-CandidateList-r18 ::= SEQUENCE (SIZE (1..maxNrofCellsLTM-r18)) OF LTM-Candidate-r18 LTM-CandidateResetL2-List-r18 ::= SEQUENCE (SIZE (1..maxNrofCellsLTM-r18)) OF LTM-Candidate-r18 -- TAG-VARLTM-CONFIG-STOP -- ASN1STOP -VarLTM-UE-Config IE VarLTM-UE-Config is used to store the generated UE configurations related to the received LTM candidate cell configurations. VarLTM-UE-Config UE variable -- ASN1START -- TAG-VARLTM-CONFIG-START VarLTM-UE-Config-r18-IEs ::= SEQUENCE { Ue-ltm-ConfigCandidateList-r18 UE-LTM-ConfigCandidateList-r18 } UE-LTM-ConfigCandidateList-r18 ::= SEQUENCE (SIZE (1..maxNrofCellsLTM-r18)) OF UE-LTM-Config-r18 UE-LTM-Candidate-r18 ::= SEQUENCE { ltm-CandidateId-r18 LTM-CandidateId-r18, ue-LTM-Config-r18 OCTET STRING, } -- TAG-VARLTM-CONFIG-STOP -- ASN1STOP

[0126] Figure 7 shows an example of a communication system 700 according to several embodiments.

[0127] In this example, the communication system 700 includes a telecommunications network 702 which includes an access network 704 such as a radio access network (RAN) and a core network 706 which includes one or more core network nodes 708. The access network 704 includes one or more access network nodes such as network nodes 710a and 710b (one or more of which may generally be referred to as network node 710), or any other similar Third Generation Partnership Project (3GPP) access node or non-3GPP access point. Furthermore, as will be understood by those skilled in the art, a network node is not necessarily limited to an implementation in which the radio portion and the baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that a network node includes a subdivided implementation or a part thereof. For example, in some embodiments, the telecommunications network 702 includes one or more open RAN (ORAN) network nodes. An ORAN network node is a node in a telecommunications network 702 that supports ORAN standards (e.g., standards published by the O-RAN Alliance or any similar organization) and can operate alone or in conjunction with other nodes to implement one or more functions of any node in the telecommunications network 702, including one or more network nodes 710 and / or core network nodes 708.

[0128] Examples of ORAN network nodes include open central units (O-CUs) including open radio units (O-RUs), open distributed units (O-DUs), O-CU control planes (O-CU-CPs), or O-CU user planes (O-CU-UPs), RAN intelligent controllers (near-real-time or non-real-time) hosting software or software plugins such as quasi-real-time control applications (e.g., xApps) or non-real-time control applications (e.g., rApps), or any combination thereof (the adjective "open" specifies support for ORAN standards). Network nodes can support ORAN standards by supporting interfaces defined by ORAN standards, such as A1, F1, W1, E1, E2, X2, Xn interfaces, open fronthaul user plane interfaces, or open fronthaul management plane interfaces. Furthermore, ORAN access nodes may be logical nodes within physical nodes. In addition, ORAN network nodes may be implemented in a virtualized environment (described further later) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform organized by a service management and orchestration framework via an O-2 interface defined by the O-RAN Alliance or equivalent technology. Network nodes 710 facilitate direct or indirect connectivity of user equipment (UEs) by connecting UEs 712a, 712b, 712c, and 712d (one or more of which may be collectively referred to as UE712) to the core network 706 over one or more wireless connections.

[0129] Exemplary wireless communications on a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for carrying information without using wires, cables, or other physical conductors. Furthermore, in various embodiments, the communication system 700 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals, whether wired or wireless. The communication system 700 may include and / or interface with any type of communication, telecommunications, data, cellular, wireless network, and / or other similar types of systems.

[0130] UE712 may be any of a broad range of communication devices, including wireless devices that are arranged, configured, and / or operable to communicate wirelessly with network node 710 and other communication devices. Similarly, network node 710 is arranged, can communicate, is configured, and / or operable to communicate directly or indirectly with UE712 and / or other network nodes or devices in telecommunications network 702 in order to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as management within telecommunications network 702.

[0131] In the illustrated example, the core network 706 connects the network node 710 to one or more hosts, such as host 716. These connections may be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes may be directly connected to hosts. The core network 706 includes one or more core network nodes (e.g., core network node 708) structured with hardware and software components. The functions of these components may be substantially the same as those described for the UE, network nodes, and / or hosts, and therefore those descriptions are generally applicable to the corresponding components of core network node 708. An exemplary core network node includes one or more of the following functions: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Decryption Function (SIDF), Unified Data Management (UDM), Security Edge Protected Proxy (SEPP), Network Exposure Function (NEF), and / or User Plane Function (UPF).

[0132] Host 716 may be owned by or under the control of a service provider other than the operator or provider of the access network 704 and / or the telecommunications network 702, and may be operated by or on behalf of such service provider. Host 716 may host a variety of applications and provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data acquisition services such as acquisition and editing of data on a variety of ambient conditions detected by multiple UEs, analytical functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

[0133] Overall, the communication system 700 in Figure 7 enables connectivity between the UE, network nodes, and hosts. In this sense, the communication system may be configured to operate according to predefined rules or procedures, such as certain standards, including but not limited to: GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), LTE (Long Term Evolution), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standards (e.g., 6G), WLAN (wireless local area network) standards such as the IEEE (Institute of Electrical and Electronics Engineers) 802.11 standard (WiFi), and / or any other suitable wireless communication standards such as WiMax (Worldwide Interoperability for Microwave Access), Bluetooth, Z-Wave, NFC (Near Field Communication), ZigBee, LiFi, and / or any LPWAN (low-power wide-area network) standards such as LoRa and Sigfox.

[0134] In some examples, the telecommunications network 702 is a cellular network implementing functions standardized by 3GPP. Therefore, the telecommunications network 702 may support network slicing to provide various logical networks to various devices connected to the telecommunications network 702. For example, the telecommunications network 702 may provide ultra-high reliability low latency communication (URLLC) services to some UEs while providing extended mobile broadband (eMBB) services to other UEs, and / or provide massive machine type communication (mMTC) / massive IoT services to further UEs.

[0135] In some examples, UE712 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to access network 704 on a predetermined schedule, triggered by internal or external events, or in response to a request from access network 704. Additionally, the UE may be configured to operate in single or multi-RAT, or multi-standards mode. For example, the UE may be configured to operate in any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0136] In the above example, the hub 714 communicates with the access network 704 to facilitate indirect communication between one or more UEs (e.g., UE712c and / or 712d) and a network node (e.g., network node 710b). In some examples, the hub 714 may be a controller, router, content source and analytics, or any other communication device described herein with respect to the UE. For example, the hub 714 may be a broadband router that enables the UE to access the core network 706. In another example, the hub 714 may be a controller that sends commands or instructions to one or more actuators within the UE. Commands or instructions may be received from the UE or network node 710, or accepted by executable code, scripts, processes, or other instructions within the hub 714. In yet another example, the hub 714 may be a data collector acting as temporary storage for the UE's data, which in some embodiments may perform analysis or other processing on that data. In yet another example, the hub 714 may be a content source. For example, with respect to a UE that is a VR headset, display, loudspeaker, or other media delivery device, the hub 714 may acquire media or data related to VR assets, video, audio, or other sensory information via network nodes, in which case the hub 714 provides it to the UE either directly, after performing local processing, and / or after adding additional local content. In another example, the hub 714 acts as a proxy server or orchestrator for the UE, in particular when one or more of the UEs are low-energy IoT devices.

[0137] Hub 714 may have a steady / persistent or intermittent connection to network node 710b. Furthermore, Hub 714 may enable different communication methods and / or schedules between Hub 714 and UEs (e.g., UE712c and / or 712d), and between Hub 714 and the core network 706. In other examples, Hub 714 is connected to the core network 706 and / or one or more UEs via a wired connection. Additionally, Hub 714 may be configured to connect to an M2M service provider on the access network 704 and / or to other UEs via a direct connection. In some scenarios, a UE may establish a wireless connection with network node 710 while still being connected via Hub 714 via a wired or wireless connection. In some embodiments, Hub 714 may be a dedicated hub, i.e., a hub whose primary function is to route communication between UEs and network node 710b. In other embodiments, the hub 714 may be a non-dedicated hub, i.e., a device capable of routing communication between the UE and the network node 710b, but also capable of acting as the source and / or destination of communication for some data channel.

[0138] Figure 8 shows several embodiments of the UE800. As used herein, UE refers to a device that is capable of, configured, deployed, and / or operating wirelessly with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cell phones, VoIP (Voice over IP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicles, in-vehicle or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including Narrowband Internet of Things (NB-IoT) UEs, Machine Type Communications (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0139] A UE may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for side-link communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE does not necessarily have a user in the sense of a person who owns and / or operates the device in question. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended to be sold to or operated by a human user, but may not be associated with a particular human user, at least initially. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended to be sold to or operated by an end user, but may be associated with a user or operated for the benefit of a user.

[0140] The UE800 includes an input / output interface 806, a power supply 808, memory 810, a communication interface 812, and / or any other components, or any combination thereof, and processing circuitry 802 operably connected via bus 804. A given UE may utilize all or a subset of the components shown in Figure 8. The level of integration between components may vary between one UE and another. Furthermore, a given UE may include multiple instances of a component, such as multiple processors, memory, transceivers, transmitters, receivers, etc.

[0141] The processing circuit 802 is configured to process instruction sets and data, and may be configured to implement some sequential state machine capable of operating to execute instruction sets stored in memory 810 as machine-readable computer programs. The processing circuit 802 may be implemented as one or more hardware-implemented state machines (e.g., discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.), programmable logic with appropriate firmware, one or more stored computer programs, a general-purpose processor such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, the processing circuit 802 may include multiple central processing units (CPUs).

[0142] In the above example, the input / output interface 806 may be configured to provide input devices, output devices, or one or more interfaces to one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, emitters, smart cards, other output devices, or any combination thereof. Input devices may allow a user to capture information to the UE800. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, webcams, etc.), microphones, sensors, mice, trackballs, directional pads, trackpads, scroll wheels, and smart cards. Presence-sensitive displays may include capacitive or resistive touch sensors for sensing user input. Sensors may include, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetic sensors, optical sensors, proximity sensors, biosensors, or any combination thereof. Output devices may use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port may be used to provide input and output devices.

[0143] In some embodiments, the power supply 808 is structured as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., an electrical outlet), a solar power device, or a battery. The power supply 808 may further include power circuits for transmitting power from the power supply 808 itself and / or an external power source to various parts of the UE800 via interfaces such as input circuits or power cables. Power transmission may be, for example, for charging the power supply 808. The power circuits may perform some shaping, conversion, or other modification on the power from the power supply 808 to suit the power of each component of the UE800 to which it is being powered.

[0144] Memory 810 may be, or may be configured to include, random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, and flash drives. In one example, memory 810 includes one or more application programs 814, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and corresponding data 816. Memory 810 may store any of a wide variety of operating systems or combinations of multiple operating systems for use by UE800.

[0145] Memory 810 may be configured to include multiple physical drive units such as RAID (Redundant Array of Independent Disks), flash memory, USB flash drives, external hard disk drives, thumb drives, pen drives, key drives, HD-DVD (High-Density Digital Versatile Disc), optical disc drives, internal hard disk drives, Blu-ray optical disc drives, HDDS (Holographic Digital Data Storage) optical disc drives, external miniDIMM (Dual In-Line Memory Module), SDRAM (Synchronous Dynamic Random Access Memory), external microDIMM SDRAM, tamper-resistant modules in the form of UICC (universal integrated circuit card) including one or more SIMs (subscriber Identity Modules) such as USIM and / or ISIM, other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a “SIM card”. The memory 810 may enable the UE800 to access instruction sets and application programs stored in temporary or non-temporary storage media to offload or upload data. Product items, such as those utilizing communication systems, may be tangibly embodied as a device-readable storage medium or containing one, or within the memory 810.

[0146] The processing circuit 802 may be configured to communicate with an access network or other network using a communication interface 812. The communication interface 812 may include one or more communication subsystems, and may include or be communicatively connected to an antenna 822. The communication interface 812 may include one or more transceivers used to communicate, for example, by communicating with one or more remote transceivers of other wirelessly communicable devices (e.g., other UEs or network nodes in the access network). Each transceiver may include a transmitter 818 and / or receiver 820 appropriate for providing network communication (e.g., optical, electrical, frequency-allocated, etc.). Furthermore, the transmitter 818 and receiver 820 may be connected to one or more antennas (e.g., antenna 822), and they may share circuit components, software, or firmware, or alternatively, be implemented separately.

[0147] In the illustrated embodiment, the communication functions of the communication interface 812 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, near-field communication such as Bluetooth, location-based communication such as the use of GPS (Global Positioning System) for location determination, other similar communication functions, or any combination thereof. The communication may be implemented in accordance with one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMAX, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, and Hypertext Transfer Protocol (HTTP).

[0148] Regardless of the sensor type, the UE may provide an output of data captured by its sensor to a network node via a wireless connection through its communication interface 812. The data captured by the UE's sensor may be communicated to a network node via another UE via a wireless connection. The output may be periodic (e.g., once every 15 minutes if reporting sensed temperature), random (e.g., to equalize the load from notifications from multiple sensors), in response to a triggering event (e.g., moisture is detected and an alert is sent), in response to a request (e.g., a user-initiated request), or as a continuous stream (e.g., a live video feed of a patient).

[0149] Other examples include actuators, motors, or switches associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch may change in response to the received wireless input. For example, the UE may include a motor that adjusts the control surface or rotor of a drone in flight according to the received input, or a robotic arm that performs a medical procedure according to the received input.

[0150] If a UE is in the form of an IoT (Internet of Things) device, it may be a device for use in one or more application domains, which include, but are not limited to, wearable technology in urban environments, augmented industrial applications, and healthcare. Non-exclusive examples of such IoT devices include, or are incorporated into, devices such as, connected refrigerators or freezers, TVs, connected lighting fixtures, electric meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, moisture detectors (flood / moisture sensors), electric door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearables for haptic enhancement or sensory enhancement, water sprinklers, animal or object tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any type of medical device such as heart rate monitors or remotely controlled surgical robots. The UE in the form of an IoT device comprises, in addition to circuitry and / or software that depends on the intended application of the IoT device, other components such as those described in relation to the UE800 shown in Figure 8.

[0151] In another specific example, in an IoT scenario, the UE may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to other UEs and / or network nodes. In this case, the UE may be an M2M device and may be referred to as an MTC device in the context of 3GPP. In one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, the UE may represent a vehicle such as a passenger car, bus, truck, ship or aircraft, or other equipment capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0152] In practice, any number of UEs may be used together for a single use case. For example, the first UE may be a drone or integrated into a drone and provide speed information of the drone (obtained through a speed sensor) to a second UE, which is a remote controller operating the drone. When the user makes a change from the remote controller, the first UE may adjust the drone's throttle (for example, by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE may include more than one of the functionalities described above. For example, the UE may include sensors and actuators and handle data communication for both the speed sensor and the actuator.

[0153] Figure 9 shows network nodes 900 according to several embodiments. As used herein, a network node is a device that is capable of communicating directly or indirectly with the UE and / or other network nodes or devices in the telecommunications network, and is configured, positioned, and / or operational in such a manner. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, node Bs, evolved node Bs (eNBs), and NR node Bs (gNBs)), O-RAN nodes, and components of O-RAN nodes (e.g., O-RUs, O-DUs, O-CUs).

[0154] Base stations may be categorized based on the amount of coverage they provide (or, in other words, their transmit power level), and therefore may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations, depending on the amount of coverage they provide. A base station may also be a relay node or a relay donor node controlling a relay device. Network nodes may also include one or all of the parts of a distributed radio base station, such as a centralized digital unit, a distributed unit (e.g., in an O-RAN access node), and / or a remote radio unit (RRU) sometimes called a remote radio head (RRH). Such remote radio units may or may not be integrated with an antenna, such as an antenna-integrated radio. Some parts of a distributed radio base station may also be referred to as nodes within a distributed antenna system (DAS).

[0155] Other examples of network nodes include multi-transmitting point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BS, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base station transceivers (BTSs), transmit points, transmit nodes, multi-cell / multicast cooperative entities (MCEs), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, and positioning nodes (including, for example, evolved serving mobile location centers (E-SMLCs) and / or drive test minimization (MDTs)).

[0156] The network node 900 includes a processing circuit 902, memory 904, a communication interface 906, and a power supply 908. The network node 900 may consist of multiple physically separate components (e.g., a node B component and an RNC component, or a BTS component and a BSC component), each of which may have its own respective components. In a scenario in which the network node 900 has multiple separate components (e.g., BTS and BSC components), one or more of these separate components may be shared among several network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, each unique pair of node Bs and RNCs may, in some examples, be considered a single separate network node. In some embodiments, the network node 900 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be redundant (e.g., separate memory 904 for different RATs), and some components may be reused (e.g., the same antenna 910 may be shared by multiple different RATs). Furthermore, the network node 900 may include multiple sets of diverse exemplary components for various wireless technologies to be integrated into the network node 900, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, RFID (Radio Frequency Identification), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or sets of chips and other components within the network node 900.

[0157] The processing circuit 902 may include one or more combinations of microprocessors, controllers, microcontrollers, central processing units, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, or other suitable computing devices, resources, or hardware, software, and / or coding logic, which can operate alone or in conjunction with other network node 900 components such as memory 904 to provide the functionality of the network node 900.

[0158] In some embodiments, the processing circuit 902 includes a system-on-a-chip (SOC). In some embodiments, the processing circuit 902 includes one or more of the radio frequency (RF) transceiver circuit 912 and the baseband processing circuit 914. In some embodiments, the RF transceiver circuit 912 and the baseband processing circuit 914 may be on separate chips (or sets of chips), substrates, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit 912 and the baseband processing circuit 914 may be on the same chip or set of chips, substrate, or unit.

[0159] Memory 904 may include, but is not limited to, any form of volatile or non-volatile computer-readable memory, including persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random-access memory (RAM), read-only memory (ROM), large storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile non-temporary device-readable and / or computer-executable memory device, for storing information, data and / or instructions that can be used by the processing circuit 902. Memory 904 may store any suitable instructions, data or information, including applications, and / or other instructions, which are executable by the processing circuit 902 and available to the network node 900, including one or more computer programs, software, logic, rules, code, and tables. Memory 904 may also be used to store any calculation results produced by the processing circuit 902 and / or any data received via the communication interface 906. In some embodiments, the processing circuit 902 and the memory 904 are integrated.

[0160] The communication interface 906 is used in wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As illustrated, the communication interface 906 includes, for example, a port / terminal 916 for sending and receiving data to and from the network over a wired connection. The communication interface 906 also includes a wireless front-end circuit 918, which is connected to or, in some embodiments, part of the antenna 910. The wireless front-end circuit 918 includes a filter 920 and an amplifier 922. The wireless front-end circuit 918 may be connected to the antenna 910 and a processing circuit 902. The wireless front-end circuit may be configured to adjust signals communicated between the antenna 910 and the processing circuit 902. The wireless front-end circuit 918 can receive digital data to be sent to other network nodes or UEs via a wireless connection. The wireless front-end circuit 918 can convert its digital data into a wireless signal with appropriate channel and bandwidth parameters using a combination of the filter 920 and / or the amplifier 922. The radio signal can then be transmitted via the antenna 910. Similarly, when data is received, the antenna 910 collects the radio signal, which can then be converted into digital data by the radio front-end circuit 918. The digital data can then be passed to the processing circuit 902. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0161] In one alternative embodiment, the network node 900 does not include a separate radio front-end circuit 918; rather, the processing circuit 902 includes the radio front-end circuit and is connected to the antenna 910. Similarly, in some embodiments, all or some of the RF transceiver circuits 912 are part of the communication interface 906. In yet another embodiment, the communication interface 906, as part of a radio unit (not shown), includes one or more ports or terminals 916, a radio front-end circuit 918, and an RF transceiver circuit 912, and the communication interface 906 communicates with a baseband processing circuit 914, which is part of a digital unit (not shown).

[0162] Antenna 910 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 910 may be connected to a wireless front-end circuit 918 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In one embodiment, antenna 910 is separate from the network node 900 and can be connected to the network node 900 through an interface or port.

[0163] The antenna 910, communication interface 906, and / or processing circuit 902 may be configured to perform any receiving operations and / or acquisition operations described herein as being performed by a network node. Any information, data, and / or signals may be received from the UE, other network nodes, and / or any other network equipment. Similarly, the antenna 910, communication interface 906, and / or processing circuit 902 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to the UE, other network nodes, and / or any other network equipment.

[0164] Power supply 908 provides power to the various components of network node 900 in a format suitable for each component (for example, at the voltage and current levels required for each component). Power supply 908 may further include, or be connected to, a power management circuit for supplying power to the components of network node 900 to perform the functions described herein. For example, network node 900 may be connectable to an external power source (e.g., a power grid, an electrical outlet) via an input circuit or interface such as an electrical cable, thereby allowing the external power source to supply power to the power circuit of power supply 908. As a further example, power supply 908 may include a power source in the form of a battery or battery pack connected to or integrated into the power circuit. The battery may provide backup power in case of failure of the external power source.

[0165] Embodiments of network node 900 may include additional components other than those shown in Figure 9 to provide a functional view of the network node, including any functionality necessary to support any of the functionalities described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 900 may include user interface equipment that enables input of information to and output of information from network node 900. This may enable users to perform diagnostic, maintenance, repair, and other management functions on network node 900.

[0166] Figure 10 is a block diagram of a possible embodiment of host 1000 of host 716 in Figure 7, relating to the various aspects described herein. Where used herein, host 1000 may be, or include, a variety of hardware and / or software, including standalone servers, blade servers, cloud-implemented servers, distributed servers, virtual machines, containers, or processing resources within a server farm. Host 1000 may provide one or more services to one or more UEs.

[0167] The host 1000 includes an input / output interface 1006, a network interface 1008, a power supply 1010, and a processing circuit 1002 operably connected via a bus 1004 to a memory 1012. In other embodiments, other components may be included. The functions of these components may be substantially the same as those described for the devices in previous drawings such as Figures 8 and 9, and thus those descriptions are generally applicable to the corresponding components of the host 1000.

[0168] Memory 1012 may include one or more computer programs, including one or more host application programs 1014, and data 1016, which may include user data, such as data generated by the UE for the host 1000 or data generated by the host 1000 for the UE. Embodiments of the host 1000 may utilize only a subset or all of the illustrated components. The host application program 1014 may be implemented in a container-based architecture and may provide support for video codecs (e.g., VVC (Versatile Video Coding), HEVC (High Efficiency Video Coding), AVC (Advanced Video Coding), MPEG, VP9) and audio codecs (e.g., FLAC, AAC (Advanced Audio Coding), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, head-up display systems). Furthermore, the host application program 1014 may provide user authentication and license checks, and may periodically report health, route, and content availability to central nodes such as devices within or at the edge of the core network. Thus, host 1000 may select and / or point to different hosts for over-the-top services for the UE. The host application program 1014 may support a variety of protocols, such as HLS (HTTP Live Streaming), RTMP (Real-Time Messaging Protocol), RTSP (Real-Time Streaming Protocol), and MPEG-DASH (Dynamic Adaptive Streaming over HTTP).

[0169] Figure 11 is a block diagram showing a virtualization environment 1100 in which functions implemented by several embodiments can be virtualized. In this context, virtualization means for generating virtual versions of devices or equipment may include a virtualization hardware platform, storage devices, and networking resources. As used herein, virtualization can be applied to any of the devices or components thereof described herein and relates to implementation examples in which at least some of its functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented within one or more virtualization environments 1100 hosted by one or more hardware nodes, such as network nodes, UEs, core network nodes, or hardware computing devices acting as hosts. Furthermore, in embodiments in which the virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes as a whole may be virtualized. In some embodiments, the virtualization environment 1100 includes a set of components defined by the O-RAN Alliance, such as an O-Cloud environment organized by a service management and orchestration framework via an O-2 interface.

[0170] Application 1102 (which may alternatively be called a software instance, virtual appliance, network function, virtual node, virtual network function, etc.) runs in a virtualized environment Q400 to implement some of the features, functions and / or benefits of some of the embodiments disclosed herein.

[0171] Hardware 1104 includes a processing circuit, memory for storing software and / or instruction sets executable by the hardware processing circuit, and / or hardware devices as described herein, such as network interfaces and input / output interfaces. The software is executed by the processing circuit to instantiate one or more virtualization layers 1106 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide VM1108a and VM1108b (one or more of which may generally be referred to as VM1108), and / or perform any of the functions, features and / or benefits described herein in relation to some of the embodiments described herein. The virtualization layer 1106 may present a virtual operating platform that appears to the VM1108 as networking hardware.

[0172] VM1108 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be executed by the corresponding virtualization layer 1106. Various embodiments of instances of the virtual appliance 1102 may be implemented in one or more of VM1108, and such implementation may be carried out in various ways. Hardware virtualization is referred to as network function virtualization (NFV) in several contexts. NFV can be used to consolidate many types of network equipment into industry-standard, high-capacity server hardware, physical switches, and physical storage that can reside in data centers and customer premises equipment.

[0173] In the context of NFV, VM1108 may be a software implementation of a physical machine that runs a program as if it were running on a physical, non-virtualized machine. Each VM1108, and the portion of hardware 1104 on which the VM runs, whether dedicated hardware for that VM or hardware shared by that VM with other VMs, forms a separate virtual network element. Also in the context of NFV, the virtual network function is responsible for handling the specific network functions running in one or more VM1108 at the top level of hardware 1104 and corresponds to application 1102.

[0174] Hardware 1104 may be implemented in a standalone network node with general-purpose or specific components. Hardware 1104 may implement some functions through virtualization. Alternatively, hardware 1104 may be part of a larger hardware cluster (e.g., one in a data center or CPE) in which multiple hardware nodes cooperate and are managed via management and orchestration 1110, which oversees, among other things, the lifecycle management of application 1102. In some embodiments, hardware 1104 is connected to one or more radio units, each including one or more transmitters and one or more receivers, which can be connected to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more suitable network interfaces, or they may be used in combination with virtual components to provide radio capabilities to virtual nodes, such as radio access nodes or base stations. In some embodiments, some signaling can be provided in conjunction with the use of a control system 1112, which may alternatively be used for communication between hardware nodes and radio units.

[0175] Figure 12 shows a communication diagram of host 1202 communicating with UE 1206 via network node 1204 over a partial wireless connection, according to one of several embodiments. Exemplary implementations of various embodiments of the UE (UE712a in Figure 7 and / or UE800 in Figure 8), network node (network node 710a in Figure 7 and / or network node 900 in Figure 9), and host (host 716 in Figure 7 and / or host 1000 in Figure 10), discussed in the preceding paragraphs, will now be described with reference to Figure 12.

[0176] Similar to host 1000, embodiments of host 1202 include hardware such as a communication interface, processing circuitry, and memory. Host 1202 also includes software stored within or accessible by host 1202, which is executable by the processing circuitry. This software may include a host application that can operate to provide services to remote users, such as UE 1206 connected via an over-the-top (OTT) connection 1250 extending between UE 1206 and host computer 1202. While providing services to remote users, the host application may provide user data transmitted using the OTT connection 1250.

[0177] Network node 1204 includes hardware that enables communication with host 1202 and UE 1206. Connection 1260 is direct or can pass through a core network (such as core network 706 in Figure 7) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, the intermediate network may be a backbone network or the internet.

[0178] UE1206 includes software stored within or accessible by UE1206, which is executable by the UE's processing circuitry. This software includes a client application, such as a web browser or a service provider-specific “app,” which may operate to provide services to human or non-human users via UE1206, with the support of host 1202. On host 1202, the host application to be executed may communicate with the client application to be executed via an OTT connection 1250 terminating at UE1206 and host 1202. While providing services to a user, the UE's client application may receive request data from the host's host application and provide user data in response to that request data. The OTT connection 1250 may transport both the request data and the user data. The UE's client application may interact with the user to generate user data that it provides to the host application via the OTT connection 1250.

[0179] The OTT connection 1250 extends via connection 1260 between host 1202 and network node 1204, and via wireless connection 1270 between network node 1204 and UE 1206, and may provide connectivity between host 1202 and UE 1206. To illustrate the communication between host 1202 and UE 1206 via network node 1204, without any explicit reference to any intermediate devices or the precise routing of messages through those devices, the connections 1260 and wireless connection 1270, which may be provided by the OTT connection 1250, are depicted abstractly.

[0180] As an example of transmitting data via the OTT connection 1250, in step 1208, host 1202 provides user data, which may be done by running a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 1206. In other embodiments, the user data is associated with UE 1206 sharing data with host 1202 without explicit human interaction. In step 1210, host 1202 initiates a transmission to UE 1206 carrying the user data. Host 1202 may initiate such a transmission in response to a request transmitted by UE 1206. Such a request may be triggered by human interaction with UE 1206 or by the operation of a client application running on UE 1206. Such a transmission may pass through network node 1204 in accordance with the teachings of the embodiments described through this disclosure. Accordingly, in step 1212, the network node 1204 transmits the user data carried in the transmission initiated by host 1202 to UE 1206, in accordance with the teachings of the embodiments described through this disclosure. In step 1214, UE 1206 receives the user data carried in the transmission, which may be done by a client application running on UE 1206 associated with a host application running on host 1202.

[0181] In some examples, UE1206 runs a client application, thereby providing user data destined for host 1202. User data may be provided in reaction to or in response to receiving data from host 1202. Accordingly, in step 1216, UE1206 may provide user data, which may be done by running a client application. While providing user data, the client application may further consider user input received from the user via the input / output interface of UE1206. Regardless of the specific way in which the user data is provided, in step 1218, UE1206 initiates transmission of the user data to host 1202 via network node 1204. In step 1220, in accordance with the teachings of the embodiments described through this disclosure, network node 1204 receives user data from UE1206 and initiates transmission of the received user data to host 1202. In step 1222, host 1202 receives the user data carried in the transmission initiated by UE1206.

[0182] One or more of the various embodiments improve the performance of the OTT service provided to the UE 1206 using the OTT connection 1250, with the wireless connection 1270 forming the final segment. For example, the signaling between the UE and network nodes as taught in these embodiments may improve, for example, data rate, latency, and power consumption, thereby providing benefits such as reduced user latency, relaxed constraints on file size, improved content resolution, better responsiveness, and longer battery life.

[0183] In an exemplary scenario, Host 1202 may collect and analyze factory status information. In another example, Host 1202 may process audio and video data, which may be acquired from the UE, for use in generating maps. In yet another example, Host 1202 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., traffic light control). In yet another example, Host 1202 may store surveillance video uploaded by the UE. In yet another example, Host 1202 may store or control access to media content such as video, audio, VR, or AR that can be broadcast, multicast, or unicast to the UE. In yet another example, Host 1202 may be used for energy pricing, remote control of non-time-critical power loads for balancing power generation needs, location services, presentation services (such as editing diagrams from data collected from remote devices), or any other function of collecting, acquiring, storing, analyzing, and / or transmitting data.

[0184] In some examples, measurement procedures may be provided for the purpose of monitoring data rate, latency, and other factors that may be improved by one or more embodiments. Further network functionality may exist as an option for reconfiguring the OTT connection 1250 between host 1202 and UE 1206 in response to variations in the measurement results. The above measurement procedures and / or network functionality for reconfiguring the OTT connection may be implemented in the software and hardware of host 1202 and / or UE 1206. In some embodiments, sensors (not shown) through which the OTT connection 1250 passes may be deployed in or associated with other devices, and these sensors may participate in the measurement procedures by supplying values ​​of the monitored quantities exemplified above or values ​​of other physical quantities, from which the monitored quantities may be calculated or estimated by software. Reconfiguration of the OTT connection 1250 may include message formatting, retransmission settings, preferred routing, etc., and such reconfiguration does not need to directly change the operation of network node 1204. Such procedures and functionality may be known or in practice in the art. In one embodiment, the measurement may include proprietary UE signaling that facilitates the measurement of throughput, propagation time, and latency by the host 1202. The measurement may be implemented by the software monitoring propagation time, errors, etc., while sending messages that are specifically empty or "dummy" messages using the OTT connection 1250.

[0185] While the computing devices described herein (e.g., UEs, network nodes, hosts) may include combinations of illustrated hardware components, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The decisions, calculations, acquisitions, or similar operations described herein may be performed by processing circuits, which may process information by, for example, converting acquired information to other information, comparing acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information, and making decisions as a result of the processing. Furthermore, while components are depicted as single boxes located within larger boxes or nested within multiple boxes, in practice, computing devices may include multiple different physical components that make up the illustrated single component, and functionality may be separated between distinct components. For example, a communication interface may be configured to include any of the components described herein, and the functionality of those components may be separated between the processing circuit and the communication interface. In other examples, computationally intensive functions of any of these components may be implemented in software or firmware, while computationally intensive functions may be implemented in hardware.

[0186] In some embodiments, some or all of the functionalities described herein may be provided by a processing circuit executing a set of instructions stored in memory, which may be a computer program product in the form of a non-temporary computer-readable storage medium. In alternative embodiments, some or all of the functionalities may be provided by the processing circuit, such as in a hardwired manner, without executing instructions stored in separate or discrete device-readable storage mediums. In any of these specific embodiments, the processing circuit can be configured to perform the functionalities described, whether or not it executes instructions stored in a non-temporary computer-readable storage medium. The benefits provided by such functionalities are not limited to the processing circuit alone or other components of the computing device, but are enjoyed by the computing device as a whole, and / or by the end user and the wireless network in general.

[0187] A list of exemplary embodiments of several other embodiments of this disclosure is provided below.

[0188] Group A Implementation

[0189] 1. A method performed by a user device (UE) for an L1 / L2 triggered mobility (LTM) cell switch procedure, the method being: The LTM reference configuration and LTM candidate cell configuration are received (200), To obtain the complete LTM candidate cell configuration of an LTM candidate cell, combine the LTM reference configuration and the LTM candidate cell configuration (202), Receiving an LTM cell switch command from a source network node (204), wherein the LTM cell switch command includes at least instructions for the LTM candidate cell configuration. Apply the complete LTM candidate cell configuration of the instructed LTM candidate cell configuration (206), This includes sending an uplink signaling (208) to confirm the completion of the LTM cell switch procedure.

[0190] 2. The method according to Embodiment 1, wherein combining the LTM reference configuration and the LTM candidate cell configuration to obtain the complete LTM candidate cell configuration of the LTM candidate cell (202) Receiving one of the LTM reference configuration and at least one LTM candidate cell configuration from a source network node, and generating a complete LTM candidate cell configuration in response to the said reception following a previous reception of the other of the LTM reference configuration and at least one LTM candidate cell configuration from the source network node.

[0191] 3. A method according to Embodiment 1 or 2, wherein combining an LTM reference configuration and an LTM candidate cell configuration to obtain a complete LTM candidate cell configuration (202) is, This includes generating a complete LTM candidate cell configuration in response to receiving an LTM cell switch command from a source network node.

[0192] 4. A method according to any one of Embodiments 1 to 3, wherein combining an LTM reference configuration and an LTM candidate cell configuration to obtain a complete LTM candidate cell configuration (202) This includes applying an LTM candidate cell configuration on top of an LTM reference configuration, in accordance with one or more of the following: Perform a set of actions common to both the LTM reference configuration and the LTM candidate cell configuration; Performing separate sets of actions in the LTM reference configuration and the LTM candidate cell configuration; Perform a set of actions on the LTM reference configuration and / or LTM candidate cell configuration in accordance with rules or guidelines that define the processing of ASN.1 structures, fields, or information elements of the LTM reference configuration and LTM candidate cell configuration.

[0193] 5. A method according to Embodiment 4, in which a set of actions on an LTM reference configuration and / or LTM candidate cell configuration is performed in accordance with rules or guidelines that define the processing of ASN.1 structures, fields, or information elements of the LTM reference configuration and the LTM candidate cell configuration, includes determining from the rules or guidelines at least one of the following: Operations used on the values ​​of ASN.1 structures, fields, or information elements in LTM reference configurations and / or LTM candidate cell configurations; Operations used based on the type of ASN.1 structure, field, or information element in the LTM reference configuration and / or LTM candidate cell configuration; The sequence of operations performed on the values ​​of ASN.1 structures, fields, or information elements in the LTM reference configuration and / or LTM candidate cell configuration; Operations used based on the values ​​of ASN.1 structures, fields, or information elements in the LTM reference configuration and / or LTM candidate cell configuration; Operations used based on the presence of ASN.1 structures, fields, or information elements in the LTM reference configuration and / or LTM candidate cell configuration; and Operations used based on the requirement codes of ASN.1 structures, fields, or information elements in LTM reference configurations and / or LTM candidate cell configurations.

[0194] 6. A method according to any one of Embodiments 1 to 3, further, Based on the receipt of the LTM reference configuration and the LTM candidate cell configuration, prepare a complete portion of the LTM candidate cell configuration, This includes preparing a complete LTM candidate cell configuration based on a portion in response to the receipt of an LTM cell switch command.

[0195] 7. A method according to any one of Embodiments 1 to 6, wherein combining an LTM reference configuration and an LTM candidate cell configuration to obtain a complete LTM candidate cell configuration of an LTM candidate cell (202) This includes defining the LTM candidate cell configuration as the complete LTM candidate cell configuration.

[0196] 8. A method according to any one of Embodiments 1 to 7, further comprising, after receiving an LTM cell switch command (204) and before applying a complete LTM candidate cell configuration (206), at least one of the following: Copy timers, counters, and / or configurations from the current UE configuration to the complete LTM candidate cell configuration; In the current UE configuration, clear the dedicated configuration previously received from the source network node via dedicated signaling; In the current UE configuration, clear the common configuration previously received from the source network node via system information; and Perform an L2 reset.

[0197] 9. A method according to any one of embodiments 1 to 8, further comprising, after receiving an LTM cell switch command (204) and before applying a complete LTM candidate cell configuration (206), at least one of the following: If a dedicated configuration does not exist within the complete LTM candidate cell configuration, apply the default configuration; Applying the complete LTM candidate cell configuration to the target cell; and To confirm the completion of the LTM cell switch procedure, send uplink signaling to the target network node.

[0198] Group B Implementation

[0199] 10. A method performed by a source network node to initiate an L1 / L2 triggered mobility (LTM) cell switch procedure in a user equipment (UE), the method being: Send the LTM reference configuration and LTM candidate cell configuration to the UE (300), Sending an LTM cell switch command to the UE to initiate an LTM cell switch procedure (302), wherein the LTM cell switch command includes instructions for an LTM candidate cell configuration.

[0200] 11. The method according to Embodiment 10, wherein the LTM candidate cell configuration transmitted to the UE includes an indication that the LTM candidate cell configuration is a complete LTM candidate cell configuration.

[0201] 12. The method according to Embodiment 11, wherein an indication that the LTM candidate cell configuration is a complete LTM candidate cell configuration is sent to the UE in a message that is not the same as the message to which the LTM candidate cell configuration is sent.

[0202] 13. A method performed by a target network node for an L1 / L2 triggered mobility (LTM) cell switch procedure, the method being: Initiate configuration of LTM candidate cell configuration at user equipment (UE) via another network node (400), This includes receiving a signal from the UE (402) indicating that the LTM cell switching procedure has completed successfully and the UE has started working with the target network node according to the LTM candidate cell configuration.

[0203] 14. The method according to Embodiment 13, wherein the LTM candidate cell configuration includes an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.

[0204] Group C Embodiment

[0205] 15. User equipment for L1 / L2 trigger mobility (LTM) cell switch procedures, A processing circuit configured to perform any of the steps of the Group A embodiment, It includes a power supply circuit configured to supply power to a processing circuit.

[0206] 16. Source network node for L1 / L2 triggered mobility (LTM) cell switch procedure, A processing circuit configured to perform any of the steps of the Group B embodiment, It includes a power supply circuit configured to supply power to a processing circuit.

[0207] 17. Target network node for L1 / L2 triggered mobility (LTM) cell switch procedure, A processing circuit configured to perform any of the steps of the Group B embodiment, It includes a power supply circuit configured to supply power to a processing circuit.

[0208] 18. User equipment (UE) for L1 / L2 trigger mobility (LTM) cell switch procedure, wherein the UE is: An antenna configured to transmit and receive wireless signals, A wireless front-end circuit connected to an antenna and a processing circuit, configured to adjust the signals communicated between the antenna and the processing circuit, A processing circuit configured to perform any of the steps of the Group A embodiment, An input interface connected to a processing circuit and configured to allow input of information processed by the processing circuit to the UE, An output interface connected to a processing circuit and configured to output information processed by the processing circuit from the UE, It includes a battery connected to the processing circuit and configured to supply power to the UE.

[0209] 19. A host that operates in a communication system and is configured to provide an over-the-top (OTT) service, wherein the host is A processing circuit configured to provide user data, The system includes a network interface configured to initiate the transmission of user data to a source network node in a cellular network for transmission to a user equipment (UE), wherein the source network node has a communication interface and processing circuitry, and the processing circuitry of the source network node is configured to perform any of the operations of the Group B embodiment for transmitting user data from the host to the UE.

[0210] 20. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host is A processing circuit configured to provide user data, The system includes a network interface configured to initiate the transmission of user data to a target network node in a cellular network for transmission to a user equipment (UE), wherein the target network node has a communication interface and processing circuitry, and the processing circuitry of the target network node is configured to perform any of the operations of the Group B embodiment for transmitting user data from the host to the UE.

[0211] 21. The host of the above-described embodiment, The host processing circuit is configured to run a host application that provides user data. The UE includes processing circuitry configured to run a client application associated with the host application in order to receive user data transmitted from the host.

[0212] 22. A method performed on a host configured to operate in a communication system further including a source network node and user equipment (UE), the method being: Providing user data to the UE, The process includes initiating a transmission that carries user data to the UE via a cellular network including a source network node, the source network node performing any of the actions of the Group B embodiment to transmit user data from the host to the UE.

[0213] 23. A method of the embodiment described above, further comprising transmitting user data provided to the UE by the host at the source network node.

[0214] 24. A method performed on a host configured to operate in a communication system further including a target network node and user equipment (UE), the method being: Providing user data to the UE, The process includes initiating a transmission that carries user data to the UE via a cellular network including a target network node, the target network node performing any of the actions of the Group B embodiment to transmit user data from the host to the UE.

[0215] 25. A method of the embodiment described above, further comprising, at the target network node, transmitting user data provided to the UE by the host.

[0216] 26. A method according to either of the two embodiments described above, wherein user data is provided on the host by running a host application that interacts with a client application running on the UE, and the client application is associated with the host application.

[0217] 27. A communication system configured to provide over-the-top (OTT) services, wherein the communication system is Including the host, the host is, A processing circuit configured to provide user data associated with over-the-top services to user equipment (UE), The system includes a network interface configured to initiate the transmission of user data to a cellular source network node for transmission to a UE, wherein the source network node has a communication interface and processing circuitry, and the processing circuitry of the source network node is configured to perform any of the operations of the Group B embodiment for transmitting user data from the host to the UE.

[0218] 28. A communication system of the above-described embodiment, further, Source network node and / or, It has UE (Unified Element).

[0219] 29. A communication system configured to provide over-the-top (OTT) services, wherein the communication system is Including the host, the host is, A processing circuit configured to provide user data associated with over-the-top services to user equipment (UE), The system includes a network interface configured to initiate the transmission of user data to a cellular target network node for transmission to a UE, the target network node having a communication interface and processing circuitry, the processing circuitry of the target network node being configured to perform any of the operations of the Group B embodiment for transmitting user data from the host to the UE.

[0220] 30. A communication system according to the above-described embodiment, further, Target network node and / or, It has UE (Unified Element).

[0221] 31. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host is A processing circuit configured to initiate the reception of user data, The system comprises a network interface configured to receive user data from a source network node in a cellular network, the source network node having a communication interface and processing circuitry, the processing circuitry of the source network node being configured to perform any of the operations of the Group B embodiment in order to receive user data from a user equipment (UE) to a host.

[0222] 32. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host is A processing circuit configured to initiate the reception of user data, The system comprises a network interface configured to receive user data from a target network node in a cellular network, the target network node having a communication interface and processing circuitry, the processing circuitry of the target network node being configured to perform any of the operations of the Group B embodiment in order to receive user data from a user equipment (UE) to a host.

[0223] 33. The host of the two embodiments described above, The host processing circuit is configured to run a host application that receives user data. The host application is configured to interact with client applications running on the UE, and the client applications are associated with the host application.

[0224] 34. In either of the two embodiments described above, initiating the reception of user data includes requesting user data.

[0225] 35. A method performed by a host configured to operate in a communication system further including a source network node and user equipment (UE), the method being: The host includes initiating the reception of user data from the UE, which originates from a transmission received by the source network node from the UE, and the source network node performs any of the steps of the Group B embodiment to receive user data from the UE for the host.

[0226] 36. A method of the embodiment described above, further comprising transmitting the received user data to a host at the source network node.

[0227] 37. A method performed by a host configured to operate in a communication system further including a target network node and user equipment (UE), the method being: The host includes initiating the reception of user data from the UE, which originates from a transmission received by the target network node from the UE, and the target network node performs any of the steps of the Group B embodiment to receive user data from the UE for the host.

[0228] 38. A method of the embodiment described above, further comprising transmitting the received user data to a host at the target network node.

[0229] 39. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host is A processing circuit configured to provide user data, The system includes a network interface configured to initiate the transmission of user data to a cellular network for transmission to a user device (UE), the UE having a communication interface and processing circuitry, the UE's communication interface and processing circuitry being configured to perform any of the operations of the Group A embodiments for receiving user data from a host.

[0230] 40. The host of the above-described embodiment, wherein the cellular network further includes source network nodes configured to communicate with the UE in order to transmit user data from the host to the UE.

[0231] 41. A host of the two embodiments described above, wherein the cellular network further includes target network nodes configured to communicate with the UE in order to transmit user data from the host to the UE.

[0232] 42. The host of the two embodiments described above, The host processing circuit is configured to run the host application, thereby providing user data. The host application is configured to interact with client applications running on the UE, and the client applications are associated with the host application.

[0233] 43. A method performed by a host operating in a communication system further including a source network node and user equipment (UE), the method being: Providing user data to the UE, The process includes initiating a transmission that carries user data to the UE via a cellular network including a source network node, and the UE performs any of the actions of the Group A embodiment to receive user data from the host.

[0234] 34. The method of the embodiment described above, further, This includes, on the host, running the host application associated with the client application running on the UE in order to receive user data from the host application.

[0235] 35. The method of the embodiment described above, further, This includes sending input data provided by running a host application on the host to a client application running on the UE, User data is provided by the client application in response to input data from the host application.

[0236] 36. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host is A processing circuit configured to provide user data, The system comprises a network interface configured to initiate the transmission of user data to a cellular network for transmission to a user device (UE), the UE having a communication interface and processing circuitry, the UE's communication interface and processing circuitry being configured to perform any of the operations of any of the Group A embodiments for transmitting user data to a host.

[0237] 37. The host of the above-described embodiment, wherein the cellular network further includes source network nodes configured to communicate with the UE to transmit user data from the UE to the host.

[0238] 38. The host of the two embodiments described above, The host processing circuit is configured to run the host application, thereby providing user data. The host application is configured to interact with client applications running on the UE, and the client applications are associated with the host application.

[0239] 39. A method performed by a host configured to operate in a communication system further including a source network node and user equipment (UE), the method being: The host includes receiving user data transmitted to the host by the UE via a source network node, and the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.

[0240] 40. The method of the embodiment described above, further, This includes, on the host, running a host application associated with a client application running on the UE in order to receive user data from the UE.

[0241] 41. The methods of the two embodiments described above, further, This includes sending input data provided by running a host application on the host to a client application running on the UE, User data is provided by the client application in response to input data from the host application.

[0242] reference [1] RP-223520, 3GPP Work Item Description: Further Extensions to NR Mobility, MediaTek Inc., Apple, 3GPP TSG RAN Meeting #98-e, Electronic Meeting, 12-16 December 2022. [2] 3GPP TS 38.331 V17.4.0 (2023-03)

[0243] appendix

[0244] [Table 12]

[0245] [Table 13]

[0246] Start of changes 5.3.5 RRC Reconfiguration 5.3.5.1 General

[0247] [Table 14]

[0248] The purpose of this procedure is to modify RRC connections, such as establishing / modifying / releasing RB / BH RLC channels / Uu relay RLC channels / PC5 relay RLC channels, performing reconfigurations with synchronization, setting / modifying / releasing measurements, adding / modifying / releasing SCells and cell groups, adding / modifying / releasing conditional handover configurations, adding / modifying / releasing conditional PSCell modification or conditional PSCell addition configurations, and adding / modifying LTM candidate cells. As part of the procedure, NAS-specific information may be transferred from the network to the UE. RRC reconfiguration for performing reconfiguration with synchronization includes, but is not limited to, the following cases: - Synchronized reconfiguration and security key refresh, including RA to Pcell / PSCell, MAC reset, security refresh, and re-establishment of RLC and PDCP triggered by explicit L2 indicators; - Reconfiguration with synchronization without security key refresh, including RA to Pcell / PSCell, MAC reset, RLC re-establishment, and PDCP data recovery (in the case of AM DRB or AM MRB) triggered by an explicit L2 indicator. - Reconfiguration and security key refresh with synchronization for DAPS, including RA to target Pcell and establishment of target MAC, and, - For non-DAPS bearers: Security refresh and re-establishment of RLC and PDCP triggered by an explicit L2 indicator; - For DAPS bearers: Establish RLC for the target Pcell, refresh security, and reconfigure PDCP to add encryption, integrity protection, and ROHC functions to the target Pcell; - For SRB: Refresh the security of the target Pcell and establish RLC and PDCP; - Reconfiguration with synchronization for DAPS without security key refresh, including RA to target Pcell and establishment of target MAC; and - For non-DAPS bearers: RLC re-establishment and PDCP data recovery triggered by an explicit L2 indicator (for AM DRB or AM MRB). - For DAPS bearers: Reconfiguration of PDCP to add RLC establishment for target Pcell, encryption function, integrity protection function, and ROHC function for target Pcell; - For SRB: Establish RLC and PDCP of the target Pcell. - Reconfiguration with synchronization for switching from direct to indirect paths, without involvement of the target side's RA and without PDCP re-establishment / PDCP data recovery (in the case of AM DRB) triggered by an explicit L2 indicator. In (NG)EN-DC and NR-DC, SRB3 can be used for measurement configuration and reporting, (re)configuration and reporting of UE assistance for power saving, (re)configuration and reporting of IAB node IP addresses, (re)configuration of MAC, RLC, BAP, physical layer, RLF timers and constants of SCG configuration, reconfiguration of PDCP of DRB associated with S-KgNB or SRB3, reconfiguration of SDAP of DRB associated with S-KgNB in ​​NGEN-DC and NR-DC, adding / modifying / releasing conditional PSCell change configurations when MN involvement is not required for (re)configuration, and sending RRC messages between MN and UE during fast MCG link recovery. In (NG)EN-DC and NR-DC, unless RRCReconfiguration is received within DLInformationTransferMRDC, RRCReconfiguration received via SRB3 includes only measConfig, radioBearerConfig, conditionalReconfiguration, bap-Config, iab-IP-AddressConfigurationList, otherConfig, and / or secondaryCellGroup. The network may initiate the RRC reconfiguration procedure for UEs with RRC_CONNECTED. The network applies the procedure as follows: - RB establishment (except SRB1 established during RRC connection establishment) is performed only if AS security is activated; - Establishing a BH RLC channel for IAB is only performed if AS security is activated; - The establishment of Uu relay RLC channels and PC5 relay RLC channels (other than SL-RLC0 and SL-RLC1) for L2 U2N relay UEs is performed only when AS security is activated, and the establishment of PC5 relay RLC channels (other than SL-RLC0 and SL-RLC1) for L2 U2N remote UEs is performed only when AS security is activated; - The addition of secondary cell groups and SCells is only performed when AS security is activated; -reconfigurationWithSync is included in secondaryCellGroup only if at least one RLC bearer or BH RLC channel is configured in the SCG; -reconfigurationWithSync is included in masterCellGroup only if AS security is activated and SRB2 has at least one DRB or multicast MRB, or in the case of IAB, SRB2 is configured and not suspended; - The conditionalReconfiguration of CPC is only included if at least one RLC bearer is configured in SCG; -The conditional reconfiguration of the CHO or CPA is only included if AS security is activated and SRB2 has at least one DRB or multicast MRB, or in the case of IAB, SRB2 is configured and not suspended. -LTM's ltm-CandidateConfig is only included if AS security is activated, SRB2 is configured with at least one DRB, and it is not suspended. Editor's note: Whether to apply ltm-CandidateConfig to MBS or IAB depends on FFS. When a UE receives an RRCReconfiguration or performs a conditional reconfiguration (CHO, CPA, or CPC), it must perform the following actions: 1>If RRCReconfiguration is applied due to a conditional reconfiguration being performed during cell selection while timer T311 was running, as defined in 5.3.7.3: 2> If present, delete all entries in MCG and SCG VarConditionalReconfig; 1>If RRCReconfiguration includes daps-SourceRelease: 2> Reset the source MAC and release the source MAC configuration; 2>Regarding each DAPS bearer: 3> Release the RLC entity and the associated logical channels of the source SpCell as specified in TS 38.322[4], section 5.1.3; 3> Reconfigure the PDCP entity to release the DAPS as specified in TS 38.323[5]; 2>Regarding each SRB: 3> Release the PDCP entity of the source SpCell; 3> Release the RLC entity and the associated logical channels of the source SpCell as specified in TS 38.322[4], section 5.1.3; 2> Release the physical channel configuration of the source SpCell; 2> Key used in source SpCell (K gNB key, K RRCenc key, K RRCint key, K Upint Key, and K Upenc Discard the key if one exists; 1>If RRCReconfiguration is received via another RAT (i.e., inter-RAT handover to NR): 2>When RRCReconfiguration does not include fullConfig and the UE is connected to 5GC (i.e., delta signaling during handover within 5GC): 3> Reuse the source RAT SDAP and PDCP configuration if available (i.e., the current SDAP / PDCP configuration of all RBs from the source E-UTRA RAT before receiving the inter-RAT HO RRCReconfiguration message); 1>Otherwise: 2>If RRCReconfiguration includes fullConfig: 3> Perform the full configuration procedure as specified in 5.3.5.11; 1>If RRCReconfiguration includes masterCellGroup: 2> Perform the cell group configuration of the received masterCellGroup according to 5.3.5.5; 1>If RRCReconfiguration includes masterKeyUpdate: Perform the AS security key update procedure as specified in 2>5.3.5.7; 1>If RRCReconfiguration includes sk-Counter: 2> Perform the security key update procedure as specified in 5.3.5.7; 1>If RRCReconfiguration includes secondaryCellGroup: 2> Perform the SCG cell group configuration according to 5.3.5.5; 1>If RRCReconfiguration includes mrdc-SecondaryCellGroupConfig: 2> If mrdc-SecondaryCellGroupConfig is set to setup: 3> If mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd: Perform MR-DC release as specified in section 4>5.3.5.10; 3>If the received mrdc-SecondaryCellGroup is set to nr-SCG: 4> For the RRCReconfiguration message included in nr-SCG, perform RRC reconfiguration according to section 5.3.5.3; 3>If the received mrdc-SecondaryCellGroup is set to eutra-SCG: 4>For the RRCConnectionReconfiguration message included in eutra-SCG, perform RRC connection reconfiguration as specified in TS 36.331

[10] , section 5.3.5.3; 2> Otherwise (mrdc-SecondaryCellGroupConfig is set to release) Perform MR-DC release as specified in Section 3>5.3.5.10; 1>If the RRCReconfiguration Message includes radioBearerConfig: 2> Perform the wireless bearer configuration according to 5.3.5.6; 1>If the RRCReconfiguration Message includes radioBearerConfig2: 2> Perform the wireless bearer configuration according to 5.3.5.6; 1>If the RRCReconfiguration message contains measConfig: Perform the measurement configuration procedure as specified in 2>5.5.2; 1>If the RRCReconfiguration message contains dedicatedNAS-MessageList: 2> Transfer each element of the dedicatedNAS-MessageList to the upper layer in the same order in which it is listed; 1>If the RRCReconfiguration Message includes dedicatedSIB1-Delivery: 2>Execute the action upon receiving SIB1 as specified in 5.2.2.4.2; Note 0: If this RRCReconfiguration is associated with an MCG and includes reconfigurationWithSync in spCellConfig and dedicatedSIB1-Delivery, the UE will initiate a request to obtain the required SIB (if necessary) in accordance with Section 5.2.2.3.5 only after the random access procedure to the target SpCell is complete. 1>If RRCReconfiguration MessagededicatedSystemInformationDelivery is included: 2>Execute the action upon receiving system information as specified in 5.2.2.4; 1>If the RRCReconfiguration message contains dedicatedPosSysInfoDelivery: 2> Perform the action upon receiving posSIB(s) as specified in Section 5.2.2.4.16; 1>If the RRCReconfiguration Message includes otherConfig: 2> Perform the other configuration steps as specified in 5.3.5.9; 1>If the RRCReconfiguration Message includes bap-Config: 2> Perform the BAP configuration procedure as specified in 5.3.5.12; 1>If the RRCReconfiguration Message includes iab-IP-AddressConfigurationList: 2>If iab-IP-AddressToReleaseList is included: Release the IP address as specified in 3>5.3.5.12a.1.1; 2>If iab-IP-AddressToAddModList is included: 3> Perform IAB IP address addition / update as specified in 5.3.5.12a.1.2; 1>If RRCReconfiguration MessageconditionalReconfiguration is included: 2> Perform a conditional reconfiguration as specified in 5.3.5.13; 1>If the RRCReconfiguration message contains needForGapsConfigNR: 2>If needForGapsConfigNR is set to setup: 3> It is assumed that it is configured to provide measurement gap requirement information for the NR target band; 2>Otherwise: 3> It is considered that the system is not configured to provide measurement gap requirement information for the NR target band; 1>If the RRCReconfiguration message contains needForGapNCSG-ConfigNR: 2>If needForGapNCSG-ConfigNR is set to setup: 3> It is assumed that it is configured to provide measurement gap and NCSG requirement information for the NR target band; 2>Otherwise: 3> It is considered not configured to provide measurement gap and NCSG requirement information for the NR target band; 1>If the RRCReconfiguration message contains needForGapNCSG-ConfigEUTRA: 2>If needForGapNCSG-ConfigEUTRA is set to setup: 3> It is assumed that the system is configured to provide measurement gap and NCSG requirement information for the E-UTRA target band; 2>Otherwise: 3> It is considered that the system is not configured to provide measurement gap and NCSG requirement information for the E-UTRA target band; 1>If the RRCReconfiguration Message contains sl-ConfigDedicatedNR: 2> Perform the side-link-specific configuration procedure as specified in 5.3.5.14; Note 0a: If sl-ConfigDedicatedNR is received embedded within an E-UTRA RRCConnectionReconfiguration message, the UE does not construct an NR RRCReconfigurationComplete message for the received sl-ConfigDedicatedNR. 1>If the RRCReconfiguration Message contains sl-L2RelayUE-Config: Perform the L2 U2N relay UE configuration procedure as specified in 2>5.3.5.15; 1>If the RRCReconfiguration message contains sl-L2RemoteUE-Config: 2> Perform the L2 U2N remote UE configuration procedure as specified in 5.3.5.16; 1>If the RRCReconfiguration Message includes dedicatedPagingDelivery: 2>Execute the Paging message reception procedure as specified in 5.3.2.3; 1>If the RRCReconfiguration Message includes sl-ConfigDedicatedEUTRA-Info: 2>Perform the relevant procedures for V2X sidelink communication in accordance with TS 36.331

[10] , sections 5.3.10 and 5.5.2; 1>If the RRCReconfiguration Message contains ul-GapFR2-Config: Perform the FR2 UL gap configuration procedure as specified in 2>5.3.5.13c; 1>If the RRCReconfiguration Message includes musim-GapConfig: Perform the MUSIM gap configuration procedure as specified in 2>5.3.5.9a; 1>If the RRCReconfiguration Message includes appLayerMeasConfig: Perform the application layer measurement configuration procedure as specified in 2>5.3.5.13d; 1>If the RRCReconfiguration message contains ue-TxTEG-RequestUL-TDOA-Config: 2>If ue-TxTEG-RequestUL-TDOA-Config is set to setup: 3>Execute the UE positioning assistance information procedure as specified in 5.7.14; 2>Otherwise: 3> Release the configuration of UE positioning assistance information; 1>If the RRCReconfiguration message contains ltm-CandidateConfig: Perform the LTM configuration procedure as specified in 2>5.3.5.x; 1>Set the contents of the RRCReconfigurationComplete message as follows: Note X: If this procedure is initiated by generating a complete LTM candidate cell configuration, the UE should generate only one RRCReconfigurationComplete message, even if it is processing the LTM reference configuration and the LTM candidate cell configuration. 2>If RRCReconfiguration includes a masterCellGroup that contains reportUplinkTxDirectCurrent: 3>Include an uplinkTxDirectCurrentList in each MCG serving cell that has UL; 3> If present, include the uplinkDirectCurrentBWP-SUL for each MCG serving cell in which a SUL carrier is configured in the uplinkTxDirectCurrentList; 2>If RRCReconfiguration includes a masterCellGroup containing reportUplinkTxDirectCurrentTwoCarrier: 3>Include a list of uplinkTxDC locations for the in-band uplink carrier aggregation configured within the MCG in uplinkTxDirectCurrentTwoCarrierList; 2>If RRCReconfiguration includes a masterCellGroup that contains reportUplinkTxDirectCurrentMoreCarrier: 3>Include a list of uplinkTxDC locations for the in-band uplink carrier aggregation configured within the MCG in uplinkTxDirectCurrentMoreCarrierList; 2>If RRCReconfiguration contains a secondaryCellGroup that includes reportUplinkTxDirectCurrent: 3>Include an uplinkTxDirectCurrentList in each SCG serving cell that has UL; 3> If present, include the uplinkDirectCurrentBWP-SUL for each SCG serving cell in which a SUL carrier is configured in the uplinkTxDirectCurrentList; 2>If RRCReconfiguration contains a secondaryCellGroup that includes reportUplinkTxDirectCurrentTwoCarrier: 3>Include a list of uplinkTxDC locations for in-band uplink carrier aggregations configured within the SCG in uplinkTxDirectCurrentTwoCarrierList; 2>If RRCReconfiguration contains a secondaryCellGroup that includes reportUplinkTxDirectCurrentMoreCarrier: 3>Include a list of uplinkTxDC locations for in-band uplink carrier aggregations configured within the SCG in uplinkTxDirectCurrentMoreCarrierList; Note 0b: The UE does not expect to receive reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier in both masterCellGroup and secondaryCellGroup. The network consists of at most one of reportUplinkTxDirectCurrent, reportUplinkTxDirectCurrentTwoCarrier, or reportUplinkTxDirectCurrentMoreCarrier in a single RRC message. 2>If the RRCReconfiguration message contains mrdc-SecondaryCellGroupConfig where mrdc-SecondaryCellGroup is set to eutra-SCG: 3>Include the E-UTRA RRCConnectionReconfigurationComplete message in eutra-SCG-Response in accordance with TS 36.331

[10] , section 5.3.5.3; 2>If the RRCReconfiguration message contains mrdc-SecondaryCellGroupConfig where mrdc-SecondaryCellGroup is set to nr-SCG: 3>Include the SCG RRCReconfigurationComplete message in nr-SCG-Response; 3> If a conditional reconfiguration is performed and the RRCReconfiguration message is applied, and the RRCReconfiguration message does not include reconfigurationWithSync in masterCellGroup: 4>Include the condReconfigId of the selected cell in selectedCondRRCReconfig for conditional reconfiguration execution; 2> If RRCReconfiguration includes reconfigurationWithSync in MCG's spCellConfig: 3>If the UE has log measurement data available for NR, and the RPLMN is included in the plmn-IdentityList stored in VarLogMeasReport: 4>Include logMeasAvailable in the RRCReconfigurationComplete message; 4>If the Bluetooth measurement results are included in the log measurement data available to the NR held by the UE: 5>Include logMeasAvailableBT in the RRCReconfigurationComplete message; 4>If the WLAN measurement results are included in the log measurement data available to NR that the UE has: 5>Include logMeasAvailableWLAN in the RRCReconfigurationComplete message; 3>If VarLogMeasReport contains sigLoggedMeasType: 4>When the T330 timer is running and the log measurement configuration is for NR: 5> Set sigLogMeasConfigAvailable to true in the RRCReconfigurationComplete message; 4>Otherwise: 5>If the UE has log measurement data available to NR: 6> Set sigLogMeasConfigAvailable to false in the RRCReconfigurationComplete message; 3>If the UE has connection establishment failure or connection reopening failure information available in VarConnEstFailReport or VarConnEstFailReportList, and the RPLMN is equal to the plmn-Identity stored in at least one entry in VarConnEstFailReport or VarConnEstFailReportList: 4>Include connEstFailInfoAvailable in the RRCReconfigurationComplete message; 3>If the UE has available radio link failure or handover failure information in the VarRLF-Report, and the RPLMN is included in the plmn-IdentityList stored in the VarRLF-Report; or 3>If the UE has radio link failure or handover failure information available in the VarRLF-Report of TS 36.331

[10] , and the UE is compatible with cross-RAT RLF reporting, and the RPLMN is included in the plmn-IdentityList stored in the VarRLF-Report of TS 36.331

[10] : 4>Include rlf-InfoAvailable in the RRCReconfigurationComplete message; 3>If successHO-Config was configured when the UE connected to the source Pcell; and, As defined in 3>5.3.7.3, if RRCReconfiguration is applied due to a conditional reconfiguration being performed during cell selection while timer T311 was running: 4>If the random access procedure triggered for reconfigurationWithSync of spCellConfig in MCG completes successfully, perform the action for determining the success of the handover, as specified in Section 5.7.10.6; 3>If the UE has available handover success information in the VarSuccessHO-Report, and the RPLMN is included in the plmn-IdentityList stored in the VarSuccessHO-Report: 4>Include successHO-InfoAvailable in the RRCReconfigurationComplete message; 2> If an RRCReconfiguration message is received via SRB1 but is not within mrdc-SecondaryCellGroup, E-UTRA RRCConnectionReconfiguration, or E-UTRA RRCConnectionResume: 3>If the UE is configured to provide measurement gap requirement information for the NR target band: 4>If the RRCReconfiguration message contains needForGapsConfigNR: or 4>If the NeedForGapsInfoNR information has changed compared to when UE last reported this information: 5>Include NeedForGapsInfoNR and configure its contents as follows: 6>Set the gap requirement information for in-frequency measurements for each NR serving cell, including intraFreq-needForGap; 6>If requestedTargetBandFilterNR is configured: 7> For each supported NR band included in requestedTargetBandFilterNR, include an entry in interFreq-needForGap and set the gap requirement information for that band; 6>Otherwise: 7>Include an entry in interFreq-needForGap and configure the gap requirement information corresponding to each supported NR band; 3>If the UE is configured to provide measurement gap and NCSG requirement information for the NR target band: 4> If the RRCReconfiguration message contains needForGapNCSG-ConfigNR; or 4>needForGapNCSG-InfoNR information has changed compared to when UE last reported this information: 5>Include needForGapNCSG-InfoNR and configure its contents as follows: 6> Set the in-frequency measurement gap and NCSG requirement information for each NR serving cell, including intraFreq-needForNCSG; 6>If requestedTargetBandFilterNCSG-NR is configured: 7>For each supported NR band included in requestedTargetBandFilterNCSG-NR, include an entry in interFreq-needForNCSG and set the NCSG requirement information for that band; 6>Otherwise: 7> For each supported NR band, include an entry in interFreq-needForNCSG and configure the corresponding NCSG requirement information; 3>If the UE is configured to provide measurement gap and NCSG requirement information for the E-UTRA target band: 4>If the RRCReconfiguration message contains needForGapNCSG-ConfigEUTRA: or 4>needForGapNCSG-InfoEUTRA information has changed compared to when UE last reported this information: 5>Include NeedForGapNCSG-InfoEUTRA and configure its contents as follows: 6>If requestedTargetBandFilterNCSG-EUTRA is configured, include an entry in needForNCSG-EUTRA for each supported E-UTRA band included in requestedTargetBandFilterNCSG-EUTRA and set the NCSG requirement information for that band; otherwise, include an entry in needForNCSG-EUTRA for each supported E-UTRA band and set the corresponding NCSG requirement information; 2> If this procedure is initiated by generating a complete LTM candidate cell configuration: 3>Finish the procedure. 1>If the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (the UE is in (NG)EN-DC): 2> If an RRCReconfiguration message is received via E-UTRA SRB1 as specified in TS 36.331

[10] ; or 2>If an RRCReconfiguration message is received via the E-UTRA RRC message RRCConnectionReconfiguration within MobilityFromNRCommand (Handover from NR Standalone to (NG)EN-DC); 3>When RRCReconfiguration is applied by a conditional reconfiguration execution of a CPC configured via conditionalReconfiguration included in nr-SecondaryCellGroupConfig as defined in TS 36.331

[10] : 4> Submit the RRCReconfigurationComplete message via E-UTRA MCG embedded in the E-UTRA RRC message ULInformationTransferMRDC, as specified in TS 36.331

[10] , section 5.6.2a. 3> If the E-UTRA RRCConnectionResume message contains an RRCReconfiguration message: 4> Submit the RRCReconfigurationComplete message embedded in the E-UTRA RRC message RRCConnectionResumeComplete, as specified in TS 36.331

[10] , section 5.3.3.4a; 3>Otherwise: 4> Submit the RRCReconfigurationComplete embedded in the E-UTRA RRC message RRCConnectionReconfigurationComplete via E-UTRA, as specified in TS 36.331

[10] , section 5.3.5.3 / 5.3.5.4 / 5.4.2.3; 3> If the E-UTRA message (RRCConnectionReconfiguration or RRCConnectionResume) containing the RRCReconfiguration message does not include scg-State: Perform SCG activation as specified in 4>5.3.5.13a; 4>If reconfigurationWithSync is included in the spCellConfig of SCG: 5>Initiate a random access procedure on the PSCell as specified in TS 38.321[3]; 4> If the SCG was deactivated before receiving the E-UTRA RRC message containing the RRCReconfiguration message: 5> If bfd-and-RLM was not set to true before receiving an E-UTRA RRCConnectionReconfiguration or RRCConnectionResume message containing an RRCReconfiguration message, or if a lower layer indicates that a random access procedure is required for SCG activation: 6>Initiate a random access procedure on the SpCell as specified in TS 38.321[3]; 5> Otherwise, end the procedure; 4> Otherwise, end the procedure; 3>Otherwise: Perform SCG deactivation as specified in 4>5.3.5.13b; 4>Finish the procedure; 2>DLInformationTransferIf an RRCReconfiguration message is received within nr-SecondaryCellGroupConfig of an RRCConnectionReconfiguration message received via SRB3 in MRDC: 3> Submit the RRCReconfigurationComplete embedded in the E-UTRA RRC message RRCConnectionReconfigurationComplete via E-UTRA, as specified in TS 36.331

[10] , section 5.3.5.3 / 5.3.5.4; 3>If scg-State is not included in RRCConnectionReconfiguration: 4>If reconfigurationWithSync is included in the spCellConfig of SCG: 5>Initiate a random access procedure on the SpCell as specified in TS 38.321[3]; 4> Otherwise, end the procedure; 3>Otherwise: Perform SCG deactivation as specified in 4>5.3.5.13b; 4>Finish the procedure; Note 1: The order in which the UE sends the RRCConnectionReconfigurationComplete message and executes random access procedures toward the SCG is left to the UE implementation. 2> If not (RRCReconfiguration was received via SRB3) but not within DLInformationTransferMRDC: 3> To send using the new configuration, submit the RRCReconfigurationComplete message to the lower layer via SRB3; Note 2: In (NG)EN-DC and NR-DC, if an RRCReconfiguration is received via SRB1 or within DLInformationTransferMRDC via SRB3, random access is triggered by the RRC layer itself because there are not necessarily other UL transmissions. If an RRCReconfiguration is received via SRB3 but not within DLInformationTransferMRDC, random access is triggered by the MAC layer upon arrival of RRCReconfigurationComplete. 1>Instead, if the RRCReconfiguration message is received via SRB1 in nr-SCG within mrdc-SecondaryCellGroup (if the UE in NR-DC, mrdc-SecondaryCellGroup, receives it via RRCReconfiguration or RRCResume through SRB1): 2>When RRCReconfiguration is applied by a conditional reconfiguration execution of a CPC configured via conditionalReconfiguration included in nr-SCG within mrdc-SecondaryCellGroup: As specified in Section 3>5.7.2a.3, submit the RRCReconfigurationComplete message embedded in the NR RRC message ULInformationTransferMRDC via the NR MCG. 2> If the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message does not include scg-State: Perform SCG activation as specified in 3>5.3.5.13a; 3>If reconfigurationWithSync is included in nr-SCG's spCellConfig: 4>Initiate a random access procedure on the PSCell as specified in TS 38.321[3]; 3> If the SCG was deactivated before receiving an NR RRC message containing an RRCReconfiguration message: 4> If bfd-and-RLM was not configured to true before receiving an RRCReconfiguration or RRCResume message containing an RRCReconfiguration message; or 4> If the lower layer indicates that a random access procedure is required for SCG activation: 5>Initiate a random access procedure on the PSCell as specified in TS 38.321[3]; 4> Otherwise, end the procedure; 3> Otherwise, end the procedure; 2>Other cases 3> Perform SCG deactivation as specified in 5.3.5.13b; 3>Finish the procedure; Note 2a: The order in which the UE sends the RRCReconfigurationComplete message and executes random access procedures toward the SCG is left to the UE implementation. 1> Instead, if the RRCReconfiguration message is received via SRB3 (UE is in NR-DC): 2>If the RRCReconfiguration message is received within DLInformationTransferMRDC: 3> If the RRCReconfiguration message is received within nr-SCG in mrdc-SecondaryCellGroup (NR SCG RRC reconfiguration): 4>If the RRCReconfiguration message contains an RRCReconfiguration message and does not include scg-State: 5>If reconfigurationWithSync is included in nr-SCG's spCellConfig: 6>Initiate a random access procedure on the PSCell as specified in TS 38.321[3]; 5>Otherwise: 6>Finish the procedure; 4>Otherwise: Perform SCG deactivation as specified in 5>5.3.5.13b; 5>Finish the procedure; 3>Otherwise: 4>If RRCReconfiguration does not include mrdc-SecondaryCellGroupConfig: 5>If RRCReconfiguration includes scg-State: Perform SCG deactivation as specified in 6>5.3.5.13b; 4> To send using the new configuration, submit the RRCReconfigurationComplete message to the lower layer via SRB1; 2>Otherwise: 3> To send using the new configuration, submit the RRCReconfigurationComplete message to the lower layer via SRB3; 1>Otherwise (if RRCReconfiguration is received via SRB1): 2>UE is within NR-DC, and; 2>If RRCReconfiguration does not include mrdc-SecondaryCellGroupConfig: 3>If RRCReconfiguration includes scg-State: Perform SCG deactivation as specified in 4>5.3.5.13b; 3>Otherwise: Perform SCG activation without an SN message, as specified in 4>5.3.5.13b1; 2>If reconfigurationWithSync is included in the spCellConfig of MCG: 3>If ta-Report is configured with the value enabled and the UE supports TA reporting: 4> Indicates the start of TA reporting to lower layers; 2> To send using the new configuration, submit the RRCReconfigurationComplete message to the lower layer via SRB1; 2> If this is the first RRCReconfiguration message after the successful completion of the RRC re-establishment procedure: 3> Restart the suspended IAB-MT SRB2, SRB4, DRB, multicast MRB, BH RLC channels, and the L2 U2N relay UE Uu relay RLC channel; 1> If the spCellConfig of the MCG or SCG includes reconfigurationWithSync and the MAC of the NR cell group successfully completes the random access procedure triggered above; or 1>If the reconfigurationWithSync in the MCG's spCellConfig includes sl-PathSwitchConfig and the RRCReconfigurationComplete message is successfully sent (i.e., a PC5 RLC acknowledgment is received from the target L2 U2N relay UE): 2> If operating, stop timer T304 for that cell group; 2>If sl-PathSwitchConfig is included in reconfigurationWithSync: 3> Stop Timer T420; 3> Release all wireless resources, including RLC entities and MAC configurations on the source side; 3> Reset the MAC used in the source cell; Note 2b: PDCP and SDAP, configured by the source before the path switch and reconfigured and reused by the target when delta signaling is used, are not released as part of this procedure. 2> If running, stop the timer T310 of the source SpCell; 2> Apply the CSI reporting configuration, scheduling request configuration, and sounding RS configuration to any part where the UE does not need to know the SFN of each target SpCell; 2> If there are parts of the measurement and wireless resource configuration where the UE needs to know the SFN of each target SpCell (e.g., measurement gap, periodic CQI reporting, scheduling request configuration, sounding RS configuration), then obtain and apply the SFN of that target SpCell; 2> For each DRB configured as a DAPS bearer, request an uplink data switch to the PDCP entity as specified in TS 38.323[5]; 2>If reconfigurationWithSync is included in the spCellConfig of MCG: 3>If T390 is running: 4> Stop timer T390 for all access categories; Perform the action as specified in 4>5.3.14.4; 3>If the T350 is working: 4> Stop Timer T350; 3> RRCReconfiguration does not include dedicatedSIB1-Delivery, and 3>If the active downlink BWP indicated by firstActiveDownlinkBWP-Id of the MCG target SpCell has a common search space composed of searchSpaceSIB1: 4> Obtain the SIB1 scheduled for the target SpCell of the MCG as specified in TS 38.213

[13] ; 4>When SIB1 is obtained, perform the action specified in section 5.2.2.4.2; 2>If reconfigurationWithSync is included in the spCellConfig of MCG: or 2>If reconfigurationWithSync is included in spCellConfig of SCG, and CPA or CPC is configured: 3> If present, delete all entries in MCG and SCG VarConditionalReconfig; 3> Delete all entries in VarConditionalReconfiguration, if any, as specified in TS 36.331

[10] , section 5.3.5.9.6; 3> If configured, each measId in MCG measConfig, and if configured, each measId in SCG measConfig, if the associated reportConfig has the reportType set in condTriggerConfig: 4> For the associated reportConfigId: 5> Remove the entry with the matching reportConfigId from reportConfigList in VarMeasConfig; 4> If the associated measObjectId is only associated with a reportConfig where reportType is set to condTriggerConfig: 5> Remove the entry with the matching measObjectId from the measObjectList in VarMeasConfig; 4> Remove the matching measId entry from measIdList in VarMeasConfig; 2>If reconfigurationWithSync is included in masterCellGroup or secondaryCellGroup: 3> If the UE has started sending UEAssistanceInformation messages to the corresponding cell group in the past 1 second, and the UE is still configured to provide the corresponding UE assistance information to the corresponding cell group; or 3> If a conditional reconfiguration run applies the RRCReconfiguration message, and the UE is configured to provide UE assistance information for the corresponding cell group, and the UE is configured to do so in accordance with Section 5.7.4.2, and has therefore initiated sending the UEAssistanceInformation message for the corresponding cell group: 4> In order to provide the relevant UE assistance information, initiate sending of UEAssistanceInformation messages to the corresponding cell group in accordance with Section 5.7.4.3; 4> Start or restart the MUSIM prohibit timer (if any) associated with the corresponding UE assistance information for which a timer value has been set in the corresponding configuration value, or exit without responding to the timer; 3> If the target Pcell provides SIB12 and the UE starts sending a SidelinkUEInformationNR message indicating a change in NR sidelink communication / discovery-related parameters associated with the target Pcell (i.e., a change in sl-RxInterestedFreqList or sl-TxResourceReqList) within the second immediately preceding the UE receiving an RRCReconfiguration message containing reconfigurationWithSync in the MCG's spCellConfig; or 3>If a conditional reconfiguration execution applies the RRCReconfiguration message, the UE is responsive to NR sidelink communication / discovery, SIB12 is provided by the target Pcell, and the UE was configured to do so in accordance with 5.8.3.2, and therefore initiated sending the SidelinkUEInformationNR message: Instruct the sending of SidelinkUEInformationNR messages according to 4>5.8.3.3; 2>If reconfigurationWithSync is included in masterCellGroup: 3> Application layer measurement is configured, and an application layer measurement report container has been received from a higher layer, but the message has not been successfully sent or at least one segment of the message has not been acknowledged by a lower layer: 4> Resubmit the MeasurementReportAppLayer message or all segments of the MeasurementReportAppLayer message to the lower layer for transmission via SRB4; 2>If reconfigurationWithSync is included in masterCellGroup and the target cell is providing SIB21: 3>If the UE started sending an MBSInterestIndication message in the second immediately preceding the receipt of this RRCReconfiguration message; or 3> If a conditional reconfiguration execution applies an RRCReconfiguration message, and the UE starts sending MBSInterestIndication messages after receiving this RRCReconfiguration message: Initiate sending of MBSInterestIndication messages according to section 4>5.9.4; 2>Finish the procedure. Note 3: The UE is required to acquire the broadcast SIB1 only if it can acquire it without interrupting the reception of unicast or MBS multicast data; in other words, broadcast and unicast / MBS multicast beams are quasi-coexistent. Note 4: The UE sets the contents of UEAssistanceInformation according to the latest configuration (i.e., the configuration after applying the RRCReconfiguration message) and the latest UE preferences. The UE may include a lot of information in UEAssistanceInformation in addition to the relevant UE assistance information, as per 5.7.4.2. Therefore, the contents of a UEAssistanceInformation message may not be the same as the contents of a previous UEAssistanceInformation message. End of changes Start of changes 5.3.5.5.1 General The network configures a master cell group (MCG) and zero or one secondary cell group (SCG) in the UE. In (NG)EN-DC, the MCG is configured as specified in TS 36.331

[10] , and in NE-DC, the SCG is configured as specified in TS 36.331

[10] . The network provides cell group configuration parameters in CellGroupConfig IE. The UE performs the following actions based on the received CellGroupConfig IE: 1>If CellGroupConfig contains spCellConfig with reconfigurationWithSync: Editor's note: For reconfiguration procedures involving synchronization and whether to reuse IE, see FFS. Perform a reconfiguration with synchronization according to 2>5.3.5.5.2; 2> Restart all suspended radio bearers except the SRB in the source cell group, restart SCG transmission for all radio bearers, restart the BH RLC channel of the IAB-MT if suspended, and restart SCG transmission for the BH RLC channel; Note: If the SCG is deactivated, reactivating SCG transmission on all radio bearers does not imply that PDCP PDUs can be transmitted or received on SCG RLC bearers. 1> If CellGroupConfig contains rlc-BearerToReleaseList or rlc-BearerToReleaseListExt: 2> Perform RLC bearer release as specified in 5.3.5.5.3; 1> If CellGroupConfig contains rlc-BearerToAddModList: 2> Perform RLC bearer addition / modification as specified in 5.3.5.5.4; 1>If CellGroupConfig includes mac-CellGroupConfig: 2> Configure the MAC entity for this cell group as specified in 5.3.5.5.5; 1>If CellGroupConfig contains sCellToReleaseList: 2> Perform SCell release as specified in 5.3.5.5.8; 1>If CellGroupConfig contains spCellConfig: Configure the SpCell as specified in 2>5.3.5.5.7; 1>If CellGroupConfig contains sCellToAddModList: 2>Perform SCell additions / modifications as specified in 5.3.5.5.9; 1>If CellGroupConfig contains bh-RLC-ChannelToReleaseList: 2> Perform BH RLC channel release as specified in 5.3.5.5.10; 1>If CellGroupConfig contains bh-RLC-ChannelToAddModList: 2>Perform BH RLC channel addition / modification as specified in 5.3.5.5.11; 1>If CellGroupConfig contains uu-RelayRLC-ChannelToReleaseList: 2> Perform Uu relay RLC channel release as specified in 5.3.5.5.12; 1>If CellGroupConfig contains uu-RelayRLC-ChannelToAddModList: 2> Perform the Uu relay RLC channel addition / modification as specified in 5.3.5.5.13; 5.3.5.5.3 RLC Bearer Release The UE must do the following: 1> For each logicalChannelIdentity / LogicalChannelIdentityExt value contained in rlc-BearerToReleaseList / rlc-BearerToReleaseListExt, which is part of the current UE configuration within the same cell group, (release LCH); or For each logicalChannelIdentity value released as a result of SCG release according to 1>5.3.5.4: 2> Release the RLC entity as specified in section 5.1.3 of TS 38.322[4]; 2> Release the corresponding logical channel. 5.3.5.5.4 Addition / Modification of RLC Bearer For each RLC-BearerConfig received in IE via rlc-BearerToAddModList, the UE must perform the following: 1> If this procedure is initiated by generating a complete LTM candidate cell configuration: 2> Create RLC entities for LTM candidate cell configurations that need to generate a complete configuration; 2>Finish the procedure. 1>If the current configuration of the UE includes an RLC bearer with an received logicalChannelIdentity / LogicalChannelIdentityExt within the same cell group: Note X: This case does not apply if this procedure was initiated by generating an LTM candidate cell configuration. 2> If the RLC bearer is associated with the DAPS bearer, or 2> If any DAPS bearer is configured and the RLC bearer is associated with the SRB: 3> Reconfigure the RLC entities of the target cell group according to the received rlc-Config; 3> Reconfigure the logical channels of the target cell group according to the received mac-LogicalChannelConfig; 2>Otherwise: 3>reestablish if RLC is received: 4> Re-establish the RLC entity as specified in TS 38.322[4]; 3> Reconfigure the RLC entities according to the received rlc-Config; 3> Reconfigure the logical channel according to the received mac-LogicalChannelConfig; 3>If you receive a servedMBS-RadioBearer: 4> Associate this logical channel with the PDCP entity identified by servedMBS-RadioBearer; Note 1: In the case of DRB and SRB, the network does not reassociate an already configured logical channel with another radio bearer. Therefore, servedRadioBearer does not exist in this case. In the case of MRB, the network does not reassociate an already configured logical channel with a DRB, SRB, or another MRB (i.e., an MRB of another PDCP entity). Therefore, multicastRLC-BearerConfig does not exist in this case. Note 2: In a DAPS handover, when the UE receives instructions for the successful completion of random access from a lower layer to a target cell, as specified in TS 38.321[3], it may perform re-establishment of the RLC entity of the RLC bearer associated with the non-DAPS bearer (if reestablishRLC is configured). 1> Otherwise (including when the full configuration option is used, and when the logical channels with the given logicalChannelIdentity / LogicalChannelIdentityExt are not configured within the same cell group) 2>If servedRadioBearer associates a logical channel with an SRB and rlc-Config is not included: 3> For the corresponding SRB, establish the RLC entity according to the default configuration defined in 9.2; 2>Otherwise: 3> Establish an RLC entity according to the received rlc-Config; 2>If servedRadioBearer associates a logical channel with an SRB and mac-LogicalChannelConfig is not included: 3> For the corresponding SRB, configure this MAC entity along with the logical channel according to the default configuration defined in 9.2; 2>Otherwise: 3> Configure this MAC entity with a logical channel according to the received mac-LogicalChannelConfig; 2> Associate this logical channel with a PDCP entity identified by servedRadioBearer or servedMBS-RadioBearer; 5.3.5.5.5 MAC Entity Configuration The UE must do the following: 1>If SCG MAC is not part of the current UE configuration (i.e., SCG established): 2> Create an SCG MAC entity; 1> If any DAPS bearer is configured: 2> Reconfigure the MAC main configuration of the target cell group according to the received mac-CellGroupConfig, excluding tag-ToReleaseList and tag-ToAddModList; 1> If this procedure is initiated by generating a complete LTM candidate cell configuration: 2> Create MAC entities for LTM candidate cell configurations that need to generate a complete configuration excluding tag-ToReleaseList and tag-ToAddModList; 1>Otherwise: 2> Reconfigure the MAC main configuration of the cell group according to the received mac-CellGroupConfig, excluding tag-ToReleaseList and tag-ToAddModList; 1>If the received mac-CellGroupConfig contains tag-ToReleaseList: 2> For each TAG-Id value included in tag-ToReleaseList, which is part of the current UE configuration: 3>Release the TAG indicated by TAG-Id; 1>If the received mac-CellGroupConfig contains tag-ToAddModList: 2> For each tag-Id value included in tag-ToAddModList that is not part of the current UE configuration (adding a TAG): 3> Add a TAG corresponding to the tag-Id according to the received timeAlignmentTimer; 2> For each tag-Id value included in tag-ToAddModList, which is part of the current UE configuration (TAG modification): 3> Reconstruct the TAG corresponding to the tag-Id according to the received timeAlignmentTimer. 5.3.5.5.6 RLF Timer and Constant Configuration The UE must do the following: 1>If the received rlf-TimersAndConstants is set to release: 2> If any DAPS bearer is configured: 3>Use the values ​​of timers T301, T310, T311 and constants N310, N311 of the target cell group as they are included in the ue-TimersAndConstants received in SIB1; 2>Otherwise: 3>Use the values ​...

Claims

1. A method performed by a user device (UE) for an L1 / L2 trigger mobility (LTM) cell switching procedure, the method being: Receiving the LTM reference configuration and the LTM candidate cell configuration (200), To obtain the complete LTM candidate cell configuration of the LTM candidate cell, the LTM reference configuration and the LTM candidate cell configuration are combined (202), Receiving an LTM cell switch command from a source network node (204), wherein the LTM cell switch command includes at least an instruction for the LTM candidate cell configuration. Applying the complete LTM candidate cell configuration of the instructed LTM candidate cell configuration (206), Send an uplink signaling (208) to confirm the completion of the LTM cell switch procedure, Methods that include...

2. A method according to claim 1, wherein the combination (202) of the LTM reference configuration and the LTM candidate cell configuration in order to obtain a complete LTM candidate cell configuration of the LTM candidate cell is A method comprising receiving one of the LTM reference configuration and the at least one LTM candidate cell configuration from the source network node, and generating the complete LTM candidate cell configuration in response to the reception following a previous reception of the other of the LTM reference configuration and the at least one LTM candidate cell configuration from the source network node.

3. A method according to any one of claims 1 to 2, wherein the combination (202) of the LTM reference configuration and the LTM candidate cell configuration in order to obtain a complete LTM candidate cell configuration of the LTM candidate cell is A method comprising generating the complete LTM candidate cell configuration in response to the reception of the LTM cell switch command from the source network node.

4. A method according to any one of claims 1 to 3, wherein the combination (202) of the LTM reference configuration and the LTM candidate cell configuration in order to obtain a complete LTM candidate cell configuration of the LTM candidate cell is Execute a set of actions common to the LTM reference configuration and the LTM candidate cell configuration. Performing separate sets of actions in the LTM reference configuration and the LTM candidate cell configuration, Perform a set of actions on the LTM reference configuration and / or the LTM candidate cell configuration in accordance with rules or guidelines that define the processing of the ASN. 1 structure, fields, or information elements of the LTM reference configuration and the LTM candidate cell configuration. A method comprising applying the LTM candidate cell configuration on top of the LTM reference configuration according to one or more of the following.

5. The method according to claim 4, wherein performing a set of actions on the LTM reference configuration and / or the LTM candidate cell configuration in accordance with rules or guidelines defining the processing of ASN. 1 structures, fields, or information elements of the LTM reference configuration and the LTM candidate cell configuration is, from the rules or guidelines, Operations used on the values ​​of the ASN. 1 structure, field, or information element of the LTM reference configuration and / or the LTM candidate cell configuration; Operations used based on the type of ASN. 1 structure, field, or information element of the LTM reference configuration and / or the LTM candidate cell configuration; The sequence of operations performed on the values ​​of the ASN.1 structure, field, or information element of the LTM reference configuration and / or the LTM candidate cell configuration; Operations used based on the values ​​of the ASN. 1 structure, field, or information element of the LTM reference configuration and / or the LTM candidate cell configuration; Operations used based on the presence of the ASN. 1 structure, field, or information element in the LTM reference configuration and / or the LTM candidate cell configuration; and A method comprising determining at least one of the operations to be used based on the need code of the ASN. 1 structure, field, or information element of the LTM reference configuration and / or the LTM candidate cell configuration.

6. A method according to any one of claims 1 to 3, further, To prepare a portion of the complete LTM candidate cell configuration based on the reception of the LTM reference configuration and the LTM candidate cell configuration, In response to the reception of the LTM cell switch command, prepare the complete LTM candidate cell configuration based on the portion, Methods that include...

7. A method according to any one of claims 1 to 6, wherein the combination (202) of the LTM reference configuration and the LTM candidate cell configuration in order to obtain a complete LTM candidate cell configuration of the LTM candidate cell is A method comprising defining the LTM candidate cell configuration as the complete LTM candidate cell configuration.

8. A method according to any one of claims 1 to 7, wherein after receiving the LTM cell switch command (204) and before applying the complete LTM candidate cell configuration (206), Copy the timers, counters, and / or configurations from the current UE configuration to the complete LTM candidate cell configuration. In the current UE configuration, clear the dedicated configuration previously received from the source network node via dedicated signaling. In the current UE configuration, clear the common configuration previously received from the source network node via system information, and A method comprising at least one of the following: performing an L2 reset.

9. A method according to any one of claims 1 to 8, wherein after receiving the LTM cell switch command (204) and before applying the complete LTM candidate cell configuration (206), If no dedicated configuration exists within the complete LTM candidate cell configuration, the default configuration shall be applied. Applying the complete LTM candidate cell configuration to the target cell, and A method comprising at least one of the following: sending the uplink signaling to a target network node to confirm the completion of the LTM cell switch procedure.

10. A method performed by a source network node to initiate an L1 / L2 trigger mobility (LTM) cell switch procedure in a user device (UE), wherein the method is: The LTM reference configuration and the LTM candidate cell configuration are transmitted to the UE (300), Sending an LTM cell switch command to the UE (302) to initiate an LTM cell switch procedure, wherein the LTM cell switch command includes instructions for the LTM candidate cell configuration. Methods that include...

11. A method according to claim 10, wherein the LTM candidate cell configuration transmitted to the UE includes an instruction as to whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.

12. A method according to claim 11, wherein the indication that the LTM candidate cell configuration is a complete LTM candidate cell configuration is sent to the UE in a message that is not the same as the message to which the LTM candidate cell configuration is sent.

13. A method performed by a target network node for an L1 / L2 triggered mobility (LTM) cell switch procedure, the method being: The configuration of the LTM candidate cell configuration on the user equipment (UE) is initiated via another network node (400), The UE receives a signaling (402) indicating that the LTM cell switching procedure has been successfully completed and that the UE has started working with the target network node according to the LTM candidate cell configuration, Methods that include...

14. A method according to claim 13, wherein the LTM candidate cell configuration includes an indication that the LTM candidate cell configuration is a complete LTM candidate cell configuration.

15. User equipment (101, 712A, 712B, 712C, 712D, 800, 1206) for L1 / L2 trigger mobility (LTM) cell switch procedures, A processing circuit (802) configured to perform any one of the steps described in any one of claims 1 to 9, A power supply circuit (808) configured to supply power to the processing circuit, User equipment equipped with these features.

16. Source network nodes (102, 710A, 710B, 900, 1204) for an L1 / L2 triggered mobility (LTM) cell switch procedure, wherein the source network nodes are: A processing circuit (902) configured to perform any of the steps described in any one of claims 10 to 14, A power supply circuit (908) configured to supply power to the processing circuit, A source network node equipped with this feature.

17. Target network nodes (103, 710A, 710B, 900, 1204) for L1 / L2 triggered mobility (LTM) cell switch procedure, wherein the target network nodes are A processing circuit (902) configured to perform any of the steps described in any one of claims 10 to 14, A power supply circuit (908) configured to supply power to the processing circuit, A target network node equipped with these features.

18. User equipment (UE) for an L1 / L2 trigger mobility (LTM) cell switch procedure, wherein the UE is An antenna configured to transmit and receive wireless signals, A wireless front-end circuit connected to the antenna and the processing circuit, configured to adjust the signals communicated between the antenna and the processing circuit, The processing circuit is configured to perform any one of the steps described in any one of claims 1 to 9, An input interface connected to the processing circuit and configured to enable input of information processed by the processing circuit to the UE, An output interface connected to the processing circuit and configured to output information processed by the processing circuit from the UE, A battery connected to the processing circuit and configured to supply power to the UE, User equipment equipped with these features.

Images