Configuration of Layer 1 and Layer 2 mobility based on measurement reports in connected state

Abstract

A method (1300) by a user equipment (UE) (402, 502, 602, 800) in a connected state is provided for configuring layer 1 / layer 2 (L1 / L2)-based inter-cell mobility. The method includes transmitting (1302) a measurement report including one or more measurements associated with one or more cells. The UE receives (1304) a radio resource control (RRC) reconfiguration message including at least one configuration of an L1 / L2-based inter-cell mobility candidate cell. The UE transmits (1306) an RRC reconfiguration complete message.

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication, and more particularly to a system and method for configuring (constructing) layer 1 (L1) / layer 2 (L2) mobility based on measurement reports while in a connected state.

Background Art

[0002] According to 3GPP (registered trademark) TS 38.473 (§8.3.4), the central unit of the gNodeB (gNB-CU) can initiate a user equipment (UE) context modification procedure to modify an established UE context, for example, to establish, modify, and release radio resources. FIG. 1 shows a successful operation of the UE context modification procedure.

[0003] As shown in FIG. 1, a UE context modification request message is initiated by the gNB-CU. When receiving a UE CONTEXT MODIFICATION REQUEST (UE context modification request) message, the distributed unit of the gNodeB (gNB-DU) executes the modification and, if successful, reports the update in a UE CONTEXT MODIFICATION RESPONSE (UE context modification response) message.

[0004] In Release 18, 3GPP (registered trademark) agreed on a work item (WI) related to further new radio (NR) mobility enhancements, particularly in the technical area titled L1 / L2-based inter-cell mobility. See the WI description (WID) of RP-213565 (https: / / www.3gpp.org / ftp / TSG_RAN / TSG_RAN / TSGR_94e / -Docs / / RP-213565.zip, last accessed on June 15, 2022).

[0005] According to WID, a serving cell change must be performed at some point when a UE moves from the coverage area of ​​one cell to another. Current serving cell changes are triggered by Layer 3 (L3) measurements and involve a reconfiguration triggered by Radio Resource Control (RRC) signaling, along with synchronization for the primary cell (PCell) and primary secondary cell (PSCell) changes, as well as a release addition for the secondary cell (SCell) where applicable. All cases involve a complete L2 and L1 reset. Beam Switch Mobility This leads to longer latency, greater overhead, and longer downtime. The goal of L1 / L2 mobility extension is to enable serving cells to be modified via L1 / L2 signaling in order to reduce latency, overhead, and downtime.

[0006] The goal is to define L1 / L2-based inter-cell mobility mechanisms and procedures for reducing mobility delays. ○ Configuration and maintenance for multiple candidate cells to enable rapid application of configurations for candidate cells [RAN2, RAN3] ○ Dynamic switching mechanism between candidate serving cells (including special cells (SpCell) and SCell) for potentially applicable scenarios based on L1 / L2 signaling [RAN2, RAN1] ○L1 measurement and reporting, and L1 extensions for inter-cell beam management including beam indication [RAN1, RAN2] *Note 1: Early involvement of RAN2 is needed, including the possibility of further clarifying the interaction between this bullet point and the previous bullet point. ○ Timing advance management [RAN1, RAN2] ○CU-DU interface signaling [RAN3] to support L1 / L2 mobility as needed. Note 2: Extensions specific to frequency range 2 (FR2) are not excluded if they exist. Note 3: The L1 / L2-based inter-cell mobility procedure is applicable to the following scenarios: • Standalone, carrier aggregation (CA), and new wireless dual connectivity (NR-DC) cases involving serving cell changes within a single configured grant (CG) • IntraDU case and IntraCU interDU case (applicable to standalone and CA types: no new RAN interface is expected) Both intra-frequency and inter-frequency • Both frequency range 1 (FR1) and FR2 • Source and target cells may or may not be synchronized.

[0007] Currently, there are one or more challenges. For example, as explained above, mobility delay Among the goals of L1 / L2-based inter-cell mobility to reduce the gaps between cells is CU-DU interface signaling to support L1 / L2 mobility, where necessary. The following scenarios are also mentioned: intra-DU cases and intra-CU • InterDU case (applicable to standalone and CA types).

[0008] For UEs in RRC_CONNECTED, it is unclear what criteria the network uses to determine when to configure a UE with L1 / L2 mobility candidates. Furthermore, in a radio access network (RAN) segmented architecture, it is unclear how CUs and DUs interact to configure the UE with L1 / L2 mobility candidates and other necessary configurations to support L1 / L2 mobility, such as channel state information (CSI) measurements (e.g., CSI-MeasConfig). Another issue arises when a UE has limitations on the maximum number of L1 / L2 inter-cell mobility candidates it can configure (e.g., K1), and the DU to which the UE is connected (serving DU) may configure more than K1 candidates. In this case, it is unclear how to determine which L1 / L2 inter-cell mobility candidate cells the UE should configure. [Overview of the Initiative]

[0009] In some aspects of this book and its embodiments, solutions to these or other problems may be provided. For example, this method and system are for configuring L1 / L2-based inter-cell mobility for a UE in the RRC_CONNECTED state. According to some embodiments, the decision to configure one or more L1 / L2-based inter-cell mobility candidates is based on measurement reports, which are reported by the UE and received at the CU via the DU.

[0010] According to some embodiments, the method by the UE includes sending a measurement report containing one or more measurements associated with one or more cells to a connected state for configuring L1 / L2-based inter-cell mobility. The UE receives an RRC reconfiguration message containing the configuration of at least one L1 / L2-based inter-cell mobility candidate cell. The UE sends an RRC Reconfiguration Complete message.

[0011] According to some embodiments, a connected UE for configuring L1 / L2-based inter-cell mobility is adapted to transmit a measurement report containing one or more measurements associated with one or more cells. The UE is adapted to receive an RRC reconfiguration message containing the configuration of at least one L1 / L2-based inter-cell mobility candidate cell. The UE is adapted to transmit an RRC reconfiguration complete message.

[0012] According to some embodiments, a method by a CU for configuring L1 / L2-based inter-cell mobility for a connected UE includes sending at least one request to a candidate DU for configuring L1 / L2-based inter-cell mobility for the UE. The at least one request indicates at least one L1 / L2-based inter-cell mobility candidate cell. The CU receives from the candidate DU at least one configuration of an L1 / L2-based inter-cell mobility candidate cell. The CU sends an RRC Reconfiguration to the candidate DU to be sent to the UE, the RRC Reconfiguration including at least one configuration of an L1 / L2-based inter-cell mobility candidate cell. The CU receives from the candidate DU confirmation of completion of the RRC Reconfiguration from the UE.

[0013] According to some embodiments, a CU for configuring L1 / L2-based inter-cell mobility for a connected UE is adapted to send at least one request to a candidate DU for configuring L1 / L2-based inter-cell mobility for the UE. The at least one request indicates at least one L1 / L2-based inter-cell mobility candidate cell. The CU is adapted to receive at least one configuration of the L1 / L2-based inter-cell mobility candidate cell from the candidate DU. The CU is adapted to send an RRC reconfiguration to the candidate DU to be sent to the UE, the RRC reconfiguration including at least one configuration of the L1 / L2-based inter-cell mobility candidate cell. The CU is adapted to receive from the candidate DU that the RRC reconfiguration is complete from the UE.

[0014] According to some embodiments, a method by a candidate DU for configuring L1 / L2-based inter-cell mobility for a connected UE includes receiving at least one request from a CU to the candidate DU for configuring L1 / L2-based inter-cell mobility for the UE. The at least one request indicates at least one L1 / L2-based inter-cell mobility candidate cell. The candidate DU sends at least one configuration of the L1 / L2-based inter-cell mobility candidate cell to the CU. The candidate DU receives RRC reconfiguration from the CU. RRC reconfiguration includes at least one configuration of the L1 / L2-based inter-cell mobility candidate cell. The candidate DU receives RRC reconfiguration completion from the UE and sends RRC reconfiguration completion from the UE to the CU.

[0015] According to some embodiments, a target DU for configuring L1 / L2-based inter-cell mobility for a connected UE is adapted to receive at least one request from a CU for a candidate DU for configuring L1 / L2-based inter-cell mobility for the UE. The at least one request indicates at least one L1 / L2-based inter-cell mobility candidate cell. The candidate DU is adapted to send at least one configuration of the L1 / L2-based inter-cell mobility candidate cell to the CU. The candidate DU is adapted to receive RRC reconfiguration from the CU. RRC reconfiguration includes at least one configuration of the L1 / L2-based inter-cell mobility candidate cell. The candidate DU is configured to receive RRC reconfiguration completion from the UE and send RRC reconfiguration completion from the UE to the CU.

[0016] Certain embodiments may provide one or more of the following technical advantages. For example, some embodiments may provide the technical advantage of defining CU-DU interface signaling to support more knowledgeable L1 / L2 mobility configurations, since the UE is based on measurement reports when it is in the RRC_CONNECTED state. A clear advantage is when the UE has a limit on a maximum number (e.g., K1) of L1 / L2 inter-cell mobility candidates, and the DU to which the UE is connected may constitute more than K1 candidates, and as a result, the content of the measurement report indicates which candidate is best. For example, the measurement report may indicate the one with the strongest / highest reference signal received power (RSRP) and / or reference signal received quality (RSRQ) and / or signal-to-interference noise ratio (SINR). Thus, a technical advantage may be that, according to some embodiments, the configuration of L1 / L2 inter-cell mobility candidates does not exceed the UE's capabilities.

[0017] As another example, some embodiments may offer the technical advantage of enabling a UE connected to a CU and DU in the RRC_CONNECTED state to receive an RRC reconfiguration prepared by both the CU and DU in the RAN (e.g., NG-RAN) that includes the configuration necessary to perform L1 / L2-based inter-cell mobility. For example, according to some embodiments, the configuration of an L1 / L2 inter-cell mobility candidate is generated by the DU, which is the same DU to which the UE is connected, and the same DU reconfigures the CSI measurement configuration necessary to support L1 / L2 inter-cell mobility, such as reconfiguring the UE to perform CSI measurements on one or more L1 / L2 inter-cell mobility candidates and report these measurements, so that the network (e.g., DU) can make more knowledge-based mobility decisions for L1 / L2 inter-cell mobility. Therefore, in a RAN partitioned architecture, it may be a technical advantage to reveal how the CU and DU interact to configure the UE with L1 / L2 mobility candidates and other necessary configurations to support L1 / L2 mobility, such as the configuration of CSI measurements (e.g., CSI-MeasConfig).

[0018] Other advantages will be readily apparent to those skilled in the art. Certain embodiments may have none of, some of, or all of the listed advantages. [Brief explanation of the drawing]

[0019] For a more complete understanding of the disclosed embodiments, as well as their features and advantages, refer to the following description in conjunction with the accompanying drawings.

[0020] [Figure 1] This demonstrates the successful operation of the UE context modification procedure. [Figure 2] This illustrates an exemplary partitioned architecture having both an NG-Radio Access Network (NG-RAN) and a fifth-generation core (5GC) according to a specific embodiment. [Figure 3] shows possible deployment scenarios of a logical gNB / en-gNB according to a particular embodiment. [Figure 4] shows an exemplary architecture for separating gNB-CU-CP and gNB-CU-UP according to a particular embodiment. [Figure 5] shows an exemplary signaling flow for configuring UE402 in the RRC_CONNECTED state for L1 / L2 mobility according to some embodiments. [Figure 6] shows an exemplary signaling flow for a UE, a CU, and a DU according to a particular embodiment. [Figure 7] shows another exemplary signaling between a UE, a DU, and a CU, by which a single procedure can be triggered to configure multiple L1 / L2 inter-cell mobility candidates according to some embodiments. [Figure 8] shows an exemplary communication system according to a particular embodiment. [Figure 9] shows an exemplary UE according to an embodiment. [Figure 10] shows an exemplary network node according to an embodiment. [Figure 11] shows a block diagram of a host according to a particular embodiment. [Figure 12] shows a virtualization environment in which functions implemented by some embodiments can be virtualized according to an embodiment. [Figure 13] shows a host that communicates with a UE via a partial radio connection and via a network node according to a particular embodiment. [Figure 14] shows a method by a UE in a connected state for configuring L1 / L2-based inter-cell mobility according to a particular embodiment. [Figure 15] shows a method by a CU for configuring L1 / L2-based inter-cell mobility for a UE in a connected state according to some embodiments. [Figure 16]This describes a method by candidate DUs for configuring L1 / L2-based inter-cell mobility for connected UEs, according to several embodiments. [Modes for carrying out the invention]

[0021] Herein, some embodiments intended in this specification will be described more fully with reference to the accompanying drawings. Embodiments are provided as examples to convey the scope of the subject to those skilled in the art.

[0022] As used herein, “node” may be a network node or UE. Examples of network nodes include node B, base station (BS), multistandard radio (MSR) radio nodes such as MSR BS, enode B (eNB), gnode B (gNB), master eNB (MeNB), secondary eNB (SeNB), integrated access backhaul (IAB) node, network control unit, and radio network. control device (RNC), base station control unit (BSC), repeater, donor node control repeater, Base transceiver Station (BTS), Central Unit (e.g., within a gNB), Distributed Unit (e.g., within a gNB), Baseband Unit, Centralized Baseband, C-RAN, Access Point (AP), Transmitting Point, Transmitting Node, Remote Radio Unit (RRU), Remote Radio Head (RRH) 、 These include nodes in a distributed antenna system (DAS), core network nodes (e.g., mobile switching centers (MSCs), mobility management entities (MMEs), etc.), operation and maintenance (O&M), operation support systems (OSS), self-organizing networks (SONs), and positioning nodes (e.g., E-SMLCs).

[0023] Another example of a node is the non-restrictive term User Equipment (UE), which refers to any type of wireless device that communicates with network nodes and / or other UEs in a cellular or mobile communication system. Examples of UEs include target devices, device-to-device (D2D) UEs, vehicle-to-vehicle (V2V) UEs, machine-type UEs, MTC UEs, or machine-to-machine communication UEs (M2M), personal digital assistants (PDAs), tablets, mobile devices, smartphones, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), and Unified Serial Bus (USB) dongles.

[0024] According to some embodiments, the general term “wireless network node” or simply “network node (NW node)” is used. It refers to a base station, wireless base station, base transceiver station, base station controller, network control device , evolution Type node B (eNB), node B, gNodeB (gNB), relay It can be any type of network node, which may include nodes, access points, wireless access points, remote radio units (RRUs), remote radio heads (RRHs), central units (e.g., in a gNB), distributed units (e.g., in a gNB), baseband units, centralized baseband, C-RAN, access points (APs), etc.

[0025] The term Radio Access Technology (RAT) is used, for example, in Universal Terrestrial Radio Access Network (UTRA). evolution This can refer to any RAT such as Universal Terrestrial Radio Access Network (E-UTRA), Narrowband Internet of Things (NB-IoT), WiFi, Bluetooth®, Next Generation RAT, NR, 4G, 5G, etc. Any device referred to by the terms node, network node, or wireless network node may support one or more RATs.

[0026] Figure 2 shows an exemplary partitioned architecture 100 having both NG-RAN (NG-Radio Access Network) and 5GC (Fifth Generation Core) according to several embodiments. As shown in the figure, the NG-RAN is partitioned into CU202 and DU204 via the F1 interface. In this particular example, the RAN is a Next Generation RAN (NG-RAN), which may be called a 5G RAN, but this method is applicable to any RAN, such as a 6G RAN architecture.

[0027] As illustrated, a RAN (e.g., NG-RAN) consists of a set of RAN nodes (e.g., gNBs) connected to a core network (e.g., 5GC) via a RAN / CN interface (e.g., NG interface). In the case of NG-RAN, it may comprise one or more next-generation eNBs (ng-eNBs), which may consist of an ng-eNB-CU and one or more ng-eNB-DUs. A gNB may consist of a gNB-CU and one or more gNB-DUs. The gNB-CU and gNB-DUs are connected via an F1 interface. A gNB-DU may be connected to multiple gNB-CUs by appropriate implementation. While the methods and systems presented herein are applicable to NG-RAN as an example, these methods are also applicable to any RAN architecture, such as a 6G RAN.

[0028] NG, Xn, and F1 are logical interfaces. In the case of NG-RAN, the NG and Xn-C interfaces for the gNB, consisting of gNB-CU and gNB-DU, terminate at gNB-CU. In the case of Evolved UMTS Terrestrial Radio Access Network (UTRAN) New Radio-Dual Connectivity (EN-DC), the S1-U and X2-C interfaces for the gNB, consisting of gNB-CU and gNB-DU, terminate within gNB-CU. The gNB-CU and connected gNB-DU are visible only as gNBs to other gNBs and 5GCs. Figure 3 shows possible deployment scenarios of logical gNB / en-gNB according to a specific embodiment. The protocol terminations of the NG and Xn interfaces are indicated by ellipses, and the terms “central entity” and “distributed entity” as used below refer to physical network nodes.

[0029] Figure 4 shows an exemplary architecture 300 for separating gNB-CU-CP302 and gNB-CU-UP304 in gNB306 according to a particular embodiment. It is recognized that one or more of the following may apply according to various embodiments. *gNB may consist of gNB-CU-CP302, multiple gNB-CU-UP304, and multiple gNB-DU308. *gNB-CU-CP302 can be connected to gNB-DU308 via the F1-C interface. *gNB-CU-UP304 can be connected to gNB-DU308 via the F1-U interface. *gNB-CU-UP304 can be connected to gNB-CU-CP302 via the E1 interface. *One gNB-DU308 can only be connected to one gNB-CU-CP302. *One gNB-CU-UP304 can only be connected to one gNB-CU-CP302. *One gNB-DU308 can be connected to multiple gNB-CU-UP304s under the control of the same gNB-CU-CP302. *A single gNB-CU-UP304 can be connected to multiple gNB-DU308s under the control of the same gNB-CU-CP302. Therefore, when this method refers to a CU, it includes actions performed by any entity contained within the CU (e.g., CU-CP, gNB-CU-CP).

