EP4696054A1 - Generation of a complete l1/l2-triggered mobility candidate cell configuration - Google Patents

Generation of a complete l1/l2-triggered mobility candidate cell configuration

Info

Publication number
EP4696054A1
EP4696054A1 EP24725005.3A EP24725005A EP4696054A1 EP 4696054 A1 EP4696054 A1 EP 4696054A1 EP 24725005 A EP24725005 A EP 24725005A EP 4696054 A1 EP4696054 A1 EP 4696054A1
Authority
EP
European Patent Office
Prior art keywords
ltm
configuration
candidate cell
cell configuration
integer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP24725005.3A
Other languages
German (de)
French (fr)
Inventor
Antonino ORSINO
Icaro Leonardo DA SILVA
Pontus Wallentin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP4696054A1 publication Critical patent/EP4696054A1/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link

Definitions

  • the present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.
  • L1/L2 based inter-cell mobility includes a technical area entitled L1/L2 based inter-cell mobility.
  • WID when the UE moves from the coverage area of one cell to another cell, at some point a serving cell change needs to be performed.
  • serving cell change is triggered by L3 measurements and is done by RRC signalling triggered Reconfiguration with Synchronisation for change of PCell and PSCell, as well as release add for SCells when applicable. All cases involve complete L2 (and L1) resets, leading to longer latency, larger overhead and longer interruption time than beam switch mobility.
  • the goal of L1/L2 based inter-cell mobility is to enable a serving cell change via L1/L2 signalling, in order to reduce the latency, overhead and interruption time.
  • Some embodiments disclosed herein are directed to a method performed by a user equipment, UE, for a L1/L2-triggered mobility, LTM, cell switch procedure.
  • the method includes receiving LTM reference configuration and LTM candidate cell configuration.
  • the method further includes combining the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell.
  • the method further includes receiving, from a source network node, a LTM cell switch command.
  • the LTM cell switch command includes at least an indication of a LTM candidate cell configuration.
  • the method further includes applying the complete LTM candidate cell configuration of the indicated LTM candidate cell configuration and sending an uplink signalling to acknowledge completion of the LTM cell switch procedure.
  • Some other embodiments are directed to a method performed by a source network node for initiating a L1/L2-triggered mobility, LTM, cell switch procedure at a user equipment, UE.
  • the method includes sending a LTM reference configuration and a LTM candidate cell configuration to the UE, and sending a LTM cell switch command for initiating a LTM cell switch procedure to the UE.
  • the LTM cell switch command includes an indication of the LTM candidate cell configuration.
  • Some other embodiments are directed to a method performed by a target network node for a L1/L2-triggered mobility, LTM, cell switch procedure.
  • the method includes initiating configuration of a LTM candidate cell configuration at a user equipment, UE, through another network node.
  • the method further includes receiving a signalling from the UE which indicates that the LTM cell switch procedure has been successfully completed and that the UE is starting to operate with the target network node according to the LTM candidate cell configuration.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • the proposed embodiments may enable the UE as to when and how to generate a complete LTM candidate cell configuration to be used when an LTM cell switch procedure is triggered by the reception of an LTM cell switch command. Even if the LTM cell switch command may include an indication of a LTM candidate cell configuration, in case the UE previously received also an LTM reference configuration, the UE cannot directly use the LTM candidate cell configuration, since the UE should combine the LTM reference configuration and the LTM candidate cell configuration to generate a complete LTM candidate cell configuration.
  • the UE when receiving an LTM cell switch command that includes an indication of a 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 will guarantee that the LTM cell switch procedure will not fails due to a wrong LTM candidate cell configuration applied (or used) by the UE.
  • Figure 1 illustrates a system structure including the entities which are involved in some embodiments of inventive concepts
  • Figure 2 illustrates flow charts of operations and associated methods by a UE according to some embodiments
  • Figure 3 illustrates flow charts of operations and associated methods by a source network node according to some embodiments
  • Figure 4 illustrates flow charts of operations and associated methods by a target network node according to some embodiments
  • Figure 6 illustrates the corresponding Figure 5.3.5.1-2 from 3GPP TS 38.331 V17.4.0 (2023-03) exhibiting RRC reconfiguration, failure;
  • Figure 7 illustrates an example of a communication system in accordance with some embodiments
  • Figure 8 illustrates a UE in accordance with some embodiments of inventive concepts
  • Figure 9 illustrates a network node in accordance with some embodiments.
  • Figure 10 is a block diagram of a host, which may be an embodiment of the host of Figure 7, in accordance with some embodiments;
  • L1/L2 based inter-cell mobility are applicable to the following scenarios: standalone, CA and NR-DC case with serving cell change within one CG; intra- DU case and intra-CU inter-DU case (applicable for Standalone and CA: no new RAN interfaces are expected); both intra-frequency and inter-frequency; both frequency range 1 (FR1) and FR2; and source and target cells may be synchronized or non-synchronized.
  • LTM L1/L2-triggered mobility
  • the UE is pre-configured, by the network, with an RRC configuration per LTM candidate cell, sometimes also known as a LTM candidate cell configuration.
  • a LTM candidate cell configuration may be an RRCReconfiguration message (e.g. delta signaling associated to a reference configuration or the UE’s current configuration) or one or more IEs/ fields/ parameters such as CellGroupConfig.
  • the UE performs L1 measurements (e.g. CSI measurements, such as SS-RSRP, L1 RSRP per SSB) on these LTM candidate cells and transmits corresponding L1 measurement reports to the network (e.g. on PUCCH and/or PUSCH).
  • the network then triggers the execution of a LTM cell switch in the UE to one of these LTM candidate cells by transmitting an LTM cell switch command (such as a MAC CE), to the UE, which then connects to the particular LTM candidate cell and switches to an RRC configuration of this LTM candidate cell.
  • an LTM cell switch command such as a MAC CE
  • the UE when the LTM is executed, the UE receives a LTM cell switch command in the form of a MAC Control Element, MAC CE, and triggers the LTM cell switch procedure.
  • This command contains also the necessary information for the UE to perform the cell switch, including an indication of an LTM candidate cell configuration.
  • RAN2 has also agreed that, during the configuration of LTM, 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.
  • LTM candidate cell configuration It not known what are the UE actions when the UE needs to apply the LTM candidate cell configuration on top of the LTM reference configuration.
  • various embodiments of the present disclosure are directed to methods and corresponding operations for a User Equipment (UE), to perform a 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 a complete LTM candidate cell configuration for a LTM candidate cell.
  • the methods and operations further include receiving from a source network node a LTM cell switch command (e.g. a MAC CE), including an indication of a LTM candidate cell configuration and applying (or start using, switching to) the complete LTM candidate cell configuration of the indicated LTM candidate cell configuration and in response sending an uplink signalling to acknowledge the completion of the LTM cell switch procedure.
  • a LTM cell switch command e.g. a MAC CE
  • the UE generates a complete LTM candidate cell configuration, by the UE first processing the received LTM reference configuration and then applying on top (to the output of the processing) the received LTM candidate cell configuration.
  • the UE generates a complete LTM candidate cell configuration
  • the UE processes the LTM reference configuration and LTM candidate cell configuration at the same time (e.g., concurrent processing) and performs operations such as ADDITION, INTERSECT, SUBTRACTION, DIVISION in order to combine the LTM reference configuration and LTM candidate cell configuration.
  • the UE generates a complete LTM candidate cell configuration when receiving a LTM reference configuration and LTM candidate cell configuration. For example, the UE generate the complete LTM candidate cell configuration during the configuration of LTM.
  • the UE generates a complete LTM candidate cell configuration when an LTM cell switch procedure is triggered by the reception of an LTM cell switch command comprising an indication of which LTM candidate cell configuration to use.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • the proposed embodiments enable the UE when and how to generate a complete LTM candidate cell configuration to be used when an LTM cell switch procedure is triggered by the reception of an LTM cell switch command. Even if the LTM cell switch command may include an indication of a LTM candidate cell configuration, in case the UE previously received also an LTM reference configuration, the UE cannot directly use the LTM candidate cell configuration, since the UE should combine the LTM reference configuration and the LTM candidate cell configuration to generate a complete LTM candidate cell configuration.
  • the UE when receiving an LTM cell switch command that includes an indication of a 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 will guarantee that the LTM cell switch procedure will not fails due to a wrong LTM candidate cell configuration applied (or used) by the UE.
  • the present disclosure refers to the term “L1/L2 based inter-cell mobility” as used in the Work Item Description in 3GPP, though it interchangeably also uses the terms L1/L2 mobility, L1- mobility, LI based mobility, L1/L2-centric inter-cell mobility, L1/L2 inter-cell mobility L1/L2- Triggered Mobility, Lower-layer triggered Mobility or LTM.
  • the basic principle is that the UE receives a lower layer signaling from the network indicating to the UE a change (or switch or activation) of its serving cell (e.g.
  • a lower layer signaling is a message/ signaling of a lower layer protocol, which may be referred as a L1/L2 inter-cell mobility execution command or LTM cell switch command.
  • the change of serving cell e.g. change of PCell
  • Scell(s) may also lead to a change in Scell(s) for the same cell group e.g. in case the command triggers the UE to change to another cell group configuration of the same type (e.g. another MCG configuration).
  • the UE Before the UE receives the LTM cell switch command, the UE is configured by the network with one or more LTM candidate cell configurations (e.g. reception of an RRC Reconfiguration message, with at least one LTM candidate cell configuration)
  • a LTM candidate cell configuration may include parameters in the IE CellGroupConfig for an LTM candidate cell and/or an embedded RRC Reconfiguration for an LTM candidate cell.
  • LTM cell switch procedure refers to the process of a UE switching (or changing) its cell from a source cell to a target cell (which may be called here an LTM candidate cell or a neighbour cell), using L1/L2-triggered mobility (LTM).
  • LTM L1/L2-triggered mobility
  • an LTM cell switch procedure may sometimes also be known as L1/L2 based inter-cell mobility execution, LTM execution, dynamic switch, LTM switch, (LTM) cell switch, (LTM) serving cell change or (LTM) cell change.
  • switching to the LTM candidate cell configuration comprises the UE considering that an LTM candidate cell becomes its new special cell (SpCell) e.g. PCell in case of LTM being configured for a Master Cell Group (MCG) and/or PSCell in case of LTM being configured for a Secondary Cell Group (SCG); or, changing its SpCell from the current PCell to an LTM candidate cell.
  • SpCell new special cell
  • the LTM candidate cell configuration comprises parameters of a serving cell (or multiple serving cells, such as a cell group), comprising one or more of the groups of parameters, such as an RRCReconfiguration message an IE CellGroupConfig or an IE SpCellConfig (or the IE SCellConfig, in the case of a Secondary Cell).
  • a LTM candidate cell configuration may in one example comprise one or more of: i) the PCell configuration and one or more SCell configuration(s) of a Master Cell Group (MCG); i) the PSCell configuration and one or more SCell configuration(s) of a secondary Cell Group (SCG).
  • the terms (LTM) candidate configuration, LTM configuration, (LTM) candidate target cell configuration, (LTM) target candidate (cell) configuration may be used interchangeably when referring to LTM candidate cell configuration.
  • the text refers also to a partial complete LTM candidate cell configuration.
  • This may be a configuration that is an intermediate result of what will eventually become a complete LTM candidate cell configuration.
  • it may contain only a LTM reference configuration, a subset of the protocol entities, and ASN.1 structures/fields/information elements for each layer of the protocol stack (e.g., a MAC, RLC, PDCP, RRC entity) which will be included in a final complete LTM candidate cell configuration.
  • a partial 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., a MAC, RLC, PDCP, RRC entity) which are present but empty (e.g. not configured), absent or present but partially configured.
  • FIG. 1 illustrates a system structure including the entities which are involved in some embodiments.
  • the User Equipment (UE) 101 is a wireless terminal, such as a cellular smartphone, sometimes connected to the source network node 102 over a wireless interface 104 and sometimes connected to a target network node 103, to which the UE 101 is connected over a wireless interface 105.
  • the source network node 102 In the context of a mobility procedure, such as a LTM cell switch procedure, for the UE, the source network node 102, sometimes also referred to as the serving network node, controls a source cell 109 (sometimes called serving cell or Special Cell (SpCell).
  • the target network node 103 controls a target cell 110 (sometimes called neighbour cell, candidate cell or LTM candidate cell).
  • Methods for a user equipment, UE, to perform a LTM cell switch procedure comprise receiving an LTM reference configuration, and an LTM candidate cell configuration. More than one LTM reference configuration and more than one LTM candidate cell configuration may be received and used for obtaining the complete LTM candidate cell configuration.
  • LTM reference configuration may include more than one LTM reference configuration.
  • LTM candidate cell configuration may include more than one LTM candidate cell configuration.
  • the method further combines an LTM reference configuration and a LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell, further receiving from a source network node a LTM cell switch command (e.g.
  • FIG. 1 illustrates flow charts of operations and associated methods by a UE according to some embodiments of inventive concepts.
  • An example embodiment includes a method performed by a UE for a LTM cell switch procedure.
  • the method includes receiving 200 LTM reference configuration and LTM candidate cell configuration.
  • the method also includes combining 202 the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell.
  • the method also includes receiving 204, from a source network node, a LTM cell switch command, wherein the LTM cell switch command comprise at least an indication of a LTM candidate cell configuration.
  • the method also includes applying 206 the complete LTM candidate cell configuration of the indicated LTM candidate cell configuration.
  • the method also includes sending 208 an uplink signalling to acknowledge completion of the LTM cell switch procedure.
  • the UE generates the complete LTM candidate cell configuration upon the reception of the LTM reference configuration and the LTM candidate cell configuration from the source network node.
  • the UE generates the complete LTM candidate cell configuration when receiving an LTM candidate cell configuration. This means that the UE will not process an LTM reference configuration until it receives an LTM candidate cell configuration (the reception of the LTM candidate cell configuration is the trigger for the generation of the complete LTM candidate cell configuration.
  • the UE process and store in its memory first the LTM reference configuration (regardless of if at least one LTM candidate cell configuration has been received or not) and when receiving an LTM candidate cell configuration starts the process to generate a complete LTM candidate cell configuration.
  • the UE process and store first the LTM reference configuration it create a sort of “template” that is common to all the received LTM candidate cell configurations.
  • the UE generates the complete LTM candidate cell configuration upon the reception of an LTM cell switch command by the source network node.
  • the combining 202 the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell includes generating the complete LTM candidate cell configuration responsive to the reception of the LTM cell switch command from the source network node.
  • the UE start to process and combine the LTM reference configuration and the LTM candidate cell configuration to generate a complete LTM candidate cell configuration only when an LTM cell switch command is received by the source node.
  • the UE process and store in its memory first the LTM reference configuration (regardless of if at least one LTM candidate cell configuration has been received or not) when this is received, but it process the LTM candidate cell configuration to generate a complete LTM candidate cell configuration only when an LTM cell switch command is received by the source node.
  • the UE generates the 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.
  • the UE may generate the complete LTM candidate cell configuration by performing a set of actions that are common for the LTM reference configuration and the LTM candidate cell configuration.
  • One example of this is for the UE to execute only one time the actions as specified in clause 5.3.5.3 of 3GPP TS 38.331 V17.4.0 (2023-03).
  • the UE actions are different in case the UE is processing the LTM reference configuration and the LTM candidate cell configuration. This can be achieved, for instance, by clarify in clause 5.3.5.3 of 3GPP TS 38.331 V17.4.0 (2023-03). which UE actions apply to the case when the LTM reference configuration is processed and when the LTM candidate cell configuration is processed.
  • the UE may generate the complete LTM candidate cell configuration by performing a set of actions that are separate for the LTM reference configuration and the LTM candidate cell configuration.
  • the set of actions performed for the LTM reference configuration may be different from another set of actions performed for the LTM candidate cell configuration.
  • One example of this is for the UE to execute the actions as specified in clause 5.3.5.3 of 3GPP TS 38.331 V17.4.0 (2023-03) independently for the LTM reference configuration and the LTM candidate cell configuration.
  • the UE may generate the complete LTM candidate cell configuration by performing a set of actions where how to process and combine the LTM reference configuration and the LTM candidate cell configuration in order to generate a complete LTM candidate cell configuration is left to the UE implementation.
  • the UE may generate the complete LTM candidate cell configuration by performing a set of actions for the LTM reference configuration and the LTM candidate cell configuration according to a rule or guideline stating how to handle the ASN.1 structures/fields/information elements in the LTM reference configuration and the LTM candidate cell configuration.
  • a rule or guideline may state whether to use the value of an ASN.1 structure/field/information element in the LTM reference configuration or the value in the corresponding ASN.1 structure/field/information element in the LTM candidate cell configuration.
  • a rule or guideline may state to use an operation on the value of an ASN.1 structure/field/information element in the LTM reference configuration and/or the value in the corresponding ASN.1 structure/field/information element in the LTM candidate cell configuration.
  • operation may be ADDITION, INTERSECT, SUBTRACTION, DIVISION, MULTIPLICATION, LOGICAL AND, LOGICAL OR, LOGICAL XOR, CONCATENATION, REPLACEMENT.
  • a rule or guideline may state how to handle a certain type of an ASN.1 structure/field/information element in the LTM reference configuration and the LTM candidate cell configuration.
  • a type may be one of SEQUENCE, SetupRelease, ToAddModList, ToReleaseList, lists, ENUMERATED, CHOICE, OCTET STRING, INTEGER, BOOLEAN, BIT STRING.
  • how to handle may be to append, concatenate, combine, remove or replace involving individual substructures, subfields/elements part of an ASN.1 structure/field/information element in the LTM reference configuration and individual elements part of an the corresponding ASN.1 structure/field/information element in the LTM candidate cell configuration.
  • subfields/elements part of an ASN.1 structure/field/information element are part of lists.
  • how to handle may be in which order to perform a certain operation involving both an ASN.1 structure/field/information element in the LTM reference configuration and the corresponding ASN.1 structure/field/information element in the LTM candidate cell configuration.
  • a rule or guideline may state how to handle a certain value of an ASN.1 structure/field/information element in the LTM reference configuration and the LTM candidate cell configuration.
  • a rule or guideline may state how to handle presence of an ASN.1 structure/field/information element in the LTM reference configuration and the LTM candidate cell configuration.
  • presence may be absent/present, optional presence, conditional presence.
  • how to handle an optional ASN.1 structure/field/information element when it is absent in the LTM reference configuration and the corresponding ASN.1 structure/field/information element is present in the LTM candidate cell configuration or vice versa.
  • how to handle a conditional ASN.1 structure/field/information element when it is absent in the LTM reference configuration and the corresponding ASN.1 structure/field/information element is present in the LTM candidate cell configuration or vice versa.
  • a rule or guideline may state how to handle certain Need codes of an ASN.1 structure/field/information element in the LTM reference configuration and the LTM candidate cell configuration.
  • a Need code may be Specified (S), Maintain (M), No action (N), Release (R).
  • S Specified
  • M Maintain
  • N No action
  • R Release
  • a rule or guideline may state how to handle conditions of an ASN.1 structure/field/information element in the LTM reference configuration and the LTM candidate cell configuration.
  • a rule or guideline may state how to handle extensions of an ASN.1 structure/field/information element in the LTM reference configuration and the LTM candidate cell configuration.
  • the combining 202 the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell includes applying the LTM candidate cell configuration on top of the LTM reference configuration according to one or more of the following: performing a set of actions that are common for the LTM reference configuration and the LTM candidate cell configuration; performing a set of actions that are separate for the LTM reference configuration and the LTM candidate cell configuration; and performing a set of actions for the LTM reference configuration and/or the LTM candidate cell configuration according to a rule or guideline defining handling of ASN.1 structures, fields, or information elements in the LTM reference configuration and the LTM candidate cell configuration.
  • the UE when the UE receives the LTM reference configuration and the LTM candidate cell configuration, the UE processes only the LTM reference configuration and prepare placeholder for configuration to be completed upon the reception of a LTM cell switch command when also the LTM candidate cell configuration is processed.
  • one possible example can be that the UE when processing the LTM reference configuration create (builds, creates, constructs, sets its content) an initial configuration, protocol entities, and ASN.1 structures/fields/information elements for each layer of the protocol stack (e.g., a MAC, RLC, PDCP, RRC entity) then the final configuration of these configurations, protocol entities, and ASN.1 structures/fields/information elements is only obtained when processing the LTM candidate cell configuration (e.g., when the LTM cell switch command is received).
  • the LTM reference configuration create (builds, creates, constructs, sets its content) an initial configuration, protocol entities, and ASN.1 structures/fields/information elements for each layer of the protocol stack (e.g., a MAC, RLC, PDCP, RRC entity) then the final configuration of these configurations, protocol entities, and ASN.1 structures/fields/information elements is only obtained when processing the LTM candidate cell configuration (e.g., when the LTM cell switch command is received).
  • the UE receives both a LTM reference configuration and a LTM candidate cell configuration but consider the LTM candidate cell configuration as 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 comprises all the necessary configuration to operate in a target LTM candidate cell when a LTM cell switch procedure is initiated.
  • the indication on whether the LTM candidate cell configuration is a complete LTM candidate cell configuration is received by the source network node within the LTM cell switch command.
  • the indication on whether the LTM candidate cell configuration is a complete LTM candidate cell configuration is received by the source network node as part of the message (e.g., RRCReconfiguration message) that includes a LTM reference configuration and one or more LTM candidate cell configurations.
  • the indication on whether the LTM candidate cell configuration is a complete LTM candidate cell configuration is received within the LTM candidate cell configuration.
  • the indication on whether the LTM candidate cell configuration is a complete LTM candidate cell configuration is implicit based on the presence or absence of the LTM reference configuration.
  • the complete LTM candidate cell configuration should be generated by applying the LTM candidate cell configuration on top of the LTM reference configuration, while if the LTM reference configuration is absent the LTM candidate cell configuration is a complete LTM candidate cell configuration.
  • abent or “present” can also be mean that the ASN.1 field/structure/information element is “empty” (for the case of absent) or contain some information (for the case of present).
  • the UE upon performing a LTM cell switch procedure due to the reception of a LTM cell switch command comprising an indication of a LTM candidate cell configuration, and before the UE applies the corresponding complete LTM candidate cell configuration related to the indicated LTM candidate cell configuration, the UE performs one or more of the following actions.
  • the UE copies such configuration from its current UE configuration to the complete LTM candidate cell configuration if timers, counters, or any other configuration needs to have a continuity also in the target source node indicated within the LTM cell switch command.
  • timers and counters are handled by the UE. In case these timers and counters should not be stopped when performing a LTM cell switch procedure, the UE takes a snapshot of these timer and counter and continue to use the current values in the target source node towards which the LTM cell switch procedure was performed.
  • the UE clears all the dedicated configuration from its current UE configuration. These are configuration received by dedicated signalling by the source network node. [0091] Third, the UE clears all the common configuration from its current UE configuration. These are configuration received via system information (broadcast) by the source network node.
  • An example embodiment based on the above, after receiving 204 the LTM cell switch command and before applying 206 the complete LTM candidate cell configuration, further comprising at least one of: copying a timer, a counter, and/or a configuration from a current UE configuration to the complete LTM candidate cell configuration; clearing in the current UE configuration, a dedicated configuration earlier received through dedicated signaling from the source network node; clearing in the current UE configuration, a common configuration earlier received through system information from the source network node; and performing an L2 reset.
  • L2 reset may imply a MAC reset, a RLC reestablishment, or a PDCP recovery, and any combination of them.
  • the UE applies a default configuration if a dedicated configuration is not present within the complete LTM candidate cell configuration.
  • a dedicated configuration is not present within the complete LTM candidate cell configuration.
  • One example is the MAC entity. Let’s assume that the UE has to reset the MAC entity when performing a LTM cell switch procedure but no MAC configuration is provided withing the complete LTM candidate cell configuration, in this case the UE applies the MAC default configuration as specified in 3GPP TS 38.331 V17.4.0 (2023-03).
  • the UE applies the complete LTM candidate cell configuration in the target cell. For example, UE starts using the resources which are added or modified as result of applying the complete LTM candidate cell configuration. For example, UE stops using the resources which are released as result of applying the complete LTM candidate cell configuration.
  • the UE sends an UL signalling to the target network node to acknowledge that the LTM cell switch procedure was successfully completed.
  • An example embodiment based on the above, after receiving 204 the LTM cell switch command and before applying 206 the complete LTM candidate cell configuration, further comprising at least one of: applying a default configuration if a dedicated configuration is not present within the complete LTM candidate cell configuration; applying the complete LTM candidate cell configuration in a target cell; and sending the uplink signalling to a target network node to acknowledge the completion of the LTM cell switch procedure.
  • source DU source network node
  • Various embodiments discuss methods for a source network node (source DU), such as a source gNB, a source DU or a source CU, to initiate a LTM cell switch procedure at the UE, include transmitting at least one LTM reference configuration, and at least one LTM candidate cell configuration. More than one LTM reference configuration and more than one LTM candidate cell configuration may be transmitted.
  • the term “LTM reference configuration” may include more than one LTM reference configuration.
  • the term “LTM candidate cell configuration” may include more than one LTM candidate cell configuration.
  • the method further includes transmitting a LTM cell switch command (e.g. a MAC CE) for initiating a LTM cell switch procedure, including an indication of a LTM candidate cell configuration.
  • a LTM cell switch command e.g. a MAC CE
  • Figure 3 illustrates flow charts of operations and associated methods by a source network node according to some embodiments of inventive concepts.
  • a method performed by a source network node for initiating a LTM cell switch procedure at a UE includes sending 300 a LTM reference configuration and a LTM candidate cell configuration to the UE.
  • the method also includes sending 302 a LTM cell switch command for initiating a LTM cell switch procedure to the UE.
  • the LTM cell switch command comprises an indication of the LTM candidate cell configuration.
  • the message containing the LTM candidate cell configuration transmitted to the UE contains an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.
  • the LTM candidate cell configuration sent to the UE contains an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.
  • the indication is explicit for the UE to consider the LTM candidate cell configuration as a complete LTM candidate cell configuration.
  • the indication is implicit for the UE to consider the LTM candidate cell configuration as a complete LTM candidate cell configuration and indicate to the UE that the transmitted LTM reference configuration should not be considered for the generation of a complete LTM candidate cell configuration related to a LTM candidate cell configuration.
  • the message where the where the LTM candidate cell configuration is transmitted to the UE is an RRCReconfiguration.
  • the indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration is transmitted to the UE in a message that is not the same on that one in which the LTM candidate cell configuration is transmitted.
  • the indication of 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 a message in which the LTM candidate cell configuration is transmitted.
  • this message can be a MAC CE, L1 signalling, or RRC message.
  • target DU target network node
  • a method is performed by a target network node for a L1/L2-triggered mobility, LTM, cell switch procedure.
  • the method includes initiating 400 configuration of an LTM candidate cell configuration at a user equipment, UE, through another network node.
  • the method also includes receiving 402 a signalling from the UE which indicates that the LTM cell switch procedure has been successfully completed and that the UE is starting to operate with the target network node according to the LTM candidate cell configuration.
  • the LTM candidate cell configuration contains an indication on whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.
  • the LTM candidate cell configuration contains an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.
  • the indication is explicit for the UE to consider the LTM candidate cell configuration as a complete LTM candidate cell configuration.
  • the indication is implicit for the UE to consider the LTM candidate cell configuration as a complete LTM candidate cell configuration and indicate to the UE that the transmitted LTM reference configuration should not be considered for the generation of a complete LTM candidate cell configuration related to a LTM candidate cell configuration.
  • Figure 5 illustrates the corresponding Figure 5.3.5.1-1 from 3GPP TS 38.331 V17.4.0 (2023-03) exhibiting RRC reconfiguration, successful.
  • Figure 6 illustrates the corresponding Figure 5.3.5.1-2 from 3GPP TS 38.331 V17.4.0 (2023-03) exhibiting RRC reconfiguration, failure.
  • the purpose of this procedure is to modify an RRC connection, e.g. to establish/modify/release RBs/BH RLC channels/Uu Relay RLC channels/PC5 Relay RLC channels, to perform reconfiguration with sync, to setup/modify/release measurements, to add/modify/release SCells and cell groups, to add/modify/release conditional handover configuration, to add/modify/release conditional PSCell change or conditional PSCell addition configuration, to add/modify/ LTM candidate cells.
  • NAS dedicated information may be transferred from the Network to the UE.
  • RRC reconfiguration to perform reconfiguration with sync includes, but is not limited to, the following cases:
  • - for DAPS bearer establishment of RLC for the target Pcell, refresh of security and reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target Pcell;
  • - for SRB refresh of security and establishment of RLC and PDCP for the target Pcell; - reconfiguration with sync for DAPS but without security key refresh, involving RA to the target Pcell, establishment of target MAC, and
  • - for DAPS bearer establishment of RLC for target Pcell, reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target Pcell;
  • SRB3 can be used for measurement configuration and reporting, for UE assistance (re-)configuration and reporting for power savings, for IP address (re-)configuration and reporting for lAB-nodes, to (re-)configure MAC, RLC, BAP, physical layer and RLF timers and constants of the SCG configuration, and to reconfigure PDCP for DRBs associated with the S-K gNB or SRB3, and to reconfigure SDAP for DRBs associated with S-K gNB in NGEN-DC and NR-DC, and to add/modify/release conditional PSCell change configuration, provided that the (re-)configuration does not require any MN involvement, and to transmit RRC messages between the MN and the UE during fast MCG link recovery.
  • the Network may initiate the RRC reconfiguration procedure to a UE in RRC_CONNECTED.
  • the Network applies the procedure as follows:
  • reconfigurationWithSync is included in masterCellGroup only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB, SRB2, are setup and not suspended;
  • conditionalReconfiguration for CPC is included only when at least one RLC bearer is setup in SCG;
  • conditionalReconfiguration for CHO or CPA is included only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB, SRB2, are setup and not suspended.
  • the Itm-CandidateConfig for LTM is included only when AS security has been activated, and SRB2 with at least one DRB are setup and not suspended.
  • the UE shall perform the following actions upon reception of the RRCReconfiguration, or upon execution of the conditional reconfiguration (CHO, CPA or CPC):
  • the K gNB key, the K RRCenc key, the K RRCint key, the Kupint key and the K UPenc key discard the keys used in the source SpCell (the K gNB key, the K RRCenc key, the K RRCint key, the Kupint key and the K UPenc key), if any;
  • the RRCReconfiguration message includes the ue-TxTEG-RequestUL-TDOA-Config-.
  • 3> include the uplinkTxDirectCurrentList for each MCG serving cell with UL;
  • uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG
  • the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrentMoreCarrier.
  • uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG
  • 3> include the uplinkTxDirectCurrentList for each SCG serving cell with UL; 3>include uplinkDirectCurrentBWP-SUL for each SCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentLisf,
  • uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG
  • the RRCReconfiguration includes the secondary CellGroup containing the reportUplinkTxDirectCurrentMoreCarrier.
  • uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG
  • the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to eutra-SCG:
  • the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to nr-SCG:
  • 4> include the logMeasAvailable in the RRCReconfigurationComplete message; 4> if Bluetooth measurement results are included in the logged measurements the UE has available for NR:
  • 4> include rlf-InfoAvailable in the RRCReconfigurationComplete message; > if the UE was configured with successHO-Config when connected to the source Pcell; and > if the applied RRCReconfiguration is not due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3: 4> perform the actions for the successful handover report determination as specified in clause 5.7.10.6, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the MCG;
  • 6> include intraFreq-needForGap and set the gap requirement information of intra-frequency measurement for each NR serving cell;
  • 6> include intraFreq-needForNCSG and set the gap and NCSG requirement information of intra-frequency measurement for each NR serving cell;
  • NR include an entry in interFreq-needForNCSG and set the NCSG requirement information for that band;
  • 5> include the NeedForGapNCSG-InfoEUTRA and set the contents as follows:
  • requestedTargetBandFilterNCSG-EUTRA is configured, for each supported E-UTRA band included in requestedTargetBandFilterNCSG-EUTRA, include an entry in needForNCSG-EUTRA and set the NCSG requirement information for that band; otherwise, include an entry for each supported E-UTRA band in needForNCSG-EUTRA and set the corresponding NCSG requirement information;
  • the random access is triggered by RRC layer itself as there is not necessarily other UL transmission.
  • the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete. l>else if the RRCReconfiguration message was received via SRB1 within the nr-SCG within mrdc-SecondaryCellGroup (UE in NR-DC, mrdc-SecondaryCellGroup was received in RRCReconfiguration or RRCResume via SRB1):
  • searchSpaceSIBl if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG, has a common search space configured by searchSpaceSIBl :
  • the UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e. the broadcast and unicast/MBS multicast beams are quasi co-located.
  • the UE sets the content of UEAssistancelnformation according to latest configuration (i.e. the configuration after applying the RRCReconfiguration message) and latest UE preference.
  • the UE may include more than the concerned UE assistance information within the UEAssistancelnformation according to 5.7.4.2. Therefore, the content of UEAssistancelnformation message might not be the same as the content of the previous UEAssistancelnformation message.
  • the network configures the UE with Master Cell Group (MCG), and zero or one Secondary Cell Group (SCG).
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • NG Master Cell Group
  • SCG Secondary Cell Group
  • the UE performs the following actions based on a received CellGroupConfig IE:
  • the UE shall: l>for each logicalChannelldentity/LogicalChannelldentityExt value included in the rlc- BearerToReleaseList/rlc-BearerToReleaseListExt that is part of the current UE configuration within the same cell group (LCH release); or l>for each logicalChannelldentity value that is to be released as the result of an SCG release according to 5.3.5.4:
  • the UE For each RLC-BearerConfig received in the rlc-BearerToAddModList IE the UE shall: l>if the UE's current configuration contains an RLC bearer with the received losicalChannelldentit /LosicalChannelldentit Ext within the same cell group:
  • the UE may perform RLC entity re-establishment (if reestablishRLC is set) for an RLC bearer associated with a non-DAPS bearer when indication of successful completion of random access towards target cell is received from lower layers as specified in TS 38.321 [3]. l>else if a logical channel with the given logicalChannelldentity/LogicalChannelldentityExt is not configured within the same cell group, including the case when full configuration option is used:
  • the UE shall:
  • the UE shall:
  • the UE shall: l>if the UE is acting as L2 U2N Remote UE:
  • the UE may perform the evaluation of the low mobility criterion for this cell group as specified in 5.7.13.1; > if the SpCellConfig contains the goodServingCellEvaluationRLM'.
  • the UE may perform the evaluation of the good serving cell quality criterion for this SpCell as specified in 5.7.13.2;
  • the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2;
  • the UE shall:
  • the UE shall: l>for each sCelllndex value included in the sCellToAddModList that is not part of the current
  • the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2. l>for each sCelllndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):
  • 3> configure lower layers to consider the SCell to be in deactivated state.
  • the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2.
  • the UE shall perform the following actions based on a received RadioBearerConfig IE:
  • RadioBearerConfig includes the srb3-ToRelease or srb4-ToRelease'.
  • RadioBearerConfig includes the srb-ToAddModList or if any DAPS bearer is configured:
  • RadioBearerConfig includes the drb-ToReleaseList:
  • RadioBearerConfig includes the drb-ToAddModList:
  • RadioBearerConfig includes the mrb-ToReleaseList:
  • RadioBearerConfig includes the mrb-ToAddModList:
  • the UE shall: l>if srb3-ToRelease is included:
  • the UE shall: l>If any DAPS bearer is configured, for each SRB:
  • 3> configure the PDCP entity for the target cell group with state variables continuation as specified in TS 38.323 [5], and with the same security configuration as the PDCP entity for the source cell group; l>for each srb-Identity value included in the srb-ToAddModList that is not part of the current UE configuration (SRB establishment or reconfiguration from E-UTRA PDCP to NR PDCP): 2> establish a PDCP entity;
  • target RAT of handover is E-UTRA/5GC;
  • K RRCenc and K RRCint keys associated with the master key (K eNB ) or secondary key (S-K gNB ) as indicated in keyToUse, if applicable;
  • target RAT of handover is E-UTRA/5GC;
  • 5> configure the PDCP entity to apply the integrity protection algorithm and K RRCint key configured/derived as specified in TS 36.331 [10], i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
  • 5> configure the PDCP entity to apply the ciphering algorithm and K RRCenc key configured/derived as specified in TS 36.331 [10], i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
  • the PDCP entity configures the PDCP entity to apply the integrity protection algorithm and K RRCint key associated with the master key (K eNB ) or secondary key (S-K gNB ), as indicated in keyToUse, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
  • the PDCP entity configures the PDCP entity to apply the ciphering algorithm and K RRCenc key associated with the master key (K eNB ) or secondary key (S-K gNB ) as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
  • the PDCP entity configures the PDCP entity to apply the integrity protection algorithm and K RRCint key associated with the master key (K eNB /K gNB ) or secondary key (S-K gNB ), as indicated in keyToUse , i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
  • the PDCP entity configures the PDCP entity to apply the ciphering algorithm and K RRCenc key associated with the master key (K eNB /K gNB ) or secondary key (S-K gNB ) as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
  • the UE shall: l>for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuration; or l>for each drb-Identity value that is to be released as the result of full configuration according to 5.3.5.11:
  • the UE shall: l>for each drb-Identity value included in the drb-ToAddModList that is not part of the current
  • UE configuration (DRB establishment including the case when full configuration option is used):
  • target RAT of handover is E-UTRA/5GC;
  • K UPenc the key associated with the master key (K eNB ) or secondary key (S-K gNB ) as indicated in keyToUse, if applicable;
  • 5> indicate the establishment of the user plane resources for the pdu-Session to upper layers
  • target RAT of handover is E-UTRA/5GC;
  • the PDCP entity configures the PDCP entity with the ciphering algorithm and K UPenc key associated with the master key (K eNB / K gNB ) or the secondary key (S-K gNB /S-K eNB ), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;
  • the UE When determining whether a drb-Identity value is part of the current UE configuration, the UE does not distinguish which RadioBearerConfig and DRB- ToAddModList that DRB was originally configured in.
  • the network To re-associate a DRB with a different key (K eNB to S-K gNB , K gNB to S-K eNB , K gNB to S-K gNB , or vice versa), the network provides the drb-Identity value in the (target) drb-ToAddModList and sets the reestablishPDCP flag. The network does not list the drb-Identity in the (source) drb- ToReleaseList.
  • the network When setting the reestablishPDCP flag for a radio bearer, the network ensures that the RLC receiver entities do not deliver old PDCP PDUs to the re-established PDCP entity. It does that e.g. by triggering a reconfiguration with sync of the cell group hosting the old RLC entity or by releasing the old RLC entity.
  • UE configuration refers to the parameters configured by NR
  • Ciphering and integrity protection can be enabled or disabled for a DRB.
  • the enabling/disabling of ciphering or integrity protection can be changed only by releasing and adding the DRB.
  • the UE may perform PDCP entity re-establishment (if reestablishPDCP is set) or the PDCP data recovery (if recoverPDCP is set) for a non- DAPS bearer when indication of successful completion of random access towards target cell is received from lower layers as specified in TS 38.321 [3]. In this case, the UE suspends data transmission and reception for all non-DAPS bearers in the source MCG for duration of the DAPS handover.
  • the UE shall perform the following actions based on a received LTM-CandidateConfig IE: 1> store the received Itm-ReferenceConfiguration in VarLTM-Config, if present; 1> if the LTM-CandidateConfig includes the Itm-CandidateToReleaseList:
  • the UE shall: l>for each Itm-Candidateld in the Itm-CandidateToReleaseList:
  • the UE shall: l>for each Itm-Candidateld in the Itm-CandidateToAddModList:
  • the purpose of this procedure is for the UE to generate a complete LTM candidate cell configuration to be stored and applied only when an indication of an LTM cell switch is received by lower layers. During the generation of a complete LTM candidate cell configuration, the current UE configuration is not modified.
  • the UE shall:
  • the UE Upon the indication by lower layers that an LTM cell switch procedure is triggered, the UE shall:
  • the RRCReconfiguration message is the command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC main configuration and physical channel configuration) and AS security configuration.
  • Signalling radio bearer SRB1 or SRB3
  • RRCReconfiguration :: SEQUENCE ⁇ rrc-Transactionldentifier RRC-Transactionldentifier, criticalExtensions CHOICE ⁇ rrcReconfiguration RRCReconfiguration-IEs, criticalExtensionsFuture SEQUENCE ⁇ ⁇ ⁇
  • RRCReconfiguration-Ies :: SEQUENCE ⁇ radioBearerConfig RadioBearerConfig
  • RRCReconfiguration-vl530-Ies SEQUENCE ⁇ masterCellGroup OCTET STRING (CONTAINING CellGroupConfig)
  • OPTIONAL Cond MasterKeyChange dedicatedSIB 1 -Delivery OCTET STRING (CONTAINING SIB 1 )
  • OPTIONAL Need N dedicatedSystemlnformationDelivery OCTET STRING (CONTAINING Systeminformation) OPTIONAL, - Need N otherConfig OtherConfig OPTIONAL, —
  • RRCReconfiguration-vl560-Ies :: SEQUENCE ⁇ mrdc-SecondaryCellGroupConfig SetupRelease ⁇ MRDC-SecondaryCellGroupConfig ⁇ OPTIONAL, - Need M radioBearerConfig2 OCTET STRING (CONTAINING RadioBearerConfig)
  • OPTIONAL Need N sl-ConfigDedicatedNR-r16 SetupRelease ⁇ SL-ConfigDedicatedNR-r16 ⁇
  • OPTIONAL - Need M dedicatedPagingDelivery-r 17 OCTET STRING (CONTAINING Paging)
  • OPTIONAL - Need M ue-TxTEG-RequestUL-TDOA-Config-r17 SetupRelease ⁇ UE-TxTEG-RequestUL-TDOA-
  • 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, -
  • MasterKeyUpdate SEQUENCE ⁇ keySetChangelndicator BOOLEAN, nextHopChainingCount NextHopChainingCount, nas-Container OCTET STRING OPTIONAL, -
  • OnDemandSIB-Request-r16 SEQUENCE ⁇ onDemandSIB-RequestProhibitTimer-r16 ENUMERATED ⁇ sO, sOdot5, si, s2, s5, slO, s20, s30 ⁇ ⁇
  • T316-r16 ENUMERATED ⁇ ms50, mslOO, ms200, ms300, ms400, ms500, ms600, mslOOO, ms 1500, ms2000 ⁇
  • IAB-IP-AddressConfigurationList-r16 SEQUENCE ⁇ iab-IP-AddressToAddModList-r16 SEQUENCE (SIZE(l..maxIAB-IP-Address-r16)) OF
  • IAB-IP-AddressConfiguration-r16 OPTIONAL Need N iab-IP-AddressToReleaseList-r16 SEQUENCE (SIZE(l..maxIAB-IP-Address-r16)) OF IAB-
  • IAB-IP-AddressConfiguration-r16 SEQUENCE ⁇ iab-IP- Addresslndex-r16 IAB -IP- Addresslndex-r16, iab-IP-Address-r16 IAB-IP-Address-r16 OPTIONAL,
  • SL-TimeOffsetEUTRA-r16 ENUMERATED ⁇ msO, ms0dot25, ms0dot5, ms0dot625, ms0dot75, msl, msldot25, msldot5, msldot75, ms2, ms2dot5, ms3, ms4, ms5, ms6, ms8, mslO, ms20 ⁇
  • UE-TxTEG-RequestUL-TDOA-Config-r17 CHOICE ⁇ oneShot-r17 NULL, periodicReporting-r17 ENUMERATED ⁇ msl60, ms320, msl280, ms2560, ms61440, ms81920, ms368640, ms737280 ⁇ ⁇
  • the IE LTM-CandidateConfig is used to provide LTM candidate cell configuration.
  • maxAI-DCI-PayloadSize-r16 INTEGER :: 128 —Maximum size of the DCI payload scrambled with ai-RNTI
  • SIB4 maxCelllntra INTEGER :: 16 — Maximum number of intra-Freq cells listed in
  • SIB3 maxCellMeasEUTRA INTEGER :: 32 — Maximum number of cells in E-
  • maxFreqldle-r16 INTEGER :: 8 — Maximum number of carrier frequencies for idle/inactive measurements
  • NZP Non-Zero-
  • maxNrofSRS-TriggerStates-2 INTEGER 2 — Maximum number of SRS trigger states minus 2.
  • maxFreqPlusl INTEGER :: 9 — Max number of frequencies for Slicing.
  • maxFreqIDC-r16 INTEGER :: 128 — Max number of frequencies for IDC indication.
  • maxComblDC-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-
  • 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-l-r16 INTEGER :: 7 — Maximum number of combinations of mixed Rel-16 and Rel-15 PDCCH
  • VarLTM-Config is used to store the reference configuration and the LTM candidate cell configurations.
  • VarLTM-Config-rl8-IEs SEQUENCE ⁇ ltm-ReferenceConfiguration-rl8 OCTET STRING (CONTAINING RRCReconfiguration),
  • LTM-CandidateList-r 18 :: SEQUENCE (SIZE (l..maxNrofCellsLTM-rl8)) OF LTM-Candidate- rl8
  • LTM-CandidateResetL2-List-rl8 SEQUENCE (SIZE (l..maxNrofCellsLTM-rl8)) OF LTM- Candidate-rl8
  • the IE VarLTM-UE-Config is used to store the generated UE configuration related to the received LTM candidate cell configurations.
  • VarLTM-UE-Config-rl8-IEs :: SEQUENCE ⁇
  • UE-LTM-ConfigCandidateList-rl8 SEQUENCE (SIZE (L.maxNrofCellsLTM-rl8)) OF UE- LTM-Config-r 18
  • Figure 7 shows an example of a communication system 700 in accordance with some embodiments.
  • the communication system 700 includes a telecommunication network 702 that 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 be generally referred to as network nodes 710), or any other similar 3 rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points.
  • 3GPP 3 rd Generation Partnership Project
  • a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor.
  • the telecommunication network 702 includes one or more Open-RAN (ORAN) network nodes.
  • ORAN Open-RAN
  • An ORAN network node is a node in the telecommunication network 702 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 702, including one or more network nodes 710 and/or core network nodes 708.
  • ORAN Open-RAN
  • Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification).
  • a near-real time control application e.g., xApp
  • rApp non-real time control application
  • the network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface.
  • an ORAN access node may be a logical node in a physical node.
  • an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized.
  • the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.
  • the network nodes 710 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 712a, 712b, 712c, and 712d (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over 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 conveying information without the use of wires, cables, or other material conductors.
  • the communication system 700 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 700 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 712 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 710 and other communication devices.
  • the network nodes 710 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 712 and/or with other network nodes or equipment in the telecommunication network 702 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 702.
  • the core network 706 connects the network nodes 710 to one or more hosts, such as host 716. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 706 includes one more core network nodes (e.g., core network node 708) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 708.
  • Example core network nodes include functions of one or more of a 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 De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function

Landscapes

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

Abstract

A method performed by a user equipment, UE, for a L1/L2-triggered mobility, LTM, cell switch procedure including receiving LTM reference configuration and LTM candidate cell configuration The method further includes combining the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell. The method further includes receiving, from a source network node, a LTM cell switch command. The LTM cell switch command includes at least an indication of a LTM candidate cell configuration. The method further includes applying the complete LTM candidate cell configuration of the indicated LTM candidate cell configuration and sending an uplink signalling to acknowledge completion of the LTM cell switch procedure.

Description

GENERATION OF A COMPLETE L1/L2-TRIGGERED MOBILITY CANDIDATE CELL CONFIGURATION
TECHNICAL FIELD
[0001] The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.
BACKGROUND
[0001] In 3rd Generation Partnership Project (3GPP) Release 18, a work item known as Further NR mobility enhancements has been agreed. This work item includes a technical area entitled L1/L2 based inter-cell mobility. According to the Work Item Description, WID [1], when the UE moves from the coverage area of one cell to another cell, at some point a serving cell change needs to be performed. Currently serving cell change is triggered by L3 measurements and is done by RRC signalling triggered Reconfiguration with Synchronisation for change of PCell and PSCell, as well as release add for SCells when applicable. All cases involve complete L2 (and L1) resets, leading to longer latency, larger overhead and longer interruption time than beam switch mobility. The goal of L1/L2 based inter-cell mobility is to enable a serving cell change via L1/L2 signalling, in order to reduce the latency, overhead and interruption time.
[0002] Referring to 3GPP Release 18 Further NR mobility enhancements, one objective of the work is to specify mechanism and procedures of L1/L2 based inter-cell mobility for mobility latency reduction.
SUMMARY
[0003] Some embodiments disclosed herein are directed to a method performed by a user equipment, UE, for a L1/L2-triggered mobility, LTM, cell switch procedure. The method includes receiving LTM reference configuration and LTM candidate cell configuration. The method further includes combining the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell. The method further includes receiving, from a source network node, a LTM cell switch command. The LTM cell switch command includes at least an indication of a LTM candidate cell configuration. The method further includes applying the complete LTM candidate cell configuration of the indicated LTM candidate cell configuration and sending an uplink signalling to acknowledge completion of the LTM cell switch procedure.
[0004] Some other embodiments are directed to a method performed by a source network node for initiating a L1/L2-triggered mobility, LTM, cell switch procedure at a user equipment, UE. The method includes sending a LTM reference configuration and a LTM candidate cell configuration to the UE, and sending a LTM cell switch command for initiating a LTM cell switch procedure to the UE. The LTM cell switch command includes an indication of the LTM candidate cell configuration. [0005] Some other embodiments are directed to a method performed by a target network node for a L1/L2-triggered mobility, LTM, cell switch procedure. The method includes initiating configuration of a LTM candidate cell configuration at a user equipment, UE, through another network node. The method further includes receiving a signalling from the UE which indicates that the LTM cell switch procedure has been successfully completed and that the UE is starting to operate with the target network node according to the LTM candidate cell configuration.
[0006] Certain embodiments may provide one or more of the following technical advantage(s). The proposed embodiments may enable the UE as to when and how to generate a complete LTM candidate cell configuration to be used when an LTM cell switch procedure is triggered by the reception of an LTM cell switch command. Even if the LTM cell switch command may include an indication of a LTM candidate cell configuration, in case the UE previously received also an LTM reference configuration, the UE cannot directly use the LTM candidate cell configuration, since the UE should combine the LTM reference configuration and the LTM candidate cell configuration to generate a complete LTM candidate cell configuration. Therefore, when receiving an LTM cell switch command that includes an indication of a 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 will guarantee that the LTM cell switch procedure will not fails due to a wrong LTM candidate cell configuration applied (or used) by the UE.
[0007] Other methods implemented by UEs and network nodes and corresponding UEs and networks will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional methods and corresponding UEs and network nodes be included within this description, be within the scope of the present inventive subject matter, and be protected by the accompanying claims. Moreover, it is intended that all embodiments disclosed herein can be implemented individually or combined in any way and/or combination. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain nonlimiting embodiments of inventive concepts. In the drawings:
[0009] Figure 1 illustrates a system structure including the entities which are involved in some embodiments of inventive concepts;
[0010] Figure 2 illustrates flow charts of operations and associated methods by a UE according to some embodiments;
[0011] Figure 3 illustrates flow charts of operations and associated methods by a source network node according to some embodiments;
[0012] Figure 4 illustrates flow charts of operations and associated methods by a target network node according to some embodiments;
[0013] Figure 5 illustrates the corresponding Figure 5.3.5.1-1 from 3GPP TS 38.331 V17.4.0 (2023-03) exhibiting RRC reconfiguration, successful;
[0014] Figure 6 illustrates the corresponding Figure 5.3.5.1-2 from 3GPP TS 38.331 V17.4.0 (2023-03) exhibiting RRC reconfiguration, failure;
[0015] Figure 7 illustrates an example of a communication system in accordance with some embodiments;
[0016] Figure 8 illustrates a UE in accordance with some embodiments of inventive concepts;
[0017] Figure 9 illustrates a network node in accordance with some embodiments;
[0018] Figure 10 is a block diagram of a host, which may be an embodiment of the host of Figure 7, in accordance with some embodiments;
[0019] Figure 11 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and
[0020] Figure 12 illustrates a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.
DETAILED DESCRIPTION
[0021] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.
[0022] Further to the above description, configuration and maintenance for multiple candidate cells to allow fast application of configurations for candidate cells [RAN2, RAN3] is defined. Additionally, dynamic switch mechanism among candidate serving cells (including SpCell and SCell) for the potential applicable scenarios based on L1/L2 signalling [RAN2, RAN1], is defined. Additionally, L1 enhancements for inter-cell beam management, including L1 measurement and reporting, and beam indication [RAN1, RAN2]. It is noted that early RAN2 involvement is necessary, including the possibility of further clarifying the interaction between this with the previous statement. Additionally, Timing Advance management [RAN1, RAN2] is defined. Additionally, CU-DU interface signaling to support L1/L2 mobility, if needed [RAN3], is defined.
[0023] It is also noted that frequency range 2 (FR2) specific enhancements are not precluded, if any.
[0024] It is also noted that the procedure of L1/L2 based inter-cell mobility are applicable to the following scenarios: standalone, CA and NR-DC case with serving cell change within one CG; intra- DU case and intra-CU inter-DU case (applicable for Standalone and CA: no new RAN interfaces are expected); both intra-frequency and inter-frequency; both frequency range 1 (FR1) and FR2; and source and target cells may be synchronized or non-synchronized.
[0025] In 3GPP, discussions have started on solutions for L1/L2 based inter-cell mobility (sometimes also referred to as LTM, L1/L2-triggered mobility or lower layer-triggered mobility.
[0026] A basic principle with L1/L2-triggered mobility (LTM) is that the UE is pre-configured, by the network, with an RRC configuration per LTM candidate cell, sometimes also known as a LTM candidate cell configuration. Such a LTM candidate cell configuration may be an RRCReconfiguration message (e.g. delta signaling associated to a reference configuration or the UE’s current configuration) or one or more IEs/ fields/ parameters such as CellGroupConfig. The UE performs L1 measurements (e.g. CSI measurements, such as SS-RSRP, L1 RSRP per SSB) on these LTM candidate cells and transmits corresponding L1 measurement reports to the network (e.g. on PUCCH and/or PUSCH). The network then triggers the execution of a LTM cell switch in the UE to one of these LTM candidate cells by transmitting an LTM cell switch command (such as a MAC CE), to the UE, which then connects to the particular LTM candidate cell and switches to an RRC configuration of this LTM candidate cell. [0027] There currently exist certain challenge(s). Many details of the procedures for L1/L2-based inter-cell mobility are still open in 3GPP. This applies also for the details of the so called LTM cell switch procedure. So far RAN2 has concluded that the UE, when configured with LTM, receives from the network at least a LTM candidate cell configuration. Further, when the LTM is executed, the UE receives a LTM cell switch command in the form of a MAC Control Element, MAC CE, and triggers the LTM cell switch procedure. This command contains also the necessary information for the UE to perform the cell switch, including an indication of an LTM candidate cell configuration.
[0028] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Related to this, RAN2 has also agreed that, during the configuration of LTM, 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.
[0029] One problem that is not yet specified is how in practice the UE should generate a complete
LTM candidate cell configuration. It not known what are the UE actions when the UE needs to apply the LTM candidate cell configuration on top of the LTM reference configuration.
[0030] In order to address the above challenges, various embodiments of the present disclosure are directed to methods and corresponding operations for a User Equipment (UE), to perform a 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 a complete LTM candidate cell configuration for a LTM candidate cell. The methods and operations further include receiving from a source network node a LTM cell switch command (e.g. a MAC CE), including an indication of a LTM candidate cell configuration and applying (or start using, switching to) the complete LTM candidate cell configuration of the indicated LTM candidate cell configuration and in response sending an uplink signalling to acknowledge the completion of the LTM cell switch procedure.
[0031] In some embodiments, the UE generates a complete LTM candidate cell configuration, by the UE first processing the received LTM reference configuration and then applying on top (to the output of the processing) the received LTM candidate cell configuration.
[0032] In some embodiments, the UE generates a complete LTM candidate cell configuration, the UE processes the LTM reference configuration and LTM candidate cell configuration at the same time (e.g., concurrent processing) and performs operations such as ADDITION, INTERSECT, SUBTRACTION, DIVISION in order to combine the LTM reference configuration and LTM candidate cell configuration.
[0033] In some embodiments, the UE generates a complete LTM candidate cell configuration when receiving a LTM reference configuration and LTM candidate cell configuration. For example, the UE generate the complete LTM candidate cell configuration during the configuration of LTM.
[0034] In some embodiments, the UE generates a complete LTM candidate cell configuration when an LTM cell switch procedure is triggered by the reception of an LTM cell switch command comprising an indication of which LTM candidate cell configuration to use.
[0035] Certain embodiments may provide one or more of the following technical advantage(s). The proposed embodiments enable the UE when and how to generate a complete LTM candidate cell configuration to be used when an LTM cell switch procedure is triggered by the reception of an LTM cell switch command. Even if the LTM cell switch command may include an indication of a LTM candidate cell configuration, in case the UE previously received also an LTM reference configuration, the UE cannot directly use the LTM candidate cell configuration, since the UE should combine the LTM reference configuration and the LTM candidate cell configuration to generate a complete LTM candidate cell configuration. Therefore, when receiving an LTM cell switch command that includes an indication of a 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 will guarantee that the LTM cell switch procedure will not fails due to a wrong LTM candidate cell configuration applied (or used) by the UE.
[0036] Some of the embodiments according to inventive concepts are now described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Additional information may also be found in the document provided in the Appendix.
[0037] The present disclosure refers to the term “L1/L2 based inter-cell mobility” as used in the Work Item Description in 3GPP, though it interchangeably also uses the terms L1/L2 mobility, L1- mobility, LI based mobility, L1/L2-centric inter-cell mobility, L1/L2 inter-cell mobility L1/L2- Triggered Mobility, Lower-layer triggered Mobility or LTM. The basic principle is that the UE receives a lower layer signaling from the network indicating to the UE a change (or switch or activation) of its serving cell (e.g. change of PCell, from a source to a target PCell), wherein a lower layer signaling is a message/ signaling of a lower layer protocol, which may be referred as a L1/L2 inter-cell mobility execution command or LTM cell switch command. The change of serving cell (e.g. change of PCell) may also lead to a change in Scell(s) for the same cell group e.g. in case the command triggers the UE to change to another cell group configuration of the same type (e.g. another MCG configuration). Before the UE receives the LTM cell switch command, the UE is configured by the network with one or more LTM candidate cell configurations (e.g. reception of an RRC Reconfiguration message, with at least one LTM candidate cell configuration) A LTM candidate cell configuration may include parameters in the IE CellGroupConfig for an LTM candidate cell and/or an embedded RRC Reconfiguration for an LTM candidate cell.
[0038] The term LTM cell switch procedure refers to the process of a UE switching (or changing) its cell from a source cell to a target cell (which may be called here an LTM candidate cell or a neighbour cell), using L1/L2-triggered mobility (LTM). In the context of L1/L2-triggered mobility (LTM), an LTM cell switch procedure may sometimes also be known as L1/L2 based inter-cell mobility execution, LTM execution, dynamic switch, LTM switch, (LTM) cell switch, (LTM) serving cell change or (LTM) cell change. In the context of some embodiments, switching to the LTM candidate cell configuration comprises the UE considering that an LTM candidate cell becomes its new special cell (SpCell) e.g. PCell in case of LTM being configured for a Master Cell Group (MCG) and/or PSCell in case of LTM being configured for a Secondary Cell Group (SCG); or, changing its SpCell from the current PCell to an LTM candidate cell.
[0039] Even if the term switch or change of cells is used, that may comprise a switch or change of a whole cell group configuration, which includes a change in the SpCell (e.g. change of PCell, or change of PSCell) and a change in SCells of the cell group (e.g. addition, modification and/or release of one or more SCells).
[0040] The text refers to a LTM candidate cell, which is a cell the UE is configured with when configured with L1/L2-triggered mobility. That is a cell the UE can move to in a LTM cell switch procedure, upon reception of a LTM cell switch command. Such cells may also be called candidate cell(s), candidates, mobility candidates, non-serving cells, additional cells, target candidate cell, target candidate, etc. A LTM candidate cell is a cell the UE may perform measurements on (e.g. CSI measurements) so that the UE reports these measurements and network may take educated decision on which beam (e.g. TCI state) and/or cell the UE is to be switched to. An LTM candidate cell may be a candidate to be a target PCell or PSCell, or an SCell of a cell group (e.g. MCG SCell or a SCG SCell).
[0041] The text refers to at least one LTM candidate cell configuration and that the UE has received at least one LTM candidate cell configuration. This is also sometimes referred to as a configuration of a LTM candidate cell, which may be an RRC configuration, such as encapsulated in an RRC Reconfiguration message, that the UE receives when being configured with L1/L2-Triggered Mobility. A LTM candidate cell configuration comprises the configuration which the UE needs to start to operate accordingly when it performs an LTM cell switch procedure to that LTM candidate cell e.g. upon reception of the LTM cell switch command to that LTM candidate cell, which becomes the target cell and the current (new) SpCell, or an SCell in a serving frequency. The LTM candidate cell configuration comprises parameters of a serving cell (or multiple serving cells, such as a cell group), comprising one or more of the groups of parameters, such as an RRCReconfiguration message an IE CellGroupConfig or an IE SpCellConfig (or the IE SCellConfig, in the case of a Secondary Cell). A LTM candidate cell configuration may in one example comprise one or more of: i) the PCell configuration and one or more SCell configuration(s) of a Master Cell Group (MCG); i) the PSCell configuration and one or more SCell configuration(s) of a secondary Cell Group (SCG). The terms (LTM) candidate configuration, LTM configuration, (LTM) candidate target cell configuration, (LTM) target candidate (cell) configuration may be used interchangeably when referring to LTM candidate cell configuration.
[0042] The actual LTM candidate cell configuration and its exact content and/or structure of this IE and/or embedded message may be called an RRC model for the candidate configuration, or simply RRC model. An LTM candidate cell configuration comprises the configuration which the UE needs to operate accordingly when it performs (executes) L1/L2 based inter-cell mobility execution to a LTM candidate cell, upon reception of the lower layer signaling (MAC CE) indicating a L1/L2 based inter-cell mobility to a LTM candidate cell (which becomes the target cell and the current (new) PCell, or an SCell in a serving frequency), or upon reception of the lower layer signaling (MAC CE) indicating a L1/L2 based inter-cell mobility to a LTM candidate cell configuration indicated with a candidate configuration identifier, identity or index (sometimes also denoted candidate configuration ID). The UE may be configured with multiple LTM candidate cell configurations, so a Candidate DU (C-DU) generates and sends to the CU multiple configuration(s). The actual LTM candidate cell configuration the UE receives during the LTM configuration may be a delta signaling to be applied on top of a reference configuration, so that the actual configuration the UE is to use in the LTM candidate cell upon LTM cell switch is the combination of the LTM candidate cell configuration and the reference configuration (e.g. separately signaled by the network to the UE). That combination of the LTM candidate cell configuration and the reference configuration the UE uses may also be called a complete LTM candidate cell configuration. For the context of disclosed embodiments, unless stated otherwise, this complete LTM candidate cell configuration may also be considered as an LTM candidate cell configuration. [0043] The term “beam” may correspond to a spatial direction in which a signal is transmitted (e.g. by a network node) or received (e.g. by the UE), or a spatial filter applied to a signal which is transmitted or received. Thus, transmitting signals different beams could correspond to transmitting signals in different spatial directions. When the text refers to a “beam which is selected” it may refer to a beam index and/or a Reference Signal (RS) index or identifier, such as a Synchronization Signal block (SSB) index, or a CSI-RS resource identifier. Thus, selecting a beam may correspond to selecting an SSB, associated to an SSB index. Or, selecting a beam may correspond to selecting a CSI-RS, associated to a CSI-RS resource identifier.
[0044] In the text the term “apply X on top of Y”. This is an action where the UE applies first a configuration (e.g., a LTM reference configuration) that is common for all the LTM candidate cell configured and then applies a second configuration (e.g., a LTM candidate cell configuration) as a delta of this first configuration.
[0045] The text refers also to a complete LTM candidate cell configuration. This is a configuration that is obtained by the combination of a first configuration (e.g., a LTM reference configuration) and a second configuration (e.g., a LTM candidate cell configuration). The complete LTM candidate cell configuration is the final configuration that the UE should apply and use when performing an LTM cell switch procedure towards a LTM target candidate cell. Please note that the LTM reference configuration or the LTM candidate cell configuration may not be enough for the UE to operate in the LTM target candidate cell.
[0046] The text refers also to a partial complete LTM candidate cell configuration. This may be a configuration that is an intermediate result of what will eventually become a complete LTM candidate cell configuration. For example it may contain only a LTM reference configuration, a subset of the protocol entities, and ASN.1 structures/fields/information elements for each layer of the protocol stack (e.g., a MAC, RLC, PDCP, RRC entity) which will be included in a final complete LTM candidate cell configuration. In some cases a partial 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., a MAC, RLC, PDCP, RRC entity) which are present but empty (e.g. not configured), absent or present but partially configured.
[0047] Figure 1 illustrates a system structure including the entities which are involved in some embodiments. The User Equipment (UE) 101 is a wireless terminal, such as a cellular smartphone, sometimes connected to the source network node 102 over a wireless interface 104 and sometimes connected to a target network node 103, to which the UE 101 is connected over a wireless interface 105. [0048] In the context of a mobility procedure, such as a LTM cell switch procedure, for the UE, the source network node 102, sometimes also referred to as the serving network node, controls a source cell 109 (sometimes called serving cell or Special Cell (SpCell). The target network node 103 controls a target cell 110 (sometimes called neighbour cell, candidate cell or LTM candidate cell). Each of source network node 102 and the target network node 103 may be a base station such as e.g. gNB, or, e.g. in case of a distributed CU/DU (centralized unit/distributed unit) RAN architecture, a distributed unit, sometimes known as either gNB-DU or DU. Hence the source network node 1002 corresponds to a source DU, S-DU, sometimes also known as serving DU, and the target network node 103 corresponds to a target DU. T-DU (sometimes called neighbour DU or candidate DU, C- DU). Both the source network node 102 and the target network node 103 are connected to a third network node 106, sometime also referred to as serving network node. The source network node and the target network node may be the same network node. In some scenarios the source network node 102 and the target network node 103 may be connected to different third network nodes 106.
[0049] Further, the third network node 106 may, e.g. in case of a distributed CU/DU RAN architecture, be a central unit (CU) sometimes referred to as the serving CU, known as either a gNB- CU, CU, gNB-CU-CP or gNB-CU-UP, or a core network node such as an User Plane Function, UPF or an Access and Mobility management Function, AMF.
[0050] Methods for a user equipment, UE, to perform a LTM cell switch procedure, comprise receiving an LTM reference configuration, and an LTM candidate cell configuration. More than one LTM reference configuration and more than one LTM candidate cell configuration may be received and used for obtaining the complete LTM candidate cell configuration. For brevity, the term “LTM reference configuration” may include more than one LTM reference configuration. Similarly, the term “LTM candidate cell configuration” may include more than one LTM candidate cell configuration. The method further combines an LTM reference configuration and a LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell, further receiving from a source network node a LTM cell switch command (e.g. a MAC CE), including an indication of a LTM candidate cell configuration and apply (or start using, switching to) the complete LTM candidate cell configuration of the indicated LTM candidate cell configuration and in response sending an uplink signalling to acknowledge the completion of the LTM cell switch procedure. It is noted that the step of applying the complete LTM candidate cell configuration and/or the step of sending of the uplink signalling may be optional steps for the broadest embodiment related to the UE operations and methods. [0051] Figure 2 illustrates flow charts of operations and associated methods by a UE according to some embodiments of inventive concepts.
[0052] An example embodiment, based on the above, includes a method performed by a UE for a LTM cell switch procedure. The method includes receiving 200 LTM reference configuration and LTM candidate cell configuration. The method also includes combining 202 the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell. The method also includes receiving 204, from a source network node, a LTM cell switch command, wherein the LTM cell switch command comprise at least an indication of a LTM candidate cell configuration. The method also includes applying 206 the complete LTM candidate cell configuration of the indicated LTM candidate cell configuration. The method also includes sending 208 an uplink signalling to acknowledge completion of the LTM cell switch procedure.
[0053] In some embodiments, the UE generates the complete LTM candidate cell configuration upon the reception of the LTM reference configuration and the LTM candidate cell configuration from the source network node.
[0054] In an example embodiment, based on the above, the combining 202 the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell includes generating the complete LTM candidate cell configuration responsive to the reception of one of LTM reference configuration and the at least one LTM candidate cell configuration from the source network node following earlier reception of the other one of the LTM reference configuration and the at least one LTM candidate cell configuration from the source network node.
[0055] In one example the UE generates the complete LTM candidate cell configuration when receiving an LTM candidate cell configuration. This means that the UE will not process an LTM reference configuration until it receives an LTM candidate cell configuration (the reception of the LTM candidate cell configuration is the trigger for the generation of the complete LTM candidate cell configuration.
[0056] In one example the UE process and store in its memory first the LTM reference configuration (regardless of if at least one LTM candidate cell configuration has been received or not) and when receiving an LTM candidate cell configuration starts the process to generate a complete LTM candidate cell configuration. Here when the UE process and store first the LTM reference configuration it create a sort of “template” that is common to all the received LTM candidate cell configurations. [0057] In some embodiments, the UE generates the complete LTM candidate cell configuration upon the reception of an LTM cell switch command by the source network node.
[0058] In an example embodiment, based on the above, the combining 202 the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell includes generating the complete LTM candidate cell configuration responsive to the reception of the LTM cell switch command from the source network node.
[0059] In one example the UE start to process and combine the LTM reference configuration and the LTM candidate cell configuration to generate a complete LTM candidate cell configuration only when an LTM cell switch command is received by the source node.
[0060] In one example the UE process and store in its memory first the LTM reference configuration (regardless of if at least one LTM candidate cell configuration has been received or not) when this is received, but it process the LTM candidate cell configuration to generate a complete LTM candidate cell configuration only when an LTM cell switch command is received by the source node.
[0061] In some embodiments, the UE generates the 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.
[0062] First, the UE may generate the complete LTM candidate cell configuration by performing a set of actions that are common for the LTM reference configuration and the LTM candidate cell configuration. One example of this is for the UE to execute only one time the actions as specified in clause 5.3.5.3 of 3GPP TS 38.331 V17.4.0 (2023-03). In one example, the UE actions are different in case the UE is processing the LTM reference configuration and the LTM candidate cell configuration. This can be achieved, for instance, by clarify in clause 5.3.5.3 of 3GPP TS 38.331 V17.4.0 (2023-03). which UE actions apply to the case when the LTM reference configuration is processed and when the LTM candidate cell configuration is processed.
[0063] Second, the UE may generate the complete LTM candidate cell configuration by performing a set of actions that are separate for the LTM reference configuration and the LTM candidate cell configuration. For example, the set of actions performed for the LTM reference configuration may be different from another set of actions performed for the LTM candidate cell configuration. One example of this is for the UE to execute the actions as specified in clause 5.3.5.3 of 3GPP TS 38.331 V17.4.0 (2023-03) independently for the LTM reference configuration and the LTM candidate cell configuration. [0064] Third, the UE may generate the complete LTM candidate cell configuration by performing a set of actions where how to process and combine the LTM reference configuration and the LTM candidate cell configuration in order to generate a complete LTM candidate cell configuration is left to the UE implementation.
[0065] Fourth, the UE may generate the complete LTM candidate cell configuration by performing a set of actions for the LTM reference configuration and the LTM candidate cell configuration according to a rule or guideline stating how to handle the ASN.1 structures/fields/information elements in the LTM reference configuration and the LTM candidate cell configuration.
[0066] In one example, a rule or guideline may state whether to use the value of an ASN.1 structure/field/information element in the LTM reference configuration or the value in the corresponding ASN.1 structure/field/information element in the LTM candidate cell configuration.
[0067] In one example, a rule or guideline may state to use an operation on the value of an ASN.1 structure/field/information element in the LTM reference configuration and/or the value in the corresponding ASN.1 structure/field/information element in the LTM candidate cell configuration. For example, operation may be ADDITION, INTERSECT, SUBTRACTION, DIVISION, MULTIPLICATION, LOGICAL AND, LOGICAL OR, LOGICAL XOR, CONCATENATION, REPLACEMENT.
[0068] In one example, a rule or guideline may state how to handle a certain type of an ASN.1 structure/field/information element in the LTM reference configuration and the LTM candidate cell configuration. For example, a type may be one of SEQUENCE, SetupRelease, ToAddModList, ToReleaseList, lists, ENUMERATED, CHOICE, OCTET STRING, INTEGER, BOOLEAN, BIT STRING. For example, how to handle may be to append, concatenate, combine, remove or replace involving individual substructures, subfields/elements part of an ASN.1 structure/field/information element in the LTM reference configuration and individual elements part of an the corresponding ASN.1 structure/field/information element in the LTM candidate cell configuration. For example, when these individual substructures, subfields/elements part of an ASN.1 structure/field/information element are part of lists. For example, how to handle may be in which order to perform a certain operation involving both an ASN.1 structure/field/information element in the LTM reference configuration and the corresponding ASN.1 structure/field/information element in the LTM candidate cell configuration. [0069] In one example, a rule or guideline may state how to handle a certain value of an ASN.1 structure/field/information element in the LTM reference configuration and the LTM candidate cell configuration.
[0070] In one example, a rule or guideline may state how to handle presence of an ASN.1 structure/field/information element in the LTM reference configuration and the LTM candidate cell configuration. For example, presence may be absent/present, optional presence, conditional presence. For example, how to handle an optional ASN.1 structure/field/information element when it is absent in the LTM reference configuration and the corresponding ASN.1 structure/field/information element is present in the LTM candidate cell configuration or vice versa. For example, how to handle a conditional ASN.1 structure/field/information element when it is absent in the LTM reference configuration and the corresponding ASN.1 structure/field/information element is present in the LTM candidate cell configuration or vice versa.
[0071] In one example, a rule or guideline may state how to handle certain Need codes of an ASN.1 structure/field/information element in the LTM reference configuration and the LTM candidate cell configuration. For example, a Need code may be Specified (S), Maintain (M), No action (N), Release (R). For example, how to handle an ASN.1 structure/field/information element with certain Need code when it is absent in the LTM reference configuration and when the corresponding ASN.1 structure/field/information element is present in the LTM candidate cell configuration or vice versa.
[0072] In one example, a rule or guideline may state how to handle conditions of an ASN.1 structure/field/information element in the LTM reference configuration and the LTM candidate cell configuration.
[0073] In one example, a rule or guideline may state how to handle extensions of an ASN.1 structure/field/information element in the LTM reference configuration and the LTM candidate cell configuration.
[0074] In an example embodiment, based on the above, the combining 202 the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell includes applying the LTM candidate cell configuration on top of the LTM reference configuration according to one or more of the following: performing a set of actions that are common for the LTM reference configuration and the LTM candidate cell configuration; performing a set of actions that are separate for the LTM reference configuration and the LTM candidate cell configuration; and performing a set of actions for the LTM reference configuration and/or the LTM candidate cell configuration according to a rule or guideline defining handling of ASN.1 structures, fields, or information elements in the LTM reference configuration and the LTM candidate cell configuration.
[0075] In the previous example embodiment, the performing a set of actions for the LTM reference configuration and the LTM candidate cell configuration according to a rule or guideline defining handling of ASN.1 structures, fields, or information elements in the LTM reference configuration and the LTM candidate cell configuration, comprises determining from the rule or guideline at least one of: an operation to use on a value of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; an operation to use based on a type of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; an order in which to perform an operation on a value of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; an operation to use based on a value of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; an operation to use based on presence of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; and an operation to use based on a need code of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration. [0076] In some embodiments, the UE prepares a partial complete LTM candidate cell configuration upon the reception of an LTM reference configuration and the LTM candidate cell configuration and upon the reception of a LTM cell switch command the UE generate a complete LTM candidate cell configuration
[0077] An example embodiment, based on the above, the method further includes preparing a part of the complete LTM candidate cell configuration based on reception of an LTM reference configuration and the LTM candidate cell configuration. The method also further includes, responsive to the reception of a LTM cell switch command, preparing the complete LTM candidate cell configuration based on the part.
[0078] In one example, when the UE receives the LTM reference configuration and the LTM candidate cell configuration, the UE processes only the LTM reference configuration and prepare placeholder for configuration to be completed upon the reception of a LTM cell switch command when also the LTM candidate cell configuration is processed.
[0079] In one case, one possible example can be that the UE when processing the LTM reference configuration create (builds, creates, constructs, sets its content) an initial configuration, protocol entities, and ASN.1 structures/fields/information elements for each layer of the protocol stack (e.g., a MAC, RLC, PDCP, RRC entity) then the final configuration of these configurations, protocol entities, and ASN.1 structures/fields/information elements is only obtained when processing the LTM candidate cell configuration (e.g., when the LTM cell switch command is received).
[0080] In one case, one possible example can be that the UE processes both the LTM reference configuration and LTM candidate cell configuration by creating configurations, protocol entities, and ASN.1 structures/fields/information elements for each layer of the protocol stack (e.g., a MAC, RLC, PDCP, RRC entity) that will be used when performing an LTM cell switch procedure. However, these configurations, protocol entities, and ASN.1 structures/fields/information only applies (or used, or configured) only upon the reception of a LTM cell switch command.
[0081] In some embodiments, the UE generates complete LTM candidate cell configuration is left to the UE implementation. Even if this is left to the UE implementation, still can be specified some high level principle such as that the UE should apply the LTM reference configuration on top of the LTM candidate cell configuration. An indication that can be captured in the specification is whether the UE should generate a complete LTM candidate cell configuration upon the reception of LTM reference configuration and the LTM candidate cell configuration or upon the reception of a LTM cell switch command.
[0082] In some embodiments, the UE receives both a LTM reference configuration and a LTM candidate cell configuration but consider the LTM candidate cell configuration as 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 comprises all the necessary configuration to operate in a target LTM candidate cell when a LTM cell switch procedure is initiated.
[0083] An example embodiment, based on the above, the combining 202 the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell includes defining the LTM candidate cell configuration as the complete LTM candidate cell configuration.
[0084] In one example, the indication on whether the LTM candidate cell configuration is a complete LTM candidate cell configuration is received by the source network node within the LTM cell switch command.
[0085] In one example, the indication on whether the LTM candidate cell configuration is a complete LTM candidate cell configuration is received by the source network node as part of the message (e.g., RRCReconfiguration message) that includes a LTM reference configuration and one or more LTM candidate cell configurations. [0086] In one example, the indication on whether the LTM candidate cell configuration is a complete LTM candidate cell configuration is received within the LTM candidate cell configuration. [0087] In one example, the indication on whether the LTM candidate cell configuration is a complete LTM candidate cell configuration is implicit based on the presence or absence of the LTM reference configuration. For instance, if the LTM reference configuration is present the complete LTM candidate cell configuration should be generated by applying the LTM candidate cell configuration on top of the LTM reference configuration, while if the LTM reference configuration is absent the LTM candidate cell configuration is a complete LTM candidate cell configuration. Here ’’absent” or “present” can also be mean that the ASN.1 field/structure/information element is “empty” (for the case of absent) or contain some information (for the case of present).
[0088] In some embodiments, upon performing a LTM cell switch procedure due to the reception of a LTM cell switch command comprising an indication of a LTM candidate cell configuration, and before the UE applies the corresponding complete LTM candidate cell configuration related to the indicated LTM candidate cell configuration, the UE performs one or more of the following actions.
[0089] First, the UE copies such configuration from its current UE configuration to the complete LTM candidate cell configuration if timers, counters, or any other configuration needs to have a continuity also in the target source node indicated within the LTM cell switch command. One example is the handling of timers and counters. In case these timers and counters should not be stopped when performing a LTM cell switch procedure, the UE takes a snapshot of these timer and counter and continue to use the current values in the target source node towards which the LTM cell switch procedure was performed. For instance, it at the time of initiating the LTM cell switch procedure Timerl=5s and Counterl=10, after performing the LTM cell switch procedure the UE will have an initial value of Timerl=5s and Counterl=10 when start to operate in the target source cell toward which the LTM cell switch procedure was performed. Please note that in this case the initial value of the timer may be greater than 5s since also the time for the UE to switch from the source network node to the target network node would be to be taken into account (since the timer is still running during this period). One example is the handling of the PDCP and SDAP layer. Since one assumption of LTM is that PDCP and SDAP are not released during LTM, in such a case the UE can simply copy paste the configuration related to such entity from its current UE configuration to the complete LTM candidate cell configuration before performing an LTM cell switch procedure.
[0090] Second, the UE clears all the dedicated configuration from its current UE configuration. These are configuration received by dedicated signalling by the source network node. [0091] Third, the UE clears all the common configuration from its current UE configuration. These are configuration received via system information (broadcast) by the source network node.
[0092] An example embodiment, based on the above, after receiving 204 the LTM cell switch command and before applying 206 the complete LTM candidate cell configuration, further comprising at least one of: copying a timer, a counter, and/or a configuration from a current UE configuration to the complete LTM candidate cell configuration; clearing in the current UE configuration, a dedicated configuration earlier received through dedicated signaling from the source network node; clearing in the current UE configuration, a common configuration earlier received through system information from the source network node; and performing an L2 reset.
[0093] Additionally, in some embodiments, upon performing a LTM cell switch procedure due to the reception of a LTM cell switch command comprising an indication of a LTM candidate cell configuration, and before the UE applies the corresponding complete LTM candidate cell configuration related to the indicated LTM candidate cell configuration, the UE performs one or more of the following actions
[0094] Fourth, the UE performs an L2 reset. Here, L2 reset may imply a MAC reset, a RLC reestablishment, or a PDCP recovery, and any combination of them.
[0095] Fifth, the UE applies a default configuration if a dedicated configuration is not present within the complete LTM candidate cell configuration. One example is the MAC entity. Let’s assume that the UE has to reset the MAC entity when performing a LTM cell switch procedure but no MAC configuration is provided withing the complete LTM candidate cell configuration, in this case the UE applies the MAC default configuration as specified in 3GPP TS 38.331 V17.4.0 (2023-03).
[0096] Sixth, the UE applies the complete LTM candidate cell configuration in the target cell. For example, UE starts using the resources which are added or modified as result of applying the complete LTM candidate cell configuration. For example, UE stops using the resources which are released as result of applying the complete LTM candidate cell configuration.
[0097] Seventh, the UE sends an UL signalling to the target network node to acknowledge that the LTM cell switch procedure was successfully completed.
[0098] An example embodiment, based on the above, after receiving 204 the LTM cell switch command and before applying 206 the complete LTM candidate cell configuration, further comprising at least one of: applying a default configuration if a dedicated configuration is not present within the complete LTM candidate cell configuration; applying the complete LTM candidate cell configuration in a target cell; and sending the uplink signalling to a target network node to acknowledge the completion of the LTM cell switch procedure. [0099] Now embodiments related to methods performed by a source network node (source DU) are discussed herein.
[0100] Various embodiments discuss methods for a source network node (source DU), such as a source gNB, a source DU or a source CU, to initiate a LTM cell switch procedure at the UE, include transmitting at least one LTM reference configuration, and at least one LTM candidate cell configuration. More than one LTM reference configuration and more than one LTM candidate cell configuration may be transmitted. For brevity, the term “LTM reference configuration” may include more than one LTM reference configuration. Similarly, the term “LTM candidate cell configuration” may include more than one LTM candidate cell configuration. The method further includes transmitting a LTM cell switch command (e.g. a MAC CE) for initiating a LTM cell switch procedure, including an indication of a LTM candidate cell configuration.
[0101] Figure 3 illustrates flow charts of operations and associated methods by a source network node according to some embodiments of inventive concepts.
[0102] In an example embodiment, based on the above, a method performed by a source network node for initiating a LTM cell switch procedure at a UE. The method includes sending 300 a LTM reference configuration and a LTM candidate cell configuration to the UE. The method also includes sending 302 a LTM cell switch command for initiating a LTM cell switch procedure to the UE. The LTM cell switch command comprises an indication of the LTM candidate cell configuration.
[0103] In some embodiments, the message containing the LTM candidate cell configuration transmitted to the UE contains an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.
[0104] An example embodiment, based on the above, the LTM candidate cell configuration sent to the UE contains an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.
[0105] In one example, the indication is explicit for the UE to consider the LTM candidate cell configuration as a complete LTM candidate cell configuration.
[0106] In one example, the indication is implicit for the UE to consider the LTM candidate cell configuration as a complete LTM candidate cell configuration and indicate to the UE that the transmitted LTM reference configuration should not be considered for the generation of a complete LTM candidate cell configuration related to a LTM candidate cell configuration.
[0107] In one example the message where the where the LTM candidate cell configuration is transmitted to the UE is an RRCReconfiguration. [0108] In some embodiments, the indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration is transmitted to the UE in a message that is not the same on that one in which the LTM candidate cell configuration is transmitted.
[0109] An example embodiment, based on the above, the indication of 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 a message in which the LTM candidate cell configuration is transmitted.
[0110] In one example, this message can be a MAC CE, L1 signalling, or RRC message.
[0111] Now embodiments related to methods performed by a target network node (target DU) are discussed herein.
[0112] Various embodiments discuss a target network node (target DU), such as a target gNB, a target DU, or a target CU, to configure at the UE (e.g., via a third network node or the source network node) a LTM candidate cell configuration and further receiving a signalling from the UE which indicates that an LTM cell switch procedure has been successfully completed and that now the UE is starting to operate in the target network node according to the received LTM candidate cell configuration.
[0113] Figure 4 illustrates flow charts of operations and associated methods by a target network node according to some embodiments of inventive concepts.
[0114] In an example embodiment, based on the above, a method is performed by a target network node for a L1/L2-triggered mobility, LTM, cell switch procedure. The method includes initiating 400 configuration of an LTM candidate cell configuration at a user equipment, UE, through another network node. The method also includes receiving 402 a signalling from the UE which indicates that the LTM cell switch procedure has been successfully completed and that the UE is starting to operate with the target network node according to the LTM candidate cell configuration.
[0115] In some embodiments, the LTM candidate cell configuration contains an indication on whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.
[0116] In an example embodiment, based on the above, the LTM candidate cell configuration contains an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.
[0117] In one example, the indication is explicit for the UE to consider the LTM candidate cell configuration as a complete LTM candidate cell configuration.
[0118] In one example, the indication is implicit for the UE to consider the LTM candidate cell configuration as a complete LTM candidate cell configuration and indicate to the UE that the transmitted LTM reference configuration should not be considered for the generation of a complete LTM candidate cell configuration related to a LTM candidate cell configuration.
[0119] Further embodiments are now explained in the context of operational implementations that may be used with 3GPP TS 38.331 Rel-18 V17.4.0 (2023-03). Some embodiments which are added to the current 3GPP TS 38.331 Rel-18 V17.4.0 (2023-03) are indicated by underlining.
[0120] RRC reconfiguration is now discussed.
[0121] Figure 5 illustrates the corresponding Figure 5.3.5.1-1 from 3GPP TS 38.331 V17.4.0 (2023-03) exhibiting RRC reconfiguration, successful.
[0122] Figure 6 illustrates the corresponding Figure 5.3.5.1-2 from 3GPP TS 38.331 V17.4.0 (2023-03) exhibiting RRC reconfiguration, failure.
[0123] The purpose of this procedure is to modify an RRC connection, e.g. to establish/modify/release RBs/BH RLC channels/Uu Relay RLC channels/PC5 Relay RLC channels, to perform reconfiguration with sync, to setup/modify/release measurements, to add/modify/release SCells and cell groups, to add/modify/release conditional handover configuration, to add/modify/release conditional PSCell change or conditional PSCell addition configuration, to add/modify/ LTM candidate cells. As part of the procedure, NAS dedicated information may be transferred from the Network to the UE.
RRC reconfiguration to perform reconfiguration with sync includes, but is not limited to, the following cases:
- reconfiguration with sync and security key refresh, involving RA to the Pcell/PSCell, MAC reset, refresh of security and re-establishment of RLC and PDCP triggered by explicit L2 indicators;
- reconfiguration with sync but without security key refresh, involving RA to the Pcell/PSCell, MAC reset and RLC re-establishment and PDCP data recovery (for AM DRB or AM MRB) triggered by explicit L2 indicators.
- reconfiguration with sync for DAPS and security key refresh, involving RA to the target Pcell, establishment of target MAC, and
- for non-DAPS bearer: refresh of security and re-establishment of RLC and PDCP triggered by explicit L2 indicators;
- for DAPS bearer: establishment of RLC for the target Pcell, refresh of security and reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target Pcell;
- for SRB: refresh of security and establishment of RLC and PDCP for the target Pcell; - reconfiguration with sync for DAPS but without security key refresh, involving RA to the target Pcell, establishment of target MAC, and
- for non-DAPS bearer: RLC re-establishment and PDCP data recovery (for AM DRB or AM MRB) triggered by explicit L2 indicators.
- for DAPS bearer: establishment of RLC for target Pcell, reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target Pcell;
- for SRB: establishment of RLC and PDCP for the target Pcell.
- reconfiguration with sync for direct-to-indirect path switch, not involving RA at target side, involving re-establishment of PDCP /PDCP data recovery (for AM DRB) triggered by explicit L2 indicators.
In (NG)EN-DC and NR-DC, SRB3 can be used for measurement configuration and reporting, for UE assistance (re-)configuration and reporting for power savings, for IP address (re-)configuration and reporting for lAB-nodes, to (re-)configure MAC, RLC, BAP, physical layer and RLF timers and constants of the SCG configuration, and to reconfigure PDCP for DRBs associated with the S-KgNB or SRB3, and to reconfigure SDAP for DRBs associated with S-KgNB in NGEN-DC and NR-DC, and to add/modify/release conditional PSCell change configuration, provided that the (re-)configuration does not require any MN involvement, and to transmit RRC messages between the MN and the UE during fast MCG link recovery. In (NG)EN-DC and NR-DC, only measConfig, radioBearerConfig, conditionalReconfiguration, bap-Config, iab-IP-AddressConfigurationList, otherConfig and/or secondaryCellGroup are included in RRCReconfiguration received via SRB3, except when RRCReconfiguration is received within DLInformationTransferMRDC.
5.3.5.2 Initiation
The Network may initiate the RRC reconfiguration procedure to a UE in RRC_CONNECTED. The Network applies the procedure as follows:
- the establishment of RBs (other than SRB1, that is established during RRC connection establishment) is performed only when AS security has been activated;
- the establishment of BH RLC Channels for IAB is performed only when AS security has been activated;
- the establishment of Uu Relay RLC channels and PC5 Relay RLC channels (other than SL- RLCO and SL-RLC1) for L2 U2N Relay UE is performed only when AS security has been activated, and the establishment of PC5 Relay RLC channels for L2 U2N Remote UE (other than SL-RLCO and SL-RLC1) is performed only when AS security has been activated; - the addition of Secondary Cell Group and SCells is performed only when AS security has been activated;
- the reconfigurationWithSync is included in secondaryCellGroup only when at least one RLC bearer or BH RLC channel is setup in SCG;
- the reconfigurationWithSync is included in masterCellGroup only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB, SRB2, are setup and not suspended;
- the conditionalReconfiguration for CPC is included only when at least one RLC bearer is setup in SCG;
- the conditionalReconfiguration for CHO or CPA is included only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB, SRB2, are setup and not suspended.
- the Itm-CandidateConfig for LTM is included only when AS security has been activated, and SRB2 with at least one DRB are setup and not suspended.
Editor’s Note: FFS on whether Itm-CandidateConfig applies also for the case of MBS or IAB.
5.3.53 Reception of an RRCReconfiguration by the UE
The UE shall perform the following actions upon reception of the RRCReconfiguration, or upon execution of the conditional reconfiguration (CHO, CPA or CPC):
1> if the RRCReconfiguration is applied due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3:
2> remove all the entries within the MCG and the SCG VarConditionalReconfig, if any;
1> if the RRCReconfiguration includes the daps-SourceReleasc.
2> reset the source MAC and release the source MAC configuration;
2>for each DAPS bearer:
3>release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell;
3>reconfigure the PDCP entity to release DAPS as specified in TS 38.323 [5];
2>for each SRB:
3> release the PDCP entity for the source SpCell;
3>release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell;
2> release the physical channel configuration for the source SpCell;
2> discard the keys used in the source SpCell (the KgNB key, the KRRCenc key, the KRRCint key, the Kupint key and the KUPenc key), if any;
1> if the RRCReconfiguration is received via other RAT (i.e., inter-RAT handover to NR):
2> if the RRCReconfiguration does not include the fullConfig and the UE is connected to 5GC (i.e., delta signalling during intra 5GC handover):
3>re-use the source RAT SDAP and PDCP configurations if available (i.e., current SDAP/PDCP configurations for all RBs from source E-UTRA RAT prior to the reception of the inter-RAT HO RRCReconfiguration message); l>else:
2>if the RRCReconfiguration includes the fullConfig:
3>perform the full configuration procedure as specified in 5.3.5.11;
1> if the RRCReconfiguration includes the masterCellGroup:
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
1> if the RRCReconfiguration includes the masterKeyUpdate
2> perform AS security key update procedure as specified in 5.3.5.7;
1> if the RRCReconfiguration includes the sk-Counter:
2> perform security key update procedure as specified in 5.3.5.7;
1> if the RRCReconfiguration includes the secondaryCellGroup
2> perform the cell group configuration for the SCG according to 5.3.5.5;
1> if the RRCReconfiguration includes the mrdc-SecondaryCellGroupConfig:
2> if the mrdc-SecondaryCellGroupConfig is set to setup:
3> if the mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd:
4> perform MR-DC release as specified in clause 5.3.5.10;
3> if the received mrdc-SecondaryCellGroup is set to nr-SCG:
4> perform the RRC reconfiguration according to 5.3.5.3 for the RRCReconfiguration message included in nr-SCG',
3> if the received mrdc-SecondaryCellGroup is set to eutra-SCG:
4>perform the RRC connection reconfiguration as specified in TS 36.331 [10], clause
5.3.5.3 for the RRCConnectionReconfiguration message included in eutra-SCG',
2>else (mrdc -Secondary CellGroupConfig is set to release):
3>perform MR-DC release as specified in clause 5.3.5.10;
1> if the RRCReconfiguration message includes the radioBearerConfig:
2> perform the radio bearer configuration according to 5.3.5.6; 1> if the RRCReconfiguration message includes the radioBearerConfig2: 2> perform the radio bearer configuration according to 5.3.5.6;
1> if the RRCReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
1> if the RRCReconfiguration message includes the dedicatedNAS-MessageList:
2> forward each element of the dedicatedNAS-MessageList to upper layers in the same order as listed;
1> if the RRCReconfiguration message includes the dedicatedSIBl-Delivery.
2> perform the action upon reception of SIB/ as specified in 5.2.2.4.2;
NOTE 0: If this RRCReconfiguration is associated to the MCG and includes reconfigurationWithSync in spCellConfig and dedicatedSIBl-Delivery, the UE initiates (if needed) the request to acquire required SIBs, according to clause 5.2.2.3.5, only after the random access procedure towards the target SpCell is completed.
1> if the RRCReconfiguration message includes the dedicatedSystemlnformationDelivery.
2> perform the action upon reception of System Information as specified in 5.2.2.4;
1> if the RRCReconfiguration message includes the dedicatedPosSysInfoDelivery.
2> perform the action upon reception of the contained posSIB(s), as specified in clause 5.2.2.4.16;
1> if the RRCReconfiguration message includes the otherConfig:
2> perform the other configuration procedure as specified in 5.3.5.9;
1> if the RRCReconfiguration message includes the bap-Config:
2> perform the BAP configuration procedure as specified in 5.3.5.12;
1> if the RRCReconfiguration message includes the iab-IP-AddressConfigurationList:
2> if iab-IP-AddressToReleaseList is included:
3> perform release of IP address as specified in 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 the RRCReconfiguration message includes the conditionalReconfiguration: 2> perform conditional reconfiguration as specified in 5.3.5.13;
1> if the RRCReconfiguration message includes the needForGapsConfigNR
2> if needForGapsConfigNR is set to setup:
3> consider itself to be configured to provide the measurement gap requirement information of NR target bands; 2>else:
3> consider itself not to be configured to provide the measurement gap requirement information of NR target bands;
1> if the RRCReconfiguration message includes the needForGapNCSG-ConfigNR:
2> if needForGapNCSG-ConfigNR is set to setup:
3> consider itself to be configured to provide the measurement gap and NCSG requirement information of NR target bands;
2>else:
3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of NR target bands;
1> if the RRCReconfiguration message includes the needForGapNCSG-ConfigEUTRA
2>if needForGapNCSG-ConfigEUTRA is set to setup:
3> consider itself to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands;
2>else:
3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands;
1> if the RRCReconfiguration message includes the sl-ConfigDedicatedNR:
2> perform the sidelink dedicated configuration procedure as specified in 5.3.5.14;
NOTE Oa: If the sl-ConfigDedicatedNR was received embedded within an E-UTRA RRCConnectionReconfiguration message, the UE does not build an NR RRCReconfigurationComplete message for the received sl-ConfigDedicatedNR.
1> if the RRCReconfiguration message includes the sl-L2RelayUE-Config:
2> perform the L2 U2N Relay UE configuration procedure as specified in 5.3.5.15;
1> if the RRCReconfiguration message includes the 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 the dedicatedPagingDelivery:
2> perform the Paging message reception procedure as specified in 5.3.2.3;
1> if the RRCReconfiguration message includes the sl-ConfigDedicatedEUTRA-Info:
2> perform related procedures for V2X sidelink communication in accordance with TS 36.331 [10], clause 5.3.10 and clause 5.5.2;
1> if the RRCReconfiguration message includes the ul-GapFR2 -Config:
2> perform the FR2 UL gap configuration procedure as specified in 5.3.5.13c; :> if the RRCReconfiguration message includes the musim-GapConfig:
2> perform the MUSIM gap configuration procedure as specified in 5.3.5.9a;
1> if the RRCReconfiguration message includes the appLayerMeasConfig'.
2> perform the application layer measurement configuration procedure as specified in 5.3.5.13d;
1> if the RRCReconfiguration message includes the ue-TxTEG-RequestUL-TDOA-Config-.
2>if ue-TxTEG-RequestUL-TDOA-Config is set to setup-.
3>perform the UE positioning assistance information procedure as specified in 5.7.14;
2>else:
3> release the configuration of UE positioning assistance information;
1> if the RRCReconfiguration message includes the Itm-CandidateConfig:
2> perform the LTM configuration procedure as specified in 5.3.5.x; 1> set the content of the RRCReconfigurationComplete message as follows:
NOTE X: In case this procedure is initiated due to the generation of a complete LTM candidate cell configuration, the UE should generate only one RRCReconfigurationComplete only after the generation of the complete LTM candidate cell configuration is completed.
2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurren:.
3> include the uplinkTxDirectCurrentList for each MCG serving cell with UL;
3>include uplinkDirectCurrentBWP-SUL for each MCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList-,
2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrentTwoCarrier:
3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG;
2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrentMoreCarrier.
3> include in the uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG;
2> if the RRCReconfiguration includes the secondary CellGroup containing the reportUplinkTxDirectCurrenf.
3> include the uplinkTxDirectCurrentList for each SCG serving cell with UL; 3>include uplinkDirectCurrentBWP-SUL for each SCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentLisf,
2> if the RRCReconfiguration includes the secondary CellGroup containing the reportUplinkTxDirectCurrentTwoCarrier'.
3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG;
2> if the RRCReconfiguration includes the secondary CellGroup containing the reportUplinkTxDirectCurrentMoreCarrier.
3> include in the uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG;
NOTE Ob: The UE does not expect that the reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier is received in both masterCellGroup and in secondaryCellGroup. Network only configures at most one of reportUplinkTxDirectCurrent, reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier in one RRC message.
2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to eutra-SCG:
3> include in the eutra-SCG-Response the E-UTRA RRCConnectionReconfigurationComplete message in accordance with TS 36.331 [10] clause 5.3.5.3;
2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to nr-SCG:
3> include in the nr-SCG-Response the SCG RRCReconfigurationComplete message;
3> if the RRCReconfiguration message is applied due to conditional reconfiguration execution and the RRCReconfiguration message does not include the reconfigurationWithSync in the masterCellGroup'.
4> include in the selectedCondRRCReconfig the condReconfigld for the selected cell of conditional reconfiguration execution;
2> if the RRCReconfiguration includes the reconfigurationWithSync in spCellConfig of an MCG:
3> if the UE has logged measurements available for NR and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasRepor:.
4> include the logMeasAvailable in the RRCReconfigurationComplete message; 4> if Bluetooth measurement results are included in the logged measurements the UE has available for NR:
5> include the logMeasAvailableBT in the RRCReconfigurationComplete message;
4> if WLAN measurement results are included in the logged measurements the UE has available for NR:
5> include the logMeasAvailableWLAN in the RRCReconfigurationComplete message; > if the sigLoggedMeasType in VarLogMeasReport is included:
4> if T330 timer is running and the logged measurements configuration is for NR:
5> set sigLogMeasConfigAvailable to true in the RRCReconfigurationComplete message;
4> else:
5> if the UE has logged measurements available for NR:
6>set sigLogMeasConfigAvailable to false in the RRCReconfigurationComplete message; > if the UE has connection establishment failure or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList:
4> include connEstFaillnfoAvailable in the RRCReconfigurationComplete message; > if the UE has radio link failure or handover failure information available in VarRLF - Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF -Report, or > if the UE has radio link failure or handover failure information available in VarRLF - Report of TS 36.331 [10] and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331 [10]:
4> include rlf-InfoAvailable in the RRCReconfigurationComplete message; > if the UE was configured with successHO-Config when connected to the source Pcell; and > if the applied RRCReconfiguration is not due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3: 4> perform the actions for the successful handover report determination as specified in clause 5.7.10.6, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the MCG;
3> if the UE has successful handover information available in VarSuccessHO-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessHO-Report:
4> include successHO-InfoAvailable in the RRCReconfigurationComplete message; >if the RRCReconfiguration message was received via SRB1, but not within mrdc- SecondaryCellGroup or E-UTRA RRCConnectionReconfiguration or E-UTRA RRCConnectionResume:
3> if the UE is configured to provide the measurement gap requirement information of NR target bands:
4> if the RRCReconfiguration message includes the needForGapsConfigNR', or
4> if the NeedForGapsInfoNR information is changed compared to last time the UE reported this information:
5> include the NeedForGapsInfoNR and set the contents as follows:
6> include intraFreq-needForGap and set the gap requirement information of intra-frequency measurement for each NR serving cell;
6> if requestedTargetBandFilterNR is configured:
7>for each supported NR band that is also included in requestedTargetBandFilterNR, include an entry in interFreq-needForGap and set the gap requirement information for that band;
6>else:
7> include an entry in interFreq-needForGap and set the corresponding gap requirement information for each supported NR band;
3> if the UE is configured to provide the measurement gap and NCSG requirement information of NR target bands:
4> if the RRCReconfiguration message includes the needForGapNCSG-ConfigNR', or
4> if the needForGapNCSG-InfoNR information is changed compared to last time the UE reported this information:
5> include the NeedForGapNCSG-InfoNR and set the contents as follows:
6> include intraFreq-needForNCSG and set the gap and NCSG requirement information of intra-frequency measurement for each NR serving cell;
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>else:
7> include an entry for each supported NR band in interFreq-needForNCSG and set the corresponding NCSG requirement information;
3> if the UE is configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands:
4> if the RRCReconfiguration message includes the needForGapNCSG-ConfigEUTRA', or
4> if the needForGapNCSG-InfoEUTRA information is changed compared to last time the UE reported this information:
5> include the NeedForGapNCSG-InfoEUTRA and set the contents as follows:
6> if requestedTargetBandFilterNCSG-EUTRA is configured, for each supported E-UTRA band included in requestedTargetBandFilterNCSG-EUTRA, include an entry in needForNCSG-EUTRA and set the NCSG requirement information for that band; otherwise, include an entry for each supported E-UTRA band in needForNCSG-EUTRA and set the corresponding NCSG requirement information;
2> if this procedure is initiated due to the generation of a complete LTM candidate cell configuration:
3> the procedure ends; l>if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (UE in (NG)EN-DC): 2> if the RRCReconfiguration message was received via E-UTRA SRB1 as specified in TS 36.331 [10]; or
2> if the RRCReconfiguration message was received via E-UTRA RRC message RRCConnectionReconfiguration within MobilityFromNRCommand (handover from NR standalone to (NG)EN-DC);
3> if the RRCReconfiguration is applied due to a conditional reconfiguration execution for CPC which is configured via conditionalReconfiguration contained in nr- SecondaryCellGroupConfig specified in TS 36.331 [10]:
4> submit the RRCReconfigurationComplete message via the E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331 [10], clause 5.6.2a.
3>else if the RRCReconfiguration message was included in E-UTRA RRCConnectionResume message:
4> submit the RRCReconfigurationComplete message via E-UTRA embedded in E- UTRA RRC message RRCConnectionResumeComplete as specified in TS 36.331 [10], clause 5.3.3.4a;
3>else:
4> submit the RRCReconfigurationComplete via E-UTRA embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10], clause 5.3.5.3/5.3.5.4Z5.4.2.3;
3> if the scg-State is not included in the E-UTRA message (RRCConnectionReconfiguration or RRCConnectionResume') containing the RRCReconfiguration message:
4>perform SCG activation as specified in 5.3.5.13a;
4> if reconfigurationWithSync was included in spCellConfig of an SCG:
5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];
4> else if the SCG was deactivated before the reception of the E-UTRA RRC message containing the RRCReconfiguration message:
5> if bfd-and-RLM was not configured to true before the reception of the E-UTRA RRCConnectionReconfiguration or RRCConnectionResume message containing the RRCReconfiguration message or if lower layers indicate that a Random Access procedure is needed for SCG activation:
6> initiate the Random Access procedure on the SpCell, as specified in TS 38.321 [3];
5>else the procedure ends;
4>else the procedure ends;
3>else:
4>perform SCG deactivation as specified in 5.3.5.13b;
4>the procedure ends; > if the RRCReconfiguration message was received within nr-SecondaryCellGroupConfig in RRCConnectionReconfiguration message received via SRB3 within
DLInformationTransferMRDC'.
3> submit the RRCReconfigurationComplete via E-UTRA embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10], clause 5.3.5.3/5.3.5.4;
3> if the scg-State is not included in the RRCConnectionReconfiguration:
4> if reconfigurationWithSync was included in spCellConfig of an SCG:
5> initiate the Random Access procedure on the SpCell, as specified in TS 38.321 [3];
4>else the procedure ends;
3>else:
4>perform SCG deactivation as specified in 5.3.5.13b;
4>the procedure ends;
NOTE 1: The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.
2>else (RRCReconfiguration was received via SRB3) but not within DLInformationTransferMRDC'.
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;
NOTE 2: In (NG)EN-DC and NR-DC, in the case RRCReconfiguration is received via
SRB1 or within DLInformationTransferMRDC via SRB3, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is received via SRB3 but not within DLInformationTransferMRDC, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete. l>else if the RRCReconfiguration message was received via SRB1 within the nr-SCG within mrdc-SecondaryCellGroup (UE in NR-DC, mrdc-SecondaryCellGroup was received in RRCReconfiguration or RRCResume via SRB1):
2> if the RRCReconfiguration is applied due to a conditional reconfiguration execution for CPC which is configured via conditionalReconfiguration contained in nr-SCG within mrdc-SecondaryCellGroup'.
3> submit the RRCReconfigurationComplete message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3.
2> if the scg-State is not included in the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message:
3>perform SCG activation as specified in 5.3.5.13a; 3> if reconfigurationWithSync was included in spCellConfig in nr-SCG:
4> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];
3>else if the SCG was deactivated before the reception of the NR RRC message containing the RRCReconfiguration message:
4> if bfd-and-RLM was not configured to true before the reception of the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message; or
4> if lower layers indicate that a Random Access procedure is needed for SCG activation:
5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];
4>else the procedure ends;
3>else the procedure ends;
2>else
3>perform SCG deactivation as specified in 5.3.5.13b;
3>the procedure ends;
NOTE 2a: The order in which the UE sends the RRCReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation. l>else if the RRCReconfiguration message was received via SRB3 (UE in NR-DC):
2> if the RRCReconfiguration message was received within DLInformationTransferMRDC
3> if the RRCReconfiguration message was received within the nr-SCG within mrdc-
SecondaryCellGroup (NR SCG RRC Reconfiguration):
4> if the scg-State is not included in the RRCReconfiguration message containing the RRCReconfiguration message:
5> if reconfigurationWithSync was included in spCellConfig in nr-SCG:
6> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];
5>else:
6>the procedure ends;
4> else:
5>perform SCG deactivation as specified in 5.3.5.13b;
5>the procedure ends;
3>else: 4> if the RRCReconfiguration does not include the mrdc-SecondaryCellGroupConfig:
5> if the RRCReconfiguration includes the scg-State:
6> perform SCG deactivation as specified in 5.3.5.13b;
4> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
2>else:
3> if this procedure is initiated due to the processing of Itm-Candidate received within Itm- CandidateConfig;
4> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration only upon the execution of an LTM cell switch procedure as specified in 5.3.5.X.5;
3> else:
4> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration; l>else (RRCReconfiguration was received via SRB1):
2>if the UE is in NR-DC and;
2> if the RRCReconfiguration does not include the mrdc-SecondaryCellGroupConfig'.
3> if the RRCReconfiguration includes the scg-State-.
4>perform SCG deactivation as specified in 5.3.5.13b;
3>else:
4>perform SCG activation without SN message as specified in 5.3.5.13bl ;
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3> if ta-Report is configured with value enabled and the UE supports TA reporting:
4> indicate TA report initiation to lower layers;
2> if this procedure is initiated due to the processing of Itm-Candidate received within Itm- CandidateConfig;
3> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration upon the execution of an LTM cell switch procedure as specified in 5.3.5.X.5;
2> else:
3> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
2> if this is the first RRCReconfiguration message after successful completion of the RRC re- establishment procedure:
3>resume SRB2, SRB4, DRBs, multicast MRB, and BH RLC channels for IAB-MT, and Uu Relay RLC channels for L2 U2N Relay UE, that are suspended;
1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG and when MAC of an NR cell group successfully completes a Random Access procedure triggered above; or,
1> if sl-PathSwitchConfig was included in reconfigurationWithSync included in spCellConfig of an MCG, and when successfully sending RRCReconfigurationComplete message (i.e., PC5 RLC acknowledgement is received from target L2 U2N Relay UE):
2>stop timer T304 for that cell group if running;
2> if sl-PathSwitchConfig was included in reconfigurationWithSync:
3>stop timer T420;
3> release all radio resources, including release of the RLC entities and the MAC configuration at the source side;
3>reset MAC used in the source cell;
NOTE 2b: PDCP and SDAP configured by the source prior to the path switch that are reconfigured and re-used by target when delta signalling is used, are not released as part of this procedure.
2>stop timer T310 for source SpCell if running;
2> apply the parts of the CSI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any;
2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
2>for each DRB configured as DAPS bearer, request uplink data switching to the PDCP entity, as specified in TS 38.323 [5];
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3>if T390 is running:
4>stop timer T390 for all access categories;
4>perform the actions as specified in 5.3.14.4.
3>if T350 is running:
4>stop timer T350; 3> if RRCReconfiguration does not include dedicatedSIBl -Delivery and
3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG, has a common search space configured by searchSpaceSIBl :
4> acquire the SIBI, which is scheduled as specified in TS 38.213 [13], of the target SpCell of the MCG;
4>upon acquiring SIBI, perform the actions specified in clause 5.2.2.4.2; > if the reconfigurationWithSync was included in spCellConfig of an MCG; or > if the reconfigurationWithSync was included in spCellConfig of an SCG and the CPA or
CPC was configured:
3>remove all the entries within the MCG and the SCG VarConditionalReconfig, if any;
3>remove all the entries within VarConditionalReconfiguration as specified in TS 36.331 [10], clause 5.3.5.9.6, if any;
3>for each measld of the MCG measConfig, if configured, and for each measld of the SCG measConfig, if configured, if the associated reportConfig has a reportType set to condTriggerConfig
4> for the associated reportConfigld'.
5> remove the entry with the matching reportConfigld from the reportConfigList within the VarMeasConfig',
4> if the associated measObjectld is only associated to a reportConfig with reportType set to condTriggerConfig'.
5> remove the entry with the matching measObjectld from the measObjectList within the VarMeasConfig',
4> remove the entry with the matching measld from the measIdList within the VarMeasConfig', > if reconfigurationWithSync was included in masterCellGroup or secondary CellGroup'.
3> if the UE initiated transmission of a UEAssistancelnformation message for the corresponding cell group during the last 1 second, and the UE is still configured to provide the concerned UE assistance information for the corresponding cell group; or
3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution, and the UE is configured to provide UE assistance information for the corresponding cell group, and the UE has initiated transmission of a UEAssistancelnformation message for the corresponding cell group since it was configured to do so in accordance with 5.7.4.2:
4> initiate transmission of a UEAssistancelnformation message for the corresponding cell group in accordance with clause 5.7.43 to provide the concerned UE assistance information;
4> start or restart the prohibit timer (if exists) or the leave without response timer for the MUSIM associated with the concerned UE assistance information with the timer value set to the value in corresponding configuration;
3> if SIB12 is provided by the target Pcell, and the UE initiated transmission of a SidelinkUEInformationNR message indicating a change of NR sidelink communication/discovery related parameters relevant in target Pcell (i.e. change of sl- RxInterestedFreqList or sl-TxResourceReqList) during the last 1 second preceding reception of the RRCReconfiguration message including reconfigurationWithSync in spCellConfig of an MCG; or
3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution and the UE is capable of NR sidelink communication/discovery and SIB12 is provided by the target Pcell, and the UE has initiated transmission of a SidelinkUEInformationNR message since it was configured to do so in accordance with 5.83.2:
4> initiate transmission of the SidelinkUEInformationNR message in accordance with 5.8.33; > if reconfigurationWithSync was included in masterCellGroup'.
3> if configured with application layer measurements and if application layer measurement report container has been received from upper layers for which the successful transmission of the message or at least one segment of the message has not been confirmed by lower layers:
4> re-submit the MeasurementReportAppLayer message or all segments of the MeasurementReportAppLayer message to lower layers for transmission via SRB4; > if reconfigurationWithSync was included in masterCellGroup and the target cell provides SIB2I:
3> if the UE initiated transmission of an MBSInterestlndication message during the last 1 second preceding reception of this RRCReconfiguration message; or
3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution, and the UE has initiated transmission of an MBSInterestlndication message after having received this RRCReconfiguration message:
4> initiate transmission of an MBSInterestlndication message in accordance with clause 5.9.4;
2>the procedure ends.
NOTE 3: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e. the broadcast and unicast/MBS multicast beams are quasi co-located.
NOTE 4: The UE sets the content of UEAssistancelnformation according to latest configuration (i.e. the configuration after applying the RRCReconfiguration message) and latest UE preference. The UE may include more than the concerned UE assistance information within the UEAssistancelnformation according to 5.7.4.2. Therefore, the content of UEAssistancelnformation message might not be the same as the content of the previous UEAssistancelnformation message.
5.3.5.5 Cell Group configuration
5.3.5.5.1 General
The network configures the UE with Master Cell Group (MCG), and zero or one Secondary Cell Group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331 [10], and for NE- DC, the SCG is configured as specified in TS 36.331 [10]. The network provides the configuration parameters for a cell group in the CellGroupConfig IE.
The UE performs the following actions based on a received CellGroupConfig IE:
1> if the CellGroupConfig contains the spCellConfig with reconfigurationWithSync: and
1> if this procedure is not initiated due to the generation of a complete LTM candidate cell configuration:
2> perform Reconfiguration with sync according to 5.3.5.5.2;
2> resume all suspended radio bearers except the SRBs for the source cell group, and resume SCG transmission for all radio bearers, and resume BH RLC channels and resume SCG transmission for BH RLC channels for IAB-MT, if suspended;
NOTE: If the SCG is deactivated, resuming SCG transmission for all radio bearers does not imply that PDCP PDUs can be transmitted or received on SCG RLC bearers.
1> if the CellGroupConfig contains the rlc-BearerToReleaseList or rlc-BearerToReleaseListExf. 2> perform RLC bearer release as specified in 5.3.5.5.3; l>if the CellGroupConfig contains the rlc-BearerToAddModList. 2> perform the RLC bearer addition/modification as specified in 5.3.5.5.4; l>if the CellGroupConfig contains the mac-CellGroupConfig
2> configure the MAC entity of this cell group as specified in 5.3.5.5.5; l>if the CellGroupConfig contains the sCellToReleaseLis .
2> perform SCell release as specified in 5.3.5.5.8; l>if the CellGroupConfig contains the spCellConfig-.
2>configure the SpCell as specified in 5.3.5.5.7; l>if the CellGroupConfig contains the sCellToAddModList:
2> perform SCell addition/modification as specified in 5.3.5.5.9; l>if the CellGroupConfig contains the bh-RLC-ChannelToReleaseList:
2> perform BH RLC channel release as specified in 5.3.5.5.10; l>if the CellGroupConfig contains the bh-RLC-ChannelToAddModList:
2> perform the BH RLC channel addition/modification as specified in 5.3.5.5.11; l>if the CellGroupConfig contains the uu-RelayRLC-ChannelToReleaseList:
2> perform Uu Relay RLC channel release as specified in 5.3.5.5.12; l>if the CellGroupConfig contains the 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 shall: l>for each logicalChannelldentity/LogicalChannelldentityExt value included in the rlc- BearerToReleaseList/rlc-BearerToReleaseListExt that is part of the current UE configuration within the same cell group (LCH release); or l>for each logicalChannelldentity value that is to be released as the result of an SCG release according to 5.3.5.4:
2> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3;
2> release the corresponding logical channel.
5.3.5.5.4 RLC bearer addition/modification
For each RLC-BearerConfig received in the rlc-BearerToAddModList IE the UE shall: l>if the UE's current configuration contains an RLC bearer with the received losicalChannelldentit /LosicalChannelldentit Ext within the same cell group:
NOTE X: This case does not apply when this procedure is initiated due to the generation of an LTM candidate cell configuration.
2> if the RLC bearer is associated with an DAPS bearer, or 2> if any DAPS bearer is configured and the RLC bearer is associated with an SRB:
3> reconfigure the RLC entity or entities for the target cell group in accordance with the received rlc-Config-,
3> reconfigure the logical channel for the target cell group in accordance with the received mac-LogicalChannel Config ;
2>else:
3> if reestablishRLC is received:
4> re-establish the RLC entity as specified in TS 38.322 [4];
3>reconfigure the RLC entity or entities in accordance with the received rlc-Config-, 3> reconfigure the logical channel in accordance with the received mac- LogicalChannelConfig;
3> if servedMBS-RadioBearer is received:
4> associate this logical channel with the PDCP entity identified by servedMBS- RadioBearer,
NOTE 1: For DRB and SRB, the network does not re-associate an already configured logical channel with another radio bearer. Hence, servedRadioBearer is not present in this case. For MRB, the network does not re-associate an already configured logical channel with DRB or SRB or another MRB (i.e. MRB with another PDCP entity). Hence multicastRLC-BearerConfig is not present in this case.
NOTE 2: In DAPS handover, the UE may perform RLC entity re-establishment (if reestablishRLC is set) for an RLC bearer associated with a non-DAPS bearer when indication of successful completion of random access towards target cell is received from lower layers as specified in TS 38.321 [3]. l>else if a logical channel with the given logicalChannelldentity/LogicalChannelldentityExt is not configured within the same cell group, including the case when full configuration option is used:
2>if the servedRadioBearer associates the logical channel with an SRB and rlc-Config is not included:
3> establish an RLC entity in accordance with the default configuration defined in 9.2 for the corresponding SRB;
2>else:
3> establish an RLC entity in accordance with the received rlc-Config-,
2>if the servedRadioBearer associates the logical channel with an SRB and if mac- LogicalChannelConfig is not included:
3> configure this MAC entity with a logical channel in accordance to the default configuration defined in 9.2 for the corresponding SRB;
2>else:
3> configure this MAC entity with a logical channel in accordance to the received mac- LogicalChamelConfig;
2> associate this logical channel with the PDCP entity identified by servedRadioBearer or servedMBS-RadioBearer.
53.5.5.5 MAC entity configuration
The UE shall:
1> if SCG MAC is not part of the current UE configuration (i.e. SCG establishment):
2> create an SCG MAC entity; l>if any DAPS bearer is configured:
2> reconfigure the MAC main configuration for the target cell group in accordance with the received mac-CellGroupConfig excluding tag-ToReleaseList and tag-ToAddModList',
1> if this procedure is initiated due to the generation of a complete LTM candidate cell configuration:
2> create a MAC entity for the LTM candidate cell configuration for which a complete configuration needs to be generated excluding tag-ToReleaseList and tag-ToAddModList', l>else:
2> reconfigure the MAC main configuration of the cell group in accordance with the received mac-CellGroupConfig excluding tag-ToReleaseList and tag-ToAddModList',
1> if the received mac-CellGroupConfig includes the tag-ToReleaseList:
2>for each TAG-Id value included in the tag-ToReleaseList that is part of the current UE configuration:
3>release the TAG indicated by TAG-Id',
1> if the received mac-CellGroupConfig includes the tag-ToAddModList:
2>for each tag-id value included in tag-ToAddModList that is not part of the current UE configuration (TAG addition):
3>add the TAG, corresponding to the tag-id, in accordance with the received timeAlignmentTimer;
2>for each tag-id value included in tag-ToAddModList that is part of the current UE configuration (TAG modification): 3> reconfigure the TAG, corresponding to the tag-id, in accordance with the received timeAlignmentTimer.
5.3.5.5.6 RLF Timers & Constants configuration
The UE shall:
1> if the received rlf-TimersAndConstants is set to release'.
2>if any DAPS bearer is configured:
3>use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in ue-TimersAndConstants received in SIB I',
2>else:
3>use values for timers T301, T310, T311 and constants N310, N311, as included in ue- TimersAndConstants received in SIBI ; l>else:
2>if any DAPS bearer is configured:
3> configure the value of timers and constants for the target cell group in accordance with received rlf- T imersAndConstants ;
2>else:
3> (re- (configure the value of timers and constants in accordance with received rlf-
TimersAndConstants:
3> if this procedure is not initiated due to the generation of a complete LTM candidate cell configuration:
4>stop timer T310 for this cell group, if running:
4>stop timer T312 for this cell group, if running:
4> reset the counters N310 and N311.
5.3.5.5.7 SpCell Configuration
The UE shall: l>if the UE is acting as L2 U2N Remote UE:
2>if the SpCellConfig contains the rlf-TimersAndConstants which is set to setup:
3>use value for timers T311 as received in rlf-TimersAndConstants',
2>else if rlf-TimersAndConstants is not configured for this cell group or SpCellConfig contains the rlf-TimersAndConstants which is set to release:
3>use value for timers T311, as included in ue-TimersAndConstants received in SIBI', l>else
2> if the SpCellConfig contains the rlf-TimersAndConstants: 3>configure the RLF timers and constants for this cell group as specified in 5.3.5.5.6;
2>else if rlf-TimersAndConstants is not configured for this cell group:
3> if any DAPS bearer is configured:
4>use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in ue-TimersAndConstants received in SIBP,
3>else
4>use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1;
2> if the SpCellConfig contains spCellConfigDedicated'.
3> configure the SpCell in accordance with the spCellConfigDedicated',
3>consider the bandwidth part indicated in first ActiveUplinkBWP-Id, if included in the spCellConfigDedicated, to be the active uplink bandwidth part;
3> if the firstActiveDownlinkBWP-Id is included in the spCellConfigDedicated'.
4> if the SpCellConfig is included in an RRCReconfiguration message contained in an NR or E-UTRA RRC message indicating that the SCG is deactivated:
5> consider the bandwidth part indicated vafirstActiveDownlinkBWP-Id to be the bandwidth part for Radio Link Monitoring, Beam Failure Detection and measurements;
4> else:
5> consider the bandwith part indicated in firstActiveDownlinkBWP-Id to be the active downlink bandwidth part;
3> if any of the reference signal(s) that are used for radio link monitoring are reconfigured by the received spCellConfigDedicated'. and
1> if this procedure is not initiated due to the generation of a complete LTM candidate cell configuration:
4>stop timer T310 for the corresponding SpCell, if running;
4>stop timer T312 for the corresponding SpCell, if running;
4> reset the counters N310 and N311. > if the SpCellConfig contains the lowMobilityEvaluationConnected'.
2>the UE may perform the evaluation of the low mobility criterion for this cell group as specified in 5.7.13.1; > if the SpCellConfig contains the goodServingCellEvaluationRLM'.
2>the UE may perform the evaluation of the good serving cell quality criterion for this SpCell as specified in 5.7.13.2;
1> if the SpCellConfig contains the goodServingCellEvaluationBFD:
2>the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2;
5.3.5.5.8 SCell Release
The UE shall:
1> if the release is triggered by reception of the sCellToReleaseList:
2>for each sCelllndex value included in the sCellToReleaseList:
3> if the current UE configuration includes an SCell with value sCelllndex:
4> release the SCell.
Editor’s Note: FFS on whether the release of an SCell by an LTM candidate cell configuration is a valid case.
5.3.5.5.9 SCell Addition/Modification
The UE shall: l>for each sCelllndex value included in the sCellToAddModList that is not part of the current
UE configuration (SCell addition):
2> add the SCell, corresponding to the sCelllndex, in accordance with the sCellConfigCommon and sCellConfigDedicated',
2>if the sCellState is included:
3> configure lower layers to consider the SCell to be in activated state;
2>else:
3> configure lower layers to consider the SCell to be in deactivated state;
2>for each measld included in the measIdList within VarMeasConfig:
3> if SCells are not applicable for the associated measurement; and
3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measld: and
3> if this procedure is not initiated due to the generation of a complete LTM candidate cell configuration:
4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measld',
2> if the SCellConfig contains the goodServingCellEvaluationBFD:
3>the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2. l>for each sCelllndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):
NOTE X: This case does not apply when this procedure is initiated due to the generation of an LTM candidate cell configuration.
2> modify the SCell configuration in accordance with the sCellConfigDedicated',
2>if the sCellState is included:
3> configure lower layers to consider the SCell to be in activated state;
2>else:
3> configure lower layers to consider the SCell to be in deactivated state.
2> if the SCellConfig contains the goodServingCellEvaluationBFD'.
3>the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2.
5.3.5.6 Radio Bearer configuration
5.3.5.6.1 General
The UE shall perform the following actions based on a received RadioBearerConfig IE:
1> if the RadioBearerConfig includes the srb3-ToRelease or srb4-ToRelease'.
2> perform the SRB release as specified in 5.3.5.6.2;
1> if the RadioBearerConfig includes the srb-ToAddModList or if any DAPS bearer is configured:
2> perform the SRB addition or reconfiguration as specified in 5.3.5.6.3;
1> if the RadioBearerConfig includes the drb-ToReleaseList:
2> perform DRB release as specified in 5.3.5.6.4;
1> if the RadioBearerConfig includes the drb-ToAddModList:
2> perform DRB addition or reconfiguration as specified in 5.3.5.6.5;
1> if the RadioBearerConfig includes the mrb-ToReleaseList:
2> perform multicast MRB release as specified in 5.3.5.6.6;
1> if the RadioBearerConfig includes the mrb-ToAddModList:
2> perform multicast MRB addition or reconfiguration as specified in 5.3.5.6.7;
1> if this procedure is not initiated due to the generation of a complete LTM candidate cell configuration:
2> release all SDAP entities, if any, that have no associated DRB as specified in TS 37.324 [24] clause 5.1.2, and indicate the release of the user plane resources for PDU Sessions associated with the released SDAP entities to upper layers; l>release all SDAP entities that have no associated multicast MRB as specified in TS 37.324 [24] clause 5.1.2, and indicate the release of user plane resources for these MBS multicast sessions to upper layers.
5.3.5.6.2 SRB release
The UE shall: l>if srb3-ToRelease is included:
2> release the PDCP entity and the srb-Identity of the SRB 3; l>if srb4-ToRelease is included
2> release the PDCP entity and the srb-Identity of the SRB 4.
5.3.5.6.3 SRB addition/modification
The UE shall: l>If any DAPS bearer is configured, for each SRB:
2>establish a PDCP entity for the target cell group as specified in TS 38.323 [5], with the same configuration as the PDCP entity for the source cell group;
2>if the masterKeyUpdate is received:
3> configure the PDCP entity with the security algorithms according to securityConfig and apply the keys (KRRCenc and KRRCint) associated with the master key (KgNB);
2>else:
3> configure the PDCP entity for the target cell group with state variables continuation as specified in TS 38.323 [5], and with the same security configuration as the PDCP entity for the source cell group; l>for each srb-Identity value included in the srb-ToAddModList that is not part of the current UE configuration (SRB establishment or reconfiguration from E-UTRA PDCP to NR PDCP): 2> establish a PDCP entity;
2> if AS security has been activated:
3> if target RAT of handover is E-UTRA/5GC; or
3> if the UE is connected to E-UTRA/5GC:
4> if the UE is capable of E-UTRA/5GC, but not capable of NGEN-DC:
5> configure the PDCP entity with the security algorithms and keys (KRRCenc and KRRCint) configured/derived as specified in TS 36.331 [10];
4>else (i.e., UE capable of NGEN-DC):
5> configure the PDCP entity with the security algorithms according to securityConfig and apply the keys (KRRCenc and KRRCint) associated with the master key (KeNB) or secondary key (S-KgNB) as indicated in keyToUse, if applicable;
3>else (i.e., UE connected to NR or UE connected to E-UTRA/EPC):
4> configure the PDCP entity with the security algorithms according to securityConfig and apply the keys (KRRCenc and KRRCint) associated with the master key (KeNB/ KgNB) or secondary key (S-KgNB) as indicated in keyToUse, if applicable;
2>if the current UE configuration as configured by E-UTRA in TS 36.331 [10] includes an SRB identified with 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 the pdcp-Config is included:
3> configure the PDCP entity in accordance with the received pdcp-Config-,
2>else:
3> configure the PDCP entity in accordance with the default configuration defined in 9.2.1 for the corresponding SRB ;
1> if any DAPS bearer is configured, for each srb-Identity value included in the srb- ToAddModList that is part of the current UE configuration:
2>if the pdcp-Config is included:
3> reconfigure the PDCP entity for the target cell group in accordance with the received pdcp-Config-, l>else, for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration:
NOTE X: This case does not apply when this procedure is initiated due to the generation of an LTM candidate cell configuration.
2>if the reestablishPDCP is set:
3> if target RAT of handover is E-UTRA/5GC; or
3> if the UE is connected to E-UTRA/5GC:
4> if the UE is capable of E-UTRA/5GC, but not capable of NGEN-DC:
5> configure the PDCP entity to apply the integrity protection algorithm and KRRCint key configured/derived as specified in TS 36.331 [10], i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; 5> configure the PDCP entity to apply the ciphering algorithm and KRRCenc key configured/derived as specified in TS 36.331 [10], i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
4>else (i.e., a UE capable of NGEN-DC):
5> configure the PDCP entity to apply the integrity protection algorithm and KRRCint key associated with the master key (KeNB) or secondary key (S-KgNB), as indicated in keyToUse, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
5> configure the PDCP entity to apply the ciphering algorithm and KRRCenc key associated with the master key (KeNB) or secondary key (S-KgNB) as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
3>else (i.e., UE connected to NR or UE in EN-DC):
4> configure the PDCP entity to apply the integrity protection algorithm and KRRCint key associated with the master key (KeNB/KgNB) or secondary key (S-KgNB), as indicated in keyToUse , i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
4> configure the PDCP entity to apply the ciphering algorithm and KRRCenc key associated with the master key (KeNB/KgNB) or secondary key (S-KgNB) as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent 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>else, if the discardOnPDCP is set:
3>trigger the PDCP entity to perform SDU discard as specified in TS 38.323 [5];
2>if the pdcp-Config is included:
3>reconfigure the PDCP entity in accordance with the received pdcp-Config.
5.3.5.6.4 DRB release
The UE shall: l>for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuration; or l>for each drb-Identity value that is to be released as the result of full configuration according to 5.3.5.11:
2> release the PDCP entity and the drb-Identity,
2> if SDAP entity associated with this DRB is configured:
3> indicate the release of the DRB to SDAP entity associated with this DRB (TS 37.324 [24], clause 5.3.3);
2>if the DRB is associated with an eps-Bearerldentity.
3> if a new bearer is not added either with NR or E-UTRA with same eps-Bearerldentity.
4> indicate the release of the DRB and the eps-Bearerldentity of the released DRB to upper layers.
NOTE 1: The UE does not consider the message as erroneous if the drb-ToReleaseList includes any drb-Identity value that is not part of the current UE configuration.
NOTE 2: Whether or not the RLC and MAC entities associated with this PDCP entity are reset or released is determined by the CellGroupConfig.
5.3.5.6.5 DRB addition/modification
The UE shall: l>for each drb-Identity value included in the drb-ToAddModList that is not part of the current
UE configuration (DRB establishment including the case when full configuration option is used):
2> if this procedure is not initiated due to the generation of a complete LTM candidate cell configuration:
3> establish a PDCP entity and configure it in accordance with the received pdcp-Config;
2> if the PDCP entity of this DRB is not configured with cipheringDisabled:
3> if target RAT of handover is E-UTRA/5GC; or
3> if the UE is connected to E-UTRA/5GC:
4> if the UE is capable of E-UTRA/5GC but not capable of NGEN-DC:
5> configure the PDCP entity with the ciphering algorithm and KUPenc key configured/derived as specified in TS 36.331 [10];
4>else (i.e., a UE capable of NGEN-DC):
5> configure the PDCP entity with the ciphering algorithms according to securityConfig and apply the key (KUPenc) associated with the master key (KeNB) or secondary key (S-KgNB) as indicated in keyToUse, if applicable;
3>else (i.e., UE connected to NR or UE connected to E-UTRA/EPC):
4> configure the PDCP entity with the ciphering algorithms according to securityConfig and apply the KUPenc key associated with the master key (KeNB/KgNB) or the secondary key (S-KgNB/S-KeNB) as indicated in keyToUse;
2> if the PDCP entity of this DRB is configured with integrity Protection-.
3> configure the PDCP entity with the integrity protection algorithms according to securityConfig and apply the Kupint key associated with the master (KeNB/KgNB) or the secondary key (S-KgNB) as indicated in keyToUse-,
2>if an sdap-Config is included:
3> if an SDAP entity with the received pdu-Session does not exist:
4>establish an SDAP entity as specified in TS 37.324 [24] clause 5.1.1;
4> if an SDAP entity with the received pdu-Session did not exist prior to receiving this reconfiguration:
5> indicate the establishment of the user plane resources for the pdu-Session to upper layers;
3> configure the SDAP entity in accordance with 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 in mappedQoS-FlowsToAdd, if the QFI value is previously configured, the QFI value is released from the old DRB ;
2>if the DRB is associated with an eps-Bearerldentity.
3> if the DRB was configured with the same eps-Bearerldentity either by NR or E-UTRA prior to receiving this reconfiguration:
4> associate the established DRB with the corresponding eps-Bearerldentity;
3>else:
4> indicate the establishment of the DRB(s) and the eps-Bearerldentity of the established DRB(s) to upper layers; l>for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration and configured as DAPS bearer:
NOTE X: This case does not apply when this procedure is initiated due to the generation of an LTM candidate cell configuration.
2> reconfigure the PDCP entity to configure DAPS with the ciphering function, integrity protection function and ROHC function of the target cell group as specified in TS 38.323 [5] and configure it in accordance with the received pdcp-Config;
2>if the masterKeyUpdate is received:
3> if the ciphering function of the target cell group PDCP entity is not configured with cipheringDisabled:
4> configure the ciphering function of the target cell group PDCP entity with the ciphering algorithm according to securityConfig and apply the KUPenc key associated with the master key (KgNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received from the target cell group 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 with integrityProtection:
4> configure the integrity protection function of the target cell group PDCP entity with the integrity protection algorithms according to securityConfig and apply the Kupint key associated with the master key (KgNB) as indicated in keyToUse'.
2>else:
3> configure the ciphering function and the integrity protection function of the target cell group PDCP entity with the same security configuration as the PDCP entity for the source cell group;
2> if the sdap-Config is included and when indication of successful completion of random access towards target cell is received from lower layers as specified in [3]: 3>reconfigure the SDAP entity in accordance with the received sdap-Config as specified in TS 37.324 [24];
3>for each QFI value added in mappedQoS-FlowsToAdd, if the QFI value is previously configured, the QFI value is released from the old DRB ; l>for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration and not configured as DAPS bearer:
2>if the reestablishPDCP is set:
3> if target RAT of handover is E-UTRA/5GC; or
3> if the UE is connected to E-UTRA/5GC:
4> if the UE is capable of E-UTRA/5GC but not capable of NGEN-DC:
5> if the PDCP entity of this DRB is not configured with cipheringDisabled:
6> configure the PDCP entity with the ciphering algorithm and KUPenc key configured/derived as specified in TS 36.331 [10], clause 5.4.2.3, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;
4>else (i.e., a UE capable of NGEN-DC):
5> if the PDCP entity of this DRB is not configured with cipheringDisabled'.
6> configure the PDCP entity with the ciphering algorithm and KUPenc key associated with the master key (KeNB) or the secondary key (S-KgNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;
3>else (i.e., UE connected to NR or UE connected to E-UTRA/EPC (in EN-DC or capable of EN-DQ):
4> if the PDCP entity of this DRB is not configured with cipheringDisabled:
5> configure the PDCP entity with the ciphering algorithm and KUPenc key associated with the master key (KeNB/ KgNB) or the secondary key (S-KgNB/S-KeNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;
4> if the PDCP entity of this DRB is configured with integrity Protection'.
5> configure the PDCP entity with the integrity protection algorithms according to securityConfig and apply the Kupint key associated with the master key (KeNB/KgNB) or the secondary key (S-KgNB) as indicated in keyToUse',
3> if drb-ContinueROHC is included in pdcp-Config'.
4> indicate to lower layer that drb-ContinueROHC is configured;
3> if drb-ContinueEHC-DL is included in pdcp-Config'.
4> indicate to lower layer that drb-ContinueEHC-DL is configured;
3> if drb-ContinueEHC-UL is included in pdcp-Config'.
4> indicate to lower layer that drb-ContinueEHC-UL is configured;
3> if drb-ContinueUDC is included in pdcp-Config'.
4> indicate to lower layer that drb-ContinueUDC is configured;
3> re-establish the PDCP entity of this DRB as specified in TS 38.323 [5], clause 5.1.2; >else, if the recoverPDCP is set:
3>trigger the PDCP entity of this DRB to perform data recovery as specified in TS 38.323 [5]; >if the pdcp-Config is included:
3>reconfigure the PDCP entity in accordance with the received pdcp-Config. 2>if the sdap-Config is included:
3>reconfigure the SDAP entity in accordance with the received sdap-Config as specified in TS37.324 [24];
3>for each QFI value added in mappedQoS-FlowsToAdd, if the QFI value is previously configured, the QFI value is released from the old DRB ;
N0TE 1: Void.
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 that DRB was originally configured in. To re-associate 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 in the (target) drb-ToAddModList and sets the reestablishPDCP flag. The network does not list the drb-Identity in the (source) drb- ToReleaseList.
NOTE 3: When setting the reestablishPDCP flag for a radio bearer, the network ensures that the RLC receiver entities do not deliver old PDCP PDUs to the re-established PDCP entity. It does that e.g. by triggering a reconfiguration with sync of the cell group hosting the old RLC entity or by releasing the old RLC entity.
NOTE 4: In this specification, UE configuration refers to the parameters configured by NR
RRC unless otherwise stated.
NOTE 5: Ciphering and integrity protection can be enabled or disabled for a DRB. The enabling/disabling of ciphering or integrity protection can be changed only by releasing and adding the DRB.
NOTE 6: In DAPS handover, the UE may perform PDCP entity re-establishment (if reestablishPDCP is set) or the PDCP data recovery (if recoverPDCP is set) for a non- DAPS bearer when indication of successful completion of random access towards target cell is received from lower layers as specified in TS 38.321 [3]. In this case, the UE suspends data transmission and reception for all non-DAPS bearers in the source MCG for duration of the DAPS handover.
5.3.5.x LTM configuration and execution
5.3.5.x.1 General
The UE shall perform the following actions based on a received LTM-CandidateConfig IE: 1> store the received Itm-ReferenceConfiguration in VarLTM-Config, if present; 1> if the LTM-CandidateConfig includes the Itm-CandidateToReleaseList:
2> perform the LTM candidate cell release as specified in 5.3.5.X.2;
1> if the LTM-CandidateConfig includes the ltm-CandidateResetL2-List:
2>add the received ltm-CandidateResetL2-List to VarLTM-Config;
1> if the LTM-CandidateConfig includes the Itm-CandidateToAddModList:
2> perform the LTM candidate cell addition or reconfiguration as specified in 5.3.5.X.3;
1> perform the actions to generate a complete LTM configuration as specified in 5.3.5.X.4;
NOTE X: It is up to the UE implementation to postpone the generation of a complete LTM configuration until the executing of an LTM cell switch.
Editor’s Note: FFS on whether the UE performs the compliance check of the reference and LTM candidate cell configuration upon their reception of upon the execution of the LTM cell switch.
Editor’s Note: FFS on how and whether to indicate that no RACH is needed for an LTM candidate cell.
Editor’s Note: FFS on how UE should establish the TA for a LTM candidate cell.
5.3.5.X.2 LTM candidate cell release
The UE shall: l>for each Itm-Candidateld in the Itm-CandidateToReleaseList:
2>if the current VarLTM-Config includes an Itm-Candidate with the given Itm-Candidateld'. 3>release the Itm-Candidate from VarLTM-Config;
5.3.5.X.3 LTM candidate cell addition/modification
The UE shall: l>for each Itm-Candidateld in the Itm-CandidateToAddModList:
2>if the current VarLTM-Config includes an Itm-Candidate with the given Itm-Candidateld-.
3> modify the Itm-Candidate within VarLTM-Config in accordance with the received Itm- Candidate-,
2>else:
3>add the received Itm-Candidate to VarLTM-Config.
5.3.5.X.4 Generation of UE LTM configuration
The purpose of this procedure is for the UE to generate a complete LTM candidate cell configuration to be stored and applied only when an indication of an LTM cell switch is received by lower layers. During the generation of a complete LTM candidate cell configuration, the current UE configuration is not modified. The UE shall:
1> for each Itm-Candidate in Itm-CandidateConfigList within VarLTM-Config;
2> store the Itm-Candidateld included in Itm-Candidate within VarLTM-UE-Config;
2> if Itm-Candidate includes Itm-ConfigComplete;
3> generate a complete LTM candidate cell configuration for the received Itm-Candidate according to the actions described in clause 5.3.5.3 and store it in ue-LTM-Config within VarLTM-UE-Config.
2> else:
3> generate a complete LTM candidate cell configuration by applying Itm-Candidate on top of referenceconfiguration according to the actions described in clause 5.3.5.3 and store it in ue-LTM-Config within VarLTM-UE-Config.
Editor’s Note: FFS on the need of Itm-ConfigComplete to indicate to the UE that the LTM candidate cell configuration in Itm-Candidate is a full configuration.
Editor’s Note: FFS on whether we need to rely on the full configuration procedure or a new procedure for LTM is created when the UE generates a complete LTM candidate cell configuration.
5.3.5.X.5 LTM cell switch execution
Upon the indication by lower layers that an LTM cell switch procedure is triggered, the UE shall:
1> release/clear all current dedicated radio configuration except for the following:
2> if the LTM cell switch is triggered on the MCG:
- the MCG C-RNTI;
- the AS security configurations associated with the master key;
2> else, if the LTM cell switch is triggered on the SCG:
- the SCG C-RNTI;
- the AS security configurations associated with the secondary key;
- the SRB1/SRB2 configurations and DRB configurations as configured by radioBearerConfig or radioBearerConfig2;
Editor’s Note: FFS on whether the radio bearer needs to be kept when execution the LTM cell switch.
- the UE variables VarLTM-Config and VarLTM-UE-Config.
1> release/clear all current common radio configuration;
1> use the default values specified in 9.2.3 for timers T310, T311 and constants N310, N311;
1> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the following:
- parameters for which values are provided in SIB1;
1> apply the value of the newUE-Identity as the C-RNTI for this cell group according to the LTM candidate cell configuration related to the the LTM candidate cell configuration identity as received by lower layers;
1> configure lower layers in accordance with the received spCellConfigCommon according to the LTM candidate cell configuration indicated by lower layers; l>configure lower layers in accordance with the received rach-ConfigDedicated according to the LTM candidate cell configuration indicated by lower layers.
1> apply the default MAC Cell Group configuration as specified in 9.2.2;
1> configure the PDCP entity for LTM candidate cell configuration indicated by lower layers with state variables continuation as specified in TS 38.323 [5], and with the same security configuration as the PDCP entity for the source cell group; l>stop timer T310 for the corresponding SpCell, if running;
1> if this procedure is executed for the MCG:
2>if timer T316 is running;
3>stop timer T316; l>stop timer T312 for the corresponding SpCell, if running;
1> apply the specified BCCH configuration defined in 9.1.1.1 for the target SpCell;
1> acquire the MIB of the target SpCell as indicated in the LTM candidate cell configuration indicated by lower layers, which is scheduled as specified in TS 38.213 [13], if applicable;
1> apply the LTM configuration in UE-LTM-Config within VarLTM-UE-Config related to the LTM candidate cell configuration identity as received by lower layers.
1> submit the RRCReconfigurationComplete message lower layers for transmission using the new configuration.
Editor’s Note: FFS on whether the sending of the RRCReconfigurationComplete message should be triggered in this section or in section 5.3.5.3 (i.e., Reception of an RRCReconfiguration by the UE).
Editor’s Note: FFS on whether further UE actions need to be specified for e.g., subsequent LTM cell switch or interaction with lower layers.
Editor’s Note: FFS on the UE actions (for no L2 reset) based on ltm-CandidateNoResetL2-List.
Editor’s Note: FFS on how and whether to indicate that no RACH is needed for an LTM candidate cell. Editor’s Note: FFS on how to handle the TA (and when the UE has no TA) in the source cell (in case no RACH is performed) upon an LTM cell switch and whether this should be specified in RRC or MAC.
Editor’s Note: FFS on the supervision timer for the LTM cell switch.
Editor’s Note: FFS on how to provide the UL grant to the UE in case no RACH is performed during the LTM cell switch.
6.2 RRC messages
6.2.2 Message definitions
- RRCReconfiguration
The RRCReconfiguration message is the command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC main configuration and physical channel configuration) and AS security configuration.
Signalling radio bearer: SRB1 or SRB3
RLC-SAP: AM
Logical channel: DCCH
Direction: Network to UE
RRCReconfiguration message
- ASN1 START
- TAG-RRCRECONFIGURATION-START
RRCReconfiguration ::= SEQUENCE { rrc-Transactionldentifier RRC-Transactionldentifier, 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-v 1530-Ies
OPTIONAL }
RRCReconfiguration-vl530-Ies ::= SEQUENCE { masterCellGroup OCTET STRING (CONTAINING CellGroupConfig)
OPTIONAL, - Need M fullConfig ENUMERATED {true}
OPTIONAL, - Cond FullConfig dedicatedNAS-MessageList SEQUENCE (SIZE(L.maxDRB)) OF DedicatedNAS-
Message OPTIONAL, — Cond nonHO masterKeyUpdate MasterKeyUpdate
OPTIONAL, — Cond MasterKeyChange dedicatedSIB 1 -Delivery OCTET STRING (CONTAINING SIB 1 )
OPTIONAL, - Need N dedicatedSystemlnformationDelivery OCTET STRING (CONTAINING Systeminformation) OPTIONAL, - Need N otherConfig OtherConfig OPTIONAL, —
Need M nonCriticalExtension RRCReconfiguration-v 1540-Ies
OPTIONAL }
RRCReconfiguration-v 1540-Ies ::= SEQUENCE { otherConfig-v 1540 OtherConfig-v 1540
OPTIONAL, - Need M nonCriticalExtension RRCReconfiguration-v 1560-Ies
OPTIONAL }
RRCReconfiguration-vl560-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- v 1610-Ies
OPTIONAL } RRCReconfiguration-vl610-Ies ::= SEQUENCE { otherConfig- v 1610 OtherConfig- v 1610
OPTIONAL, - Need M bap-Config-r16 SetupRelease { BAP-Config-r16 }
OPTIONAL, - Need M iab-IP-AddressConfigurationList-r16 IAB-IP-AddressConfigurationList-r16
OPTIONAL, - Need M conditionalReconfigur ation-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-v 1700-Ies
OPTIONAL } RRCReconfiguration-vl700-Ies ::= SEQUENCE { otherConfig- v 1700 QtherConfig-vl700 OPTIONAL, -
Need M sl-L2RelayUE-Config-r 17 SetupRelease { SL-L2RelayUE-Config-r17 }
OPTIONAL, - Need M sl-L2RemoteUE-Config-r 17 SetupRelease { SL-L2RemoteUE-Config-r17 }
OPTIONAL, - Need M dedicatedPagingDelivery-r 17 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-r 17 SetupRelease { MUSIM-GapConfig-r17 }
OPTIONAL, - Need M ul-GapFR2-Config-r 17 SetupRelease { UL-GapFR2-Config-r17 }
OPTIONAL, - Need M scg-State-r17 ENUMERATED { deactivated }
OPTIONAL, - Need N appLayerMeasConfig-r 17 AppLayerMeasConfig-r 17
OPTIONAL, - Need M ue-TxTEG-RequestUL-TDOA-Config-r17 SetupRelease {UE-TxTEG-RequestUL-TDOA-
Config-r17} OPTIONAL, - Need M nonCriticalExtension RRCReconfiguration-v 18xy
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-B AP-RoutingID-r16 BAP-RoutingID-r16
OPTIONAL, - Need M defaultUL-BH-RLC-Channel-r16 BH-RLC-ChannelID-r16
OPTIONAL, - Need M
HowControlFeedbackT ype-r16 ENUMERATED {perBH-RLC-Channel, perRoutingID, both } OPTIONAL, - Need R
MasterKeyUpdate : := SEQUENCE { keySetChangelndicator BOOLEAN, nextHopChainingCount NextHopChainingCount, nas-Container OCTET STRING OPTIONAL, -
Cond securityNASC
}
OnDemandSIB-Request-r16 ::= SEQUENCE { onDemandSIB-RequestProhibitTimer-r16 ENUMERATED {sO, sOdot5, si, s2, s5, slO, s20, s30} }
T316-r16 ::= ENUMERATED {ms50, mslOO, ms200, ms300, ms400, ms500, ms600, mslOOO, ms 1500, ms2000}
IAB-IP-AddressConfigurationList-r16 ::= SEQUENCE { iab-IP-AddressToAddModList-r16 SEQUENCE (SIZE(l..maxIAB-IP-Address-r16)) OF
IAB-IP-AddressConfiguration-r16 OPTIONAL, — Need N iab-IP-AddressToReleaseList-r16 SEQUENCE (SIZE(l..maxIAB-IP-Address-r16)) OF IAB-
IP-AddressIndex-r16 OPTIONAL, — Need N
}
IAB-IP-AddressConfiguration-r16 ::= SEQUENCE { iab-IP- Addresslndex-r16 IAB -IP- Addresslndex-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(IO)) 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 {msO, ms0dot25, ms0dot5, ms0dot625, ms0dot75, msl, msldot25, msldot5, msldot75, ms2, ms2dot5, ms3, ms4, ms5, ms6, ms8, mslO, ms20}
UE-TxTEG-RequestUL-TDOA-Config-r17 ::= CHOICE { oneShot-r17 NULL, periodicReporting-r17 ENUMERATED { msl60, ms320, msl280, ms2560, ms61440, ms81920, ms368640, ms737280 } }
- TAG-RRCRECONFIGURATION-STOP
- ASN1STOP
6.3 RRC information elements
6.3.2 Radio resource control information elements
- LTM-CandidateConfig
The IE LTM-CandidateConfig is used to provide LTM candidate cell configuration.
LTM-CandidateConfig information element
- ASN1 START
- TAG-LTM-CANDIDATECONFIG-START - ASN1STOP
6.4 RRC multiplicity and type constraint values
- Multiplicity and type constraint definitions
- ASN1 START
- TAG-MULTIPLICITY-AND-TYPE-CONSTRAINT-DEFINITIONS-START max AdditionalR ACH-r 17 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 maxB andsUTRA-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 maxB T -IdReport-r16 INTEGER :: = 32 — Maximum number of Bluetooth IDs to report maxBT-Name-r16 INTEGER : := 4 — Maximum number of Bluetooth name maxC AG-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-l-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 maxCelllnter INTEGER ::= 16 — Maximum number of inter-Freq cells listed in
SIB4 maxCelllntra 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 maxCarrierT ypePairList-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 SIB 5 maxEUTR A-N S -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 maxFreqldle-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 I AB -DU maxNrofAppLayerMeas-r17 INTEGER ::= 16 — Max number of simultaneous application layer measurements maxNrofAppLayerMeas-l-r17 INTEGER ::= 15 — Max number of simultaneous application layer measurements minus 1 maxNrofAvailabilityCombinationsPerSet-r16 INTEGER ::= 512 — Max number of AvailabilityCombinationld used in the DCI format 2_5 maxNrofAvailabilityCombinationsPerSet-l-r16 INTEGER ::= 511 — Max number of AvailabilityCombinationld used in the DCI format 2_5 minus 1 maxNrofIABResourceConfig-r17 INTEGER ::= 65536 — Max number of IAB- ResourceConfiglD used in MAC CE maxNrofIABResourceConfig-l-r17 INTEGER ::= 65535 — Max number of IAB- ResourceConfiglD 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-l-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-l-r17 INTEGER ::= 7 — Max number of conditional candidate
SpCells minus 1 maxNrofCSI-RS-ResourcesToA verage 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-r 17 INTEGER :: = 64 — Maximum number of PDSCH time domain resource allocations for multi-PDSCH
— scheduling maxNrofPDU-Sessions-r 17 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-r!7 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 B WPs per serving cell maxNrofComblDC 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 maxNrofPhysicalResourceBlocksPlusl 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 -r 17 INTEGER ::= 39 — Max number of Search Space links minus 1 maxNrofB FDResourcePerSet-r 17 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 maxi AB -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-l-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-Objectld-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 maxNrofObj ectld 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-l-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) maxSimultaneousB ands 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-PO-PerSet INTEGER ::= 8 — Maximum number of PO-pucch present in a pO-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-l-r16 INTEGER ::= 63 — Maximum number of RSs used as pathloss reference for PUCCH power control
— minus 1 extended. maxNrofPUCCH-PathlossReferenceRSs-l-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 maxNrofPO-PUSCH- AlphaSets INTEGER ::= 30 — Maximum number of PO-pusch- alpha-sets (see TS 38.213 [13], clause 7.1) maxNrofPO-PUSCH- AlphaSets- 1 INTEGER ::= 29 — Maximum number of PO-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-l-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-l-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. maxB andsMRDC INTEGER ::= 1280 maxB andsEUTR A 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. maxFreqPlusl INTEGER ::= 9 — Max number of frequencies for Slicing. maxFreqIDC-r16 INTEGER ::= 128 — Max number of frequencies for IDC indication. maxComblDC-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 maxNrofSpatialRelationlnfos INTEGER ::= 8 maxNrofSpatialRelationlnfos-plus-l INTEGER ::= 9 maxNrofSpatialRelationlnfos-r16 INTEGER :: = 64 maxNrofSpatialRelationlnfosDiff-r16 INTEGER ::= 56 — Difference between maxNrofSpatialRelationInfos-r16 and maxNrofSpatialRelationlnfos maxNroflndexesToReport INTEGER ::= 32 maxNrof!ndexesToReport2 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-r!7 INTEGER ::= 64 — Maximum number of TCI states. maxUL-TCI-l-r!7 INTEGER ::= 63 — Maximum number of TCI states minus 1. maxNrof AdditionalPCI-r 17 INTEGER ::= 7 — Maximum number of additional PCI maxMPE-Resources-r 17 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 maxMB SFN -Allocations INTEGER ::= 8 maxNrofMultiB ands INTEGER :- 8 maxCellSFTD INTEGER ::= 3 — Maximum number of cells for SFTD reporting maxReportConfigld 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 fetype2Rl 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-l-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 SIB s maxSI-Message INTEGER: — 32 — Maximum number of SI messages maxSIB -MessagePlusl-r 17 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 maxB arringlnfoSet 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 maxKO-SchedulingOffset-r16 INTEGER ::= 16 — Maximum number of slots configured as min. scheduling offset (KO) maxK2-SchedulingOffset-r16 INTEGER ::= 16 — Maximum number of slots configured as min. scheduling offset (K2) maxKO-SchedulingOffset-r17 INTEGER ::= 64 — Maximum number of slots configured as min. scheduling offset (KO) 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 DO format 2-6 maxDCI-2-7-Size-r 17 INTEGER ::= 43 — Maximum size of DO format 2-7 maxDCI-2-6-Size- 1 -r16 INTEGER ::= 139 — Maximum DO 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 PO 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 DO size for CI maxCI-DCI-PayloadSize- 1 -r16 INTEGER ::= 125 — Maximum number of the DO 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 max WLAN -N ame -r16 INTEGER ::= 4 — Maximum number of WLAN name maxR AReport-r16 INTEGER ::= 8 — Maximum number of RA procedures information to be included in the RA report maxT xConfig-r16 INTEGER ::= 64 — Maximum number of sidelink transmission parameters configurations maxT xConfig- 1 -r16 INTEGER ::= 63 — Maximum number of sidelink transmission parameters configurations minus 1 maxPS SCH-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-r 17 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-l-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-r 17 INTEGER : := 4 — Maximum number of Preconfigured
PRS processing windows per DL BWP maxNrofPPW-ID-l-r17 INTEGER ::= 15 — Maximum number of Preconfigured
PRS processing windows minus 1 maxNrOfTxTEGReport-r 17 INTEGER ::= 256 — Maximum number of UE Tx Timing Error Group Report maxNrOfTxTEG-ID - 1 -r 17 INTEGER ::= 7 — Maximum number of UE Tx Timing
Error Group ID minus 1 maxNrofDormancyGroups INTEGER ::= 5 maxNrofPagingSubgroups-r 17 INTEGER ::= 8 — Maximum number of paging subgroups per paging occasion maxNrofPUCCH-ResourceGroups-l-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 maxNrofl xDC-T woCarrier-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 -r 17 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-Resources PerSet- 1 -r 17 INTEGER ::= 63 — Maximum number of PRS resources for one set minus 1 maxNrofPRS-ResourceOffsetValue-l-r17 INTEGER ::= 511 maxNrofGapId-r 17 INTEGER ::= 8 — Maximum number of measurement gap ID is FFS maxNrofPreConfigPosGapId-r 17 INTEGER ::= 16 — Maximum number of preconfigured positioning measurement gap maxNrOfGapPri-r 17 INTEGER ::= 16 — Maximum number of gap priority level maxCEFReport-r 17 INTEGER ::= 4 — Maximum number of CEF reports by the
UE maxNrofMultiplePDSCHs-r17 INTEGER ::= 8 — Maximum number of PDSCHs in
PDSCH TDRA list maxSlicelnfo-r 17 INTEGER ::= 8 — Maximum number of NS AGs maxCellSlice-r 17 INTEGER ::= 16 — Maximum number of cells supporting the
NSAG maxNrofTRS-ResourceSets-r17 INTEGER ::= 64 — Maximum number of TRS resource maxNrofSearchSpaceGroups-l-r17 INTEGER : := 2 — Maximum number of search space groups minus 1 maxNrofRemoteUE-r 17 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 MBSInterestlndication maxNrofDRX-ConfigPTM-r 17 INTEGER ::= 64 — Max number of DRX configuration for PTM provided in MBS broadcast in a
— cell maxNrofDRX-ConfigPTM-l-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-l-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-l-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-l-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-l-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-l-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
— capabilities maxNrofCellsLTM-r 18 _ INTEGER : := 99999 — Maximum number of LTM candidate cells
- TAG-MULTIPLICITY-AND-TYPE-CONSTRAINT-DEFINITIONS-STOP
- ASN1STOP
Editor's note: maxKO-SchedulingOffset and maxKO-SchedulingOffset need confirmation by RAN1.
7.4 UE variables
- VarLTM-Config
The IE VarLTM-Config is used to store the reference configuration and the LTM candidate cell configurations. VarLTM-Config UE variable
- ASN1 START
- TAG-VARLTM-CONFIG-START
VarLTM-Config-rl8-IEs ::= SEQUENCE { ltm-ReferenceConfiguration-rl8 OCTET STRING (CONTAINING RRCReconfiguration),
Itm-CandidateList-r 18 LTM-CandidateList-r 18 ltm-CandidateResetL2-List-r 18 LTM-CandidateResetL2-List-r 18
}
LTM-CandidateList-r 18 ::= SEQUENCE (SIZE (l..maxNrofCellsLTM-rl8)) OF LTM-Candidate- rl8
LTM-CandidateResetL2-List-rl8 ::= SEQUENCE (SIZE (l..maxNrofCellsLTM-rl8)) OF LTM- Candidate-rl8
- TAG-VARLTM-CONFIG-STOP
- ASN1STOP
VarLTM-UE-Config
The IE VarLTM-UE-Config is used to store the generated UE configuration related to the received LTM candidate cell configurations.
VarLTM-UE-Config UE variable
- ASN1 START
- TAG-VARLTM-CONFIG-START
VarLTM-UE-Config-rl8-IEs ::= SEQUENCE {
Ue-ltm-ConfigCandidateList-r 18 UE-LTM-ConfigCandidateList-r 18
}
UE-LTM-ConfigCandidateList-rl8 ::= SEQUENCE (SIZE (L.maxNrofCellsLTM-rl8)) OF UE- LTM-Config-r 18
UE-LTM-Candidate-rl8 ::= SEQUENCE {
Itm-Candidateld-r 18 LTM-Candidateld-r 18, ue-LTM-Config-rl8 OCTET STRING,
}
- TAG-VARLTM-CONFIG-STOP
- ASN1STOP
[0124] Figure 7 shows an example of a communication system 700 in accordance with some embodiments.
[0125] In the example, the communication system 700 includes a telecommunication network 702 that 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 be generally referred to as network nodes 710), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 702 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 702 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 702, including one or more network nodes 710 and/or core network nodes 708.
[0126] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies. The network nodes 710 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 712a, 712b, 712c, and 712d (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections.
[0127] Example wireless communications over 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 conveying information without the use of wires, cables, or other material conductors. Moreover, in different 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 may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 700 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [0128] The UEs 712 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 710 and other communication devices. Similarly, the network nodes 710 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 712 and/or with other network nodes or equipment in the telecommunication network 702 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 702.
[0129] In the depicted example, the core network 706 connects the network nodes 710 to one or more hosts, such as host 716. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 706 includes one more core network nodes (e.g., core network node 708) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 708. Example core network nodes include functions of one or more of a 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 De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
[0130] The host 716 may be under the ownership or control of a service provider other than an operator or provider of the access network 704 and/or the telecommunication network 702, and may be operated by the service provider or on behalf of the service provider. The host 716 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
[0131] As a whole, the communication system 700 of Figure 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Fong Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
[0132] In some examples, the telecommunication network 702 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 702. For example, the telecommunications network 702 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.
[0133] In some examples, the UEs 712 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 704. Additionally, a UE may be configured for operating in single- or multi-RAT or multi- standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
[0134] In the example, the hub 714 communicates with the access network 704 to facilitate indirect communication between one or more UEs (e.g., UE 712c and/or 712d) and network nodes (e.g., network node 710b). In some examples, the hub 714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 714 may be a broadband router enabling access to the core network 706 for the UEs. As another example, the hub 714 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 710, or by executable code, script, process, or other instructions in the hub 714. As another example, the hub 714 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 714 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 714 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 714 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0135] The hub 714 may have a constant/persistent or intermittent connection to the network node 710b. The hub 714 may also allow for a different communication scheme and/or schedule between the hub 714 and UEs (e.g., UE 712c and/or 712d), and between the hub 714 and the core network 706. In other examples, the hub 714 is connected to the core network 706 and/or one or more UEs via a wired connection. Moreover, the hub 714 may be configured to connect to an M2M service provider over the access network 704 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 710 while still connected via the hub 714 via a wired or wireless connection. In some embodiments, the hub 714 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 710b. In other embodiments, the hub 714 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 710b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
[0136] Figure 8 shows a UE 800 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
[0137] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0138] The UE 800 includes processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a power source 808, a memory 810, a communication interface 812, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 8. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0139] The processing circuitry 802 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 810. The processing circuitry 802 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 802 may include multiple central processing units (CPUs).
[0140] In the example, the input/output interface 806 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 800. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
[0141] In some embodiments, the power source 808 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 808 may further include power circuitry for delivering power from the power source 808 itself, and/or an external power source, to the various parts of the UE 800 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 808. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 808 to make the power suitable for the respective components of the UE 800 to which power is supplied.
[0142] The memory 810 may be or be configured to include memory such as 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, flash drives, and so forth. In one example, the memory 810 includes one or more application programs 814, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 816. The memory 810 may store, for use by the UE 800, any of a variety of various operating systems or combinations of operating systems. [0143] The memory 810 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or IS IM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 810 may allow the UE 800 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 810, which may be or comprise a device- readable storage medium.
[0144] The processing circuitry 802 may be configured to communicate with an access network or other network using the communication interface 812. The communication interface 812 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 822. The communication interface 812 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 818 and/or a receiver 820 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 818 and receiver 820 may be coupled to one or more antennas (e.g., antenna 822) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0145] In the illustrated embodiment, communication functions of the communication interface 812 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/intcrnct protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0146] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 812, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0147] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
[0148] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 800 shown in Figure 8.
[0149] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. [0150] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0151] Figure 9 shows a network node 900 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).
[0152] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
[0153] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
[0154] The network node 900 includes a processing circuitry 902, a memory 904, a communication interface 906, and a power source 908. The network node 900 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 900 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances 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 duplicated (e.g., separate memory 904 for different RATs) and some components may be reused (e.g., a same antenna 910 may be shared by different RATs). The network node 900 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 900, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 900.
[0155] The processing circuitry 902 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 900 components, such as the memory 904, to provide network node 900 functionality.
[0156] In some embodiments, the processing circuitry 902 includes a system on a chip (SOC). In some embodiments, the processing circuitry 902 includes one or more of radio frequency (RF) transceiver circuitry 912 and baseband processing circuitry 914. In some embodiments, the radio frequency (RF) transceiver circuitry 912 and the baseband processing circuitry 914 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 912 and baseband processing circuitry 914 may be on the same chip or set of chips, boards, or units. [0157] The memory 904 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non- transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 902. The memory 904 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 902 and utilized by the network node 900. The memory 904 may be used to store any calculations made by the processing circuitry 902 and/or any data received via the communication interface 906. In some embodiments, the processing circuitry 902 and memory 904 is integrated.
[0158] The communication interface 906 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 906 comprises port(s)/terminal(s) 916 to send and receive data, for example to and from a network over a wired connection. The communication interface 906 also includes radio front-end circuitry 918 that may be coupled to, or in certain embodiments a part of, the antenna 910. Radio front-end circuitry 918 comprises filters 920 and amplifiers 922. The radio front-end circuitry 918 may be connected to an antenna 910 and processing circuitry 902. The radio front-end circuitry may be configured to condition signals communicated between antenna 910 and processing circuitry 902. The radio front-end circuitry 918 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 918 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 920 and/or amplifiers 922. The radio signal may then be transmitted via the antenna 910. Similarly, when receiving data, the antenna 910 may collect radio signals which are then converted into digital data by the radio front-end circuitry 918. The digital data may be passed to the processing circuitry 902. In other embodiments, the communication interface may comprise different components and/or different combinations of components.
[0159] In certain alternative embodiments, the network node 900 does not include separate radio front-end circuitry 918, instead, the processing circuitry 902 includes radio front-end circuitry and is connected to the antenna 910. Similarly, in some embodiments, all or some of the RF transceiver circuitry 912 is part of the communication interface 906. In still other embodiments, the communication interface 906 includes one or more ports or terminals 916, the radio front-end circuitry 918, and the RF transceiver circuitry 912, as part of a radio unit (not shown), and the communication interface 906 communicates with the baseband processing circuitry 914, which is part of a digital unit (not shown).
[0160] The antenna 910 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 910 may be coupled to the radio front-end circuitry 918 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 910 is separate from the network node 900 and connectable to the network node 900 through an interface or port.
[0161] The antenna 910, communication interface 906, and/or the processing circuitry 902 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 910, the communication interface 906, and/or the processing circuitry 902 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
[0162] The power source 908 provides power to the various components of network node 900 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 908 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 900 with power for performing the functionality described herein. For example, the network node 900 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 908. As a further example, the power source 908 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
[0163] Embodiments of the network node 900 may include additional components beyond those shown in Figure 9 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 900 may include user interface equipment to allow input of information into the network node 900 and to allow output of information from the network node 900. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 900.
[0164] Figure 10 is a block diagram of a host 1000, which may be an embodiment of the host 716 of Figure 7, in accordance with various aspects described herein. As used herein, the host 1000 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1000 may provide one or more services to one or more UEs.
[0165] The host 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input/output interface 1006, a network interface 1008, a power source 1010, and a memory 1012. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 8 and 9, such that the descriptions thereof are generally applicable to the corresponding components of host 1000.
[0166] The 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, e.g., data generated by a UE for the host 1000 or data generated by the host 1000 for a UE. Embodiments of the host 1000 may utilize only a subset or all of the components shown. The host application programs 1014 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1014 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1000 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1014 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real- Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
[0167] Figure 11 is a block diagram illustrating a virtualization environment 1100 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to
Ill any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1100 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1100 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.
[0168] Applications 1102 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
[0169] Hardware 1104 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1106 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1108a and 1108b (one or more of which may be generally referred to as VMs 1108), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1106 may present a virtual operating platform that appears like networking hardware to the VMs 1108.
[0170] The VMs 1108 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1106. Different embodiments of the instance of a virtual appliance 1102 may be implemented on one or more of VMs 1108, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. [0171] In the context of NFV, a VM 1108 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine. Each of the VMs 1108, and that part of hardware 1104 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1108 on top of the hardware 1104 and corresponds to the application 1102.
[0172] Hardware 1104 may be implemented in a standalone network node with generic or specific components. Hardware 1104 may implement some functions via virtualization. Alternatively, hardware 1104 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1110, which, among others, oversees lifecycle management of applications 1102. In some embodiments, hardware 1104 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1112 which may alternatively be used for communication between hardware nodes and radio units.
[0173] Figure 12 shows a communication diagram of a host 1202 communicating via a network node 1204 with a UE 1206 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 712a of Figure 7 and/or UE 800 of Figure 8), network node (such as network node 710a of Figure 7 and/or network node 900 of Figure 9), and host (such as host 716 of Figure 7 and/or host 1000 of Figure 10) discussed in the preceding paragraphs will now be described with reference to Figure 12.
[0174] Eike host 1000, embodiments of host 1202 include hardware, such as a communication interface, processing circuitry, and memory. The host 1202 also includes software, which is stored in or accessible by the host 1202 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1206 connecting via an over-the-top (OTT) connection 1250 extending between the UE 1206 and host 1202. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1250.
[0175] The network node 1204 includes hardware enabling it to communicate with the host 1202 and UE 1206. The connection 1260 may be direct or pass through a core network (like core network 706 of Figure 7) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. [0176] The UE 1206 includes hardware and software, which is stored in or accessible by UE 1206 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1206 with the support of the host 1202. In the host 1202, an executing host application may communicate with the executing client application via the OTT connection 1250 terminating at the UE 1206 and host 1202. In providing the service to the user, the UE’s client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1250 may transfer both the request data and the user data. The UE’s client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1250.
[0177] The OTT connection 1250 may extend via a connection 1260 between the host 1202 and the network node 1204 and via a wireless connection 1270 between the network node 1204 and the UE 1206 to provide the connection between the host 1202 and the UE 1206. The connection 1260 and wireless connection 1270, over which the OTT connection 1250 may be provided, have been drawn abstractly to illustrate the communication between the host 1202 and the UE 1206 via the network node 1204, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
[0178] As an example of transmitting data via the OTT connection 1250, in step 1208, the host 1202 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1206. In other embodiments, the user data is associated with a UE 1206 that shares data with the host 1202 without explicit human interaction. In step 1210, the host 1202 initiates a transmission carrying the user data towards the UE 1206. The host 1202 may initiate the transmission responsive to a request transmitted by the UE 1206. The request may be caused by human interaction with the UE 1206 or by operation of the client application executing on the UE 1206. The transmission may pass via the network node 1204, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1212, the network node 1204 transmits to the UE 1206 the user data that was carried in the transmission that the host 1202 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1214, the UE 1206 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1206 associated with the host application executed by the host 1202. [0179] In some examples, the UE 1206 executes a client application which provides user data to the host 1202. The user data may be provided in reaction or response to the data received from the host 1202. Accordingly, in step 1216, the UE 1206 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1206. Regardless of the specific manner in which the user data was provided, the UE 1206 initiates, in step 1218, transmission of the user data towards the host 1202 via the network node 1204. In step 1220, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1204 receives user data from the UE 1206 and initiates transmission of the received user data towards the host 1202. In step 1222, the host 1202 receives the user data carried in the transmission initiated by the UE 1206.
[0180] One or more of the various embodiments improve the performance of OTT services provided to the UE 1206 using the OTT connection 1250, in which the wireless connection 1270 forms the last segment. For example, the signalling between the UE and network nodes according to teachings of these embodiments may improve the data rate, latency, power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, extended battery lifetime.
[0181] In an example scenario, factory status information may be collected and analyzed by the host 1202. As another example, the host 1202 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1202 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1202 may store surveillance video uploaded by a UE. As another example, the host 1202 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1202 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
[0182] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1250 between the host 1202 and UE 1206, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1202 and/or UE 1206. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1250 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1250 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1204. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1202. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1250 while monitoring propagation times, errors, etc.
[0183] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0184] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
[0185] A listing of example Embodiments according to some other embodiments of the present disclosure is provided below:
Group A Embodiments
1. A method performed by a user equipment, UE, for a L1/L2-triggered mobility, LTM, cell switch procedure, the method comprising: receiving (200) LTM reference configuration and LTM candidate cell configuration; combining (202) the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell; receiving (204), from a source network node, a LTM cell switch command, wherein the LTM cell switch command comprise at least an indication of a LTM candidate cell configuration; applying (206) the complete LTM candidate cell configuration of the indicated LTM candidate cell configuration; and sending (208) an uplink signalling to acknowledge completion of the LTM cell switch procedure.
2. The method of Embodiment 1, wherein the combining (202) the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell, comprises: generating the complete LTM candidate cell configuration responsive to the reception of one of LTM reference configuration and the at least one LTM candidate cell configuration from the source network node following earlier reception of the other one of the LTM reference configuration and the at least one LTM candidate cell configuration from the source network node.
3. The method of any of Embodiments 1 to 2, wherein the combining (202) the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell, comprises: generating the complete LTM candidate cell configuration responsive to the reception of the LTM cell switch command from the source network node.
4. The method of any of Embodiments 1 to 3, wherein the combining (202) the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell, comprises: applying the LTM candidate cell configuration on top of the LTM reference configuration according to one or more of the following: performing a set of actions that are common for the LTM reference configuration and the LTM candidate cell configuration; performing a set of actions that are separate for the LTM reference configuration and the LTM candidate cell configuration; and performing a set of actions for the LTM reference configuration and/or the LTM candidate cell configuration according to a rule or guideline defining handling of ASN.1 structures, fields, or information elements in the LTM reference configuration and the LTM candidate cell configuration.
5. The method of Embodiment 4, wherein the performing a set of actions for the LTM reference configuration and the LTM candidate cell configuration according to a rule or guideline defining handling of ASN.1 structures, fields, or information elements in the LTM reference configuration and the LTM candidate cell configuration, comprises determining from the rule or guideline at least one of: an operation to use on a value of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; an operation to use based on a type of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; an order in which to perform an operation on a value of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; an operation to use based on a value of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; an operation to use based on presence of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; and an operation to use based on a need code of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration.
6. The method of any of Embodiments 1 to 3, further comprising: preparing a part of the complete LTM candidate cell configuration based on reception of an LTM reference configuration and the LTM candidate cell configuration; and responsive to the reception of a LTM cell switch command, preparing the complete LTM candidate cell configuration based on the part.
7. The method of any of Embodiments 1 to 6, wherein the combining (202) the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell, comprises: defining the LTM candidate cell configuration as the complete LTM candidate cell configuration.
8. The method of any of Embodiments 1 to 7, after receiving (204) the LTM cell switch command and before applying (206) the complete LTM candidate cell configuration, further comprising at least one of: copying a timer, a counter, and/or a configuration from a current UE configuration to the complete LTM candidate cell configuration; clearing in the current UE configuration, a dedicated configuration earlier received through dedicated signaling from the source network node; clearing in the current UE configuration, a common configuration earlier received through system information from the source network node; and performing an L2 reset.
9. The method of any of Embodiments 1 to 8, after receiving (204) the LTM cell switch command and before applying (206) the complete LTM candidate cell configuration, further comprising at least one of: applying a default configuration if a dedicated configuration is not present within the complete LTM candidate cell configuration; applying the complete LTM candidate cell configuration in a target cell; and sending the uplink signalling to a target network node to acknowledge the completion of the LTM cell switch procedure.
Group B Embodiments
10. A method performed by a source network node for initiating a L1/L2-triggered mobility, LTM, cell switch procedure at a user equipment, UE, the method comprising: sending (300) a LTM reference configuration and a LTM candidate cell configuration to the UE; and sending (302) a LTM cell switch command for initiating a LTM cell switch procedure to the UE, wherein the LTM cell switch command comprises an indication of the LTM candidate cell configuration;
11. The method of Embodiment 10, wherein the LTM candidate cell configuration sent to the UE contains an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.
12. The method of Embodiment 11, wherein the indication of 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 a message in which the LTM candidate cell configuration is transmitted.
13. A method performed by a target network node for a L1/L2-triggered mobility, LTM, cell switch procedure, the method comprising: initiating (400) configuration of a LTM candidate cell configuration at a user equipment, UE, through another network node; and receiving (402) a signalling from the UE which indicates that the LTM cell switch procedure has been successfully completed and that the UE is starting to operate with the target network node according to the LTM candidate cell configuration.
14. The method of Embodiment 13, wherein the LTM candidate cell configuration contains an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration. Group C Embodiments
15. A user equipment for a L1/L2-triggered mobility, LTM, cell switch procedure, comprising: processing circuitry configured to perform any of the steps of any of the Group A Embodiments; and power supply circuitry configured to supply power to the processing circuitry.
16. A source network node for a L1/L2-triggered mobility, LTM, cell switch procedure, the source network node comprising: processing circuitry configured to perform any of the steps of any of the Group B Embodiments; power supply circuitry configured to supply power to the processing circuitry.
17. A target network node for a L1/L2-triggered mobility, LTM, cell switch procedure, the target network node comprising: processing circuitry configured to perform any of the steps of any of the Group B Embodiments; power supply circuitry configured to supply power to the processing circuitry.
18. A user equipment (UE) for a L1/L2-triggered mobility, LTM, cell switch procedure, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A Embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
19. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a source network node in a cellular network for transmission to a user equipment (UE), the source network node having a communication interface and processing circuitry, the processing circuitry of the source network node configured to perform any of the operations of any of the Group B Embodiments to transmit the user data from the host to the UE.
20. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a target network node in a cellular network for transmission to a user equipment (UE), the target network node having a communication interface and processing circuitry, the processing circuitry of the target network node configured to perform any of the operations of any of the Group B Embodiments to transmit the user data from the host to the UE.
21. The host of the previous Embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
22. A method implemented in a host configured to operate in a communication system that further includes a source network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the source network node, wherein the source network node performs any of the operations of any of the Group B Embodiments to transmit the user data from the host to the UE.
23. The method of the previous Embodiment, further comprising, at the source network node, transmitting the user data provided by the host for the UE. 24. A method implemented in a host configured to operate in a communication system that further includes a target network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the target network node, wherein the target network node performs any of the operations of any of the Group B Embodiments to transmit the user data from the host to the UE.
25. The method of the previous Embodiment, further comprising, at the target network node, transmitting the user data provided by the host for the UE.
26. The method of any of the previous 2 Embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.
27. A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular source network node for transmission to the UE, the source network node having a communication interface and processing circuitry, the processing circuitry of the source network node configured to perform any of the operations of any of the Group B Embodiments to transmit the user data from the host to the UE.
28. The communication system of the previous Embodiment, further comprising: the source network node; and/or the UE.
29. A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular target network node for transmission to the UE, the target network node having a communication interface and processing circuitry, the processing circuitry of the target network node configured to perform any of the operations of any of the Group B Embodiments to transmit the user data from the host to the UE.
30. The communication system of the previous Embodiment, further comprising: the target network node; and/or the UE.
31. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the 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 configured to perform any of the operations of any of the Group B Embodiments to receive the user data from a user equipment (UE) for the host.
32. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the 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 configured to perform any of the operations of any of the Group B Embodiments to receive the user data from a user equipment (UE) for the host.
33. The host of the previous 2 Embodiments, wherein: the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. 34. The host of the any of the previous 2 Embodiments, wherein the initiating receipt of the user data comprises requesting the user data.
35. A method implemented by a host configured to operate in a communication system that further includes a source network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the source network node has received from the UE, wherein the source network node performs any of the steps of any of the Group B Embodiments to receive the user data from the UE for the host.
36. The method of the previous Embodiment, further comprising at the source network node, transmitting the received user data to the host.
37. A method implemented by a host configured to operate in a communication system that further includes a target network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the target network node has received from the UE, wherein the target network node performs any of the steps of any of the Group B Embodiments to receive the user data from the UE for the host.
38. The method of the previous Embodiment, further comprising at the target network node, transmitting the received user data to the host.
39. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the operations of any of the Group A Embodiments to receive the user data from the host. 40. The host of the previous Embodiment, wherein the cellular network further includes a source network node configured to communicate with the UE to transmit the user data to the UE from the host.
41. The host of the previous two Embodiments, wherein the cellular network further includes a target network node configured to communicate with the UE to transmit the user data to the UE from the host.
42. The host of the previous 2 Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
43. A method implemented by a host operating in a communication system that further includes a source network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the source network node, wherein the UE performs any of the operations of any of the Group A Embodiments to receive the user data from the host.
34. The method of the previous Embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the host application.
35. The method of the previous Embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
36. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A Embodiments to transmit the user data to the host.
37. The host of the previous Embodiment, wherein the cellular network further includes a source network node configured to communicate with the UE to transmit the user data from the UE to the host.
38. The host of the previous 2 Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
39. A method implemented by a host configured to operate in a communication system that further includes a source network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the source network node by the UE, wherein the UE performs any of the steps of any of the Group A Embodiments to transmit the user data to the host.
40. The method of the previous Embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
41. The method of the previous 2 Embodiments, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application. REFERENCES
[1] RP-223520, 3GPP work item description: Further NR mobility enhancements, MediaTek Inc, Apple, 3GPP TSG RAN Meeting #98-e, Electronic Meeting, December 12-16, 2022.
[2] 3GPP TS 38.331 V17.4.0 (2023-03)
APPENDIX
5.3.5 RRC reconfiguration
Figure 5.3.5.1-1 : RRC reconfiguration, successful
Figure 5.3.5.1-2: RRC reconfiguration, failure
The purpose of this procedure is to modify an RRC connection, e.g. to establish/modify/release RBs/BH RLC channels/Uu Relay RLC channels/PC5 Relay RLC channels, to perform reconfiguration with sync, to setup/modify/release measurements, to add/modify/release SCells and cell groups, to add/modify/release conditional handover configuration, to add/modify/release conditional PSCell change or conditional PSCell addition configuration, to add/modify/LTM candidate cells. As part of the procedure, NAS dedicated information may be transferred from the Network to the UE.
RRC reconfiguration to perform reconfiguration with sync includes, but is not limited to, the following cases:
- reconfiguration with sync and security key refresh, involving RA to the Pcell/PSCell, MAC reset, refresh of security and re-establishment of RLC and PDCP triggered by explicit L2 indicators;
- reconfiguration with sync but without security key refresh, involving RA to the Pcell/PSCell, MAC reset and RLC re-establishment and PDCP data recovery (for AM DRB or AM MRB) triggered by explicit L2 indicators.
- reconfiguration with sync for DAPS and security key refresh, involving RA to the target Pcell, establishment of target MAC, and
- for non-DAPS bearer: refresh of security and re-establishment of RLC and PDCP triggered by explicit L2 indicators; - for DAPS bearer: establishment of RLC for the target Pcell, refresh of security and reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target Pcell;
- for SRB: refresh of security and establishment of RLC and PDCP for the target Pcell;
- reconfiguration with sync for DAPS but without security key refresh, involving RA to the target Pcell, establishment of target MAC, and
- for non-DAPS bearer: RLC re-establishment and PDCP data recovery (for AM DRB or AM MRB) triggered by explicit L2 indicators.
- for DAPS bearer: establishment of RLC for target Pcell, reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target Pcell;
- for SRB: establishment of RLC and PDCP for the target Pcell.
- reconfiguration with sync for direct-to-indirect path switch, not involving RA at target side, involving re-establishment of PDCP /PDCP data recovery (for AM DRB) triggered by explicit L2 indicators.
In (NG)EN-DC and NR-DC, SRB3 can be used for measurement configuration and reporting, for UE assistance (re-)configuration and reporting for power savings, for IP address (re-)configuration and reporting for lAB-nodes, to (re-)configure MAC, RLC, BAP, physical layer and RLF timers and constants of the SCG configuration, and to reconfigure PDCP for DRBs associated with the S- KgNB or SRB3, and to reconfigure SDAP for DRBs associated with S-KgNB in NGEN-DC and NR- DC, and to add/modify/release conditional PSCell change configuration, provided that the (reconfiguration does not require any MN involvement, and to transmit RRC messages between the MN and the UE during fast MCG link recovery. In (NG)EN-DC and NR-DC, only measConfig, radioBearerConfig, conditionalReconfiguration, bap-Config, iab-IP-AddressConfigurationList, otherConfig and/or secondaryCellGroup are included in RRCReconfiguration received via SRB3, except when RRCReconfiguration is received within DLInformationTransferMRDC.
The Network may initiate the RRC reconfiguration procedure to a UE in RRC_CONNECTED. The Network applies the procedure as follows:
- the establishment of RBs (other than SRB1, that is established during RRC connection establishment) is performed only when AS security has been activated;
- the establishment of BH RLC Channels for IAB is performed only when AS security has been activated;
- the establishment of Uu Relay RLC channels and PC5 Relay RLC channels (other than SL- RLCO and SL-RLC1) for L2 U2N Relay UE is performed only when AS security has been activated, and the establishment of PC5 Relay RLC channels for L2 U2N Remote UE (other than SL-RLCO and SL-RLC1) is performed only when AS security has been activated; the addition of Secondary Cell Group and SCells is performed only when AS security has been activated;
- the reconfigurationWithSync is included in secondaryCellGroup only when at least one RLC bearer or BH RLC channel is setup in SCG;
- the reconfigurationWithSync is included in masterCellGroup only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB, SRB2, are setup and not suspended;
- the conditionalReconfiguration for CPC is included only when at least one RLC bearer is setup in SCG;
- the conditionalReconfiguration for CHO or CPA is included only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB, SRB2, are setup and not suspended.
- the Itm-CandidateConfig for LTM is included only when AS security has been activated, and SRB2 with at least one DRB are setup and not suspended.
Editor’s Note: FFS on whether Itm-CandidateConfig applies also for the case of MBS or IAB.
The UE shall perform the following actions upon reception of the RRCReconfiguration, or upon execution of the conditional reconfiguration (CHO, CPA or CPC):
1> if the RRCReconfiguration is applied due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3:
2> remove all the entries within the MCG and the SCG VarConditionalReconfig, if any;
1> if the RRCReconfiguration includes the daps-SourceReleasc.
2> reset the source MAC and release the source MAC configuration;
2>for each DAPS bearer:
3>release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell;
3>reconfigure the PDCP entity to release DAPS as specified in TS 38.323 [5];
2>for each SRB:
3> release the PDCP entity for the source SpCell;
3>release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell;
2> release the physical channel configuration for the source SpCell;
2> discard the keys used in the source SpCell (the KgNB key, the KRRCenc key, the KRRCint key, the Kupint key and the KUPenc key), if any;
1> if the RRCReconfiguration is received via other RAT (i.e., inter-RAT handover to NR): 2> if the RRCReconfiguration does not include the fullConfig and the UE is connected to 5GC (i.e., delta signalling during intra 5GC handover):
3>re-use the source RAT SDAP and PDCP configurations if available (i.e., current SDAP/PDCP configurations for all RBs from source E-UTRA RAT prior to the reception of the inter-RAT HO RRCReconfiguration message); l>else:
2>if the RRCReconfiguration includes the fullConfig:
3>perform the full configuration procedure as specified in 5.3.5.11;
1> if the RRCReconfiguration includes the masterCellGroup:
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
1> if the RRCReconfiguration includes the masterKeyUpdate
2> perform AS security key update procedure as specified in 5.3.5.7;
1> if the RRCReconfiguration includes the sk-Counter:
2> perform security key update procedure as specified in 5.3.5.7;
1> if the RRCReconfiguration includes the secondaryCellGroup
2> perform the cell group configuration for the SCG according to 5.3.5.5;
1> if the RRCReconfiguration includes the mrdc-SecondaryCellGroupConfig:
2> if the mrdc-SecondaryCellGroupConfig is set to setup:
3> if the mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd:
4> perform MR-DC release as specified in clause 5.3.5.10;
3> if the received mrdc-SecondaryCellGroup is set to nr-SCG:
4> perform the RRC reconfiguration according to 5.3.5.3 for the RRCReconfiguration message included in nr-SCG',
3> if the received mrdc-SecondaryCellGroup is set to eutra-SCG:
4>perform the RRC connection reconfiguration as specified in TS 36.331 [10], clause
5.3.5.3 for the RRCConnectionReconfiguration message included in eutra-SCG',
2>else (mrdc -Secondary CellGroupConfig is set to release):
3>perform MR-DC release as specified in clause 5.3.5.10;
1> if the RRCReconfiguration message includes the radioBearerConfig:
2> perform the radio bearer configuration according to 5.3.5.6;
1> if the RRCReconfiguration message includes the radioBearerConfig2: 2> perform the radio bearer configuration according to 5.3.5.6;
1> if the RRCReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
1> if the RRCReconfiguration message includes the dedicatedNAS-MessageList:
2> forward each element of the dedicatedNAS-MessageList to upper layers in the same order as listed;
1> if the RRCReconfiguration message includes the dedicatedSIBl-Delivery.
2> perform the action upon reception of SIB/ as specified in 5.2.2.4.2;
NOTE 0: If this RRCReconfiguration is associated to the MCG and includes reconfigurationWithSync in spCellConfig and dedicatedSIBl-Delivery, the UE initiates (if needed) the request to acquire required SIBs, according to clause 5.2.2.3.5, only after the random access procedure towards the target SpCell is completed.
1> if the RRCReconfiguration message includes the dedicatedSystemlnformationDelivery.
2> perform the action upon reception of System Information as specified in 5.2.2.4;
1> if the RRCReconfiguration message includes the dedicatedPosSysInfoDelivery.
2> perform the action upon reception of the contained posSIB(s), as specified in clause 5.2.2.4.16;
1> if the RRCReconfiguration message includes the otherConfig:
2> perform the other configuration procedure as specified in 5.3.5.9;
1> if the RRCReconfiguration message includes the bap-Config:
2> perform the BAP configuration procedure as specified in 5.3.5.12;
1> if the RRCReconfiguration message includes the iab-IP-AddressConfigurationList:
2> if iab-IP-AddressToReleaseList is included:
3> perform release of IP address as specified in 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 the RRCReconfiguration message includes the conditionalReconfiguration:
2> perform conditional reconfiguration as specified in 5.3.5.13;
1> if the RRCReconfiguration message includes the needForGapsConfigNR
2> if needForGapsConfigNR is set to setup:
3> consider itself to be configured to provide the measurement gap requirement information of NR target bands; 2>else:
3> consider itself not to be configured to provide the measurement gap requirement information of NR target bands;
1> if the RRCReconfiguration message includes the needForGapNCSG-ConfigNR:
2> if needForGapNCSG-ConfigNR is set to setup:
3> consider itself to be configured to provide the measurement gap and NCSG requirement information of NR target bands;
2>else:
3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of NR target bands;
1> if the RRCReconfiguration message includes the needForGapNCSG-ConfigEUTRA
2>if needForGapNCSG-ConfigEUTRA is set to setup:
3> consider itself to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands;
2>else:
3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands;
1> if the RRCReconfiguration message includes the sl-ConfigDedicatedNR:
2> perform the sidelink dedicated configuration procedure as specified in 5.3.5.14;
NOTE Oa: If the sl-ConfigDedicatedNR was received embedded within an E-UTRA RRCConnectionReconfiguration message, the UE does not build an NR RRCReconfigurationComplete message for the received sl-ConfigDedicatedNR.
1> if the RRCReconfiguration message includes the sl-L2RelayUE-Config:
2> perform the L2 U2N Relay UE configuration procedure as specified in 5.3.5.15;
1> if the RRCReconfiguration message includes the 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 the dedicatedPagingDelivery:
2> perform the Paging message reception procedure as specified in 5.3.2.3;
1> if the RRCReconfiguration message includes the sl-ConfigDedicatedEUTRA-Info:
2> perform related procedures for V2X sidelink communication in accordance with TS 36.331 [10], clause 5.3.10 and clause 5.5.2;
1> if the RRCReconfiguration message includes the ul-GapFR2 -Config:
2> perform the FR2 UL gap configuration procedure as specified in 5.3.5.13c; 1> if the RRCReconfiguration message includes the musim-GapConfig:
2> perform the MUSIM gap configuration procedure as specified in 5.3.5.9a;
1> if the RRCReconfiguration message includes the appLayerMeasConfig-.
2> perform the application layer measurement configuration procedure as specified in 5.3.5.13d;
1> if the RRCReconfiguration message includes the ue-TxTEG-RequestUL-TDOA-Config-.
2>if ue-TxTEG-RequestUL-TDOA-Config is set to setup-.
3>perform the UE positioning assistance information procedure as specified in 5.7.14;
2>else:
3> release the configuration of UE positioning assistance information;
1> if the RRCReconfiguration message includes the Itm-CandidateConfig:
2> perform the LTM configuration procedure as specified in 5.3.5.x; l>set the content of the RRCReconfigurationComplete message as follows:
NOTE X: In case this procedure is initiated due to the generation of a complete LTM candidate cell configuration, the UE should generate only one RRCReconfigurationComplete message even if it process the LTM reference configuration and a LTM candidate cell configuration.
2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrenf.
3> include the uplinkTxDirectCurrentList for each MCG serving cell with UL;
3>include uplinkDirectCurrentBWP-SUL for each MCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList-,
2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrentTwoCarrier.
3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG;
2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrentMoreCarrier.
3> include in the uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG;
2> if the RRCReconfiguration includes the secondary CellGroup containing the reportUplinkTxDirectCurrenf.
3> include the uplinkTxDirectCurrentList for each SCG serving cell with UL;
3>include uplinkDirectCurrentBWP-SUL for each SCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList-, 2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrentTwoCarrier'.
3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG;
2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrentMoreCarrier.
3> include in the uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG;
NOTE Ob: The UE does not expect that the reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier is received in both masterCellGroup and in secondaryCellGroup. Network only configures at most one of reportUplinkTxDirectCurrent, reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier in one RRC message.
2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to eutra-SCG:
3> include in the eutra-SCG-Response the E-UTRA RRCConnectionReconfigurationComplete message in accordance with TS 36.331 [10] clause 5.3.5.3;
2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to nr-SCG:
3> include in the nr-SCG-Response the SCG RRCReconfigurationComplete message;
3> if the RRCReconfiguration message is applied due to conditional reconfiguration execution and the RRCReconfiguration message does not include the reconfigurationWithSync in the masterCellGroup'.
4> include in the selectedCondRRCReconfig the condReconfigld for the selected cell of conditional reconfiguration execution;
2> if the RRCReconfiguration includes the reconfigurationWithSync in spCellConfig of an MCG:
3> if the UE has logged measurements available for NR and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReporf.
4> include the logMeas Available in the RRCReconfigurationComplete message;
4> if Bluetooth measurement results are included in the logged measurements the UE has available for NR:
5> include the logMeasAvailableBT in the RRCReconfigurationComplete message;
4> if WLAN measurement results are included in the logged measurements the UE has available for NR:
5> include the logMeasAvailableWLAN in the RRCReconfigurationComplete message; 3> if the sigLoggedMeasType in VarLogMeasReport is included:
4> if T330 timer is running and the logged measurements configuration is for NR:
5> set sigLogMeasConfigAvailable to true in the RRCReconfigurationComplete message;
4> else:
5> if the UE has logged measurements available for NR:
6>set sigLogMeasConfigAvailable to false in the RRCReconfigurationComplete message;
3> if the UE has connection establishment failure or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList:
4> include connEstFaillnfoAvailable in the RRCReconfigurationComplete message;
3> if the UE has radio link failure or handover failure information available in VarRLF - Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF -Report, or
3> if the UE has radio link failure or handover failure information available in VarRLF - Report of TS 36.331 [10] and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331 [10]:
4> include rlf-InfoAvailable in the RRCReconfigurationComplete message;
3> if the UE was configured with successHO-Config when connected to the source Pcell; and
3> if the applied RRCReconfiguration is not due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3:
4> perform the actions for the successful handover report determination as specified in clause 5.7.10.6, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the MCG;
3> if the UE has successful handover information available in VarSuccessHO-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessHO-Report:
4> include successHO-InfoAvailable in the RRCReconfigurationComplete message; >if the RRCReconfiguration message was received via SRB1, but not within mrdc- SecondaryCellGroup or E-UTRA RRCConnectionReconfiguration or E-UTRA RRCConnectionResume:
3> if the UE is configured to provide the measurement gap requirement information of NR target bands:
4> if the RRCReconfiguration message includes the needForGapsConfigNR', or 4> if the NeedForGapsInfoNR information is changed compared to last time the UE reported this information:
5> include the NeedForGapsInfoNR and set the contents as follows:
6> include intraFreq-needForGap and set the gap requirement information of intra-frequency measurement for each NR serving cell;
6> if requestedTargetBandFilterNR is configured:
7>for each supported NR band that is also included in requestedTargetBandFilterNR, include an entry in interFreq-needForGap and set the gap requirement information for that band;
6>else:
7> include an entry in interFreq-needForGap and set the corresponding gap requirement information for each supported NR band; > if the UE is configured to provide the measurement gap and NCSG requirement information of NR target bands:
4> if the RRCReconfiguration message includes the needForGapNCSG-ConfigNR', or
4> if the needForGapNCSG-InfoNR information is changed compared to last time the UE reported this information:
5> include the NeedForGapNCSG-InfoNR and set the contents as follows:
6> include intraFreq-needForNCSG and set the gap and NCSG requirement information of intra-frequency measurement for each NR serving cell;
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>else:
7> include an entry for each supported NR band in interFreq-needForNCSG and set the corresponding NCSG requirement information; > if the UE is configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands:
4> if the RRCReconfiguration message includes the needForGapNCSG-ConfigEUTRA', or
4> if the needForGapNCSG-InfoEUTRA information is changed compared to last time the UE reported this information:
5> include the NeedForGapNCSG-InfoEUTRA and set the contents as follows:
6> if requestedTargetBandFilterNCSG-EUTRA is configured, for each supported E-UTRA band included in requestedTargetBandFilterNCSG-EUTRA, include an entry in needForNCSG-EUTRA and set the NCSG requirement information for that band; otherwise, include an entry for each supported E-UTRA band in needForNCSG-EUTRA and set the corresponding NCSG requirement information;
2> if this procedure is initiated due to the generation of a complete LTM candidate cell configuration:
3> the procedure ends. l>if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (UE in (NG)EN-DC):
2> if the RRCReconfiguration message was received via E-UTRA SRB1 as specified in TS 36.331 [10]; or
2> if the RRCReconfiguration message was received via E-UTRA RRC message RRCConnectionReconfiguration within MobilityFromNRCommand (handover from NR standalone to (NG)EN-DC);
3> if the RRCReconfiguration is applied due to a conditional reconfiguration execution for CPC which is configured via conditionalReconfiguration contained in nr- SecondaryCellGroupConfig specified in TS 36.331 [10]:
4> submit the RRCReconfigurationComplete message via the E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331 [10], clause 5.6.2a.
3>else if the RRCReconfiguration message was included in E-UTRA RRCConnectionResume message:
4> submit the RRCReconfigurationComplete message via E-UTRA embedded in E- UTRA RRC message RRCConnectionResumeComplete as specified in TS 36.331 [10], clause 5.3.3.4a;
3>else:
4> submit the RRCReconfigurationComplete via E-UTRA embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10], clause 5.3.5.3/5.3.5.4/5.4.2.3;
3> if the scg-State is not included in the E-UTRA message (RRCConnectionReconfiguration or RRCConnectionResume') containing the RRCReconfiguration message:
4>perform SCG activation as specified in 5.3.5.13a;
4> if reconfigurationWithSync was included in spCellConfig of an SCG:
5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];
4> else if the SCG was deactivated before the reception of the E-UTRA RRC message containing the RRCReconfiguration message: 5> if bfd-and-RLM was not configured to true before the reception of the E-UTRA RRCConnectionReconfiguration or RRCConnectionResume message containing the RRCReconfiguration message or if lower layers indicate that a Random Access procedure is needed for SCG activation:
6> initiate the Random Access procedure on the SpCell, as specified in TS 38.321 [3];
5>else the procedure ends;
4>else the procedure ends;
3>else:
4>perform SCG deactivation as specified in 5.3.5.13b;
4>the procedure ends;
2> if the RRCReconfiguration message was received within nr-SecondaryCellGroupConfig in RRCConnectionReconfiguration message received via SRB3 within
DLInformationTransferMRDC'.
3> submit the RRCReconfigurationComplete via E-UTRA embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10], clause 5.3.5.3/5.3.5.4;
3> if the scg-State is not included in the RRCConnectionReconfiguration'.
4> if reconfigurationWithSync was included in spCellConfig of an SCG:
5> initiate the Random Access procedure on the SpCell, as specified in TS 38.321 [3];
4>else the procedure ends;
3>else:
4>perform SCG deactivation as specified in 5.3.5.13b;
4>the procedure ends;
NOTE 1: The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.
2>else (RRCReconfiguration was received via SRB3) but not within DLInformationTransferMRDC'.
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration; NOTE 2: In (NG)EN-DC and NR-DC, in the case RRCReconfiguration is received via
SRB1 or within DLInformationTransferMRDC via SRB3, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is received via SRB3 but not within DLInformationTransferMRDC, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete. l>else if the RRCReconfiguration message was received via SRB1 within the nr-SCG within mrdc-SecondaryCellGroup (UE in NR-DC, mrdc-SecondaryCellGroup was received in RRCReconfiguration or RRCResume via SRB1):
2> if the RRCReconfiguration is applied due to a conditional reconfiguration execution for CPC which is configured via conditionalReconfiguration contained in nr-SCG within mrdc-SecondaryCellGro up :
3> submit the RRCReconfigurationComplete message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3.
2> if the scg-State is not included in the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message:
3>perform SCG activation as specified in 5.3.5.13a;
3> if reconfigurationWithSync was included in spCellConfig in nr-SCG:
4> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];
3>else if the SCG was deactivated before the reception of the NR RRC message containing the RRCReconfiguration message:
4> if bfd-and-RLM was not configured to true before the reception of the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message; or
4> if lower layers indicate that a Random Access procedure is needed for SCG activation:
5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];
4>else the procedure ends;
3>else the procedure ends;
2>else
3>perform SCG deactivation as specified in 5.3.5.13b;
3>the procedure ends;
NOTE 2a: The order in which the UE sends the RRCReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation. l>else if the RRCReconfiguration message was received via SRB3 (UE in NR-DC):
2> if the RRCReconfiguration message was received within DLInformationTransferMRDC: 3> if the RRCReconfiguration message was received within the nr-SCG within mrdc-
SecondaryCellGroup (NR SCG RRC Reconfiguration):
4> if the scg-State is not included in the RRCReconfiguration message containing the RRCReconfiguration message:
5> if reconfigurationWithSync was included in spCellConfig in nr-SCG:
6> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];
5>else:
6>the procedure ends;
4> else:
5>perform SCG deactivation as specified in 5.3.5.13b;
5>the procedure ends;
3>else:
4> if the RRCReconfiguration does not include the mrdc-SecondaryCellGroupConfig-.
5> if the RRCReconfiguration includes the scg-State-.
6> perform SCG deactivation as specified in 5.3.5.13b;
4> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
2>else:
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration; l>else (RRCReconfiguration was received via SRB1):
2>if the UE is in NR-DC and;
2> if the RRCReconfiguration does not include the mrdc-SecondaryCellGroupConfig-.
3> if the RRCReconfiguration includes the scg-State-.
4>perform SCG deactivation as specified in 5.3.5.13b;
3>else:
4>perform SCG activation without SN message as specified in 5.3.5.13bl ;
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3> if ta-Report is configured with value enabled and the UE supports TA reporting:
4> indicate TA report initiation to lower layers; 2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
2> if this is the first RRCReconfiguration message after successful completion of the RRC reestablishment procedure:
3>resume SRB2, SRB4, DRBs, multicast MRB, and BH RLC channels for IAB-MT, and Uu Relay RLC channels for L2 U2N Relay UE, that are suspended;
1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG and when MAC of an NR cell group successfully completes a Random Access procedure triggered above; or,
1> if sl-PathSwitchConfig was included in reconfigurationWithSync included in spCellConfig of an MCG, and when successfully sending RRCReconfigurationComplete message (i.e., PC5 RLC acknowledgement is received from target L2 U2N Relay UE):
2>stop timer T304 for that cell group if running;
2> if sl-PathSwitchConfig was included in reconfigurationWithSync:
3>stop timer T420;
3> release all radio resources, including release of the RLC entities and the MAC configuration at the source side;
3>reset MAC used in the source cell;
NOTE 2b: PDCP and SDAP configured by the source prior to the path switch that are reconfigured and re-used by target when delta signalling is used, are not released as part of this procedure.
2>stop timer T310 for source SpCell if running;
2> apply the parts of the CSI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any;
2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
2>for each DRB configured as DAPS bearer, request uplink data switching to the PDCP entity, as specified in TS 38.323 [5];
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3>if T390 is running:
4>stop timer T390 for all access categories;
4>perform the actions as specified in 5.3.14.4.
3>if T350 is running:
4>stop timer T350; 3> if RRCReconfiguration does not include dedicatedSIBl -Delivery and
3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG, has a common search space configured by searchSpaceSIBl :
4> acquire the SIBI, which is scheduled as specified in TS 38.213 [13], of the target SpCell of the MCG;
4>upon acquiring SIBI, perform the actions specified in clause 5.2.2.4.2; > if the reconfigurationWithSync was included in spCellConfig of an MCG; or > if the reconfigurationWithSync was included in spCellConfig of an SCG and the CPA or CPC was configured:
3>remove all the entries within the MCG and the SCG VarConditionalReconfig, if any;
3>remove all the entries within VarConditionalReconfiguration as specified in TS 36.331 [10], clause 5.3.5.9.6, if any;
3>for each measld of the MCG measConfig, if configured, and for each measld of the SCG measConfig, if configured, if the associated reportConfig has a reportType set to condTriggerConfig
4> for the associated reportConfigld'.
5> remove the entry with the matching reportConfigld from the reportConfigList within the VarMeasConfig',
4> if the associated measObjectld is only associated to a reportConfig with reportType set to condTriggerConfig'.
5> remove the entry with the matching measObjectld from the measObjectList within the VarMeasConfig',
4> remove the entry with the matching measld from the measIdList within the VarMeasConfig', > if reconfigurationWithSync was included in masterCellGroup or secondary CellGroup'.
3> if the UE initiated transmission of a UEAssistancelnformation message for the corresponding cell group during the last 1 second, and the UE is still configured to provide the concerned UE assistance information for the corresponding cell group; or
3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution, and the UE is configured to provide UE assistance information for the corresponding cell group, and the UE has initiated transmission of a UEAssistancelnformation message for the corresponding cell group since it was configured to do so in accordance with 5.7.4.2:
4> initiate transmission of a UEAssistancelnformation message for the corresponding cell group in accordance with clause 5.7.4.3 to provide the concerned UE assistance information; 4> start or restart the prohibit timer (if exists) or the leave without response timer for the MUSIM associated with the concerned UE assistance information with the timer value set to the value in corresponding configuration;
3> if SIB12 is provided by the target Pcell, and the UE initiated transmission of a SidelinkUEInformationNR message indicating a change of NR sidelink communication/discovery related parameters relevant in target Pcell (i.e. change of sl- RxInterestedFreqList or sl-TxResourceReqList) during the last 1 second preceding reception of the RRCReconfiguration message including reconfigurationWithSync in spCellConfig of an MCG; or
3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution and the UE is capable of NR sidelink communication/discovery and SIB12 is provided by the target Pcell, and the UE has initiated transmission of a SidelinkUEInformationNR message since it was configured to do so in accordance with 5.83.2:
4> initiate transmission of the SidelinkUEInformationNR message in accordance with 5.8.33;
2> if reconfigurationWithSync was included in masterCellGroup'.
3> if configured with application layer measurements and if application layer measurement report container has been received from upper layers for which the successful transmission of the message or at least one segment of the message has not been confirmed by lower layers:
4> re-submit the MeasurementReportAppLayer message or all segments of the MeasurementReportAppLayer message to lower layers for transmission via SRB4;
2> if reconfigurationWithSync was included in masterCellGroup and the target cell provides SIB2I:
3> if the UE initiated transmission of an MBSInterestlndication message during the last 1 second preceding reception of this RRCReconfiguration message; or
3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution, and the UE has initiated transmission of an MBSInterestlndication message after having received this RRCReconfiguration message:
4> initiate transmission of an MBSInterestlndication message in accordance with clause 5.9.4;
2>the procedure ends.
NOTE 3: The UE is only required to acquire broadcasted SIB I if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e. the broadcast and unicast/MBS multicast beams are quasi co-located. NOTE 4: The UE sets the content of UEAssistancelnformation according to latest configuration (i.e. the configuration after applying the RRCReconfiguration message) and latest UE preference. The UE may include more than the concerned UE assistance information within the UEAssistancelnformation according to 5.7.4.2. Therefore, the content of UEAssistancelnformation message might not be the same as the content of the previous UEAssistancelnformation message.
END OF CHANGES
START OF CHANGES
5.3.5.5.1 General
The network configures the UE with Master Cell Group (MCG), and zero or one Secondary Cell Group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331 [10], and for NE- DC, the SCG is configured as specified in TS 36.331 [10]. The network provides the configuration parameters for a cell group in the CellGroupConfig IE.
The UE performs the following actions based on a received CellGroupConfig IE:
1> if the CellGroupConfig contains the spCellConfig with reconfigurationWithSync:
Editor’s Note: FFS on whether to reuse the reconfiguration with sync procedure and IE.
2> perform Reconfiguration with sync according to 5.3.5.5.2;
2> resume all suspended radio bearers except the SRBs for the source cell group, and resume SCG transmission for all radio bearers, and resume BH RLC channels and resume SCG transmission for BH RLC channels for IAB-MT, if suspended;
NOTE: If the SCG is deactivated, resuming SCG transmission for all radio bearers does not imply that PDCP PDUs can be transmitted or received on SCG RLC bearers.
1> if the CellGroupConfig contains the rlc-BearerToReleaseList or rlc-BearerToReleaseListExf. 2> perform RLC bearer release as specified in 5.3.5.5.3; l>if the CellGroupConfig contains the rlc-BearerToAddModList.
2> perform the RLC bearer addition/modification as specified in 5.3.5.5.4; l>if the CellGroupConfig contains the mac-CellGroupConfig
2> configure the MAC entity of this cell group as specified in 5.3.5.5.5; l>if the CellGroupConfig contains the sCellToReleaseList:
2> perform SCell release as specified in 5.3.5.5.8; l>if the CellGroupConfig contains the spCellConfig-.
2>configure the SpCell as specified in 5.3.5.5.7; l>if the CellGroupConfig contains the sCellToAddModList:
2> perform SCell addition/modification as specified in 5.3.5.5.9; l>if the CellGroupConfig contains the bh-RLC-ChannelToReleaseList:
2> perform BH RLC channel release as specified in 5.3.5.5.10; l>if the CellGroupConfig contains the bh-RLC-ChannelToAddModList.
2> perform the BH RLC channel addition/modification as specified in 5.3.5.5.11; l>if the CellGroupConfig contains the uu-RelayRLC-ChannelToReleaseList:
2> perform Uu Relay RLC channel release as specified in 5.3.5.5.12; l>if the CellGroupConfig contains the 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 shall: l>for each logicalChannelldentity/LogicalChannelldentityExt value included in the rlc- BearerToReleaseList/rlc-BearerToReleaseListExt that is part of the current UE configuration within the same cell group (LCH release); or l>for each logicalChannelldentity value that is to be released as the result of an SCG release according to 5.3.5.4:
2> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3;
2> release the corresponding logical channel.
5.3.5.5.4 RLC bearer addition/modification
For each RLC-BearerConfig received in the rlc-BearerToAddModList IE the UE shall:
1> if this procedure is initiated due to the generation of a complete LTM candidate cell configuration:
2> create a RLC entity for the LTM candidate cell configuration for which a complete configuration needs to be generated;
2> the procedure ends. l>if the UE's current configuration contains an RLC bearer with the received logicalChannelldentity/LogicalChannelldentityExt within the same cell group:
NOTE X: This case does not apply when this procedure is initiated due to the generation of an LTM candidate cell configuration.
2> if the RLC bearer is associated with an DAPS bearer, or
2> if any DAPS bearer is configured and the RLC bearer is associated with an SRB: 3> reconfigure the RLC entity or entities for the target cell group in accordance with the received rlc-Config-,
3> reconfigure the logical channel for the target cell group in accordance with the received mac-LogicalChannel Config ;
2>else:
3> if reestablishRLC is received:
4> re-establish the RLC entity as specified in TS 38.322 [4];
3>reconfigure the RLC entity or entities in accordance with the received rlc-Config-,
3> reconfigure the logical channel in accordance with the received mac- LogicalChannelConfig;
3> if servedMBS-RadioBearer is received:
4> associate this logical channel with the PDCP entity identified by servedMBS- RadioBearer,
NOTE 1: For DRB and SRB, the network does not re-associate an already configured logical channel with another radio bearer. Hence, servedRadioBearer is not present in this case. For MRB, the network does not re-associate an already configured logical channel with DRB or SRB or another MRB (i.e. MRB with another PDCP entity). Hence multicastRLC-BearerConfig is not present in this case.
NOTE 2: In DAPS handover, the UE may perform RLC entity re-establishment (if reestablishRLC is set) for an RLC bearer associated with a non-DAPS bearer when indication of successful completion of random access towards target cell is received from lower layers as specified in TS 38.321 [3]. l>else (a logical channel with the given logicalChannelldentity/LogicalChannelldentityExt is not configured within the same cell group, including the case when full configuration option is used):
2>if the servedRadioBearer associates the logical channel with an SRB and rlc-Config is not included:
3> establish an RLC entity in accordance with the default configuration defined in 9.2 for the corresponding SRB;
2>else:
3> establish an RLC entity in accordance with the received rlc-Config-,
2>if the servedRadioBearer associates the logical channel with an SRB and if mac- LogicalChannelConfig is not included:
3> configure this MAC entity with a logical channel in accordance to the default configuration defined in 9.2 for the corresponding SRB;
2>else: 3> configure this MAC entity with a logical channel in accordance 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:
1> if SCG MAC is not part of the current UE configuration (i.e. SCG establishment):
2> create an SCG MAC entity; l>if any DAPS bearer is configured:
2> reconfigure the MAC main configuration for the target cell group in accordance with the received mac-CellGroupConfig excluding tag-ToReleaseList and tag-ToAddModList',
1> if this procedure is initiated due to the generation of a complete LTM candidate cell configuration:
2> create a MAC entity for the LTM candidate cell configuration for which a complete configuration needs to be generated excluding tag-ToReleaseList and tag-ToAddModList', l>else:
2> reconfigure the MAC main configuration of the cell group in accordance with the received mac-CellGroupConfig excluding tag-ToReleaseList and tag-ToAddModList',
1> if the received mac-CellGroupConfig includes the tag-ToReleaseLisr.
2>for each TAG-Id value included in the tag-ToReleaseList that is part of the current UE configuration:
3>release the TAG indicated by TAG-Id',
1> if the received mac-CellGroupConfig includes the tag-ToAddModList:
2>for each tag-id value included in tag-ToAddModList that is not part of the current UE configuration (TAG addition):
3>add the TAG, corresponding to the tag-id, in accordance with the received timeAlignmentTimer,
2>for each tag-id value included in tag-ToAddModList that is part of the current UE configuration (TAG modification):
3> reconfigure the TAG, corresponding to the tag-id, in accordance with the received timeAlignmentTimer.
5.3.5.5.6 RLF Timers & Constants configuration
The UE shall:
1> if the received rlf-TimersAndConstants is set to release'. 2>if any DAPS bearer is configured:
3>use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in ue-TimersAndConstants received in SIBT,
2>else:
3>use values for timers T301, T310, T311 and constants N310, N311, as included in ue- TimersAndConstants received in SIBI ; l>else:
2>if any DAPS bearer is configured:
3> configure the value of timers and constants for the target cell group in accordance with received rlf- T imersAndConstants ;
2>else:
3> (re-)configure the value of timers and constants in accordance with received rlf- TimersAndConstants',
3> if this procedure is not initiated due to the generation of a complete LTM candidate cell configuration:
4>stop timer T310 for this cell group, if running;
4>stop timer T312 for this cell group, if running;
4> reset the counters N310 and N311.
5.3.5.5.7 SpCell Configuration
The UE shall: l>if the UE is acting as L2 U2N Remote UE:
2>if the SpCellConfig contains the rlf-TimersAndConstants which is set to setup:
3>use value for timers T311 as received in rlf-TimersAndConstants',
2>else if rlf-TimersAndConstants is not configured for this cell group or SpCellConfig contains the rlf-TimersAndConstants which is set to release:
3>use value for timers T311, as included in ue-TimersAndConstants received in SIBT, l>else
2> if the SpCellConfig contains the rlf-TimersAndConstants:
3>configure the RLF timers and constants for this cell group as specified in 5.3.5.5.6;
2>else if rlf-TimersAndConstants is not configured for this cell group:
3> if any DAPS bearer is configured:
4>use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in ue-TimersAndConstants received in SIBT, 3>else
4>use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1;
2> if the SpCellConfig contains spCellConfigDedicated'.
3> configure the SpCell in accordance with the spCellConfigDedicated',
3>consider the bandwidth part indicated in first ActiveUplinkBWP-Id, if included in the spCellConfigDedicated, to be the active uplink bandwidth part;
3> if the firstActiveDownlinkBWP-Id is included in the spCellConfigDedicated'.
4> if the SpCellConfig is included in an RRCReconfiguration message contained in an NR or E-UTRA RRC message indicating that the SCG is deactivated:
5> consider the bandwidth part indicated vafirstActiveDownlinkBWP-Id to be the bandwidth part for Radio Link Monitoring, Beam Failure Detection and measurements;
4> else:
5> consider the bandwith part indicated in firstActiveDownlinkBWP-Id to be the active downlink bandwidth part;
3> if any of the reference signal(s) that are used for radio link monitoring are reconfigured by the received spCellConfigDedicated'. and
1> if this procedure is not initiated due to the generation of a complete LTM candidate cell configuration:
4>stop timer T310 for the corresponding SpCell, if running;
4>stop timer T312 for the corresponding SpCell, if running;
4> reset the counters N310 and N311.
1> if the SpCellConfig contains the lowMobilityEvaluationConnected'.
2>the UE may perform the evaluation of the low mobility criterion for this cell group as specified in 5.7.13.1;
1> if the SpCellConfig contains the goodServingCellEvaluationRLM'.
2>the UE may perform the evaluation of the good serving cell quality criterion for this SpCell as specified in 5.7.13.2;
1> if the SpCellConfig contains the goodServingCellEvaluationBFD'.
2>the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2;
53.5.5.8 SCell Release
The UE shall: 1> if the release is triggered by reception of the sCellToReleaseList
2>for each sCelllndex value included in the sCellToReleaseList
3> if the current UE configuration includes an SCell with value sCelllndex:
4> release the SCell.
Editor’s Note: FFS on whether the release of an SCell b an LTM candidate cell configuration is a valid case.
5.3.5.5.9 SCell Addition/Modification
The UE shall: l>for each sCelllndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):
2> add the SCell, corresponding to the sCelllndex, in accordance with the sCellConfigCommon and sCellConfigDedicated',
2>if the sCellState is included:
3> configure lower layers to consider the SCell to be in activated state;
2>else:
3> configure lower layers to consider the SCell to be in deactivated state;
2>for each measld included in the measIdList within VarMeasConfig:
3> if SCells are not applicable for the associated measurement; and
3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measld: and
3> if this procedure is not initiated due to the generation of a complete LTM candidate cell configuration:
4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measld',
2> if the SCellConfig contains the goodServingCellEvaluationBFD:
3>the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2. l>for each sCelllndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):
NOTE X: This case does not apply when this procedure is initiated due to the generation of an LTM candidate cell configuration.
2> modify the SCell configuration in accordance with the sCellConfigDedicated',
2>if the sCellState is included: 3> configure lower layers to consider the SCell to be in activated state;
2>else:
3> configure lower layers to consider the SCell to be in deactivated state.
2> if the SCellConfig contains the goodServingCellEvaluationBFD'.
3>the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2.
END OF CHANGES
START OF CHANGES
5.3.5.6.1 General
The UE shall perform the following actions based on a received RadioBearerConfig IE:
1> if the RadioBearerConfig includes the srb3-ToRelease or srb4-ToRelease'.
2> perform the SRB release as specified in 5.3.5.6.2;
1> if the RadioBearerConfig includes the srb-ToAddModList or if any DAPS bearer is configured:
2> perform the SRB addition or reconfiguration as specified in 5.3.5.6.3;
1> if the RadioBearerConfig includes the drb-ToReleaseList:
2> perform DRB release as specified in 5.3.5.6.4;
1> if the RadioBearerConfig includes the drb-ToAddModLisf.
2> perform DRB addition or reconfiguration as specified in 5.3.5.6.5;
1> if the RadioBearerConfig includes the mrb-ToReleaseList:
2> perform multicast MRB release as specified in 5.3.5.6.6;
1> if the RadioBearerConfig includes the mrb-ToAddModLisV.
2> perform multicast MRB addition or reconfiguration as specified in 5.3.5.6.7;
1> if this procedure is not initiated due to the generation of a complete LTM candidate cell configuration:
2> release all SDAP entities, if any, that have no associated DRB as specified in TS 37.324 [24] clause 5.1.2, and indicate the release of the user plane resources for PDU Sessions associated with the released SDAP entities to upper layers; l>release all SDAP entities that have no associated multicast MRB as specified in TS 37.324 [24] clause 5.1.2, and indicate the release of user plane resources for these MBS multicast sessions to upper layers. S.3.5.6.2 SRB release
The UE shall: l>if srb3-ToRelease is included:
2> release the PDCP entity and the srb-Identity of the SRB 3; l>if srb4-ToRelease is included
2> release the PDCP entity and the srb-Identity of the SRB 4.
5.3.5.6.3 SRB addition/modification
The UE shall: l>If any DAPS bearer is configured, for each SRB:
2>establish a PDCP entity for the target cell group as specified in TS 38.323 [5], with the same configuration as the PDCP entity for the source cell group;
2>if the masterKeyUpdate is received:
3> configure the PDCP entity with the security algorithms according to securityConfig and apply the keys (KRRCenc and KRRCint) associated with the master key (KgNB);
2>else:
3> configure the PDCP entity for the target cell group with state variables continuation as specified in TS 38.323 [5], and with the same security configuration as the PDCP entity for the source cell group; l>for each srb-Identity value included in the srb-ToAddModList that is not part of the current UE configuration (SRB establishment or reconfiguration from E-UTRA PDCP to NR PDCP):
2> if this procedure is initiated due to the generation of a complete LTM candidate cell configuration:
3> establish a PDCP entity for the LTM candidate cell configuration for which a complete configuration needs to be generated;
3> the procedure ends.
2> else:
3> establish a PDCP entity ;2> if AS security has been activated:
3> if target RAT of handover is E-UTRA/5GC; or
3> if the UE is connected to E-UTRA/5GC:
4> if the UE is capable of E-UTRA/5GC, but not capable of NGEN-DC:
5> configure the PDCP entity with the security algorithms and keys (KRRCenc and KRRCint) configured/derived as specified in TS 36.331 [10];
4>else (i.e., UE capable of NGEN-DC): 5> configure the PDCP entity with the security algorithms according to securityConfig and apply the keys (KRRCenc and KRRCint) associated with the master key (KeNB) or secondary key (S-KgNB) as indicated in keyToUse, if applicable;
3>else (i.e., UE connected to NR or UE connected to E-UTRA/EPC):
4> configure the PDCP entity with the security algorithms according to securityConfig and apply the keys (KRRCenc and KRRCint) associated with the master key (KeNB/ KgNB) or secondary key (S-KgNB) as indicated in keyToUse, if applicable;
2>if the current UE configuration as configured by E-UTRA in TS 36.331 [10] includes an SRB identified with 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 the pdcp-Config is included:
3> configure the PDCP entity in accordance with the received pdcp-Config-,
2>else:
3> configure the PDCP entity in accordance with the default configuration defined in 9.2.1 for the corresponding SRB ;
1> if any DAPS bearer is configured, for each srb-Identity value included in the srb- ToAddModList that is part of the current UE configuration:
2>if the pdcp-Config is included:
3> reconfigure the PDCP entity for the target cell group in accordance with the received pdcp-Config-, l>else, for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration:
NOTE X: This case does not apply when this procedure is initiated due to the generation of an LTM candidate cell configuration.
2>if the reestablishPDCP is set:
3> if target RAT of handover is E-UTRA/5GC; or
3> if the UE is connected to E-UTRA/5GC:
4> if the UE is capable of E-UTRA/5GC, but not capable of NGEN-DC:
5> configure the PDCP entity to apply the integrity protection algorithm and KRRCint key configured/derived as specified in TS 36.331 [10], i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
5> configure the PDCP entity to apply the ciphering algorithm and KRRCenc key configured/derived as specified in TS 36.331 [10], i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
4>else (i.e., a UE capable of NGEN-DC):
5> configure the PDCP entity to apply the integrity protection algorithm and KRRCint key associated with the master key (KeNB) or secondary key (S-KgNB), as indicated in keyToUse, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
5> configure the PDCP entity to apply the ciphering algorithm and KRRCenc key associated with the master key (KeNB) or secondary key (S-KgNB) as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
3>else (i.e., UE connected to NR or UE in EN-DC):
4> configure the PDCP entity to apply the integrity protection algorithm and KRRCint key associated with the master key (KeNB/KgNB) or secondary key (S-KgNB), as indicated in keyToUse , i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;
4> configure the PDCP entity to apply the ciphering algorithm and KRRCenc key associated with the master key (KeNB/KgNB) or secondary key (S-KgNB) as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent 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>else, if the discardOnPDCP is set:
3>trigger the PDCP entity to perform SDU discard as specified in TS 38.323 [5];
2>if the pdcp-Config is included:
3>reconfigure the PDCP entity in accordance with the received pdcp-Config.
5.3.5.6.4 DRB release
The UE shall: l>for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuration; or l>for each drb-Identity value that is to be released as the result of full configuration according to 5.3.5.11:
2> release the PDCP entity and the drb-Identity,
2> if SDAP entity associated with this DRB is configured: 3> indicate the release of the DRB to SDAP entity associated with this DRB (TS 37.324 [24], clause 5.3.3);
2>if the DRB is associated with an eps-Bearerldentity.
3> if a new bearer is not added either with NR or E-UTRA with same eps-Bearerldentity.
4> indicate the release of the DRB and the eps-Bearerldentity of the released DRB to upper layers.
NOTE 1: The UE does not consider the message as erroneous if the drb-ToReleaseList includes any drb-Identity value that is not part of the current UE configuration.
NOTE 2: Whether or not the RLC and MAC entities associated with this PDCP entity are reset or released is determined by the CellGroupConfig.
5.3.5.6.5 DRB addition/modification
The UE shall: l>for each drb-Identity value included in the drb-ToAddModList that is not part of the current UE configuration (DRB establishment including the case when full configuration option is used):
2> if this procedure is initiated due to the generation of a complete LTM candidate cell configuration:
3> establish a PDCP entity for the LTM candidate cell configuration for which a complete configuration needs to be generated;
3> the procedure ends.
2> else:
3> establish a PDCP entity and configure it in accordance with the received pdcp-Config-,
2> if the PDCP entity of this DRB is not configured with cipheringDisabled:
3> if target RAT of handover is E-UTRA/5GC; or
3> if the UE is connected to E-UTRA/5GC:
4> if the UE is capable of E-UTRA/5GC but not capable of NGEN-DC:
5> configure the PDCP entity with the ciphering algorithm and KUPenc key configured/derived as specified in TS 36.331 [10];
4>else (i.e., a UE capable of NGEN-DC):
5> configure the PDCP entity with the ciphering algorithms according to securityConfig and apply the key (KUPenc) associated with the master key (KeNB) or secondary key (S-KgNB) as indicated in keyToUse, if applicable;
3>else (i.e., UE connected to NR or UE connected to E-UTRA/EPC): 4> configure the PDCP entity with the ciphering algorithms according to securityConfig and apply the KUPenc key associated with the master key (KeNB/KgNB) or the secondary key (S-KgNB/S-KeNB) as indicated in keyToUse;
2> if the PDCP entity of this DRB is configured with integrity Protection-.
3> configure the PDCP entity with the integrity protection algorithms according to securityConfig and apply the Kupint key associated with the master (KeNB/KgNB) or the secondary key (S-KgNB) as indicated in keyToUse-,
2>if an sdap-Config is included:
3> if an SDAP entity with the received pdu-Session does not exist:
4> establish an SDAP entity as specified in TS 37.324 [24] clause 5.1.1;
4> if an SDAP entity with the received pdu-Session did not exist prior to receiving this reconfiguration:
5> indicate the establishment of the user plane resources for the pdu-Session to upper layers;
3> configure the SDAP entity in accordance with 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 in mappedQoS-FlowsToAdd, if the QFI value is previously configured, the QFI value is released from the old DRB ;
2>if the DRB is associated with an eps-Bearerldentity.
3> if the DRB was configured with the same eps-Bearerldentity either by NR or E-UTRA prior to receiving this reconfiguration:
4> associate the established DRB with the corresponding eps-Bearerldentity;
3>else:
4> indicate the establishment of the DRB(s) and the eps-Bearerldentity of the established DRB(s) to upper layers; l>for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration and configured as DAPS bearer:
NOTE X: This case does not apply when this procedure is initiated due to the generation of an LTM candidate cell configuration.
2> reconfigure the PDCP entity to configure DAPS with the ciphering function, integrity protection function and ROHC function of the target cell group as specified in TS 38.323 [5] and configure it in accordance with the received pdcp-Config-,
2>if the masterKeyUpdate is received:
3> if the ciphering function of the target cell group PDCP entity is not configured with cipheringDisabled: 4> configure the ciphering function of the target cell group PDCP entity with the ciphering algorithm according to securityConfig and apply the KUPenc key associated with the master key (KgNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received from the target cell group 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 with integrityProtection:
4> configure the integrity protection function of the target cell group PDCP entity with the integrity protection algorithms according to securityConfig and apply the Kupint key associated with the master key (KgNB) as indicated in keyToUse'.
2>else:
3> configure the ciphering function and the integrity protection function of the target cell group PDCP entity with the same security configuration as the PDCP entity for the source cell group;
2> if the sdap-Config is included and when indication of successful completion of random access towards target cell is received from lower layers as specified in [3]:
3>reconfigure the SDAP entity in accordance with the received sdap-Config as specified in TS 37.324 [24];
3>for each QFI value added in mappedQoS-FlowsToAdd, if the QFI value is previously configured, the QFI value is released from the old DRB ; l>for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration and not configured as DAPS bearer:
2>if the reestablishPDCP is set:
3> if target RAT of handover is E-UTRA/5GC; or
3> if the UE is connected to E-UTRA/5GC:
4> if the UE is capable of E-UTRA/5GC but not capable of NGEN-DC:
5> if the PDCP entity of this DRB is not configured with cipheringDisabled:
6> configure the PDCP entity with the ciphering algorithm and KUPenc key configured/derived as specified in TS 36.331 [10], clause 5.4.2.3, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;
4>else (i.e., a UE capable of NGEN-DC):
5> if the PDCP entity of this DRB is not configured with cipheringDisabled'.
6> configure the PDCP entity with the ciphering algorithm and KUPenc key associated with the master key (KeNB) or the secondary key (S-KgNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE; 3>else (i.e., UE connected to NR or UE connected to E-UTRA/EPC (in EN-DC or capable of EN-DQ):
4> if the PDCP entity of this DRB is not configured with cipheringDisabled:
5> configure the PDCP entity with the ciphering algorithm and KUPenc key associated with the master key (KeNB/ KgNB) or the secondary key (S-KgNB/S-KeNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;
4> if the PDCP entity of this DRB is configured with integrity Protection-.
5> configure the PDCP entity with the integrity protection algorithms according to securityConfig and apply the Kupint key associated with the master key (KeNB/KgNB) or the secondary key (S-KgNB) as indicated in keyToUse-,
3> if drb-ContinueROHC is included in pdcp-Config-.
4> indicate to lower layer that drb-ContinueROHC is configured;
3> if drb-ContinueEHC-DL is included in pdcp-Config-.
4> indicate to lower layer that drb-ContinueEHC-DL is configured;
3> if drb-ContinueEHC-UL is included in pdcp-Config-.
4> indicate to lower layer that drb-ContinueEHC-UL is configured;
3> if drb-ContinueUDC is included in pdcp-Config-.
4> indicate to lower layer that drb-ContinueUDC is configured;
3> re-establish the PDCP entity of this DRB as specified in TS 38.323 [5], clause 5.1.2;
2>else, if the recoverPDCP is set:
3>trigger the PDCP entity of this DRB to perform data recovery as specified in TS 38.323 [5];
2>if the pdcp-Config is included:
3>reconfigure the PDCP entity in accordance with the received pdcp-Config.
2>if the sdap-Config is included:
3>reconfigure the SDAP entity in accordance with the received sdap-Config as specified in TS37.324 [24];
3>for each QFI value added in mappedQoS-FlowsToAdd, if the QFI value is previously configured, the QFI value is released from the old DRB ;
NOTE 1: Void. NOTE 2: When determining whether a drb-ldentity value is part of the current UE configuration, the UE does not distinguish which RadioBearerConfig and DRB- ToAddModList that DRB was originally configured in. To re-associate a DRB with a different key (KeNB to S-KgNB, KeNB to S-KeNB, KgNB to S-KgNB, or vice versa), the network provides the drb-ldentity value in the (target) drb-ToAddModList and sets the reestablishPDCP flag. The network does not list the drb-ldentity in the (source) drb- ToReleaseList.
NOTE 3: When setting the reestablishPDCP flag for a radio bearer, the network ensures that the REC receiver entities do not deliver old PDCP PDUs to the re-established PDCP entity. It does that e.g. by triggering a reconfiguration with sync of the cell group hosting the old REC entity or by releasing the old REC entity.
NOTE 4: In this specification, UE configuration refers to the parameters configured by NR RRC unless otherwise stated.
NOTE 5: Ciphering and integrity protection can be enabled or disabled for a DRB. The enabling/disabling of ciphering or integrity protection can be changed only by releasing and adding the DRB.
NOTE 6: In DAPS handover, the UE may perform PDCP entity re-establishment (if reestablishPDCP is set) or the PDCP data recovery (if recoverPDCP is set) for a non- DAPS bearer when indication of successful completion of random access towards target cell is received from lower layers as specified in TS 38.321 [3]. In this case, the UE suspends data transmission and reception for all non-DAPS bearers in the source MCG for duration of the DAPS handover.
END OF CHANGES
START OF CHANGES
5.3.5.X.1 General
The UE shall perform the following actions based on a received LTM - Config IE: 1> store the received Itm-ReferenceConfigiiration in VarLTM -Config, if present;
1> if the LTM-CandidateConfig includes the Itm-CandidateToReleaseList'.
2> perform the LTM candidate cell release as specified in 5.3.5.X.2;
1> if the LTM-CandidateConfig includes the ltm-CandidateResetL2-List'.
2>add the received ltm-CandidateResetL2-List to VarLTM -Config;
1> if the LTM-CandidateConfig includes the Itm-CandidateToAddModList'.
2> perform the LTM candidate cell addition or reconfiguration as specified in 5.3.5.X.3;
1> perform the actions to generate a complete LTM configuration as specified in 5.3.5.X.4;
NOTE X: configuration until the executing of an LTM cell switch. Editor’s Note: FFS on whether the UE performs the compliance check of the reference and LTM candidate cell configuration upon their reception of upon the execution of the LTM cell switch.
Editor’s Note: FFS on how and whether to indicate that no RACH is needed for an LTM candidate cell.
Editor’s Note: FFS on how UE should establish the TA for a LTM candidate cell.
5.3.5.X.2 LTM candidate cell release
The UE shall: l>for each Itm-Candidateld in the Itm-CandidateToReleaseList:
2>if the current VarLTM-Config includes an Itm-Candidate with the given Itm-Candidateld'.
3>release the Itm-Candidate from VarLTM-Config',
5.3.5.X.3 LTM candidate cell addition/modification
The UE shall: l>for each Itm-Candidateld in the Itm-CandidateToAddModList:
2>if the current VarLTM-Config includes an Itm-Candidate with the given Itm-Candidateld'.
3> modify the Itm-Candidate within VarLTM-Config in accordance with the received Itm- Candidate',
2>else:
3>add the received Itm-Candidate to VarLTM-Config.
5.3.5.X.4 Generation of UE LTM configuration
The purpose of this procedure is for the UE to generate a complete LTM candidate cell configuration to be stored and applied only when an indication of an LTM cell switch is received by lower layers. During the generation of a complete LTM candidate cell configuration, the current UE configuration shall not be modified.
The UE shall:
1> for each Itm-Candidate in Itm-CandidateConfigList within VarLTM-Config;
2> store the Itm-Candidateld included in Itm-Candidate within VarLTM-UE-Config;
2> if Itm-Candidate includes Itm-ConfigComplete;
3> generate a complete LTM candidate cell configuration for the received Itm-Candidate according to the actions described in clause 5.3.5.3 and store it in ue-LTM-Config within VarLTM-UE-Config.
2> else: 3> generate a complete LTM candidate cell configuration by applying Itm-Candidate on top of referenceConfiguration according to the actions described in clause 5.3.5.3 and store it in ue-LTM-Config within VarLTM-UE-Config.
Editor’s Note: FFS on the need of Itm-ConfigComplete to indicate to the UE that the LTM candidate cell configuration in Itm-Candidate is a full configuration.
Editor’s Note: FFS on whether we need to rely on the full configuration procedure or a new procedure for LTM is created when the UE generates a complete LTM candidate cell configuration.
5.3.5.X.5 LTM cell switch execution
Upon the indication by lower layers that an LTM cell switch procedure is triggered, the UE shall:
1> release/clear all current dedicated radio configuration except for the following:
2> if the LTM cell switch is triggered on the MCG:
- the MCG C-RNTI:
- the AS security configurations associated with the master key:
2> else, if the LTM cell switch is triggered on the SCG:
- the SCG C-RNTI:
- the AS security configurations associated with the secondary key:
- the SRB1/SRB2 configurations and DRB configurations as configured by radioBearerConfig or radioBearerConfig2;
Editor’s Note: FFS on whether the radio bearer needs to be kept when execution the LTM cell switch.
- the UE variables VarLTM-Config and VarLTM-UE-Config.
1> release/clear all current common radio configuration:
Editor’s Note: FFS on whether ServingCellConfigCommon is always provided in a LTM candidate cell configuration or whether can be optional.
1> use the default values specified in 9.2.3 for timers T310, T311 and constants N310, N311;
1> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the following:
- parameters for which values are provided in SIB 1;
1> apply the value of the newUE-Identity as the C-RNTI for this cell group according to the LTM candidate cell configuration related to the the LTM candidate cell configuration identity as received by lower layers:
1> configure lower layers in accordance with the received spCellConfigCommon according to the LTM candidate cell configuration indicated by lower layers: l>configure lower layers in accordance with the received rach-ConfigDedicated according to the LTM candidate cell configuration indicated by lower layers.
1> configure the PDCP entity for LTM candidate cell configuration indicated by lower layers with state variables continuation as specified in TS 38.323 151. and with the same security configuration as the PDCP entity for the source cell group; l>stop timer T310 for the corresponding SpCell, if running;
1> if this procedure is executed for the MCG:
2>if timer T316 is running;
3>stop timer T316; l>stop timer T312 for the corresponding SpCell, if running; l>apply the specified BCCH configuration defined in 9.1.1.1 for the target LTM candidate cell configuration;
1> acquire the MIB of the target SpCell as indicated in the LTM candidate cell configuration indicated by lower layers, which is scheduled as specified in TS 38.213 1131, if applicable;
1> apply the LTM configuration in UE-LTM-Config within VarLTM-UE-Config related to the LTM candidate cell configuration identity as received by lower layers.
1> submit the RRCReconfigurationComplete message to lower layers for transmission using the new configuration.
Editor’s Note: FFS on whether the sending of the RRCReconfigurationComplete message should be triggered in this section or in section 5.3.5.3 (i.e., Reception o f an RRCReconfiguration by the UE).
Editor’s Note: FFS on whether further UE actions need to be specified for e.g., subsequent LTM cell switch or interaction with lower layers.
Editor’s Note: FFS on the UE actions (for no L2 reset) based on ltm-CandidateNoResetL2-List.
Editor’s Note: FFS on how and whether to indicate that no RACH is needed for an LTM candidate cell.
Editor’s Note: FFS on how to handle the TA (and when the UE has no TA) in the source cell (in case no RACH is performed) upon an LTM cell switch and whether this should be specified in RRC or MAC.
Editor’s Note: FFS on the supervision timer for the LTM cell switch.
Editor’s Note: FFS on how to provide the UL grant to the UE in case no RACH is performed during the LTM cell switch. 6.2 RRC messages
6.2.2 Message definitions
The RRCReconfiguration message is the command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC main configuration and physical channel configuration) and AS security
5 configuration.
Signalling radio bearer: SRB1 or SRB3
RLC-SAP: AM
Logical channel: DCCH
Direction: Network to UE
10 RRCReconfiguration message
10
35
6.3 RRC information elements
6.3.2 Radio resource control information elements
5 The CellGroupConfig IE is used to configure a master cell group (MCG) or secondary cell group (SCG). A cell group comprises of one MAC entity, a set of logical channels with associated RLC entities and of a primary cell (SpCell) and one or more secondary cells (SCells).
CellGroupConfig information element
6.4 RRC multiplicity and type constraint values
40
Editor’s note: maxKO-SchedulingOffset and maxKO-SchedulingOffset need confirmation by RAN1

Claims

CLAIMS:
1. A method performed by a user equipment, UE, for a L1/L2-triggered mobility, LTM, cell switch procedure, the method comprising: receiving (200) LTM reference configuration and LTM candidate cell configuration; combining (202) the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell; receiving (204), from a source network node, a LTM cell switch command, wherein the LTM cell switch command comprise at least an indication of a LTM candidate cell configuration; applying (206) the complete LTM candidate cell configuration of the indicated LTM candidate cell configuration; and sending (208) an uplink signalling to acknowledge completion of the LTM cell switch procedure.
2. The method of claim 1, wherein the combining (202) the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell, comprises: generating the complete LTM candidate cell configuration responsive to the reception of one of LTM reference configuration and the at least one LTM candidate cell configuration from the source network node following earlier reception of the other one of the LTM reference configuration and the at least one LTM candidate cell configuration from the source network node.
3. The method of any of claims 1 to 2, wherein the combining (202) the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell, comprises: generating the complete LTM candidate cell configuration responsive to the reception of the LTM cell switch command from the source network node.
4. The method of any of claims 1 to 3, wherein the combining (202) the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell, comprises: applying the LTM candidate cell configuration on top of the LTM reference configuration according to one or more of the following: performing a set of actions that are common for the LTM reference configuration and the LTM candidate cell configuration; performing a set of actions that are separate for the LTM reference configuration and the LTM candidate cell configuration; and performing a set of actions for the LTM reference configuration and/or the LTM candidate cell configuration according to a rule or guideline defining handling of ASN.1 structures, fields, or information elements in the LTM reference configuration and the LTM candidate cell configuration.
5. The method of claim 4, wherein the performing a set of actions for the LTM reference configuration and the LTM candidate cell configuration according to a rule or guideline defining handling of ASN.1 structures, fields, or information elements in the LTM reference configuration and the LTM candidate cell configuration, comprises determining from the rule or guideline at least one of: an operation to use on a value of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; an operation to use based on a type of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; an order in which to perform an operation on a value of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; an operation to use based on a value of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; an operation to use based on presence of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration; and an operation to use based on a need code of the ASN.1 structure, field, or information element in the LTM reference configuration and/or the LTM candidate cell configuration.
6. The method of any of claims 1 to 3, further comprising: preparing a part of the complete LTM candidate cell configuration based on reception of an LTM reference configuration and the LTM candidate cell configuration; and responsive to the reception of a LTM cell switch command, preparing the complete LTM candidate cell configuration based on the part.
7. The method of any of claims 1 to 6, wherein the combining (202) the LTM reference configuration and the LTM candidate cell configuration to obtain a complete LTM candidate cell configuration for a LTM candidate cell, comprises: defining the LTM candidate cell configuration as the complete LTM candidate cell configuration.
8. The method of any of claims 1 to 7, after receiving (204) the LTM cell switch command and before applying (206) the complete LTM candidate cell configuration, further comprising at least one of: copying a timer, a counter, and/or a configuration from a current UE configuration to the complete LTM candidate cell configuration; clearing in the current UE configuration, a dedicated configuration earlier received through dedicated signaling from the source network node; clearing in the current UE configuration, a common configuration earlier received through system information from the source network node; and performing an L2 reset.
9. The method of any of claims 1 to 8, after receiving (204) the LTM cell switch command and before applying (206) the complete LTM candidate cell configuration, further comprising at least one of: applying a default configuration if a dedicated configuration is not present within the complete LTM candidate cell configuration; applying the complete LTM candidate cell configuration in a target cell; and sending the uplink signalling to a target network node to acknowledge the completion of the LTM cell switch procedure.
10. A method performed by a source network node for initiating a L1/L2-triggered mobility, LTM, cell switch procedure at a user equipment, UE, the method comprising: sending (300) a LTM reference configuration and a LTM candidate cell configuration to the UE; and sending (302) a LTM cell switch command for initiating a LTM cell switch procedure to the UE, wherein the LTM cell switch command comprises an indication of the LTM candidate cell configuration.
11. The method of claim 10, wherein the LTM candidate cell configuration sent to the UE contains an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.
12. The method of claim 11, wherein the indication of 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 a message in which the LTM candidate cell configuration is transmitted.
13. A method performed by a target network node for a L1/L2-triggered mobility, LTM, cell switch procedure, the method comprising: initiating (400) configuration of a LTM candidate cell configuration at a user equipment, UE, through another network node; and receiving (402) a signalling from the UE which indicates that the LTM cell switch procedure has been successfully completed and that the UE is starting to operate with the target network node according to the LTM candidate cell configuration.
14. The method of claim 13, wherein the LTM candidate cell configuration contains an indication of whether the LTM candidate cell configuration is a complete LTM candidate cell configuration.
15. A user equipment (101, 712A, 712B, 712C, 712D, 800, 1206) for a L1/L2-triggered mobility, LTM, cell switch procedure, comprising: processing circuitry (802) configured to perform any of the steps of any of claims 1 to 9; and power supply circuitry (808) configured to supply power to the processing circuitry.
16. A source network node (102, 710A, 710B, 900, 1204) for a L1/L2-triggered mobility, LTM, cell switch procedure, the source network node comprising: processing circuitry (902) configured to perform any of the steps of any of claims 10 to 14; power supply circuitry (908) configured to supply power to the processing circuitry.
17. A target network node (103, 710A, 710B, 900, 1204) for a L1/L2-triggered mobility, LTM, cell switch procedure, the target network node comprising: processing circuitry (902) configured to perform any of the steps of any of claims 10 to 14; power supply circuitry (908) configured to supply power to the processing circuitry.
18. A user equipment (UE) for a L1/L2-triggered mobility, LTM, cell switch procedure, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of claims 1 to 9; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
EP24725005.3A 2023-04-11 2024-04-08 Generation of a complete l1/l2-triggered mobility candidate cell configuration Pending EP4696054A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363458546P 2023-04-11 2023-04-11
PCT/IB2024/053432 WO2024213994A1 (en) 2023-04-11 2024-04-08 Generation of a complete l1/l2-triggered mobility candidate cell configuration

Publications (1)

Publication Number Publication Date
EP4696054A1 true EP4696054A1 (en) 2026-02-18

Family

ID=91067131

Family Applications (1)

Application Number Title Priority Date Filing Date
EP24725005.3A Pending EP4696054A1 (en) 2023-04-11 2024-04-08 Generation of a complete l1/l2-triggered mobility candidate cell configuration

Country Status (3)

Country Link
EP (1) EP4696054A1 (en)
CN (1) CN121420599A (en)
WO (1) WO2024213994A1 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12389299B1 (en) * 2024-12-16 2025-08-12 AerKodo, LLC Lower-layer triggered mobility for recovery from radio link failure
US12382359B1 (en) * 2024-12-16 2025-08-05 AerKodo, LLC Lower-layer triggered mobility for recovery from radio link failure

Also Published As

Publication number Publication date
CN121420599A (en) 2026-01-27
WO2024213994A1 (en) 2024-10-17

Similar Documents

Publication Publication Date Title
US20240276585A1 (en) Methods and network nodes for suspend-resume for l1/l2 centric inter-cell mobility configuation(s)
US20250008563A1 (en) Random access partitioning and random access report
US20250351040A1 (en) Configuring Inter-DU L1/L2 Mobility Candidates
US20260046723A1 (en) Csi measurements for inter-cell mobility
US20250365594A1 (en) Configuring layer 1 and layer 2 mobility based on measurement reports while in a connected state
US20250097985A1 (en) Sending and Receiving a Report
EP4696054A1 (en) Generation of a complete l1/l2-triggered mobility candidate cell configuration
US20260040388A1 (en) Small Data Transmissions in a Wireless Network
US11792693B2 (en) Methods and apparatuses for redirecting users of multimedia priority services
US20260019912A1 (en) Methods, apparatus and computer-readable medium related to conditional cell change
WO2024232818A1 (en) Fast failure recovery while user equipment configured with level 1 or level 2 triggered mobility
US20250047393A1 (en) Efficient inter-cell l1-rsrp measurement and reporting
US20240413869A1 (en) Temporary reference signal-based secondary cell activation via radio resource control
US20240267914A1 (en) Mechanisms for cg-sdt associated with multiple ssb beams
US20250048168A1 (en) Configuring a User Equipment to Operate as a Cell on the Fly
US20240323995A1 (en) Secondary node requested measurement gaps at secondary node addition
WO2023073677A2 (en) Measurements in a communication network
WO2023062602A1 (en) Methods and apparatuses for handling of inter-cell multi-trp configurations during re-establishment
US20260100750A1 (en) Beam Failure Detection Monitoring
US20250048153A1 (en) Minimization of Drive Test Configuration in User Equipment
US20260107201A1 (en) BWP and L1-L2 Inter-Cell Mobility
WO2025034155A1 (en) Cell selection upon fast failure recovery for ue configured with l1/l2 triggered mobility
WO2025122053A1 (en) Methods, computer-readable media and apparatus related to mobility procedures in wireless networks
WO2025029180A1 (en) Security key exchange for secondary cell group at lower-layer triggered mobility for the master control group
EP4710624A1 (en) Configuring a user equipment to perform measurement reporting

Legal Events

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

Free format text: STATUS: UNKNOWN

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

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

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

Free format text: ORIGINAL CODE: 0009012

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20251111

AK Designated contracting states

Kind code of ref document: A1

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