[0030] The text herein refers to the term “L1 / L2-based inter-cell mobility” as used in the 3GPP® work item descriptions, but it is recognized that the text herein may also use the terms L1 / L2 mobility, L1 mobility, L1-based mobility, L1 / L2-centric inter-cell mobility, or L1 / L2 inter-cell mobility interchangeably. The basic principle is that a UE receives lower-layer signaling from the network indicating a change in its serving cell (e.g., a PCell change from source to target PCell), and lower-layer signaling is the message / signaling of a lower-layer protocol. Lower-layer protocol refers to a lower-layer protocol in the air interface protocol stack, compared to an RRC protocol (e.g., media access control (MAC)), and since RRC in the air interface protocol stack is “lower,” it is considered a lower-layer protocol, in which case lower-layer signaling / messages may correspond to MAC control elements (MAC CEs). Another example of a lower-layer protocol is Layer 1 (or physical layer L1), in which case lower-layer signaling / messages may correspond to downlink control information (DCI). Signaling information at protocol layers lower than RRC reduces processing time, consequently reducing downtime during mobility, and may also increase mobility robustness as the network can respond more quickly to changes in channel conditions. Another relevant aspect in L1 / L2 inter-cell mobility is that in multi-beam scenarios, a cell may be associated with multiple SSBs, and different SSBs may be transmitted in different spatial directions (i.e., using different beams across the cell's coverage area) during a half-frame. reasonHowever, it may be applicable to Channel State Information Reference Signal (CSI-RS) resources, which can also be transmitted in different spatial directions. Thus, in L1 / L2 inter-cell mobility, reception of lower-layer signaling indicates to the UE that one beam in the serving cell is being changed to another beam in an adjacent cell (which is a configured candidate cell), and that this is changing the serving cell.

[0031] In this specification, the term “L1 / L2 inter-cell mobility candidate cell” refers to a cell in which a UE is configured when configured using L1 / L2 inter-cell mobility. That is, it is a cell in which, upon receiving lower-layer signaling, the UE can move in the L1 / L2 inter-cell mobility procedure. These cells may also be called candidate cells, candidates, mobility candidates, non-serving cells, additional cells, etc.

[0032] The text herein refers to configurations generated by the DU, encapsulated in RRC reconstruction messages received by the UE when configured with L1 / L2 inter-cell mobility while in the RRC_CONNECTED state after sending a measurement report. Configurations are Includes one or more of the following: : • At least one CSI measurement configuration A single CSI measurement configuration includes the configuration / reconfiguration of CSI reports and / or measurement resources and / or triggers associated with one or more L1 / L2 inter-cell mobility candidates. It reconfigures / configures the UE to measure signals such as the synchronous signaling block (SSB) and / or CSI-RS resources of the L1 / L2 inter-cell mobility candidates. In an exemplary scenario where the UE is already operating in the RRC_CONNECTED state and has received at least one CSI measurement configuration, the UE may already have the CSI measurement configuration memorized, and consequently, the received at least one CSI measurement configuration may include a reconfiguration encoded in the RRC as a delta signal, where only newly applied parameters, fields, information elements (IE) and configurations provided are those associated with the measurement of the L1 / L2 inter-cell mobility candidate (e.g., the synchronous signaling block (SSB) index for the candidate), while memorized elements (e.g., those for which M codes need to be defined) remain memorized, and the UE continues to operate according to them. • The measurement resources that are configured / reconfigured (e.g., added by the network and measured by the UE) include one or more of the following: i) The UE searches And, find To enable this, an indication (e.g., indicated by an absolute or relative frequency offset such as ARFCN) showing at least one frequency of the signal (e.g., SSB and / or CSI-RS, TRS) of the L1 / L2 inter-cell mobility candidate, and / or, ii) cell identifier or identification information (e.g., physical cell identification information (PCI)), and / or, iii) one or more signal indices (e.g., SSB index and / or CSI-RS resource index), and / or, iv) a cell index encoded to fewer bits than the cell identifier and mapped thereto. • At least one CSI measurement configuration is used to reconfigure / set up the CSI-RS belonging to a candidate cell (e.g., a serving cell) that contains the CSI-MeasConfig. A CSI report that will be transmitted on the uplink control channel (e.g., the physical uplink control channel (PUCCH)) in the serving cell, which includes the CSI-MeasConfig for CSI measurements on L1 / L2 inter-cell mobility candidate cells. A CSI report on the physical uplink sharing channel (PUSCH) triggered by the DCI received in the serving cell, which includes the CSI-MeasConfig, but for measurements on L1 / L2 inter-cell mobility candidates. • The first cell group configuration associated with the current PCell in which the UE is operating in the RRC_CONNECTED state. The first cell group configuration includes the reconfiguration of the current PCell, which is a cell that has already been configured for the UE to operate in the RRC_CONNECTED state, and the configuration of one or more SCells associated with that first cell group. The first cell group configuration corresponds to a master cell group (MCG) and is provided to the UE in an IE called CellGroupConfig, as defined in 3GPP® TS 38.331. The current PCell configuration within the first cell group configuration is provided to the UE in the IE parameter called SpCellConfig. If at least one CSI measurement configuration for L1 / L2 inter-cell mobility is not present in CellGroupConfig, the UE may receive at least one CSI measurement configuration in a message not included in the first cell group configuration for operation with the current PCell / SpCell. • Configuration of at least one candidate cell for L1 / L2-based inter-cell mobility At least one of the L1 / L2-based inter-cell mobility candidate cells includes a configuration in which the UE must act accordingly when performing (implementing) L1 / L2 inter-cell mobility to that L1 / L2-based inter-cell mobility candidate cell upon receiving lower-layer signaling indicating L1 / L2-based inter-cell mobility to that L1 / L2-based inter-cell mobility candidate cell (which will be the target cell and the current (new) PCell, or SCell at the serving frequency). If the UE consists of multiple candidates, the DU generates multiple configurations (e.g., for each L1 / L2-based inter-cell mobility candidate cell) and sends them to the CU. The configuration of an L1 / L2-based inter-cell mobility candidate cell includes parameters for the serving cell (or multiple serving cells) and one or more groups of parameters within an IE called SpCellConfig (or SCellConfig for secondary cells): ○ Cell index (e.g., encoded with fewer bits than the cell identifier of an L1 / L2 intercellular mobility candidate cell). This can be a field in an IE called ServCellIndex or an IE called CandidateCellIndex, namely "servCellIndex" or "candidateCellIndex". Once configured, the index may later be referenced, for example, i) in lower-layer signaling that indicates to the UE that it is an L1 / L2 intercellular mobility candidate cell that needs to be moved in an L1 / L2 intercellular mobility procedure, and / or ii) in RRC messages indicating some action on that particular candidate cell. ○The cell configuration for a UE corresponding to the configuration of an L1 / L2-based inter-cell mobility candidate cell is called a dedicated configuration as a parameter and is possibly tailored for that particular UE according to UE capabilities / radio capabilities. The configuration may include further parameters defined in an IE called ServingCellConfig, such as the frequency configuration of the downlink and uplink (including the bandwidth part), L1 control channels (PDCCH, CORESET(pl) and PUCCH), and L1 data channels (PDSCH and PUSCH, etc.), and other parameters defined in an IE called ServingCellConfig as specified in 3GPP® TS 38.331. The cell configuration, sometimes called a cell-specific configuration or a common cell configuration, corresponds to the L1 / L2-based inter-cell mobility candidate cell configuration in IE called ServingCellConfigCommon. This can be provided within IE as ReconfigurationWithSync, or separately. This configuration includes, for example, a random access configuration for the UE to access target candidates as needed. ○Radio Link Failure Configuration. This involves Timer T310, Counter N310, Counter N311, and / or, Values ​​for timer N311, etc. ○ At least one UE identifier for identifying a UE within a candidate L1 / L2-based inter-cell mobility cell, e.g., a Cell Radio Network Temporary Identifier (C-RNTI). If the UE is configured with multiple L1 / L2 intercellular mobility candidate cells, the DU generates multiple sets of serving cell parameters, each containing one or more groups of parameters within an IE called SpCellConfig, and sends them to the CU. For example, the UE might receive a list of IEs, one SpCellConfig for each L1 / L2 intercellular mobility candidate. The configuration of L1 / L2-based inter-cell mobility candidate cells may be a SpCell configuration (e.g., PCell configuration) provided as part of a cell group configuration, which may further include one or more SCell configurations and additional cell group-specific configurations (such as a cell group identifier, physical layer configuration for the cell group, MAC layer configuration for the cell group, and simultaneous TCI state configuration for the cell group). ○In this case, the UE is configured using a cell group configuration for each candidate. Therefore, one alternative is a UE to receive one configuration for each cell group candidate, where the configuration of the L1 / L2-based inter-cell mobility candidate cell is the SpCell candidate configuration within that group. Lower-layer signaling then indicates to the UE to change to the configured cell group candidate (e.g., apply the cell group configuration for that candidate (e.g., from MCG configuration A to MCG configuration B)). If the UE is composed of multiple candidates, the DU generates multiple cell group configurations, each associated with a different L1 / L2 inter-cell mobility candidate (e.g., a list of IEs called CellGroupConfig), and sends them to the CU. Candidate L1 / L2 inter-cell mobility may use the same frequency as the current PCell, or it may use a different frequency. Candidates for L1 / L2 cell-to-cell mobility can be SCell candidates.

[0033] According to some embodiments disclosed herein, methods and systems are provided by a UE, a DU (e.g., gNB-DU308) at a RAN node in a RAN (e.g., NG-RAN), and a CU (e.g., gNB-CU302~304) at a RAN node to configure L1 / L2-based inter-cell mobility for a UE in the RRC_CONNECTED state. According to some embodiments, the decision to configure one or more L1 / L2-based inter-cell mobility candidates is based on measurement reports reported by the UE and received at the CU via the DU.

[0034] According to several embodiments, one example is a case in which the UE is connected to a source DU (serving DU) and a CU. For example, upon receiving (one or more) measurement reports via the RRC, the source CU configures one or more L1 / L2 intercellular mobility candidates in the UE. The source CU then requests the source DU to configure one or more L1 / L2 intercellular mobility candidates, i.e., the source DU is requested to also operate as a DU with L1 / L2 intercellular mobility candidate cells.

[0035] According to a particular embodiment, the source CU determines which cells to request from the DU, and the DU generates a configuration for the accepted cells, which is provided to the CU and the UE.

[0036] According to another specific embodiment, when a source DU receives a message from a CU containing one or more measurements or an entire measurement report, it determines which cells to configure as L1 / L2 inter-cell mobility candidates, and the DU generates a configuration for the accepted cells to be provided to the CU and the UE.

[0037] According to a particular embodiment, the UE may be configured with a maximum number of L1 / L2 intercellular mobility candidates that are less than the number of cells for L1 / L2 intercellular mobility in the DU to which the UE is connected (e.g., K1).

[0038] Several examples of how signaling can be implemented in RRC for the configuration of L1 / L2-based inter-cell mobility candidate cells in various embodiments are provided below. These models are described as RRC models for L1 / L2-based inter-cell mobility.

[0039] For example, an RRC model that includes exemplary signaling for additional cell-by-cell RRCReconfiguration (RRC reconfiguration) may be as follows: RRCReconfiguration-IE ::= SEQUENCE ( radioBearerConfig RadioBearerConfig masterCellGroup OCTET STRING (CONTAINING CellGroupConfig) measConfig MeasConfig [...] } ... RRCReconfiguration-IE ::= SEQUENCE ( radioBearerConfig RadioBearerConfig masterCellGroup OCTET STRING (CONTAINING CellGroupConfig) measConfig MeasConfig [...] } In this scenario, the UE receives multiple (list-format) RRC messages (i.e., RRCReconfiguration messages) within a single RRCReconfiguration message. Each RRCReconfiguration message identifies the configuration of an L1 / L2-based inter-cell mobility candidate cell, which is stored by the UE and applied / used / activated when it receives lower-layer signaling for L1 / L2 inter-cell mobility. This model allows the target node complete flexibility in modifying / releasing / retaining any parameters / fields within the RRCReconfiguration message, such as measurement configurations and bearers, as is the case with L3 reconfiguration.

[0040] As another example, an RRC model that includes exemplary signaling for additional per-cell CellGroupConfig(PCell frequency) may be as follows: RRCReconfiguration-IE ::= SEQUENCE ( radioBearerConfig RadioBearerConfig masterCellGroup OCTET STRING (CONTAINING CellGroupConfig) measConfig MeasConfig addMCG-AddModList SEQUENCE (SIZE (1...K)) OF ADD-MCG-ADDmod [...] } According to this model, the UE receives a list of IEs called CellGroupConfig within the RRCReconfiguration message, each of which identifies the configuration of a candidate cell for L1 / L2-based inter-cell mobility. Each CellGroupConfig IE is stored in the UE and applied / used / activated when it receives lower-layer signaling for L1 / L2 inter-cell mobility. This model allows the target node to modify / release / retain any parameters / fields that are part of the CellGroupConfig IE while the rest of the RRCReconfiguration message (i.e., where the CellGroupConfig IEs are received by the UE) remains unchanged. This means, for example, that measurement configurations, bearers, and security remain the same and are not modified by the target node.

[0041] As another example, an RRC model that includes exemplary signaling for K SpCellConfig(s) per cell (PCell frequency) may be as follows: CellGroupConfig ::= SEQUENCE ( cellGroupId, cellGroupId, rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC- BearerConfig rlc-BearerToReleaseList SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentity mac-CellGroupConfig MAC-CellGroupConfig physicalCellGroupConfig PhysicalCellGroupConfig spCellConfig SpCellConfig spCellToAddModList SEQUENCE (SIZE (1..K)) OF SpCellConfig sCellToAddModList SEQUENCE (SIZE (1..maxNrofScells) OF SCellConfig [...] } According to this model, the UE receives K SpCellConfigs per cell as configurations for L1 / L2-based inter-cell mobility candidate cells. This solution provides minimal flexibility to the target node, as only cell-specific parameters (e.g., bandwidth part, downlink, and uplink configurations) can be modified / released / retained.

[0042] As another example, an RRC model containing exemplary signaling for K PCIs (or more) within the same PCell (e.g., SpCellConfig) could be as follows: TCI-State ::= SEQUENCE ( tci-StateId TCI-StateId, qcl-Type1 QCL-Info, [...] } QCL-Info ::= SEQUENCE ( [...] referenceSignal CHOICE { csi-rs NZP-CSI-RS-ResourceId, SSB Index [...] } cellIndexReferenceSignal ServeCellIndex [...] }

[0043] According to this model, the UE receives K ServingCellConfigCommon(option d) per cell as the configuration of L1 / L2-based inter-cell mobility candidate cells. This solution provides minimal flexibility to the target node, as only cell-specific parameters (e.g., bandwidth part, downlink, and uplink configuration) can be modified / released / retained.

[0044] As another example, an RRC model with exemplary signaling for K SpCellConfig / ServingCellConfigCommon per cell could look like this: CellGroupConfig ::= SEQUENCE { [_] / / Omitted for simplification spCellConfig SpCellConfig addSpCellToAddModList SEQUENCE (SIZE (1...K) OF AddSpCellConfig [..] } AddSpCell Config ::= SEQUENCE { additionalSpCellIndex ServCellIndex additionalSpCellConfig SpCellConfig, additionalSpCellCommon ServingCellconfigCommon } According to this model, the UE receives K ServingCellConfigCommons per cell as the configuration for L1 / L2-based inter-cell mobility candidate cells. This solution provides minimal flexibility to the target node, as only cell-specific parameters (e.g., bandwidth part, downlink, and uplink configuration) can be modified / released / retained.

[0045] As another example, an RRC model with exemplary signaling for K ServingCellConfigCommons, one per cell, could be as follows: CellGroupConfig ::= SEQUENCE { [_] / / Omitted for simplification spCellConfig SpCellConfig addSpCellToAddModList SEQUENCE (SIZE (1...K) OF AddSpCellConfig [..] } AddSpCell Config ::= SEQUENCE { additionalSpCellIndex ServCellIndex additionalSpCellCommon ServingCellconfigCommon } According to this model, multiple PCIs are configured for the same TCI state configuration, and each PCI identifies the configuration of an L1 / L2-based inter-cell mobility candidate cell. This is a method that offers no flexibility at all, as all parameters / fields used to configure the L1 / L2-based inter-cell mobility candidate cell configuration are fixed, and only changes to the PCI, scramble ID, and C-RNTI are allowed on the target node.

[0046] Figure 5 shows an exemplary signaling flow 400 for configuring L1 / L2 mobility to UE402 in the RRC_CONNECTED state, according to several embodiments. Specifically, Figure 6 shows the signaling flow for UE402, CU404, and DU406, which includes the following steps, serving as a reference to various different embodiments.

[0047] 1. A UE402 capable of performing L1 / L2 inter-cell mobility transmits or sends a measurement report that includes one or more measurements (measurements) of one or more cells that could be candidate cells for L1 / L2 inter-cell mobility at a first frequency. According to certain embodiments, the measurement report is sent after Access Layer (AS) security is activated. According to a particular embodiment, the Measurement Report is an RRC Measurement Report message containing one or more measurements, for example, an IE called MeasResult as defined in 3GPP® TS 38.331. One or more measurements of one or more cells at a first frequency may be measurements of a cell at the same frequency (or a different frequency) as a special cell (SpCell) / primary cell (PCell) of a master cell group, or measurements of an intra-frequency adjacent cell of a PCell, or measurements of an adjacent cell of a SCell configured in an MCG and / or SCG. According to a particular embodiment, one or more measurements may be one or more of the following: Cell measurements or measurement results, such as per cell RSRP, and / or per cell RSRQ, and / or per cell SINR, based on a reference signal (e.g., CSI-RS) and / or a synchronization signal (e.g., SSB). Beam measurements or measurement results, such as per cell RSRP, and / or per cell RSRQ, and / or per cell SINR, based on a reference signal (e.g., CSI-RS) and / or synchronization signal (e.g., SSB). Beam measurements may be associated with a signal index / identifier or reference signal index / identifier, such as an SSB index or CSI-RS resource index / indicator. According to some embodiments, the measurement report is a CSI report, which is transmitted over the uplink channel of a PCell or one configured SCell(s), via the physical layer also known as L1, such as PUSCH or PUCCH in UL channel format, containing one or more measurements or information derived from one or more measurements of one or more L1 / L2 inter-cell mobility candidate cells. One or more measurements of one or more L1 / L2 inter-cell mobility candidate cells at a first frequency may be measurements of a cell at the same frequency (or a different frequency) as a special cell (SpCell) of a master cell group / primary cell (PCell), or measurements of an intra-frequency adjacent cell of the PCell. According to one embodiment, one or more measurements include one or more of the following: • Cell measurements or measurement results, such as per cell RSRP, and / or per cell RSRQ, and / or per cell SINR, based on a reference signal (e.g., CSI-RS) and / or synchronization signal (e.g., SSB). Beam measurements or measurement results, such as per cell RSRP, and / or per cell RSRQ, and / or per cell SINR, based on a reference signal (e.g., CSI-RS) and / or synchronization signal (e.g., SSB). Beam measurements may be associated with a signal index / identifier or reference signal index / identifier, such as an SSB index or CSI-RS resource index / indicator. According to some embodiments, the measurement report (whether it is a CSI report or an RRC measurement report message) contains a number of measurements equal to the number of L1 / L2 inter-cell mobility candidate cells supported by the UE, and includes measurements for one or more cells at a given frequency. This means that the UE can, based on its capabilities, keep remembering (or applying) only a limited number of L1 / L2 inter-cell mobility candidate cells. Alternatively, the measurement report (whether it is a CSI report or an RRC measurement report message) contains a number of measurements equal to the number of L1 / L2 inter-cell mobility candidate cells supported by the UE, and includes measurements for one or more cells across all configured frequencies. This means that the UE can, based on its capabilities, keep remembering (or applying) only a limited number of L1 / L2 inter-cell mobility candidate cells. According to a particular embodiment, the UE may decide to include in its measurement report only a number of measurements equal to one of the number of L1 / L2 intercellular mobility candidate cells supported by the UE. According to another specific embodiment, the UE may decide to include the number of measurements in a separate structure within the measurement report (e.g., IE in ASN.1, SEQUENCE, field) to indicate that the number is also the number of L1 / L2 intercellular mobility candidate cells supported by the UE. The UE may also include the remaining measurements in yet another structure (e.g., IE in ASN.1, SEQUENCE, field). According to a particular embodiment, the UE may decide to include one or more available measurements in the measurement report, but may also decide to include the number of L1 / L2 intercellular mobility candidate cells supported by the UE in a separate structure (e.g., a field or IE in ASN.1). According to some embodiments, before sending a measurement report, the UE receives a first message containing a measurement configuration, which may include a reporting configuration associated with a trigger criterion, where the measurement report is triggered when the trigger criterion is met. ·According to a particular embodiment, the measurement report corresponds to the RRC measurement report, the measurement configuration corresponds to an IE called MeasConfig received in an RRC message (e.g., RRCReconfiguration (RRC Reconfiguration)), and the report configuration corresponds to an IE called ReportConfig (trigger) which can configure periodic measurement reports. basis The condition is the expiration of the timer and / or the configured periodicity, and / or an event trigger for an event such as A4 or A3. measurement You can configure recurring reports (where reportType is set to "eventTriggered"), and as a result, triggers basis The standard is defined in 3GPP(registered trademark) TS 38.331 as an event entry Conditions (e.g., trigger a parameter) vinegar This will satisfy the requirement of measuring a better offset on an adjacent cell than the measurement on the PCell over a period longer than the time configured for this purpose. ○In the case of A4, the trigger condition for sending a measurement report is that for one or more measurements such as RSRP, RSRQ, and / or SINR, at least one adjacent cell (or possible L1 / L2 inter-cell mobility candidate) is better than the threshold (configured as part of the event configuration). In other words, if the UE has at least one cell whose measurement satisfies the A4 condition ( 3 GPP(registered trademark) TS 38.331, §5.5.4 In detail The defined A4 entry conditions ) If detected, the UE sends an RRC measurement report, including one or more measurements for at least one cell. The reason here is that a cell that can trigger the report is considered an adjacent cell that is not a PCell, and it is a cell in which the UE has configured a frequency within the PCell frequency. The measurement target for an adjacent cell is the same frequency as the PCell in the case of an intra-frequency. ○In the case of A3, the trigger condition for sending a measurement report is that at least one adjacent cell (or possible L1 / L2 inter-cell mobility candidate) is offset better than the SpCell (which is a PCell in the case of single connectivity), and the offset (or threshold, hysteresis) is configured as part of the event configuration for one or more measurements such as RSRP, RSRQ, and / or SINR. In other words, if the UE detects at least one cell whose measurement satisfies the A3 condition (details fall into the conditions for A3 as defined in 3GPP® TS 38.331, §5.5.4) (i.e., an adjacent cell whose measurement is better than the PCell measurement), the UE sends an RRC measurement report, including one or more measurements for at least one cell. The reason here is that a cell that can trigger a report is considered an adjacent cell since it is not a PCell, and it is a cell for which the UE has a frequency within the PCell frequency. The measurement target of an adjacent cell is the same frequency as the PCell, if it is within the frequency. According to a particular embodiment, the measurement report may correspond to a CSI report, and the measurement configuration may correspond to an IE called CSI-MeasConfig received in an RRC message (e.g., RRCReconfiguration), which includes a report configuration corresponding to an IE called CSI-ReportConfig (CSI report configuration) that constitutes periodic, non-periodic, semi-persistent, and / or event-triggered CSI reports. In the case of an event trigger, the conditions may be similar to those defined for RRC measurement reports. · According to a particular embodiment, the measurement report may correspond to an RRC measurement report or a CSI report, and the measurement configuration may include priority values ​​for each cell based on the fact that the UE should measure one or more cells at a first frequency. Alternatively, the measurement configuration may include priority values ​​per frequency based on the frequencies at which the UE should measure one or more cells for which priority needs to be prioritized. The highest priority value may mean that the cell or frequency should be measured first by the UE, or the lowest priority value may mean that the cell or frequency should be measured first by the UE. In this case, the measurement report may include one or more measurements of one or more cells at a first frequency, which may be measurements of a cell at the same frequency (or a different frequency) as a special cell (SpCell) of a master cell group / primary cell (PCell), or measurements of intra-frequency adjacent cells of a PCell, or measurements of adjacent cells of a configured SCell of an MCG or / and SCG that are prioritized based on the priority configured by the measurement configuration.

[0048] 2. A DU (e.g., gNB-DU) receiving a measurement report includes the measurement report (e.g., RRC Measurement Report message) in a UL RRC MESSAGE TRANSFER message to a CU (e.g., gNB-CU), and sends the received measurement report (e.g., MeasurementReport message) to the CU. The CU receives the measurement report encapsulated within the UL RRC MESSAGE TRANSFER message from the DU. According to a particular embodiment, upon receiving a measurement report, the CU decides to configure one or more L1 / L2 intercellular mobility candidate cells in the UE. The CU may make this decision based on the capabilities of at least one UE associated with L1 / L2 intercellular mobility for the UE that sent the measurement report. According to a particular embodiment, upon receiving a measurement report, the CU determines one or more L1 / L2 intercellular mobility candidate cells, at least one of which is one of the cells whose measurement is included in the measurement report. According to some embodiments, upon receiving a measurement report, the CU determines one or more L1 / L2 intercellular mobility candidate cells based on the measurement report. According to a particular embodiment, one or more L1 / L2 intercellular mobility candidate cells determined by the CU are the cells in the measurement report with the strongest or highest measured values ​​(e.g., RSRP, RSRQ, and SINR). For example, if a measurement report contains K cells, each with its associated measured values ​​(e.g., K RSRP values), and the UE can configure K1 < K L1 / L2 intercellular mobility candidates, the CU determines that K1 cells are the cells with the K1 strongest / highest RSRP values. The CU may recognize that one of these cells is associated with the DU to which the UE is connected, and that one of these cells can be configured as an L1 / L2 intercellular mobility candidate. According to a particular embodiment, one or more L1 / L2 intercellular mobility candidate cells determined by the CU are measurement reporting cells associated with the current PCell's DU (i.e., the DU currently serving the UE, which may be considered the source DU).

[0049] 3. The CU (e.g., gNB-CU) sends a second message to the RAN's DU (e.g., gNodeB-DU) indicating a request to the DU to configure L1 / L2-based inter-cell mobility to the UE. The request may include at least one cell and / or cell group that are candidates for L1 / L2 inter-cell mobility. The DU receives the second message containing the request. *According to a particular embodiment, upon receiving a measurement report, the CU determines the number of L1 / L2 intercellular mobility candidate cells that can be configured in the UE based on the number of measurements for one or more cells at the frequencies included in the measurement report, and / or based on the UE's capability regarding the maximum number of candidates that can be configured. Alternatively, upon receiving a measurement report, the CU determines the number of L1 / L2 intercellular mobility candidate cells that can be configured in the UE based on the number of measurements for one or more cells across all frequencies included in the measurement report, and / or based on the UE's capability regarding the maximum number of candidates that can be configured. *One procedure for configuring one candidate for each L1 / L2 intercellular mobility candidate: According to some embodiments, the CU sends a second message to the DU in the RAN (e.g., gNodeB-DU), where the DU sends a response to the CU. The second message is received by the DU and indicates a request to the DU to configure one L1 / L2-based intercellular mobility candidate cell in the UE. In response to the second message, the CU receives a third message from the DU containing the configuration of one L1 / L2-based intercellular mobility candidate cell. *One procedure for configuring multiple candidates for each L1 / L2 intercellular mobility candidate: According to one other embodiment, the CU sends several second messages to the DU in the RAN (e.g., gNodeB-DU). Each of the second messages indicates a request to the DU to configure one L1 / L2-based intercellular mobility candidate cell in the UE. The DU receives and responds. In response to each of the second messages, the CU receives a third message from the DU containing the configuration of one L1 / L2-based intercellular mobility candidate cell. *One procedure for configuring multiple candidates for each L1 / L2 intercellular mobility candidate: According to some embodiments, the CU sends a second message to the DU in the RAN (e.g., gNodeB-DU) indicating a request for the DU to configure multiple L1 / L2-based intercellular mobility candidate cells in the UE. The DU receives and responds. In response to the second message, the CU receives a third message from the DU containing one configuration for each of the L1 / L2-based intercellular mobility candidate cells to be configured. *According to some embodiments, the second message is a message used to modify the UE context within the DU, such as a UE context modification request from the CU to the DU (UE context modification request via the F1AP interface). Therefore, when the CU sends it, the CU is requesting the DU to modify the UE context by configuring L1 / L2 inter-cell mobility with one or more L1 / L2 inter-cell mobility candidates. *According to a particular embodiment, the request includes one or more proposed / recommended L1 / L2 intercellular mobility candidate cells. Based on one or more measurements or a subset of one or more measurements, the CU may decide which cells to request the DU to configure (or request the DU to configure) the L1 / L2 intercellular mobility candidate in the UE. Upon receiving the second message, the DU may decide which of the requested cells should be configured for L1 / L2 intercellular base mobility, whether it is a subset of them, all of them, or none of them. The DU may have the option to configure L1 / L2 intercellular mobility candidates not proposed by the CU in the request, in which case the DU indicates the configuration for the L1 / L2 intercellular mobility candidate. *According to a particular embodiment, the request includes one or more measurements, a subset of one or more measurements, or other content from the measurement report. Based on one or more measurements or a subset of one or more measurements, the DU may determine which cells should be configured in the UE as L1 / L2 inter-cell mobility candidates. In one option, the request includes only one or more measurements and no recommended cells, so the DU selects which cells should be configured as L1 / L2 inter-cell mobility candidates. In another option, the request includes both one or more measurements and a recommended list of L1 / L2 inter-cell mobility candidate cells determined by the CU. *According to a particular embodiment, when the CU determines one or more L1 / L2 intercellular mobility candidate cells, the CU sends a second message, where at least one candidate cell is one of the cells included in the measurement report. *According to some embodiments, CU is UE L1 / L2-based inter-cell mobility at least one indication that it is possible Based on that, the second message Request This includes sending a message, which could be an indication received by the CU. According to a particular embodiment, at least one indication is received by the CU from the core network node in the message when a message is received, such as an initial context setup request from the Access and Mobility Function (AMF). The message is transmitted via the NG-1 interface between the RAN and the CN. ○According to a particular embodiment, at least one indication is retrieved from the CU's memory or from another memory in the network (e.g., from within UE context information). ○According to certain embodiments, at least one indication is obtained via an explicit or implicit indication arriving directly from the user device. Explicit indications may be obtained via UE capabilities exchanged (sent and received) with the UE when the first RRC connection with this UE is established, or via explicit indications contained in RRC messages sent by the UE to the CU (via the DU), such as RRC measurement reports. Implicit indications may be obtained by the presence of certain fields, information elements, or structures present in the RRC ASN.1, MAC CE, or SCI, which are used only in the case of L1 / L2-based inter-cell mobility. A message from CU to DU may contain one or more of the following requests: *A set of candidates that are SpCell(s), and / or *A set of candidates that are SCells (multiple SCells are possible), and / or A set of candidate cell groups, including a SpCell L1 / L2 inter-cell mobility candidate and at least one SCell associated with the SpCell L1 / L2 inter-cell mobility candidate. One reason for including SCell candidates is that L1 / L2 inter-cell mobility should work in conjunction with carrier aggregation, and as a result, when performing L1 / L2 inter-cell mobility to a target cell that may be a SpCell candidate, the UE needs to be able to perform carrier aggregation with that SpCell after the L1 / L2 inter-cell mobility is performed.

[0050] 4. Upon receiving the request (in the second message), if the DU decides to accept the request to configure L1 / L2 inter-cell mobility for the UE, the DU will generate one or more of the following (to be later sent to the CU): ○ At least one CSI measurement configuration, ○The configuration of the first cell group associated with the current primary cell (PCell), and, ○ Configuration of at least one candidate cell for L1 / L2-based inter-cell mobility. Next, DU sends a third message to CU. The DU sends one or more of the following in response to one or more requests: *The configuration for each candidate that is a SpCell(s), and / or *The configuration for each candidate that is a SCell(s), and / or * A configuration for each candidate cell group, including the configuration of the SpCell L1 / L2 inter-cell mobility candidate and the configuration for at least one SCell associated with the SpCell L1 / L2 inter-cell mobility candidate. If the DU does not accept the L1 / L2 intercellular mobility request, different actions may be taken. *According to some embodiments, the DU indicates to the CU in a UE context correction response message that it was unsuccessful in configuring L1 / L2 mobility, including an appropriate cause value (e.g., failure due to reason X). *According to some embodiments, if the DU does not accept a request for L1 / L2 inter-cell mobility, the DU indicates that configuring L1 / L2 mobility was unsuccessful with a UE CONTEXT MODIFICATION FAILURE message, along with an appropriate cause value. *According to some embodiments, if the DU does not accept a request from the CU to configure an L1 / L2-based inter-cell mobility candidate cell but can configure other L1 / L2-based inter-cell mobility candidate cells, the DU indicates the L1 / L2-based inter-cell mobility candidate cells that can be configured, along with their cause values, in the UE context correction response or UE context correction failure message. In the latter case, upon receiving a UE context correction response or UE context correction failure message containing an L1 / L2-based inter-cell mobility candidate cell that was not initially requested by the CU, the CU may send a new message to the DU to trigger a new UE context correction request procedure (i.e., to configure all or a subset of the L1 / L2-based inter-cell mobility candidate cells proposed by the DU). Furthermore, if one or more L1 / L2 inter-cell mobility candidates (likely encoded in an F1AP IE (e.g., an IE called Candidate L1 / L2Cell List)) are included in the UE CONTEXT MODIFICATION REQUEST message, and the DU (e.g., gNB-DU) accepts a subset of these candidates, the DU (e.g., gNB-DU) will respond with an acceptable subset (e.g., a list of acceptable cells, likely encoded in an F1AP IE (e.g., an IE called L1 / L2Cell List)) if it supports L1 / L2 inter-cell mobility, which includes a subset of cells that the DU can accept (e.g., included in an IE called Candidate L1 / L2Cell List), In some cases, Any additional cells that the DU decides to add for L1 / L2 cell mobility are included in the UE CONTE MODIFICATION RESPONSE message, and the CU (e.g., gNB-CU) takes this into consideration. One option is for the gNB-DU to include cells in an IE called L1 / L2Cell List in order of preference, with the first cell in the list being the most desirable and the last cell being the least desirable (e.g., based on measurement and / or load conditions). The following is an overview of the actions taken in the DU based on CU requests for one or more L1 / L2 intercellular mobility candidates: *DU accepts all requested candidates, and in some cases, at least already 1 of Add candidate cells. The configuration of these cells is sent to the CU as a response. *DU accepts a subset of the proposed candidate cells and may re-identify some of them itself. All accepted cells are signaled in the response message. All failed cells are also signaled with the appropriate cause value. *DU cannot accept any cell from CU, but it may identify the cell itself. Then, alternative 2 is the same procedure. *The DU cannot accept any of the cells within the CU and does not identify a cell itself. In this case, the DU sends a UE context modification failure message if the L1 / L2 mobility originated from a UE context modification procedure. According to a particular embodiment, the third message is a UE context correction response (F1AP message). According to a particular embodiment, the third message is a UE context modification response (F1AP message) sent by the DU in response to the second message. The CU receives the third message.

[0051] 5. Upon receiving a third message (e.g., a UE context correction response), the CU sends a fourth message to the DU containing the RRC reconfiguration to be sent to the UE, where the RRC reconfiguration includes one or more of the following: ○ At least one CSI measurement configuration, ○The first cell group configuration associated with the current primary cell (PCell) from which UE transitions from the RRC_IDLE state to the RRC_CONNECTED state. ○ Configuration of at least one L1 / L2-based inter-cell mobility candidate cell. Next, the DU receives a fourth message. *According to a particular embodiment, the fourth message includes a DL RRC message transfer. *According to a particular embodiment, the fourth message is another UE context modification request from the CU to the DU, *According to a particular embodiment, before sending a fourth message, the CU generates an RRC Reconfiguration. It includes a configuration of at least one L1 / L2-based inter-cell mobility candidate cell for candidates proposed by the CU and accepted by the DU, and / or candidates not proposed by the CU but configured by the DU. For example, the CU (e.g., gNB-CU) generates an RRCReconfiguration message and encapsulates it in a DL RRC Message Transfer message. The RRC Reconfiguration message includes the configuration and associated procedures necessary for the UE to perform L1 / L2 inter-cell mobility, such as CSI measurement and reporting. The RRC Reconfiguration message includes information generated by the DU for L1 / L2 inter-cell mobility.

[0052] 6. The DU sends an RRC reconfiguration message (encapsulated in the fourth message) to the UE to configure one or more L1 / L2 inter-cell mobility candidates. The DU sends an RRC reconfiguration message to the UE in response to receiving the fourth message from the CU. The UE receives the RRC reconfiguration message and applies a message containing one or more of the following: ○ At least one CSI measurement configuration, ○The first cell group configuration associated with the current primary cell (PCell) from which UE transitions from the RRC_IDLE state to the RRC_CONNECTED state. ○ Configuration of at least one L1 / L2-based inter-cell mobility candidate cell. Upon receiving the RRC reconfiguration, the UE applies the message and configures the L1 / L2 inter-cell mobility candidate and CSI measurement configuration to support L1 / L2 inter-cell mobility.

[0053] 7. The UE sends the RRCReconfigurationComplete message to the DU (e.g., gNB-DU). The DU receives the message.

[0054] 8. The DU (e.g., gNB-DU) encapsulates the RRC message into a UL RRC message transfer message and sends it to the CU (e.g., gNB-CU). The CU receives the message and considers the configured UE for L1 / L2 inter-cell mobility.

[0055] From the UE's perspective, after step 7, the UE begins performing CSI measurements on one or more L1 / L2 inter-cell mobility candidates and reports the measurement results to the DU. Upon receiving this, the DU will then contact the UE. So Lower-layer signaling (e.g., MAC CE or DCI) indicating a change in the serving cell (e.g., PCell change) UE By transmitting, it may decide to trigger L1 / L2 inter-cell mobility. Upon receiving the lower-layer signaling, the UE modifies its serving cell and acts according to the configuration of the L1 / L2 inter-cell mobility candidate indicated by the lower-layer signaling. The configuration of the L1 / L2 inter-cell mobility candidate is received in step 7.

[0056] Lower-layer signaling from the network (e.g., from the DU) may be a MAC CE or DCI that includes an indication of at least one configured L1 / L2-based inter-cell mobility candidate cell that the UE needs to modify in L1 / L2 inter-cell mobility. After receiving the lower-layer signaling, the UE initiates operation in the L1 / L2-based inter-cell mobility candidate cell according to its configuration.

[0057] Further details on signaling between CU and DU (F1AP procedure) Several different aspects will be described in more detail in this section. * Use of one or more procedures to configure multiple L1 / L2 intercellular mobility candidate cells. * Configuration of L1 / L2 intercellular mobility candidate cells to become PCell and / or SCell, or configuration of a cell group for a given L1 / L2 intercellular mobility candidate cell (e.g., called CellGroupConfig). One procedure per L1 / L2 inter-cell mobility candidate.

[0058] According to one embodiment, a candidate is configured. For example, according to one embodiment, the CU sends a second message to the DU of a RAN (e.g., gNodeB-DU), such as a UE context correction request, indicating a request for the DU to configure a candidate L1 / L2-based inter-cell mobility cell in the UE, and the CU receives a third message from the DU in response to the second message, such as a UE context correction response, which contains the configuration of one candidate L1 / L2-based inter-cell mobility cell. The message may include an indication of the candidate cell (e.g., candidate PCell), such as a cell identifier (e.g., an NR CGI as defined in 3GPP® TS 38.331).

[0059] According to certain other embodiments, multiple candidates are configured. For example, according to some embodiments, the CU sends a number of second messages to the DU of the RAN (e.g., gNodeB-DU), each of which indicates a request to the DU to configure one L1 / L2-based inter-cell mobility candidate cell in the UE, and the CU receives a third message from the DU in response to each of the second messages, which includes the configuration of one L1 / L2-based inter-cell mobility candidate cell. In other words, the CU requests the DU to configure multiple candidates, and for each candidate, the CU sends a UE context modification request which includes the indication of the requested L1 / L2 inter-cell mobility candidate cell, thereby modifying the procedure of Trigger.

[0060] Figure 6 shows exemplary signaling 500 between UE502, DU504, and CU506 according to several embodiments, where each procedure constitutes each L1 / L2 inter-cell mobility candidate. Specifically, Figure 6 shows, for example, CU506 receiving a measurement report with measurements from cell A and cell B.

[0061] The CU decides to request the DU to configure cells A and B as candidate cells for L1 / L2 inter-cell mobility. *CU sends a UE CONTEXT MODIFICATION REQUEST to the DU indicating a request for cell A, and in response receives a UE CONTEXT MODIFICATION RESPONSE from the DU containing the configuration for L1 / L2 inter-cell mobility for cell A. *CU sends another UE CONTEXT MODIFICATION REQUEST to DU indicating a request for cell B, and in response, receives a UE CONTEXT MODIFICATION RESPONSE from DU containing the configuration for L1 / L2 inter-cell mobility for cell B.

[0062] Once both responses are received, the CU generates an RRC reconfiguration for the UE, encapsulates it in a DL RRC message transfer to the DU, and sends it to the DU. The DU then sends it to the UE, so the UE is configured with both cell A and cell B as L1 / L2 inter-cell mobility candidate cells.

[0063] One advantage of this approach is that it requires fewer updates to CU / DU messages, and the DU implementation can be simpler because DU is currently used to handle messages requesting the addition of a single cell for other legacy procedures. Another advantage is that even if DU fails to configure one of the cells (e.g., cell A or cell B), L1 / L2 inter-cell mobility allows the UE to configure the other cell (for which DU could have generated configuration).

[0064] One procedure for multiple L1 / L2 inter-cell mobility candidates According to some embodiments, the CU sends a second message to the RAN's DU (e.g., gNodeB-DU), such as a UE context correction request, indicating a request to the DU to configure multiple L1 / L2-based inter-cell mobility candidate cells in the UE, and in response to the second message, the CU receives a third message from the DU (such as a UE context correction response) containing multiple configurations, where each configuration corresponds to an L1 / L2-based inter-cell mobility candidate cell from multiple L1 / L2 inter-cell mobility candidate cells.

[0065] Figure 7 shows another exemplary signaling 600 between UE602, DU604, and CU606, in which a single procedure can be triggered to configure multiple L1 / L2 inter-cell mobility candidates. Specifically, Figure 7 shows the CU receiving a measurement report containing measurements from cell A and cell B.

[0066] The CU decides to request the DU to configure cells A and B as candidate cells for L1 / L2 inter-cell mobility. *CU sends a UE CONTEXT MODIFICATION REQUEST to the DU indicating requests for both cell A and cell B, and receives a UE CONTEXT MODIFICATION RESPONSE in response from the DU, which includes configurations for L1 / L2 inter-cell mobility for cell A and L1 / L2 inter-cell mobility for cell B.

[0067] If a single response is received, the CU generates an RRC reconfiguration message for the UE, encapsulates it in a DL RRC message transfer to the DU, and sends it to the DU. The DU then sends it to the UE, so the UE configures both cell A and cell B as L1 / L2 inter-cell mobility candidate cells.

[0068] One advantage of this approach is reduced signaling, as a single CU / DU message can constitute multiple candidates. A further advantage is that the overall procedure for configuring L1 / L2 inter-cell mobility for cell A and cell B is faster. How to configure L1 / L2 intercellular mobility candidate cells as SpCell, SCell, and / or cell groups.

[0069] L1 / L2 inter-cell mobility can be configured for at least one SpCell that is an L1 / L2 inter-cell mobility candidate. In this case, the UE is connected to the source cell (source SpCell), and the reception of lower-layer signaling after the UE has configured at least one L1 / L2 inter-cell mobility candidate indicates a change in that source SpCell to a target SpCell that is one of the L1 / L2 inter-cell mobility candidates configured in the UE.

[0070] L1 / L2 inter-cell mobility can be configured for at least one SCell that is an L1 / L2 inter-cell mobility candidate. In this case, the UE configures and operates according to the SCell (e.g., the master cell group which is the activated SCell), and reception of lower-layer signaling after the UE has configured at least one L1 / L2 inter-cell mobility candidate SCell indicates a change of that SCell to a different SCell at the same frequency, which may be one of the L1 / L2 inter-cell mobility candidates configured for the UE.

[0071] L1 / L2 inter-cell mobility may be configured for a cell group that includes one SpCell and one or more SCells, upon receiving a CellGroupConfig (IE). vinegar A cell (source SpCell) may be connected to a cell (source SpCell) and may constitute one or more SCells of the MCG. The reception of lower-layer signaling indicates to the UE, after the UE has configured at least one L1 / L2 inter-cell mobility candidate, that the source SpCell has been modified to a target SpCell which is one of the configured L1 / L2 inter-cell mobility candidates, and that at least one of the configured SCells has been modified (e.g., one new SCell is added, and one of the configured SCells is removed or modified).

[0072] According to some embodiments, a request (e.g., in a UE context modification request from a CU to a DU) includes at least one set of cells (e.g., a set of cells contained in a list) (e.g., within a list), which includes L1 / L2 intercellular mobility candidates (e.g., an IE called a Candidate L1 / L2Cell List, which may contain a list of cell identifiers for the requested cell). This set can be encoded as a list (e.g., as defined in RRC signaling) or any other data structure.

[0073] According to some embodiments, at least one set of cells corresponds to a set of SpCell candidates for L1 / L2 inter-cell mobility. These are candidate cells at the same or different frequencies (SSB frequencies and / or SSB subcarrier intervals) as the current SpCell (e.g., PCell) of the UE configured in the UE. ○According to a particular embodiment, the DU receives these sets of SpCells, generates a configuration for each L1 / L2-based inter-cell mobility candidate SpCell, and sends it to the CU (e.g., an IE called SpCellConfig in the UE CONTEXT MODIFICATION RESPONSE). ○According to a particular embodiment, the DU receives these sets of SpCells and generates a cell group configuration (e.g., an IE called CellGroupConfig) for each L1 / L2-based inter-cell mobility candidate SpCell, which also includes one or more SCell configurations associated with each candidate SpCell. According to a further specific embodiment, one or more SCells for each L1 / L2 intercellular mobility candidate SpCell included by the DU during the cell group configuration for each L1 / L2 intercellular mobility candidate are one of the SCells indicated by the CU in the UE CONTEXT MODIFICATION REQUEST message. According to another specific embodiment, one or more SCells for each L1 / L2 intercellular mobility candidate included by the DU in the cell group configuration for each L1 / L2 intercellular mobility candidate are not one of the SCells indicated by the CU in the UE CONTEXT MODIFICATION REQUEST message.

[0074] According to some embodiments, at least one set of cells corresponds to a set of (proposed and requested) secondary cell (SCell) candidates for L1 / L2 inter-cell mobility (e.g., for carrier aggregation). These are candidate cells at the same or different frequencies (SSB frequencies and / or SSB subcarrier intervals) as the UE's current SpCell (e.g., PCell). According to a particular embodiment, the DU receives these recommended sets of SCells, generates a configuration for each L1 / L2-based inter-cell mobility candidate SCell, and sends it to the CU (e.g., an IE called SCellConfig in the UE context modification response).

[0075] According to some embodiments, the DU receives from the CU a first set of cells corresponding to a set of SpCell candidates for L1 / L2 inter-cell mobility, and a second set of cells corresponding to a set of SCell candidates for L1 / L2 inter-cell mobility. Upon receiving these, the DU generates at least one cell group configuration, which includes a SpCell configuration for at least one of the SpCell candidates and a SCell configuration for at least one of the SCell candidates. *According to a particular embodiment, the second set of cells corresponding to the set of SCell candidates for L1 / L2 inter-cell mobility is the same set of SCells that indicate the UE CONTEXT MODIFICATION REQUEST message is, for example, the SCell of the current PCell cell group configuration contained in an IE called SCell To Be Setup List. *According to a particular embodiment, a second set of cells corresponding to a set of candidate SCells for L1 / L2 inter-cell mobility is indicated in the UE CONTEXT MODIFICATION REQUEST message as a different set of SCells compared to the SCells in the current PCell cell group configuration (e.g., included in an IE called SCell To Be Setup List), although the CU may choose to include the same SCells in both the list for the current PCell cell group configuration and the list for the candidate PCells for L1 / L2 inter-cell mobility. *According to a particular embodiment, two sets are sent by the CU and received by the DU as separate sets (e.g., in two cell lists). The DU determines how these SpCell candidates and SCell candidates are grouped or combined in the cell group configuration. For example, if the first set of cells has SPCell Id=1 and SpCell Id=2, and the second set has Scell ​​Id=4 and SCell Id=5, the DU can generate a SpCellConfig(1) for SpCell Id=1, a SCellConfig(4) for Scell ​​Id=4, a SCellConfig(5) for Scell ​​Id=5, and a cell group called CellGroupConfig(1) = SpCellConfig(1) + SCellConfig(4), and a SCellConfig(5) for L1 / L2 cell mobility, and CellGroupConfig(1) is provided to the CU in the UE CONTEXT SETUP RESPONSE.

[0076] According to some embodiments, the DU receives from the CU a set of cell groups including one SpCell candidate for L1 / L2 inter-cell mobility and at least one SCell candidate for L1 / L2 inter-cell mobility. Upon receiving this, the DU generates at least one cell group configuration including a SpCell configuration for the SpCell candidate and a SCell configuration for the SCell candidate. In this option, it is the CU that requests a particular cell group as a candidate cell group, which includes both a PCell and one or more SCells, while the DU decides whether to accept the cell group that has been requested as a candidate for L1 / L2 inter-cell mobility.

[0077] According to some embodiments, the IE is included in the UE CONTEXT MODIFICATION REQUEST message, such as the IE name (e.g., an IE named Candidate L1 / L2Cell List), which indicates one or more L1 / L2 intercellular mobility candidate cells (e.g., an IE named Candidate L1 / L2Cell List) that are requested (or proposed or recommended) by the CU to the DU, and includes one or more of the following: ○Cell identifier for each candidate cell for inter-L1 / L2 cell mobility. According to one embodiment, the cell identifier for each L1 / L2 inter-cell mobility candidate is given as one or more global cell identifiers (e.g., NR CGI), a physical cell identifier (and its associated frequency, PLMN identifier, and associated NR cell identifier). According to one embodiment, a cell identifier for each L1 / L2 intercellular mobility candidate is provided as an extended version of the IE called a candidate SpCell list (as defined in TS 38.473), which may have more values ​​(e.g., 0, 1, 2, 3...K) if an L1 / L2 intercellular mobility candidate is requested. When used, the CU includes in the first value of the list the cell to which the CU is intended to be the current SpCell, i.e., the PCell to which the UE is connected, while the other cells included are intended to be L1 / L2 intercellular mobility candidate cells. They may be considered SpCell candidates for L1 / L2 intercellular mobility. ○ For each candidate cell for inter-L1 / L2 cell mobility, a cell index encoded with fewer bits than the cell identifier. According to one embodiment, a cell index for each L1 / L2 inter-cell mobility candidate is provided as an integer. This index should be used for communication between the UE and / or CU and / or DU to point to that cell. This can be particularly important on the air interface to exchange information with a reduced number of bits when referring to that candidate cell. This makes sense because there may be more L1 / L2 inter-cell mobility candidates overall than the L1 / L2 inter-cell mobility candidates that can be configured in the UE. ○ Frequency information for each candidate cell for inter-L1 / L2 cell mobility. According to one embodiment, the frequency information includes an indication of a serving measurement target or serving frequency (e.g., a serving cell MO as defined in 3GPP® TS 38.331) and is associated with the serving frequency measurement target for which L1 / L2 inter-cell mobility candidates exist. According to one embodiment, the frequency information includes SSB frequencies that may be encoded as absolute frequency information (e.g., ARFCN as defined in 3GPP® TS 38.331). According to one embodiment, the frequency information includes CSI-RS frequencies that may be encoded as absolute frequency information (e.g., ARFCN as defined in 3GPP® TS 38.331). According to one embodiment, the frequency information includes a point A frequency which may be encoded as absolute frequency information (e.g., an ARFCN as defined in 3GPP® TS 38.331). ○ A cell group index or identifier for each candidate cell for L1 / L2 intercellular mobility and / or for groups of candidate cells for L1 / L2 intercellular mobility.

[0078] Examples of signaling The following is an example of a UE CONTEXT MODIFICATION REQUEST message from a CU to a DU (e.g., via F1AP, from gNB-CU to gNB-DU) when a request is made to configure L1 / L2 intercellular mobility for at least one SpCell that is a candidate for L1 / L2 intercellular mobility.

[0079] *************************************** 8.3.4 UE Context Correction (Initiated by gNB-CU) [...] If a Candidate L1 / L2Cell List IE (IE) is included in a UE CONTEXT MODIFICATION REQUEST message, gNB-DU assumes that these cells will be recommended and considered for L1 / L2 mobility. If an L1 / L2Cell List IE is included in the UE CONTEXT MODIFICATION REQUEST message, gNB-DU understands that the cell is configured for L1 / L2 mobility. If the L1 / L2CellGroupConfig IE is included in the CU to DU RRC Information IE within the UE CONTEXT MODIFICATION REQUEST message, the DU will understand that it is providing the cell configuration for L1 / L2 mobility. If gNB-DU cannot accept any of the cells in the Candidate L1 / L2Cell List IE, gNB-DU responds with the appropriate cause value in the UE CONTEXT MODIFICATION RESPONSE message. If an L1 / L2Cell List IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU understands that the cell is configured for L1 / L2 mobility. The gNB-DU will prioritize the inclusion of cells within the L1 / L2Cell List IE, with the first cell in the list being the most desirable and the last cell being the least desirable (e.g., based on measurement, load conditions). If the L1 / L2CellGroupConfig IE is included in the DU to CU RRC Information IE within the UE CONTEXT MODIFICATION RESPONSE message, the CU understands that it provides the cell configuration for L1 / L2 mobility. If a Candidate L1 / L2 SCell To Be Setup List IE is included in a UE CONTEXT MODIFICATION REQUEST message, gNB-DU will consider it as a list of recommended candidate SCells for L1 / L2 inter-cell mobility. The recommended cells may correspond to the requested or proposed cells. If the L1 / L2 SCell List IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU understands that the Scell ​​is configured for L1 / L2 mobility. If the L1 / L2 SCell Failed To Setup List IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU considers the corresponding SCell(s) for L1 / L2 inter-cell mobility to have failed to set up, using the appropriate cause value for each SCell that failed to set up. If the L1 / L2 Cell Failed To Setup List IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU considers the corresponding cell(s) that failed to set up L1 / L2 inter-cell mobility to have failed to set up, using the appropriate cause value for each cell that failed to set up. 8.3.4.3 Failure behavior [...] If gNB-DU cannot accept any of the cells in the Candidate L1 / L2 SCell To Be Setup List IE within the UE CONTEXT MODIFICATION REQUEST message, it responds with a UE CONTEXT MODIFICATION FAILURE message with the appropriate cause value. 8.4.2 DL RRC Message Transfer If the L1 / L2CellGroupConfig IE is included in the RRC-Container IE (RRC container IE) within the DL RRC message transfer message, the DU will understand that it provides the cell configuration for L1 / L2 mobility. 9.2.2.7 UE Context Correction Request This message is sent by gNB-CU to provide gNB-DU with UE context information changes. Direction: gNB-CU ⇒ gNB-DU [Table 1] [Table 2] [Table 3] 9.2.2.8 UE Context Correction Response This message is sent by gNB-DU to confirm modifications (changes) to the UE context. Direction: gNB-DU⇒gNB-CU [Table 4] [Table 5] 9.3.1.25 RRC information from CU to DU This IE contains RRC information sent from gNB-CU to gNB-DU. [Table 6] [Table 7]

[0080] Figure 8 shows examples of communication systems 700 according to several embodiments. In this example, the communication system 700 includes a telecommunications network 702, which includes an access network 704 such as a radio access network (RAN), and a core network 706, which includes one or more core network nodes 708. The access network 704 includes one or more access network nodes, such as network nodes 710a and 710b (one or more of which may generally be referred to as network nodes 710), or any other similar Third Generation Partnership Project (3GPP®) access nodes or non-3GPP® access points. Network nodes 710 include one or more radio connection Direct or indirect connections of user equipment (UEs) are enabled, for example, by connecting UE712a, 712b, 712c, and 712d (one or more of which may commonly be referred to as UE712) to the core network 706 via the .

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

[0082] UE712 is used for network node 710 and other communications device And to communicate wirelessly arrangementA wide variety of communications, including wireless devices that are configured, set up, and / or capable of operating. device It may be any of the above. Similarly, the network node 710 is configured, capable of, and / or capable of communicating directly or indirectly with the UE 712 and / or other network nodes or devices in the telecommunications network 702 in order to enable and / or provide network access such as wireless network access, and / or to perform other functions such as management in the telecommunications network 702.

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

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

[0085] Overall, the communication system 700 in Figure 8 enables connectivity between the UE, network nodes, and hosts. In that sense, the communication system is not limited to, but also to, any other suitable standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long-Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future-generation standards (e.g., 6G), Wireless Local Area Network (WLAN) standards such as the IEEE 802.11 standard (WiFi), and / or World Wide 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. wireless Communication standards specific standards including They can be configured to operate according to predefined rules or procedures, for example.

[0086] In some examples, the telecommunications network 702 is a cellular network implementing 3GPP® standardization features. Therefore, the telecommunications network 702 may support network slicing to provide different logical networks to different devices connected to the telecommunications network 702. For example, the telecommunications network 702 may provide ultra-high reliability low-latency communications (URLLC) services to some UEs while providing extended mobile broadband (eMBB) services to other UEs. and / or Further UEs may be provided with massive machine type communication (mMTC) / massive IoT services.

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

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

[0089] Hub 714 may have a constant / persistent or intermittent connection to network node 710b. Hub 714 may also enable other communication methods and / or scheduling between Hub 714 and UEs (e.g., UE712c and / or 712d), and between Hub 714 and the core network 706. According to other embodiments, Hub 714 may Wired connection ( Wired Connection ) The hub 714 is connected to the core network 706 and / or one or more UEs via the access network 704. Furthermore, the hub 714 may be configured to connect to an M2M service provider via the access network 704 and / or to another UE via a direct connection. In some scenarios, a UE may establish a wireless connection with the network node 710 while still being connected via the hub 714 via a wired or wireless connection. According to some embodiments, the hub 714 may be a dedicated hub, i.e., a hub whose primary function is to route communications to and from the network node 710b. According to other embodiments, the hub 714 may be a non-dedicated hub, i.e., a device that can operate to route communications between the UE and the network node 710b, but can further operate as a communication source and / or endpoint for a particular data channel.

[0090] Figure 9 shows the UE800 in several embodiments. As used herein, UE refers to a device that is capable of, configured, deployed, and / or operating wirelessly with network nodes and / or other UEs. Examples of UEs include smartphones. moveExamples include, but are not limited to, telephones, mobile phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop-based devices (LMEs), smart devices, wireless customer pre-owned equipment (CPEs), and automotive or embedded / integrated wireless devices. Other examples include any UE identified by the Third Generation Partnership Project (3GPP®), including narrowband Internet of Things (NB-IoT) UEs, machine-type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

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

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

[0093] The processing circuit 802 is configured to process instructions and data and may be configured to implement any sequential state machine capable of executing instructions stored in memory 810 as machine-readable computer programs. The processing circuit 802 may be implemented as one or more hardware-implemented state machines (e.g., discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.), one or more stored computer programs such as programmable logic with appropriate firmware, microprocessors or digital signal processors (DSPs) with appropriate software, general-purpose processors, or any combination of the above. For example, the processing circuit 802 may be multiple central processing units. process It may include a device (CPU).

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

[0095] According to some embodiments, the power supply 808 is configured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electrical outlet), a solar power device, or a battery, may also be used. The power supply 808 may further include power circuits for delivering power to various parts of the UE800 via an interface such as an input circuit or a power cable, from the power supply 808 itself and / or an external power source. Power transmission may, for example, be for charging the power supply 808. The power circuits may perform some shaping, conversion, or other modification on the power from the power supply 808 to make the power suitable for each component of the UE800 to which the power is supplied.

[0096] Memory 810 may be or may be configured to include random access memory (RAM), read-only memory (ROM), field-programmable gate array read-only memory (PROM), erasable field-programmable gate array read-only memory (EPROM), electrically erasable field-programmable gate array read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, etc. According to one embodiment, memory 810 contains one or more application programs 814 such as an operating system, a web browser application, a widget, a gadget engine, or other applications, and corresponding data 8 This includes 16. Memory 810 can store any of the various operating systems or combinations of operating systems for use by the UE800.

[0097] Memory 810 may be configured to include several physical drives, such as a 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 disk (HD-DVD) optical disk drive, internal hard disk drive, Blu-ray optical disk drive, holographic digital data storage (HDDS) optical disk drive, external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external microDIMM SDRAM, and smart card memory such as a tamper-proof module in the form of a universal integrated circuit card (UICC) containing one or more subscriber identification modules (SIMs), such as USIM and / or ISIM, other memory, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card". Memory 810 may enable UE800 to access instruction sets and application programs stored on temporary or non-temporary storage media to offload or upload data. Products that utilize communication systems, etc., may be device-readable storage media, or may be tangibly embodied as memory 810 which may include device-readable storage media, or within it.

[0098] The processing circuit 802 may be configured to communicate with an access network or other network using a communication interface 812. The communication interface 812 may comprise one or more communication subsystems, and may include or be communicatively coupled to an antenna 822. The communication interface 812 is wirelessIt may include one or more transceivers used for communication, such as by communicating with one or more remote transceivers of another device capable of communication (e.g., another UE or network node in the access network). Each transceiver may include a transmitter 818 and / or receiver 820 suitable for providing network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, 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 may be implemented separately.

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

[0100] Regardless of the type of sensor, the UE can provide the network node with the data captured by its sensor via its communication interface 812 and wireless connection. The data captured by the UE's sensor is wirelessCommunication to network nodes may be conducted via other UEs through the connection. Output may be periodic (e.g., once every 15 minutes if reporting detected temperature), random (e.g., to equalize the load from notifications from multiple sensors), in response to triggered events (e.g., humidity is detected and an alert is sent), in response to requests (e.g., user-initiated requests), or as a continuous stream (e.g., a live video feed of a patient).

[0101] As another example, UE is wireless connection From the network node wirelessly via input It comprises an actuator, motor, or switch associated with a communication interface configured to receive. wireless The state of actuators, motors, or switches may change in response to input. For example, the UE may include a motor that adjusts the control surface or rotor of a drone in flight according to the input received, or a robotic arm that performs a medical procedure according to the input received.

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

[0103] As yet another specific example, in an IoT scenario, the UE can represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE may be an M2M device and may be referred to as an MTC device in the context of 3GPP®. As one example, the UE may implement the 3GPP® NB-IoT standard. In other scenarios, the UE may be a passenger car capable of monitoring and / or reporting its operating status or other functions associated with its operation. bus, Trucks, ships, or aircraft Vehicles such as , or it may represent other devices.

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

[0105] Figure 10 shows network node 900 according to several embodiments. As used herein, network node means equipment that is capable of communicating directly or indirectly with the UE and / or other network nodes or equipment in the telecommunications network, and is configured, positioned, and / or operational in such a manner. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, node B, evolved node B (eNB), and NR node B (gNB)).

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

[0107] Other examples of network nodes include multi-transmitting point (multi-TRP) 5G access nodes, MSR BS, etc. multi Standard Wireless (MSR) equipment, wireless networks control device Networks such as RNCs or base station controllers (BSCs) control device , Base transceiver Station (BTS), transmit point, transmit node, multicell / multicast coordination entity (MCE), operation and maintenance (O&M) node, operation support system (OSS) nodeThis includes self-organizing network (SON) nodes, positioning nodes (e.g., Evolutionary Serving Mobile Location Center (E-SMLC)), and / or drive test minimization (MDT).

[0108] The network node 900 includes a processing circuit 902, a memory 904, a communication interface 906, and a power supply 908. The network node 900 may consist of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own respective components. component In certain situations, including ), one or more separate components may be shared among multiple network nodes. For example, a single RNC can control multiple nodes B. In such a scenario, each pair of unique nodes B and RNC may, in some cases, be considered a single, separate network node. In some embodiments, network node 900 is multiple Nothing It may be configured to support Line Access Technology (RAT). In such embodiments, some components may be redundant (e.g., separate memory 904 for different RATs), and some components may be reused (e.g., the same antenna 910 may be shared by multiple different RATs). The network node 900 may also include a variety of illustrated components for various wireless technologies integrated into the network node 900, such as a number of 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 chips or chipsets and other components within the network node 900.

[0109] The processing circuit 902 is a microprocessor 、 controller、 Microcontroller 、 center Calculation Processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable Computing devices This may include one or more combinations of resources, or hardware, software, and / or coding logic, and these combinations can operate alone or in conjunction with other network node 900 components such as memory 904 to provide network node 900 functionality.

[0110] According to some embodiments, the processing circuit 902 includes a system-on-a-chip (SOC). According to some embodiments, the processing circuit 902 includes one or more of a radio frequency (RF) transceiver circuit 912 and a baseband processing circuit 914. In some embodiments, radio frequency (RF) The transceiver circuit 912 and the baseband processing circuit 914 may be located on separate chips (or chipsets), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit 912 and the baseband processing circuit 914 may be located on the same chip or chipset, board, or unit.

[0111] Memory 904 may comprise any form of volatile or non-volatile computer-readable memory, including, but not limited to, persistent memory, solid-state memory, remote-mount memory, magnetic media, optical media, random-access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD), or digital video disc (DVD)), and / or any other volatile or non-volatile, non-temporary device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by the processing circuit 902. P Programs, software yeA, any preferred instruction, data, or information can be stored, including an application that includes one or more other instructions that are executed by the processing circuit 902 and can be utilized by the network node 900. Memory 904 may be used to store any operations performed by the processing circuit 902 and / or any data received via the communication interface 906. In some embodiments, the processing circuit 902 and memory 904 are integrated.

[0112] The communication interface 906 provides wired or wireless signaling and / or data between network nodes, access networks, and / or UEs. Communication It is used for the following. As illustrated, the communication interface 906 includes, for example, a port / terminal 916 for sending and receiving data to and from the network over a wired connection. The communication interface 906 also includes a wireless front-end circuit 918 connected to the antenna 910 or, according to one embodiment, being part of the antenna 310. The wireless front-end circuit 918 comprises a filter 920 and an amplifier 922. The wireless front-end circuit 918 may be connected to the antenna 910 and the processing circuit 902. The wireless front-end circuit may be configured to adjust signals communicated between the antenna 910 and the processing circuit 902. The wireless front-end circuit 918 may receive digital data to be sent to other network nodes or UEs via the wireless connection. The wireless front-end circuit 918 may use a combination of the filter 920 and / or the amplifier 922 to convert the digital data into a wireless signal having appropriate channel and bandwidth parameters. The wireless signal may then be transmitted via the antenna 910. Similarly, when receiving data, the antenna 910 can collect radio signals that are converted into digital data by the radio front-end circuit 918. The digital data may be passed to the processing circuit 902. In other embodiments, the communication interface may include different components and / or different combinations of components.

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

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

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

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

[0117] Embodiments of the network node 900 may include additional components beyond those shown in Figure 10 to provide a particular aspect of the network node's functionality, including any of the functionalities described herein and / or any functionalities essential to support the subject matter described herein. For example, the network node 900 may include a user interface device that allows information to be input to and output from the network node 900. This would allow a user to perform diagnostic, maintenance, repair, and other management functions of the network node 900.

[0118] Figure 11 is a block diagram of host 1000, which may be one embodiment of host 716 in Figure 8, according to various aspects described herein. As used herein, host 1000 may be, or include, hardware-aware and / or software in various combinations, including standalone servers, blade servers, cloud-implemented servers, distributed servers, virtual machines, containers, or processing resources within a server farm. Host 1000 can provide one or more services to one or more UEs.

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

[0120] Memory 1012 may include one or more computer programs, each including one or more host application programs 1014 and data 1016 which may include user data, such as data generated by the UE for host 1000 or data generated by host 1000 for the UE. Embodiments of host 1000 may utilize only a subset or all of the illustrated components. The host application program 1014 can be implemented in a container-based architecture and may include multiple different classes, types, or implementations of the UE (e.g., handset, desktop computer, etc.). ye Including transcoding for all-purpose display systems and head-up display systems. video codec (Support for Versatile Video Coding (e.g., 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) can be provided. The host application program 1014 may also provide user authentication and license checks, and may periodically report health, route, and content availability to central nodes, such as devices within or at the edge of the core network. Therefore, host 1000 may select and / or point to different hosts for over-the-top services for the UE. The host application program 1014 may support a variety of protocols, such as HLS (HTTP Live Streaming), RTMP (Real-Time Messaging Protocol), RTSP (Real-Time Streaming Protocol), and MPEG-DASH (Dynamic Adaptive Streaming over HTTP).

[0121] Figure 12 is a block diagram showing a virtualization environment 1100 in which functions implemented by several embodiments can be virtualized.

[0122] In this text, virtualization means creating a device or a virtual version of a device, which involves virtualizing hardware platforms, storage devices, and network resources. Where used herein, virtualization can be applied to any device or component thereof described herein and is associated with implementation examples in which at least some of its functionality is implemented as one or more virtual components. Some or all of the functionality described herein may be implemented as virtual components run by one or more virtual machines (VMs) implemented within one or more virtual environments 1100 hosted by one or more hardware nodes, such as network nodes, UEs, core network nodes, or hardware computing devices acting as hosts. Furthermore, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or a host), the node as a whole may be virtualized.

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

[0124] Hardware 1104 includes processing circuits, memory for storing software and / or instructions executable by the hardware processing circuits, and / or other hardware devices described herein, such as network interfaces and input / output interfaces. The software is executed by the processing circuits to instantiate one or more virtualization layers 1106 (also called hypervisors or virtual machine monitors (VMMs)), provide VMs 1108a and 1108b (one or more of which may generally be referred to as VMs 1108), and / or perform any of the functions, features and / or benefits described herein in relation to some embodiments described herein. The virtualization layer 1106 may present a virtual operating platform that appears to the virtual machines 1108 as networking hardware.

[0125] VM1108 comprises virtual processing, virtual memory, virtual networkwork or interfaces, and virtual storage, and may be run by the corresponding virtualization layer 1106. Various embodiments of instances of the virtual appliance 1102 may be implemented in one or more of the VM1108, and the implementation may be done in various ways. Hardware virtualization is performed in several contexts called network function virtualization (NFV). NFV may be used to integrate many types of network equipment into industry-standard high-capacity server hardware, physical switches, and physical storage that can be located in a data center, as well as customer premises equipment.

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

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

[0128] Figure 13 shows partial wireless in several embodiments. connectionThis shows a communication diagram of host 1202 communicating with UE1206 via network node 1204.

[0129] With reference to Figure 13, exemplary embodiments of various embodiments of the UE (such as UE712a in Figure 8 and / or UE800 in Figure 9), network nodes (such as network node 710a in Figure 8 and / or network node 900 in Figure 10), and hosts (such as host 716 in Figure 8 and / or host 1000 in Figure 11) as described in the previous paragraph will be described.

[0130] Similar to host 1000, embodiments of host 1202 include hardware such as a communication interface, processing circuitry, and memory. Host 1202 also includes software that is stored in or accessible by host 1202 and executable by the processing circuitry. This software includes a host application that may be capable of operating to serve a remote user, such as UE1206, connected via an over-the-top (OTT) connection 1250 extending between UE1206 and host 1202. Services When providing the service, the host application can provide user data transmitted using an OTT connection 1250.

[0131] Network node 1204 communicates with host 1202 and UE 1206. Making it possible This includes the necessary hardware. Connection 1260 can go directly through the core network (such as core network 706 in Figure 8) and / or one or more other intermediate networks, such as one or more public, private, or host networks. For example, the intermediate network may be a backbone network or the internet.

[0132] UE1206 includes hardware and software stored in or accessible by UE1206 and executable by the UE's processing circuitry. This software includes client applications, such as a web browser or a vendor-specific "app," which may operate to provide services to human or non-human users via UE1206, with the support of host 1202. On host 1202, the running host application is the UE 1 Communication with a running client application is possible via an OTT connection 1250 terminating at 206 and host 1202. While providing services to a user, the UE's client application may receive request data from the host's host application and provide user data in response to that request data. The OTT connection 1250 can transfer both request data and user data. The UE's client application may interact with the user to generate user data that it provides to the host application via the OTT connection 1250.

[0133] The OTT connection 1250 provides a connection between host 1202 and UE 1206 via connection 1260 between host 1202 and network node 1204, and wirelessly between network node 1204 and UE 1206. connection It may extend via 1270. To illustrate communication between host 1202 and UE 1206 via network node 1204 without any explicit reference to any intermediate devices and the precise routing of messages through those devices, the OTT connection 1250 may be provided by connection 1260 and wireless connection 1270, which are abstractly depicted.

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

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

[0136] One or more of the various embodiments are wireless connection 1270 uses the OTT connection 1250, which forms the final segment, to improve the performance of the OTT service provided to UE 1206. More precisely, the teachings of these embodiments may improve one or more of the following: data rate, latency, and / or power consumption, thereby providing benefits such as reduced user latency, relaxed file size constraints, improved content resolution, enhanced responsiveness, and / or extended battery life.

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

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

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

[0140] Figure 14 shows Method 1300 by connected UE402, 502, 602, 800 for configuring Layer 1 / Layer 2 (L1 / L2) based inter-cell mobility in several embodiments. The Method includes, in step 1302, transmitting a measurement report containing one or more measurements associated with one or more cells. In step 1304, the UE402, 502, 602, 800 receives an RRC reconfiguration message containing the configuration of at least one L1 / L2 based inter-cell mobility candidate cell. In step 1306, the UE402, 502, 602, 800 transmits an RRC reconfiguration complete message.

[0141] According to a particular embodiment, the RRC reconfiguration message includes one or more of at least one CSI measurement configuration and a first cell group configuration associated with the current PCell of the UE.

[0142] According to a further specific embodiment, at least one CSI measurement configuration and / or a first cell group configuration and / or at least one configuration of an L1 / L2-based inter-cell mobility candidate cell associated with the current PCell is generated by candidate DU(406, 504, 604), encapsulated by CU(404, 506, 606) during an RRC reconfiguration message, and received by UE via candidate DU.

[0143] According to a particular embodiment, the UE receives a measurement configuration, which includes a reporting configuration. The reporting configuration includes at least one trigger condition that, when met, triggers the UE to send a measurement report.

[0144] According to a particular embodiment, the UE performs one or more measurements associated with one or more cells according to a measurement configuration, the one or more measurements comprising at least one of the following: CSI measurement, L1 RSRP measurement, differential RSRP measurement, RSRQ measurement, and SINR measurement.

[0145] According to a particular embodiment, the UE determines that at least one condition has been met, and the measurement report is sent in response to the determination that at least one condition has been met.

[0146] According to a particular embodiment, one or more cells associated with a measurement report include one or more adjacent cells and / or one or more non-serving cells. Additionally or alternatively, an L1 / L2-based inter-cell mobility candidate cell is one of the one or more cells associated with the measurement report.

[0147] According to a particular embodiment, the RRC reconfiguration message includes multiple configurations, one of which is associated with one of several L1 / L2-based inter-cell mobility candidate cells.

[0148] According to a particular embodiment, the UE receives lower-layer signaling that includes an indication of an L1 / L2-based inter-cell mobility candidate cell and / or a configuration associated with the L1 / L2-based inter-cell mobility candidate cell. The indication triggers the activation of the configuration of the L1 / L2-based inter-cell mobility candidate cell. Based on the indication, the UE initiates operation in the L1 / L2-based inter-cell mobility candidate cell according to the configuration.

[0149] According to a particular embodiment, lower-layer signaling is received from a distributed unit DU and / or by at least one lower layer of the protocol stack of the UE. The at least one lower layer comprises at least one of the following: a PDCP layer, an RLC layer, a MAC layer, a Phy layer, and L1.

[0150] According to certain embodiments, lower-layer signaling is received via MAC-CE or DCI.

[0151] According to a particular embodiment, at least one L1 / L2-based inter-cell mobility candidate cell includes a candidate which is at least one of SpCell, PCell, SCell, PSCell group cell, MSG cell, and / or SCG cell.

[0152] Figure 15 shows a method 1400 by CUs 404, 506, and 606 for configuring Layer 1 / Layer 2 (L1 / L2) based inter-cell mobility for connected UEs 402, 502, 602, and 800, according to several embodiments. The method begins in step 1402 when CUs 404, 506, and 606 send at least one request to candidate DUs 406, 504, and 604 for candidate DUs to configure L1 / L2 based inter-cell mobility for the UE. The at least one request indicates at least one L1 / L2 based inter-cell mobility candidate cell. In step 1404, CUs 404, 506, and 606 receive from candidate DUs 406, 504, and 604 the configuration of at least one L1 / L2 based inter-cell mobility candidate cell. In step 1406, CU404, 506, and 606 send the RRC reconfiguration to candidate DU406, 504, and 604 to be sent to the UE. The RRC reconfiguration includes at least one configuration of an L1 / L2-based inter-cell mobility candidate cell. In step 1408, CU404, 506, and 606 receive RRC reconfiguration completion from candidate DU406, 504, and 604 from UE402, 502, 602, and 800.

[0153] According to a particular embodiment, the candidate DU is the source DU relating to the UE.

[0154] According to a particular embodiment, the RRC reconstruction includes one or more of at least one CSI measurement configuration and a first cell group configuration associated with the current PCell of the UE.

[0155] According to certain embodiments, the CU encapsulates at least one configuration of L1 / L2-based inter-cell mobility candidate cells into an RRC reconfiguration message for transmission to the UE via a candidate DU.

[0156] According to certain embodiments, the CU receives a measurement report of the UE from the source DU, and the measurement report comprises one or more measurement values associated with one or more cells.

[0157] According to certain embodiments, the one or more measurement values include one or more values associated with at least one of CSI measurement values, L1 RSRP measurement values, differential RSRP measurement values, RSRQ measurement values, and SINR measurement values.

[0158] According to certain embodiments, the measurement report is received in a UL RRC message transfer, and the one or more cells associated with the measurement report include one or more adjacent cells and / or one or more non-serving cells of the UE. Additionally or alternatively, at least one of the L1 / L2-based inter-cell mobility candidate cells is one of the one or more cells associated with the measurement report.

[0159] According to certain embodiments, a request for a candidate DU to configure L1 / L2-based inter-cell mobility for the UE is based on a received measurement report that includes one or more measurement values of one or more cells.

[0160] According to certain embodiments, the CU transmits a previous message including a measurement configuration to the source DU before the CU receives the measurement report from the source DU. The measurement configuration includes a reporting configuration, and the reporting configuration comprises at least one triggering condition for triggering the transmission of a measurement report by the UE when at least one triggering condition is satisfied.

[0161] According to certain embodiments, at least one of the following holds: • At least one request to a candidate DU for configuring L1 / L2-based inter-cell mobility in a UE is sent in at least one UE CONTEXT MODIFICATION REQUEST. • At least one configuration of an L1 / L2-based inter-cell mobility candidate cell is received in the UE CONTEXT MODIFICATION RESPONSE. • RRC reconfiguration is sent via UE CONTEXT MODIFICATION REQUEST or DL ​​RRC MESSAGE TRANSFER. RRC reconstruction completion is received via UE CONTEXT MODIFICATION RESPONSE or UL RRC MESSAGE TRANSFER.

[0162] According to a particular embodiment, at least one message is transmitted and / or received via the F1AP interface between the CU and the candidate DU.

[0163] According to a particular embodiment, the CU obtains information indicating that the UE is capable of performing L1 / L2-based inter-cell mobility.

[0164] According to a particular embodiment, the RRC reconfiguration message includes multiple configurations, each of which is associated with a corresponding one of several L1 / L2-based inter-cell mobility candidate cells.

[0165] According to a particular embodiment, at least one L1 / L2-based inter-cell mobility candidate cell includes a candidate which is at least one of SpCell, PCell, SCell, PSCell group cell, MSG cell, and SCG cell.

[0166] According to a particular embodiment, sending at least one request to a candidate DU for configuring L1 / L2-based inter-cell mobility in a UE includes sending a single message indicating a request to a candidate DU for configuring one L1 / L2-based inter-cell mobility candidate cell in a UE. The configuration of at least one L1 / L2-based inter-cell mobility candidate cell includes one configuration of L1 / L2-based inter-cell mobility candidate cells.

[0167] According to a particular embodiment, sending at least one request to a candidate DU for configuring L1 / L2-based inter-cell mobility in a UE includes sending a plurality of messages to the candidate DU, each one of which indicates a request to the candidate DU for configuring each corresponding one of a plurality of L1 / L2-based inter-cell mobility candidate cells in a UE. The configuration of at least one L1 / L2-based inter-cell mobility candidate cell includes the configuration of one L1 / L2-based inter-cell mobility candidate cell.

[0168] According to a particular embodiment, sending at least one request to a candidate DU for configuring L1 / L2-based inter-cell mobility in a UE includes sending a single message to the candidate DU, the single message indicating a request to the candidate DU for configuring multiple L1 / L2-based inter-cell mobility candidate cells in a UE. The configuration of at least one L1 / L2-based inter-cell mobility candidate cell includes multiple configurations, each of which is associated with a corresponding one of the multiple L1 / L2-based inter-cell mobility candidate cells.

[0169] Figure 16 shows Method 1500 by Candidate DUs 406, 504, 604 for configuring Layer 1 / Layer 2 (L1 / L2) based inter-cell mobility for connected UEs 402, 502, 602, 800, according to several embodiments. The Method begins in step 1502, when Candidate DUs 406, 504, 604 receive at least one request from CUs 404, 506, 606 for the Candidate DU to configure L1 / L2 based inter-cell mobility for the UE. At least one request indicates at least one L1 / L2 based inter-cell mobility candidate cell. In step 1504, Candidate DUs 406, 504, 604 send at least one configuration of an L1 / L2 based inter-cell mobility candidate cell to CUs 404, 506, 606. In step 1506, candidate DU406, 504, and 604 receive RRC reconfiguration from CU404, 506, and 606. The RRC reconfiguration includes at least one configuration of L1 / L2-based inter-cell mobility candidate cells. In step 1508, candidate DU406, 504, and 604 receive RRC reconfiguration completion from UE402, 502, 602, and 800. In step 1510, candidate DU406, 504, and 604 transmit RRC reconfiguration completion from UE402, 502, 602, and 800 to CU404, 506, and 606.

[0170] According to a particular embodiment, the RRC reconstruction includes one or more of at least one CSI measurement configuration and a first cell group configuration associated with the current primary cell of the UE.

[0171] According to a particular embodiment, the candidate DU is also a source DU with respect to the UE, and the candidate DU sends a measurement report to the CU, which includes one or more measurements of one or more cells. The candidate DU also sends an RRC reconfiguration to the UE, which includes at least one configuration of L1 / L2-based inter-cell mobility candidate cells.

[0172] According to certain embodiments, before the CU transmits the measurement report, the candidate DU receives the measurement report from the UE and encapsulates the measurement report in a message for transmission to the CU.

[0173] According to certain embodiments, the candidate DU determines at least one L1 / L2 inter-cell mobility candidate cell configured with the UE based on one or more measurement values and / or measurement reports of one or more cells.

[0174] According to certain embodiments, the one or more measurement values include one or more values associated with at least one of CSI measurement values, L1 RSRP measurement values, differential RSRP measurement values, RSRQ measurement values, and SINR measurement values.

[0175] According to certain embodiments, the one or more cells associated with the measurement report include one or more neighboring cells and / or one or more non-serving cells of the UE.

[0176] According to certain embodiments, the measurement report is transmitted to the CU in the UL RRC message transfer, and / or at least one of the L1 / L2-based inter-cell mobility candidate cells is one of the one or more cells associated with the measurement report.

[0177] According to certain embodiments, at least one of the following is true. ·At least one request to the candidate DU to configure L1 / L2-based inter-cell mobility for the UE is received included in at least one UE CONTEXT MODIFICATION REQUEST, ·The configuration of at least one of the L1 / L2-based inter-cell mobility candidate cells is transmitted included in the UE CONTEXT MODIFICATION RESPONSE, ·The RRC reconfiguration is received included in the UE CONTEXT MODIFICATION REQUEST or DL RRC MESSAGE TRANSFER, • RRC reconstruction completion is sent in either the UE CONTEXT MODIFICATION RESPONSE or UL RRC MESSAGE TRANSFER.

[0178] According to a particular embodiment, at least one message is transmitted and / or received via the F1AP interface between the CU and the candidate DU.

[0179] According to a particular embodiment, the candidate DU obtains information indicating that the UE is capable of performing L1 / L2-based inter-cell mobility.

[0180] According to a particular embodiment, the RRC reconfiguration message includes multiple configurations, each of which is associated with a corresponding one of several L1 / L2-based inter-cell mobility candidate cells.

[0181] According to a particular embodiment, at least one L1 / L2-based inter-cell mobility candidate cell comprises a candidate which is at least one of a SpCell, PCell, SCell, PSCell group cell, MCG cell, and / or SCG cell.

[0182] According to a particular embodiment, at least one request to a candidate DU for configuring L1 / L2-based inter-cell mobility in a UE includes receiving a single message indicating a request to a candidate DU for configuring one L1 / L2-based inter-cell mobility candidate cell in a UE. At least one configuration of an L1 / L2-based inter-cell mobility candidate cell includes one configuration of an L1 / L2-based inter-cell mobility candidate cell.

[0183] According to a particular embodiment, a candidate DU receiving at least one request to configure L1 / L2-based inter-cell mobility in a UE includes receiving a plurality of second messages from a CU. Each of the plurality of second messages indicates a request to the candidate DU to configure one of a plurality of L1 / L2-based inter-cell mobility candidate cells in a UE. The configuration of at least one L1 / L2-based inter-cell mobility candidate cell includes the configuration of one L1 / L2-based inter-cell mobility candidate cell.

[0184] According to a particular embodiment, receiving at least one request to a candidate DU for configuring L1 / L2-based inter-cell mobility in a UE includes receiving a second message from a CU, the second message indicating a request to the candidate DU for configuring a plurality of L1 / L2-based inter-cell mobility candidate cells in a UE. The configuration of at least one L1 / L2-based inter-cell mobility candidate cell includes a plurality of configurations, each of which is associated with a corresponding one of the plurality of L1 / L2-based inter-cell mobility candidate cells.

[0185] According to a particular embodiment, a candidate DU sends a lower-layer signaling to the UE, which includes an indication of an L1 / L2-based inter-cell mobility candidate cell and / or a configuration associated with the L1 / L2-based inter-cell mobility candidate cell, to trigger the activation of the configuration of the L1 / L2-based inter-cell mobility candidate cell, the lower-layer signaling being sent to and / or received by at least one lower layer of the UE's protocol stack. The at least one lower layer includes at least one of the PDCP layer, RLC layer, MAC layer, physical layer, and L1.

[0186] According to certain embodiments, lower-layer signaling is transmitted via MAC-CE or DCI.

[0187] According to one embodiment, some or all of the functionalities described herein may be provided by a processing circuit executing a set of instructions stored in memory, and according to one embodiment, this may be a computer program in the form of a non-temporary computer-readable storage medium. product( product ) This may also be the case. In alternative embodiments, some or all of the functionality may be provided by the processing circuit, such as in a hardwired manner, without executing instructions stored in a separate or discrete device-readable storage medium. In any of these specific embodiments, the processing circuit can be configured to perform the described functionality, with or without executing instructions stored in a non-temporary computer-readable storage medium. The benefits provided by such functionality are not limited to the processing circuit alone or other components of the computing device, but are provided by the computing device as a whole, and / or to the end user and wireless This is enjoyed by the network in general.

[0188] Exemplary Embodiments Exemplary Embodiments of Group A

[0189] Exemplary Embodiment A1: A method by user device for configuring L1 / L2-based inter-cell mobility, comprising, alone or in combination with any of the steps, features, or functions of the user device described above.

[0190] Exemplary Embodiment A2. The method of the above embodiment further includes one or more additional user device steps, features, or functions described above.

[0191] Exemplary Embodiment A3. The method of any of the above embodiments, further comprising providing user data and transferring the user data to a host computer via transmission to the network node.

[0192] Exemplary Embodiments of Group B

[0193] Exemplary Embodiment B1: A method performed by a network node for configuring L1 / L2-based intercellular mobility, comprising any of the above-described steps, features, or functions of the network node, either alone or in combination with the other above-described steps, features, or functions.

[0194] Exemplary Embodiment B2: The method of the above embodiment, further comprising one or more additional network node steps, features, or functions described above.

[0195] Exemplary embodiment B3. The method of any of the above embodiments, further comprising acquiring user data and transferring the user data to a host or user device.

[0196] Exemplary Embodiments of Group C

[0197] Exemplary Embodiment C1: A method by a connected user device (UE) for configuring L1 / L2-based inter-cell mobility, comprising: receiving a first message including a measurement configuration, wherein the measurement configuration includes a reporting configuration, and the reporting configuration includes at least one trigger condition that triggers the UE to send a measurement report; transmitting the measurement report including one or more measurements (measurements) associated with one or more cells; receiving an RRC reconfiguration message including at least one configuration of L1 / L2-based inter-cell mobility candidate cells; and transmitting an RRC reconfiguration complete message.

[0198] Exemplary Embodiment C2. The method of Exemplary Embodiment C1, wherein the RRC reconstruction message comprises one or more of at least one CSI measurement configuration and a first cell group configuration associated with the current primary cell (PCell) of the UE.

[0199] Exemplary Embodiment C3. The method according to any one of the exemplary embodiments C1 to C2, wherein at least one CSI measurement configuration and / or a first cell group configuration associated with the current PCell, and / or at least one configuration of L1 / L2-based inter-cell mobility candidate cells are generated by a distributed unit (DU), encapsulated in an RRC reconfiguration message by a central unit (CU), and received by a UE via the DU.

[0200] Exemplary Embodiment C4. A method according to any one of the exemplary embodiments C1 to C3, further comprising performing the one or more measurements associated with the one or more cells according to the measurement configuration.

[0201] Exemplary Embodiment C5. The method according to any one of the exemplary embodiments C1 to C4, wherein the measurement configuration includes a channel status information (CSI) measurement configuration. Exemplary Embodiment C6. The method according to any one of the exemplary embodiments C1 to C5, wherein the one or more measurements (measurements) include at least one of an L1 RSRP measurement (measurement), a differential RSRP measurement (measurement), an RSRQ measurement (measurement), and / or a SINR measurement (measurement).

[0202] Exemplary Embodiment C7. The method according to any one of the exemplary embodiments C1 to C6, wherein the one or more cells associated with the measurement report include one or more adjacent cells and / or one or more non-serving cells.

[0203] Exemplary Embodiment C8. The method according to any one of the exemplary embodiments C1 to C7, wherein the L1 / L2-based inter-cell mobility candidate cell is one of the one or more cells associated with the measurement report.

[0204] Exemplary Embodiment C9. A method according to any one of the exemplary embodiments C1 to C8, further comprising determining that the at least one condition is met, wherein the measurement report is transmitted in response to the determination that the at least one condition is met.

[0205] Exemplary Embodiment C10. A method according to any one of the exemplary embodiments C1 to C9, wherein the RRC reconfiguration message comprises a plurality of configurations, one of which configurations is associated with a corresponding one of a plurality of L1 / L2-based inter-cell mobility candidate cells.

[0206] Exemplary Embodiment C11. A method according to any one of the exemplary embodiments C1 to C10, further comprising: receiving lower-layer signaling including an indication of the L1 / L2-based inter-cell mobility candidate cell and / or a configuration associated with the L1 / L2-based inter-cell mobility candidate cell based on the indication; and initiating an operation within the L1 / L2-based inter-cell mobility candidate cell depending on the configuration.

[0207] Exemplary embodiment C12. A method of an exemplary embodiment C11, wherein the lower-layer signaling, including the indication, triggers the activation of the configuration of the L1 / L2-based inter-cell mobility candidate cell.

[0208] Exemplary embodiment C13. The lower layer signaling is received from the distributed unit (DU) according to the method of any one of the exemplary embodiments C11 to C12.

[0209] Exemplary Embodiment Example C14. The method according to any one of the exemplary embodiments C11 to C13, wherein the lower layer signaling is received by at least one lower layer of the protocol stack of the UE, and the at least one lower layer includes at least one of PDCP, RLC, MAC, PHY, or Layer 1.

[0210] Exemplary embodiment C15. The method according to any one of the exemplary embodiments C11 to C14, wherein the lower layer signaling is received via a MAC control element or downlink control information (DCI).

[0211] Exemplary Embodiment Example C16. The method according to any one of the exemplary embodiments C1 to C15, wherein the candidate cell for at least one L1 / L2-based inter-cell mobility is a special cell (SpCell), a primary cell (PCell), a secondary cell (SCell), a primary-secondary cell group (SCG) cell (PSCell), a master cell group (MCG) cell, and / or an SCG cell.

[0212] Exemplary Embodiment C17. A method according to Exemplary Embodiments C1 to C16, further comprising providing user data and transferring the user data to a host via the transmission to the network node.

[0213] Exemplary embodiment C18. A user device comprising a processing circuit configured to perform the method described in any of the exemplary embodiments C1 to C17.

[0214] Exemplary embodiment C19. A wireless device comprising a processing circuit configured to perform the method described in any of the exemplary embodiments C1 to C17.

[0215] Exemplary Embodiment C20: A computer program that, when executed on a computer, includes instructions that perform a method described in any of the exemplary embodiments C1 to C17.

[0216] Exemplary Embodiment C21: A computer program product comprising a computer program, which, when executed on a computer, comprises instructions that perform the method described in any of the exemplary embodiments C1 to C17.

[0217] Exemplary Embodiment C22: A non-temporary computer-readable medium that, when executed by a computer, stores instructions for performing the method described in any of the exemplary embodiments C1 to C17.

[0218] Exemplary Embodiments of Group D

[0219] Exemplary Embodiment D1. A method by a central unit for configuring L1 / L2-based inter-cell mobility for a connected user device (UE), comprising: receiving a first message from a distributed unit (DU) including a measurement report from the UE, wherein the measurement report includes one or more measurements (measurements) associated with one or more cells, and transmitting at least one second message to the DU indicating a request to the DU for configuring L1 / L2-based inter-cell mobility for the UE; receiving a third message from the DU including the configuration of at least one L1 / L2-based inter-cell mobility candidate cell; transmitting a fourth message to the DU including an RRC reconfiguration to be transmitted to the UE, wherein the RRC reconfiguration includes the at least one configuration of the L1 / L2-based inter-cell mobility candidate cell; and receiving a fifth message from the DU including the completion of the RRC reconfiguration from the UE.

[0220] Exemplary Embodiment D2. A method of Exemplary Embodiment D1, wherein the RRC reconstruction message comprises one or more of at least one CSI measurement configuration and a first cell group configuration associated with the current primary cell (PCell) of the UE.

[0221] Exemplary Embodiment D3. A method according to any one of the exemplary embodiments D1 to D2, further comprising encapsulating the at least one configuration of the L1 / L2-based inter-cell mobility candidate cell within the RRC reconfiguration message for transmission via the DU to the UE.

[0222] Exemplary Embodiment D4. The method according to any one of the exemplary embodiments D1 to D3, wherein the one or more measurements (measurements) include one or more channel status information (CSI) measurements (measurements).

[0223] Exemplary Embodiment D5. A method according to any one of Exemplary Embodiments D1 to D4, wherein the one or more measurements (measurements) include one or more values ​​associated with at least one of L1 RSRP measurements (measurements), differential RSRP measurements (measurements), RSRQ measurements (measurements), and / or SINR measurements (measurements).

[0224] Exemplary Embodiment D6. The method according to any one of the exemplary embodiments D1 to D5, wherein the one or more cells associated with the measurement report include one or more adjacent cells and / or one or more non-serving cells of the UE.

[0225] Exemplary Embodiment D7. The method according to any one of the exemplary embodiments D1 to D6, wherein at least one of the L1 / L2-based intercellular mobility candidate cells is one of the one or more cells associated with the measurement report.

[0226] Exemplary embodiment D8a. The method according to any one of the exemplary embodiments D1 to D7, wherein the first message includes a UL RRC MESSAGE TRANSFER.

[0227] Exemplary Embodiment D8b. The method according to any one of the exemplary embodiments D1 to D8a, wherein the at least one second message includes at least one UE CONTEXT MODIFICATION REQUEST.

[0228] Exemplary Embodiment D9. The method according to any one of the exemplary embodiments D1 to D8b, wherein the third message includes a UE CONTEXT MODIFICATION RESPONSE.

[0229] Exemplary Embodiment D10. The method according to any one of the exemplary embodiments D1 to D9, wherein the fourth message includes a UE context correction request or a DL RRC MESSAGE TRANSFER (DL RRC message transfer).

[0230] Exemplary Embodiment D11. The method according to any one of the exemplary embodiments D1 to D10, wherein the fifth message includes a UE context correction response or a UL RRC MESSAGE TRANSFER.

[0231] Exemplary Embodiment D12. A method according to any one of the exemplary embodiments D1 to D11, wherein at least one of the first message, the at least one second message, the third message, the fourth message, and / or the fifth message is transmitted and / or received via the F1AP interface between the CU and the DU.

[0232] Exemplary Embodiment D13. The method according to any one of the exemplary embodiments D1 to D12, wherein at least one second message indicating a request to the DU for configuring L1 / L2-based inter-cell mobility to the UE is based on a received measurement report including one or more measurements of one or more cells.

[0233] Exemplary Embodiment D14. A method according to any one of the exemplary embodiments D1 to D13, wherein the first message includes the one or more measurements and / or the measurement report of the one or more cells.

[0234] Exemplary Embodiment D15. A method according to any one of the Exemplary Embodiments D1 to D14, further comprising the DU sending a previous message, including a measurement configuration, before the CU receives the first message, including the measurement report, from the DU, the measurement configuration including a report configuration, the report configuration including at least one trigger condition, and when the at least one trigger condition is met, the transmission of the measurement report by the UE is triggered.

[0235] Exemplary Embodiment D16. The method according to any one of the exemplary embodiments D1 to D15, further comprising obtaining information indicating that the UE has the capability to perform L1 / L2-based inter-cell mobility.

[0236] Exemplary Embodiment D17. The method according to any one of the exemplary embodiments D1 to D16, wherein the RRC reconfiguration message comprises a plurality of configurations, each of which is associated with a corresponding one of a plurality of L1 / L2-based inter-cell mobility candidate cells.

[0237] Exemplary Embodiment D18. A method according to any one of the Exemplary Embodiments D1 to D17, wherein at least one L1 / L2-based inter-cell mobility candidate cell is a candidate which is at least one of a special cell (SpCell), a primary cell (PCell), a secondary cell (SCell), a primary-secondary cell group (SCG) cell (PSCell), a master cell group (MCG) cell, and / or an SCG cell.

[0238] Exemplary Embodiment D19. The method according to any one of the exemplary embodiments D1 to D18, wherein sending at least one second message to the DU includes sending one second message indicating a request to the DU to configure one L1 / L2-based inter-cell mobility candidate cell in the UE, and the third message includes the configuration of one L1 / L2-based inter-cell mobility candidate cell.

[0239] Exemplary Embodiment D20. The method according to any one of the exemplary embodiments D1 to D18, wherein sending at least one second message to the DU includes sending a plurality of second messages to the DU, one of the plurality of second messages indicating a request to the DU to configure each of a plurality of L1 / L2-based inter-cell mobility candidate cells to the UE, and the third message including the configuration of one of the L1 / L2-based inter-cell mobility candidate cells.

[0240] Exemplary Embodiment D21. A method according to any one of the Exemplary Embodiments D1 to D18, wherein sending at least one second message to the DU comprises sending one second message to the DU, the second message indicating a request to the DU to configure a plurality of L1 / L2-based inter-cell mobility candidate cells in the UE, and the third message comprises a plurality of configurations, each of which configurations is associated with each corresponding one of the plurality of L1 / L2-based inter-cell mobility candidate cells.

[0241] Exemplary Embodiment D22. The network node is a system according to any one of the exemplary embodiments D1 to D21, including a gNodeB (gNB).

[0242] Exemplary Embodiment D23. A method according to any one of the exemplary embodiments D1 to D22, further comprising acquiring user data and transferring the user data to a host or user device.

[0243] Exemplary Embodiment D24. A network node comprising a processing circuit configured to perform the method described in any one of the exemplary embodiments D1 to D23.

[0244] Exemplary Embodiment D25: A computer program that, when executed on a computer, includes instructions to perform the method described in any one of the exemplary embodiments D1 to D23.

[0245] Exemplary Embodiment D26. A computer program product comprising a computer program, which, when executed on a computer, comprises instructions that perform the method described in any one of the exemplary embodiments D1 to D23.

[0246] Exemplary Embodiment D27: A non-temporary computer-readable medium that, when executed by a computer, stores instructions for performing the method described in any one of the exemplary embodiments D1 to D23.

[0247] Exemplary Embodiments of Group E

[0248] Exemplary Embodiment E1. A method by a distributed unit for configuring L1 / L2-based inter-cell mobility for a connected user device (UE), the method comprising: transmitting a first message to a central unit (CU) including a measurement report; receiving at least one second message from the CU indicating a request to the DU for configuring L1 / L2-based inter-cell mobility for the UE, wherein the measurement report includes one or more measurements of one or more cells; transmitting a third message to the CU including the configuration of at least one L1 / L2-based inter-cell mobility candidate cell; receiving a fourth message from the CU including an RRC reconfiguration, wherein the RRC reconfiguration includes the at least one configuration of the L1 / L2-based inter-cell mobility candidate cell; transmitting the RRC reconfiguration to the UE, including the at least one configuration of the L1 / L2-based inter-cell mobility candidate cell; receiving RRC reconfiguration completion from the UE; and transmitting a fifth message from the UE including RRC reconfiguration completion to the CU.

[0249] Exemplary Embodiment E2. A method of Exemplary Embodiment E1, wherein the RRC reconstruction message comprises one or more of at least one CSI measurement configuration and a first cell group configuration associated with the current primary cell (PCell) of the UE.

[0250] Exemplary Embodiment E3. The method according to any one of the exemplary embodiments E1 to E2, further comprising: receiving the measurement report from the UE and encapsulating the measurement report in the first message for transmission to the CU, before sending the first message.

[0251] Exemplary embodiment E4. The method according to any one of the exemplary embodiments E1 to E3, wherein the one or more measurements include one or more channel status information (CSI) measurements.

[0252] Exemplary Embodiment E5. A method according to any one of the exemplary embodiments E1 to E4, wherein the one or more measured values ​​include one or more values ​​associated with at least one of the following: RSRP measurement, differential RSRP measurement, RSRQ measurement, and / or SINR measurement of L1.

[0253] Exemplary Embodiment E6. The method according to any one of the exemplary embodiments E1 to E5, wherein one or more cells associated with the measurement report include one or more adjacent cells and / or one or more non-serving cells of the UE.

[0254] The method according to any one of the exemplary embodiments E1 to E6, wherein at least one of the L1 / L2-based inter-cell mobility candidate cells is one of the one or more cells associated with the measurement report.

[0255] Exemplary embodiment E8a. The method according to any one of the exemplary embodiments E1 to E7, wherein the first message includes a UL RRC message transfer.

[0256] Exemplary Embodiment E8b. The method according to any one of the exemplary embodiments E1 to E8a, wherein the at least one second message includes at least one UE context modification request.

[0257] Exemplary embodiment E9. The method according to any one of the exemplary embodiments E1 to E8b, wherein the third message includes a UE context modification response.

[0258] Exemplary embodiment E10. The method according to any one of embodiments E1 to E9, wherein the fourth message includes a UE context correction request or a DL RRC message transfer.

[0259] Exemplary Embodiment E11. The method according to any one of the exemplary embodiments E1 to E10, wherein the fifth message includes a UE context correction response or a UL RRC message transfer.

[0260] Exemplary Embodiment E12. A method according to any one of the exemplary embodiments E1 to E11, wherein at least one of the first message, the at least one second message, the third message, the fourth message, and / or the fifth message is transmitted and / or received via the F1AP interface between the CU and the DU.

[0261] Exemplary Embodiment E13. The method according to any one of the exemplary embodiments E1 to E12, wherein at least one second message indicating a request to the DU for configuring L1 / L2-based inter-cell mobility to the UE is based on a received measurement report, including one or more measurements of one or more cells.

[0262] Exemplary Embodiment E14a. A method according to any one of the exemplary embodiments E1 to E13, wherein the first message includes one or more measurements and / or measurement reports of one or more cells.

[0263] Exemplary Embodiment E14b. A method according to any one of the exemplary embodiments E1 to E14a, further comprising determining at least one L1 / L2 intercellular mobility candidate cell to be configured for a UE based on one or more measurements and / or measurement reports of one or more cells.

[0264] Exemplary Embodiment E15a. A method according to any one of the exemplary embodiments E1 to E14b, wherein, before the measurement report is received, the method further comprises sending a previous message including a measurement configuration to the UE, the measurement configuration including a report configuration, the report configuration including at least one trigger condition, and when the at least one trigger condition is met, the transmission of the measurement report by the UE is triggered.

[0265] Exemplary embodiment E15b. A method of the exemplary embodiment E15a, further comprising receiving the measurement configuration from the CU.

[0266] Exemplary Embodiment E16. The method according to any one of the exemplary embodiments E1 to E15b, further comprising obtaining information indicating that the UE can perform L1 / L2-based inter-cell mobility.

[0267] Exemplary Embodiment E17. The method according to any one of the exemplary embodiments E1 to E16, wherein the RRC reconfiguration message comprises a plurality of configurations, each of which configurations is associated with a corresponding one of a plurality of L1 / L2-based inter-cell mobility candidate cells.

[0268] Exemplary Embodiment Example E18. The method according to any one of the exemplary embodiments E1 to E17, wherein the candidate cell for at least one L1 / L2-based inter-cell mobility is a candidate cell which is at least one of a special cell (SpCell), a primary cell (PCell), a secondary cell (SCell), a primary-secondary cell group (SCG) cell (PSCell), a master cell group (MCG) cell, and / or an SCG cell.

[0269] Exemplary Embodiment E19. The method according to any one of the exemplary embodiments E1 to E18, wherein receiving the at least one second message from the CU includes receiving a second message indicating a request to the DU to configure one L1 / L2-based inter-cell mobility candidate cell in the UE, and the third message includes the configuration of one L1 / L2-based inter-cell mobility candidate cell.

[0270] Exemplary Embodiment E20. A method according to any one of the Exemplary Embodiments E1 to E18, wherein receiving the at least one second message from the CU comprises receiving a plurality of second messages from the CU, one of which the plurality of second messages indicates a request to the DU to configure one of a plurality of L1 / L2-based inter-cell mobility candidate cells in the UE, and the third message comprises the configuration of one of the L1 / L2-based inter-cell mobility candidate cells.

[0271] Exemplary Embodiment E21. The method according to any one of the exemplary embodiments E1 to E18, wherein receiving the at least one second message from the CU comprises receiving one second message from the CU, the second message indicating a request to the DU to configure a plurality of L1 / L2-based inter-cell mobility candidate cells in the UE, and the third message comprises a plurality of configurations, each of which configurations is associated with a corresponding one of the plurality of L1 / L2-based inter-cell mobility candidate cells.

[0272] Exemplary Embodiment E22. A method according to any one of the exemplary embodiments E1 to E21, further comprising sending lower-layer signaling to the UE, which includes an indication of an L1 / L2-based inter-cell mobility candidate cell and / or a configuration associated with an L1 / L2-based inter-cell mobility candidate cell, in order to trigger the activation of the configuration of an L1 / L2-based inter-cell mobility candidate cell.

[0273] Exemplary Embodiment E23. A method of Exemplary Embodiment E22, wherein the lower layer signaling is transmitted to and / or received by at least one lower layer of the protocol stack of the UE, the at least one lower layer comprising at least one of PDCP, RLC, MAC, PHY, or Layer 1.

[0274] Exemplary embodiment E24. The method according to any one of the exemplary embodiments E22-E23, wherein lower layer signaling is transmitted via MAC control elements or downlink control information (DCI).

[0275] Exemplary Embodiment E25. The network node is the method according to any one of the exemplary embodiments E1 to E24, wherein the network node includes a gNodeB (gNB).

[0276] Exemplary Embodiment E26. A method according to any one of the exemplary embodiments E1 to E25, further comprising acquiring user data and transferring the user data to a host or user device.

[0277] Exemplary embodiment E27. A network node including a processing circuit configured to perform any of the methods of exemplary embodiments E1 to E26.

[0278] Exemplary Embodiment E28: A computer program that, when executed on a computer, includes instructions that perform a method according to any of the exemplary embodiments E1 to E26.

[0279] Exemplary Embodiment E29. A computer program product comprising a computer program, which, when executed on a computer, comprises instructions that perform the method described in any of the exemplary embodiments E1 to E26.

[0280] Exemplary Embodiment E30: A non-temporary computer-readable medium that, when executed by a computer, stores instructions for performing the method described in any of the exemplary embodiments E1 to E26.

[0281] Exemplary Embodiments of Group F

[0282] Exemplary Embodiment F1: A connected user device for configuring L1 / L2-based inter-cell mobility, comprising a processing circuit configured to perform any step in any of the exemplary embodiments in groups A and C, and a power supply circuit configured to supply power to the processing circuit.

[0283] Exemplary Embodiment F2. A network node for configuring L1 / L2-based inter-cell mobility for a connected user device (UE), comprising a processing circuit configured to perform any step of any of the exemplary embodiments in groups B, D, and E, and a power supply circuit configured to supply power to the processing circuit.

[0284] Exemplary Embodiment E3. A connected user device (UE) for configuring L1 / L2-based inter-cell mobility, the UE comprising: an antenna configured to transmit and receive radio signals; a radio front-end circuit connected to the antenna and a processing circuit and configured to adjust signals communicated between the antenna and the processing circuit; the processing circuit configured to perform any step of the exemplary embodiments in any of the groups A and C; an input interface connected to the processing circuit and configured to allow input of information to the UE to be processed by the processing circuit; an output interface connected to the processing circuit and configured to output information from the UE processed by the processing circuit; and a battery connected to the processing circuit and configured to supply power to the UE.

[0285] Exemplary Embodiment E4. A host configured to operate in a communication system to provide an over-the-top (OTT) service, comprising processing circuitry configured to provide user data and a network interface configured to initiate transmission of user data to a cellular network for transmission to a user device (UE), wherein the UE comprises a communication interface and processing circuitry, and the communication interface and processing circuitry of the UE are configured to perform any step of any of the exemplary embodiments in groups A and C to receive user data from the host.

[0286] Exemplary Embodiment E5. The host of the exemplary embodiment further includes network nodes configured to communicate with the UE in order to transmit the user data from the host to the UE.

[0287] Exemplary Embodiment E6. A host according to the two exemplary embodiments described above, wherein the processing circuit of the host is configured to execute a host application and thereby provide user data, the host application is configured to interact with a client application running on the UE, and the client application is associated with the host application.

[0288] Exemplary Embodiment E7. A method performed by a host operating in a communication system further comprising network nodes and user equipment (UEs), comprising providing user data for the UE and initiating a transmission to carry the user data to the UE via a cellular network comprising the network nodes, wherein the UE performs any operation of any embodiment in Group A in order to receive the user data from the host.

[0289] Exemplary Embodiment E8. A method of the above-described exemplary embodiment, further comprising, on the host, running a host application associated with a client application running on the UE, and receiving the user data from the UE.

[0290] Exemplary Embodiment E9. A method of the exemplary embodiment described above, further comprising the host transmitting input data to a client application running on the UE, wherein the input data is provided by running a host application, and the user data is provided by the client application in response to the input data from the host application.

[0291] Exemplary Embodiment E10. A host configured to operate in a communication system to provide over-the-top (OTT) services, 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 device (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE are configured to perform any step of any of the exemplary embodiments in groups A and C to transmit the user data to the host.

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

[0293] Exemplary Embodiment E12. A host of the two exemplary embodiments described above, wherein the processing circuit of the host is configured to run a host application and thereby provide user data, the host application is configured to interact with a client application running on the UE, and the client application is associated with the host application.

[0294] Exemplary Embodiment E13. A method performed by a host configured to operate in a communication system further including network nodes and user equipment (UEs), the host comprising receiving user data transmitted to the host by the UEs via the network nodes, wherein the UEs perform any step of any of the exemplary embodiments in groups A and C to transmit the user data to the host.

[0295] Exemplary Embodiment E14. A method of the exemplary embodiment described above, further comprising, on the host, running a host application associated with a client application running on the UE, and receiving the user data from the UE.

[0296] Exemplary Embodiment E15. A method of the exemplary embodiment described above, further comprising the host transmitting input data to a client application running on the UE, wherein the input data is provided by running a host application, and the user data is provided by the client application in response to the input data from the host application.

[0297] Exemplary Embodiment E16. A host configured to operate in a communication system to provide over-the-top (OTT) services, comprising: a processing circuit configured to provide user data; and a network interface configured to initiate the transmission of user data to a network node in a cellular network for transmission to a user device (UE), wherein the network node comprises a communication interface and a processing circuit, and the processing circuit of the network node is configured to perform any operation of any of the exemplary embodiments in groups B, D, and E in order to transmit the user data from the host to the UE.

[0298] Exemplary Embodiment E17. A host according to the above-described exemplary embodiment, wherein the processing circuit of the host is configured to run a host application that provides the user data, and the UE comprises a processing circuit configured to run a client application associated with the host application and to receive a transmission signal of the user data from the host.

[0299] Exemplary Embodiment E18. A method performed on a host configured to operate in a communication system further including network nodes and user equipment (UEs), comprising providing user data for the UEs and initiating a transmission to carry the user data to the UEs via a cellular network comprising the network nodes, wherein the network nodes perform any operation of any of the exemplary embodiments in groups B, D, and E in order to transmit the user data from the host to the UEs.

[0300] Exemplary Embodiment E19. A method of the above-described exemplary embodiment, further comprising transmitting the user data provided by the host for the UE at the network node.

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

[0302] Exemplary Embodiment E21. A communication system configured to provide an over-the-top service, wherein the communication system has a host, the host having processing circuitry configured to provide user data to a user device (UE), the user data being associated with the over-the-top service and having a network interface configured to initiate transmission of the user data to a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any operation of any of the exemplary embodiments in groups B, D, and E for transmitting the user data from the host to the UE.

[0303] Exemplary Embodiment E22. A communication system according to the above-described exemplary embodiment, further comprising the network node and / or the user device.

[0304] Exemplary Embodiment E23. A host configured to operate in a communication system to provide over-the-top (OTT) services, comprising: a processing circuit configured to initiate the reception of user data; and a network interface configured to receive the user data from a network node in a cellular network, wherein the network node comprises a communication interface and a processing circuit, and the processing circuit of the network node is configured to perform any operation of any of the exemplary embodiments in groups B, D, and E in order to receive user data from a user device (UE) to the host.

[0305] Exemplary Embodiment E24: A host of the two exemplary embodiments described above, wherein the host's processing circuit is configured to execute a host application and thereby provide the user data, the host application is configured to interact with a client application running on the UE, and the client application is associated with the host application.

[0306] Exemplary Embodiment E25. A host according to either of the two exemplary embodiments described above, wherein initiating the reception of the user data includes requesting the user data.

[0307] Exemplary Embodiment E26. A method performed by a host configured to operate in a communication system further including network nodes and user equipment (UEs), wherein the host initiates the reception of user data from the UE, the user data originating from a transmission signal received by the network node from the UE, and the network node performs any step of any of the exemplary embodiments in groups B, D, and E above to receive the user data from the UE to the host.

[0308] Exemplary Embodiment E27. A method of the above-described exemplary embodiment, further comprising transmitting the received user data to the host at the network node.

Claims

1. A method (1400) by a central unit (CU) (404, 506, 606) for configuring Layer 1 / Layer 2 (L1 / L2) based inter-cell mobility for connected user equipment (UE) (402, 502, 602, 800), wherein the method is Sending at least one request to candidate DUs (406, 504, 604) to configure L1 / L2-based inter-cell mobility in the UE (1402), wherein the at least one request indicates at least one L1 / L2-based inter-cell mobility candidate cell. Receiving at least one configuration of the L1 / L2-based inter-cell mobility candidate cell from the candidate DU (1404), Transmitting a radio resource control (RRC) reconfiguration to the candidate DU, which will be transmitted to the UE (1406), wherein the RRC reconfiguration includes the at least one configuration of the L1 / L2-based inter-cell mobility candidate cell. Receiving from the candidate DU that the RRC reconstruction from the UE is complete (1408), It has, The method further comprises obtaining information indicating that the UE enables L1 / L2-based inter-cell mobility.

2. A method according to claim 1, wherein the candidate DU is a source DU for the UE.

3. The method according to claim 1, wherein the RRC reconstruction is At least one channel state information (CSI) measurement configuration, A first cell group configuration associated with the current primary cell (PCell) of the aforementioned UE, A method that includes one or more of the following.

4. The method according to claim 1, A method comprising encapsulating the at least one configuration of the L1 / L2-based inter-cell mobility candidate cell into the RRC reconstruction for transmission to the UE via the candidate DU.

5. A method according to claim 1, comprising receiving a measurement report of the UE from a source distribution unit (DU), wherein the measurement report includes one or more measurements associated with one or more cells.

6. The method according to claim 5, wherein the one or more measured values ​​are Channel state information measurement and, Layer 1 reference signal received power measurement and, Measurement of differential reference signal received power, Reference signal reception quality measurement, Signal-to-interference noise ratio measurement, A method comprising one or more values ​​associated with at least one of the following.

7. The method according to claim 5, The aforementioned measurement report is received in a UL RRC message transfer, The one or more cells associated with the measurement report include one or more adjacent cells and / or one or more non-serving cells of the UE, At least one of the L1 / L2-based inter-cell mobility candidate cells is one or more cells associated with the measurement report, A method that is at least one of the following.

8. A method (1400) by a central unit (CU) (404, 506, 606) for configuring Layer 1 / Layer 2 (L1 / L2) based inter-cell mobility for connected user equipment (UE) (402, 502, 602, 800), wherein the method is Sending at least one request to candidate DUs (406, 504, 604) to configure L1 / L2-based inter-cell mobility in the UE (1402), wherein the at least one request indicates at least one L1 / L2-based inter-cell mobility candidate cell. Receiving at least one configuration of the L1 / L2-based inter-cell mobility candidate cell from the candidate DU (1404), Transmitting a radio resource control (RRC) reconfiguration to the candidate DU, which will be transmitted to the UE (1406), wherein the RRC reconfiguration includes the at least one configuration of the L1 / L2-based inter-cell mobility candidate cell. Receiving from the candidate DU that the RRC reconstruction from the UE is complete (1408), It has, The method further comprises receiving a measurement report of the UE from a source distribution unit (DU), the measurement report comprising one or more measurements associated with one or more cells, and the request to the candidate DU for configuring the L1 / L2-based inter-cell mobility of the UE being based on the received measurement report comprising the one or more measurements of the one or more cells.

9. The method according to claim 5, The CU sends a message including the measurement configuration to the source DU before receiving the measurement report from the source DU, Such measurement configurations include reporting configurations, The reporting configuration is a method comprising the at least one trigger condition for triggering the transmission of the measurement report by the UE when at least one trigger condition is met.

10. The method according to claim 1, The at least one request to the candidate DU for configuring L1 / L2-based inter-cell mobility in the UE is transmitted in at least one UE context modification request, The configuration of at least one of the L1 / L2-based inter-cell mobility candidate cells is included in the UE context modification response and received. The RRC reconstruction is transmitted in a UE context modification request or a DL RRC message transfer, The completion of the RRC reconstruction is received in the UE context correction response or UL RRC message transfer, A method having at least one of the following.

11. A method according to claim 1, wherein at least one message is transmitted and / or received via an F1 Application Protocol (F1AP) interface between the CU and the candidate DU.

12. A method according to claim 8, comprising obtaining information indicating that the UE enables L1 / L2-based inter-cell mobility.

13. A method according to claim 1, wherein the RRC reconstruction comprises a plurality of configurations, each of which is associated with a corresponding one of a plurality of L1 / L2-based intercellular mobility candidate cells.

14. The method according to claim 1, wherein the at least one L1 / L2-based intercellular mobility candidate cell is Special cell and, Primary cell and Secondary cell and Primary secondary cell group cell, Master cell group cell, Secondary cell group cell and A method that includes a candidate which is at least one of the following.

15. A method (1400) by a central unit (CU) (404, 506, 606) for configuring Layer 1 / Layer 2 (L1 / L2) based inter-cell mobility for connected user equipment (UE) (402, 502, 602, 800), wherein the method is Sending at least one request to candidate DUs (406, 504, 604) to configure L1 / L2-based inter-cell mobility in the UE (1402), wherein the at least one request indicates at least one L1 / L2-based inter-cell mobility candidate cell. Receiving at least one configuration of the L1 / L2-based inter-cell mobility candidate cell from the candidate DU (1404), Transmitting a radio resource control (RRC) reconfiguration to the candidate DU, which will be transmitted to the UE (1406), wherein the RRC reconfiguration includes the at least one configuration of the L1 / L2-based inter-cell mobility candidate cell. Receiving from the candidate DU that the RRC reconstruction from the UE is complete (1408), Having and sending the at least one request to the candidate DU for configuring L1 / L2-based inter-cell mobility in the UE is, This includes sending a single message indicating a request for the candidate DU to configure one L1 / L2-based inter-cell mobility candidate cell to the UE, A method wherein the at least one configuration of the L1 / L2-based inter-cell mobility candidate cell includes one configuration of the L1 / L2-based inter-cell mobility candidate cell.

16. A method (1400) by a central unit (CU) (404, 506, 606) for configuring Layer 1 / Layer 2 (L1 / L2) based inter-cell mobility for connected user equipment (UE) (402, 502, 602, 800), wherein the method is Sending at least one request to candidate DUs (406, 504, 604) to configure L1 / L2-based inter-cell mobility in the UE (1402), wherein the at least one request indicates at least one L1 / L2-based inter-cell mobility candidate cell. Receiving at least one configuration of the L1 / L2-based inter-cell mobility candidate cell from the candidate DU (1404), Transmitting a radio resource control (RRC) reconfiguration to the candidate DU, which will be transmitted to the UE (1406), wherein the RRC reconfiguration includes the at least one configuration of the L1 / L2-based inter-cell mobility candidate cell. Receiving from the candidate DU that the RRC reconstruction from the UE is complete (1408), Having and sending the at least one request to the candidate DU for configuring L1 / L2-based inter-cell mobility in the UE is, This includes sending a plurality of messages to the candidate DU, each of which one of the plurality of messages indicates a request to the candidate DU to configure one of a plurality of L1 / L2-based inter-cell mobility candidate cells into the corresponding UE. A method wherein the at least one configuration of the L1 / L2-based inter-cell mobility candidate cell includes one configuration of the L1 / L2-based inter-cell mobility candidate cell.

17. A method (1400) by a central unit (CU) (404, 506, 606) for configuring Layer 1 / Layer 2 (L1 / L2) based inter-cell mobility for connected user equipment (UE) (402, 502, 602, 800), wherein the method is Sending at least one request to candidate DUs (406, 504, 604) to configure L1 / L2-based inter-cell mobility in the UE (1402), wherein the at least one request indicates at least one L1 / L2-based inter-cell mobility candidate cell. Receiving at least one configuration of the L1 / L2-based inter-cell mobility candidate cell from the candidate DU (1404), Transmitting a radio resource control (RRC) reconfiguration to the candidate DU, which will be transmitted to the UE (1406), wherein the RRC reconfiguration includes the at least one configuration of the L1 / L2-based inter-cell mobility candidate cell. Receiving from the candidate DU that the RRC reconstruction from the UE is complete (1408), Having and sending the at least one request to the candidate DU for configuring L1 / L2-based inter-cell mobility in the UE is, This includes sending a single message to the candidate DU, the single message indicating a request to the candidate DU to configure a plurality of L1 / L2-based inter-cell mobility candidate cells in the UE, A method wherein the at least one configuration of the L1 / L2-based inter-cell mobility candidate cell comprises a plurality of configurations, each of which is associated with a corresponding one of a plurality of L1 / L2-based inter-cell mobility candidate cells.

18. A central unit (CU) for configuring Layer 1 / Layer 2 (L1 / L2) based inter-cell mobility for a connected user device (UE), wherein the CU is Send at least one request to the candidate DU for configuring L1 / L2-based inter-cell mobility in the UE, wherein the at least one request indicates at least one L1 / L2-based inter-cell mobility candidate cell. The configuration of at least one L1 / L2-based inter-cell mobility candidate cell is received from the candidate DU, A radio resource control (RRC) reconfiguration to be transmitted to the UE is transmitted to the candidate DU, wherein the RRC reconfiguration includes at least one configuration of the L1 / L2-based inter-cell mobility candidate cell. The candidate DU receives confirmation from the UE that the RRC reconstruction is complete. It is suitable for, The CU is further adapted to acquire information indicating that the UE enables L1 / L2-based inter-cell mobility.

19. A CU according to claim 18, wherein the CU is adapted to perform the method described in any one of claims 2 to 17.

20. A computer program that causes a central unit (CU) to execute the method according to any one of claims 1 to 17.

Images