RRC configuration file management

By generating and managing RRC configuration file identifiers, the problems of duplicate transmission and mismatch of configuration files during 5G RRC are solved, enabling efficient handover and connection restoration of user equipment between different cells, and improving network energy efficiency and performance.

CN123125950APending Publication Date: 2026-11-17NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580026142.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-04-11
Filing Date
2025-02-18
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

The existing 5G RRC process suffers from duplicate transmission and mismatch issues of configuration files in user equipment mobility scenarios, resulting in resource waste and latency, and affecting network performance and energy efficiency.

Method used

By generating and managing RRC profile identifiers, existing profiles can be reused when user equipment moves, reducing redundant configuration transmissions and optimizing the conversion and adaptation of RRC profiles by utilizing database storage and signaling between network nodes.

Benefits of technology

It improves the efficiency of RRC configuration management, reduces signaling latency and energy consumption, supports smooth handover and connection recovery of user equipment between different cells, and enhances network energy efficiency and performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125950A_ABST
    Figure CN123125950A_ABST
Patent Text Reader

Abstract

A method is provided to be performed by a network node in a first cell (such as a target cell), the method comprising: obtaining information of a plurality of second cell radio resource control (RRC) profiles associated with user equipment in a second cell, wherein each RRC profile includes a set of parameters for at least RRC configuration of the user equipment; and generating a plurality of first cell RRC profiles for use in the first cell based on the plurality of second cell RRC profiles.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Various example embodiments generally relate to the management of Radio Resource Control (RRC) configurations during user equipment mobility. Background Technology

[0002] When a User Equipment (UE) moves, it may undergo handover or cell reselection. In either case, RRC configuration / profile management is required. This is resource-intensive and may not be efficient. Summary of the Invention

[0003] The subject matter of the independent claims is provided according to several aspects. Additional aspects are defined in the dependent claims. Embodiments not falling within the scope of the claims are to be interpreted as examples useful for understanding this disclosure. Attached Figure Description

[0004] The invention will now be described in more detail with reference to embodiments and accompanying drawings, in which: Figure 1 One or more embodiments of the network to which this embodiment applies are presented; Figure 2 , Figure 4 , Figure 5 and Figure 6 An exemplary signaling flowchart according to some embodiments is shown; Figure 3 and Figures 7 to 12 A method according to some embodiments is shown; and Figure 13 An apparatus according to some embodiments is shown. Detailed Implementation

[0005] The following embodiments are exemplary. Although the specification may refer to "a," "an," or "some" (or more) embodiments in several places in the text, this does not necessarily mean that the same (or more) embodiments are mentioned every time, or that a particular feature applies only to a single embodiment. Individual features of different embodiments may also be combined to provide other embodiments. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, whether explicitly described or not, the application of such a feature, structure, or characteristic in conjunction with other embodiments is within the knowledge of those skilled in the art. It should be understood that although the terms "first," "second," etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another.

[0006] For the purposes of this disclosure, the phrases "at least one of A or B", "at least one of A and B", and "A and / or B" mean (A), (B), or (A and B). For the purposes of this disclosure, the phrases "A, B, and / or C" mean (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0007] The described embodiments can be implemented in a communication network, such as any of the following radio access technologies (RATs): Global Microwave Access Interoperability (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced Long Term Evolution and Enhanced LTE (eLTE), 5G (also known as NR), or any future RAT (such as 6G). Furthermore, communication within the communication network can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), and / or Discrete Fourier Transform Extended OFDM (DFT-s-OFDM).

[0008] As used herein, the term "network device" or "network node" refers to a node in a communication network through which user equipment can access the network and / or control radio communications and manage radio resources within a cell. A network node or network device may be referred to as a base station (BS), access point (AP), or access node. Depending on the technology applied, a network device may be, for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a remote radio unit (RRU), a radio head unit (RH), a remote radio head unit (RRH), a relay, an integrated access and backhaul (IAB) node, a low-power node, a non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment, low Earth orbit (LEO) satellites, and geostationary Earth orbit (GEO) satellites), or a spacecraft network device.

[0009] Furthermore, in the context of a split radio access network (RAN), network equipment can refer to a central unit (CU) and / or a distributed unit (DU) of a base station. The interface between the CU and DU may be referred to as the F1 interface in NR. In a split RAN architecture, node operations can be performed at least partially in a central / central unit (CU) (e.g., a server, host, or node) that is operatively coupled to a DU (e.g., a radio head / node). A CU can control one or more DUs, at least acting as a transmit / receive (Tx / Rx) node. In some embodiments, a DU may include, for example, a Radio Link Control (RLC), Media Access Control (MAC) layer, and a Physical (PHY) layer, while a CU may include layers above the RLC layer, such as the Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC), and Internet Protocol (IP) layer. Other functional separations are also possible. In practice, any processing task can be performed in a CU or DU, and the boundaries of responsibility transfer between the CU and DU can depend on the applied implementation.

[0010] The term "terminal device" refers to any terminal device capable of wireless communication. For example, a terminal device can be referred to as a communication device, user equipment (UE), subscriber station (SS), or mobile station (MS). Terminal devices can include mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, USB dongles, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, and so on.

[0011] As used herein, the term "resource" can refer to radio resources in the time domain, frequency domain, spatial domain, and / or code domain. Some examples of resources include, for example, physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. The terms "transmission" and / or "reception" can refer to wireless transmission and / or reception over radio resources via a radio propagation channel.

[0012] Figure 1An example of a communication network to which the examples disclosed herein can be applied is shown. The communication network, or cellular communication network, may include a network node 110 providing one or more cells (such as cell 100) and a network node 112 providing one or more other cells (such as cell 102). For example, each cell may be, for example, a macrocell, microcell, femtocell, or picocell. A cell may define the coverage area or service area of ​​a corresponding access node.

[0013] Network node 110 can provide radio access to a communication network to user equipment (UE) 120 (one or more UEs). Radio access may include downlink (DL) communication from the network node to UE 120 and uplink (UL) communication from UE 120 to the network node. Examples of uplink channels include the Physical Uplink Control Channel (PUCCH) for transmitting control information and the Physical Uplink Shared Channel (PUSCH) for transmitting data to the network. Examples of downlink channels include the Physical Downlink Control Channel (PDCCH) for transmitting control information and the Physical Downlink Shared Channel (PDSCH) for transmitting data to the user equipment.

[0014] Multiple UEs 120 and 122 can exist in the system. Each of them can be served by the same or different control nodes 110 and 112. UEs 120 and 122 can communicate with each other when a device-to-device (D2D) communication interface is established between them via a so-called side link (SL). For example, such D2D communication can be referred to as machine-to-machine, peer-to-peer (P2P) communication, or vehicle-to-vehicle (V2V) communication.

[0015] In a communication network with multiple network nodes, these nodes can connect to each other via interfaces. The LTE specification refers to such interfaces as X2 interfaces. Interfaces between LTE nodes and 5G nodes, or between two 5G nodes, can be referred to as Xn interfaces.

[0016] Network nodes 110 and 112 can also be connected to the core 116 of the communication network via another interface. The LTE specification designates the core network as an Evolved Packet Core (EPC), and the core network may include, for example, a Mobility Management Entity (MME) and gateway nodes. The MME can handle the mobility of terminal devices in a tracking area containing multiple cells and handle signaling connections between the terminal devices and the core network. Gateway nodes can handle data routing in the core network to / from terminal devices. The 5G specification designates the core network as a 5G Core (5GC). The 5G Core may include, for example, Access and Mobility Management Functions (AMF) and User Plane Functions / Gateways (UPF), as well as other functions. The AMF can handle the termination of Non-Access Stratum (NAS) signaling, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. For example, a UPF node can support packet routing and forwarding, packet inspection, and Quality of Service (QoS) processing.

[0017] Reducing network energy consumption is a key element of future wireless networks. The RRC protocol and its operation impact overall network performance, including energy efficiency. In the standard, the 5G RRC process has predetermined processing latency requirements, which the UE should be able to complete within. For example, it is required to complete RRC establishment within 10ms, RRC recovery within 6ms or 10ms, RRC reconfiguration within 10ms, and Access Layer (AS) security activation within 5ms. However, in actual deployments, RRC processing time (for both the UE and the network) can become longer, especially with higher RRC configuration requirements (higher bandwidth, larger number of frequencies). However, it has been observed that the longer RRC processing latency makes 5G RRC insufficiently fast. Therefore, a redesign is needed to achieve a robust and energy-efficient control plane for future 6G networks, while maintaining competitive key performance indicators.

[0018] The overall problem of suboptimal or insufficiently fast RRC stems from the conservative design of 5G control signaling and the limited capabilities offered by the 5G RRC process. Even for the establishment of the same type of connection (e.g., transition from RRC idle state), the UE needs to exchange and repeat the same set of messages with the network, decoding and applying the same configuration content. The most frequently repeated message is the RRC reconfiguration message, which contains the radio bearer configuration, low-layer configuration (physical layer, MAC, RLC, PDCP configuration parameters), and any RRC-specific configuration for a given characteristic (a list of related parameters). Similarly, the network providing the UE with a specific RRC configuration needs to repeat the same list of parameters in the same sequence of transmission messages in all subsequent connection establishments (see [link to relevant documentation]). Figure 2 For example, the activation of a feature's configuration (see, for example, [link to relevant documentation]). Figure 2The activation of Feature 1 in UE Reconfiguration 2 always needs to be performed after: a) Basic connection establishment (RRC establishment), b) Security activation, c) UE Reconfiguration 2 for initial RRC reconfiguration (e.g., SRB2 establishment), and d) UE capability transmission. Therefore, the existing 5G RRC process sequence is repeated every time any UE transitions to RRC connected state, which is neither optimal nor efficient.

[0019] Another issue with the use of RRC configurations (also known as RRC profiles) is how to retain and utilize configured profiles in mobility scenarios. Profiles can be retained and used when served by the same gNB because the UE context, including the profile configuration (also simply referred to as the profile or configuration), is stored on both the same gNB and the UE itself. Problems arise when the UE switches to another gNB and the profile does not match the target cell configuration. Specific issues to address may include: what enhancements are needed to the handover (HO) process to allow continued use of existing profiles; what extensions are needed to HO signaling (e.g., inter-gNB (Xn type) signaling, RRC signaling between the RAN node (source gNB and target gNB) and the UE) to support profile usage; and what behaviors the UE and RAN node should exhibit to support profile usage in mobility scenarios.

[0020] To at least partially address these issues, a solution for managing RRC profiles during UE mobility is proposed, applicable to UEs in both RRC connected and RRC idle or inactive states.

[0021] In various examples, a profile may be referred to as an RRC profile or module. A profile may include a profile identifier, such as an index (0, 1, 2…) or label, and a set of parameters for (multiple) RRC configurations, which may characterize the associated connection type. In some examples, a profile may provide one or more RRC configurations and may be stored as an RRC object. In this respect, a profile may represent an object with a set of RRC configuration parameters, which may be grouped on the network side. A profile may be learned from one or more RRC configurations and generated by a network node based on at least one connection (e.g., an RRC connection). In some examples, a profile may also be generated based on UE capabilities (UE capability information). A profile may include a set of RRC parameters for (multiple) RRC configurations, optionally with some additional instructions, such as profile-specific UE capabilities. In this regard, in some examples, a UE may be able to use only some features with a specific profile. Once generated, the profile may be stored by the network node and the UE and referenced in subsequent processes (via the profile identifier) ​​to activate UE connections without renegotiating and repeating the complete configuration transfer or retransmitting the previously used set of parameters. In some of these examples, profile identifiers (e.g., indexes, tags) may indicate use cases, features, or connectivity purposes, such as power saving / energy saving / efficient operation, high throughput / performance / eMBB operation.

[0022] Figure 3 An example method is described. This method can be implemented by a computer. It can be performed by a network node (such as the target node for handover, e.g., the gNB of the target cell) or by the network node to which the UE is attempting to perform a connection restoration procedure. Assumptions Figure 1 gNB 110 execution Figure 3 The method can be assumed that UE 120 is switching from cell 102 (source cell) to cell 100 (target cell), or is restoring its connection to cell 100.

[0023] like Figure 3As shown, in step 300, gNB 110 obtains information about multiple second-cell RRC profiles associated with UE 120 in the second cell. In this example, the second cell is cell 102 controlled by gNB 112. Each RRC profile includes a set of parameters for at least one RRC configuration for the UE. Each RRC profile may include UE-specific and cell-specific portions. That is, the UE may have communicated with gNB 112 or is at least in an RRC connected state, and may have negotiated or established multiple RRC profiles for communicating with the second cell. Therefore, the second-cell RRC profiles are associated with the UE in the second cell. In this embodiment, the multiple second-cell RRC profiles are based on at least one of the service or power-saving modes associated with the UE in the second cell.

[0024] In an embodiment, acquisition may include obtaining multiple second-cell RRC profiles from a network node of the second cell (e.g., from gNB 112) or from UE 120. This can occur, for example, in a HO request message as additional UE content to the legacy UE context. Acquiring, obtaining, or receiving an RRC profile may indicate acquiring a corresponding set of parameters for the RRC profile, which form the corresponding RRC configuration of the RRC profile. Additionally, it may also include acquiring the corresponding profile identifier (ID).

[0025] In one embodiment, obtaining multiple second-cell RRC profiles involves retrieving them from a database accessible to gNB 110. In one embodiment of retrieving profiles from the database, gNB 110 receives the identifier of UE 120 from gNB 112 (e.g., received in association with a handover request) or receives the identifier of UE 120 from the UE (received in association with an RRC recovery request from an RRC idle-state UE). gNB 110 can then retrieve multiple second-cell RRC profiles from the database based on the UE's identifier. Therefore, the database can store RRC profiles for several UEs, and gNB 110 sending a profile retrieval request identifying a particular UE to the database allows the database to return the correct UE's RRC profile to gNB 110. In other words, gNB 110 can retrieve multiple second-cell RRC profiles from the (RAN) database (DB) using the UE ID.

[0026] In one embodiment, each RRC profile is assigned a profile identifier (ID). In one embodiment, obtaining information includes obtaining identifiers for multiple second cell RRC profiles. As described above, second cell RRC profiles can be obtained from gNB 112 (e.g., the source gNB during handover). In this case, at least one identifier is received from gNB 112 in a HO request message. In another embodiment, at least one of the identifiers is received from the UE in a recovery request. In yet another embodiment, obtaining information includes obtaining multiple second cell RRC profiles corresponding to the identifiers from a database.

[0027] In step 302, gNB 110 generates multiple first-cell RRC profiles for use in the first cell, based on multiple second-cell RRC profiles. In this example, the first cell is cell 100, which is controlled by network node 110.

[0028] It should be noted that acquiring multiple second-cell RRC profiles or generating a first-cell RRC profile does not need to occur simultaneously, but can happen over a period of time. For example, in one embodiment, only one second-cell RRC profile is received, and then a first-cell RRC profile is generated. The gNB 110 can then communicate with the UE based on this first-cell RRC profile, subsequently acquire at least one additional second-cell RRC profile, and further generate it into (multiple) first-cell RRC profiles available in the first cell.

[0029] In one embodiment, gNB 110 can determine at least one first cell-specific configuration / parameter associated with at least one layer below the RRC layer in the first cell, and further generate multiple first cell RRC profiles for use in the first cell based on the at least one first cell-specific configuration / parameter. This is because various radio configurations (e.g., common control and broadcast channel configurations and parameters) differ in a cell, so existing profiles used in the second cell (which may also be generated taking into account some lower-layer configurations / parameters of the second cell) may not be directly usable in the first cell. Therefore, it is advantageous to modify the profiles used in the second cell by taking into account the lower-layer configurations (such as RLC, MAC, PHY) in the first cell so that those profiles can be applied in the first cell. The lower-layer configurations and / or parameters depending on the configuration of the gNB in ​​the first cell or the load on the radio channels include, for example, CORESET (Control Resource Set), CSI (Channel State Information) configuration, BWP (Bandwidth Part) (multiple) configurations, PDCCH configuration, PUCCH configuration, etc. Such parameters of the source cell cannot be directly reused in the target cell, but are advantageously reconfigured to match the target node.

[0030] In an embodiment, where the functionality of the gNB 110 is shared between the CU and DU, the CU portion may request the associated DU to provide the CU with (multiple) low-level configurations, such as cell group configurations related to the mobile UE (unless the CU is already aware of the configuration). This can be part of defining the CU-DU signaling required to include access information in the HO command (in the case of HO).

[0031] Note that the modification / generation / conversion from the second-cell RRC profile to the first-cell RRC profile is performed on a profile-by-profile basis, thus preserving the corresponding profile ID. For example, each of the multiple second-cell RRC profiles is identified using an identifier, creating a one-to-one mapping between the multiple second-cell RRC profiles and the multiple first-cell RRC profiles. The identifiers of the multiple second-cell RRC profiles are preserved in the multiple first-cell RRC profiles, such that a given first-cell RRC profile is assigned the same identifier as the second-cell RRC profile, which is used as the basis for generating a given first-cell RRC profile. This can advantageously simplify UE operations in the first cell (e.g., in the case of handover from the second cell to the first cell).

[0032] In embodiments, the converted first-cell RRC profile can advantageously provide the same (or as close as possible) capabilities for UE power savings and required user plane data rates as the second-cell RRC profile negotiated in the second cell (e.g., as...). Figure 4 (As shown).

[0033] After generating multiple first cell RRC profiles, gNB 110 can notify the UE of at least one of the generated first cell RRC profiles.

[0034] Then, gNB 110 can communicate with UE 120 in the first cell based on at least one of the generated first cell RRC profiles.

[0035] Before discussing more details of RRC profile management in UE mobile scenarios, let's first combine... Figure 4 This section examines how the preceding serving node can establish an RRC configuration (i.e., the second cell RRC configuration). That is, as a starting point, a specific UE's RRC profile has been negotiated between the RAN and the UE. These RRC profiles can be configured based on UE capabilities (obtained using relevant signaling) and RAN nodes (e.g., gNBs). These RRC profiles can be stored in both the UE and the RAN. In the RAN, storage can be in the gNB-CU (assuming RRC operates in the CU), or it can exist in a database (DB) that provides storage for the UE context and RRC profiles accessible by multiple RAN nodes (e.g., both the source and target gNBs during handover). In one embodiment, the number of profiles and their associated configurations can be UE-specific.

[0036] like Figure 4 The example signaling procedure for configuration file negotiation shown illustrates that configuration files can be negotiated during connection to any cell. This is assumed to be a prerequisite for mobility scenarios. (Reference) Figure 4 The negotiation process can be carried out in the following steps.

[0037] In step 400, UE 120 is in an RRC connected state with gNB 112, which acts as a serving node. In this example, the serving node is shown as including CU and DU. In step 402, UE capabilities are signaled to the serving node.

[0038] In step 404, the UE may optionally request a configuration profile, for example, based on service requirements (current or future services) or power-saving preferences. This request may include suggested RRC configuration profiles that the UE may require.

[0039] In step 406, the gNB-CU initiates the determination of a configuration profile. This may include, for example, the gNB-CU requesting low-level and cell status and configuration from the gNB-DU. At this stage, the requested configuration profile may be configured, or multiple configuration profiles may be configured. Each configuration profile will be assigned a Profile-ID. In step 408, the gNB-DU provides the requested configuration and a set of low-level and / or cell-specific parameters associated with the requested configuration profile(s). For example, the DU provides the configuration and parameter set for each configuration profile. The configuration profile is referenced by the assigned Profile-ID.

[0040] In step 410, the gNB-CU generates a message for configuring (multiple) profiles using information provided by the gNB-DU. This profile configuration may be generated based on the requested service / power saving mode. Specifically, the CU sends an RL RRC MESSAGE TRANSFER F1AP message carrying the RRC configuration, which includes (multiple) profile configurations and their corresponding IDs. In step 412, an RRC reconfiguration message is sent to the UE, which includes (multiple) profile configurations and (multiple) Profile-IDs. If multiple profiles are configured, this message may indicate the profile (Profile-ID) to be activated. In step 414, the UE responds with an RRC reconfiguration complete message to complete the process. This message may optionally include the Profile-ID to confirm the activated profile. Alternatively or additionally, this message may include all profiles supported and accepted by the UE. In step 416, the DU forwards the RRC message to the gNB-CU.

[0041] In step 418, optionally, if the database (DB) is used to store UE profiles (and other UE contexts), the gNB-CU sends the UE-specific profile configuration and (multiple) Profile-IDs to the DB. And in step 420, the DB can confirm successful reception of UE data via an acknowledgment message.

[0042] Next, refer to Figure 5Let's examine how RRC profile management is performed during handover when the UE is in RRC connected state. The starting point is that the UE (e.g., UE 120) is in RRC connected state (as shown by reference numeral 500), and the current serving RAN node (e.g., gNB 112) configures RRM measurements and measurement reporting, as well as appropriate reporting events (e.g., A3) for initiating measurement reporting. In this example, the UE context and RRC profile configuration are stored in a database (DB) accessible to the RAN node, in this case, both the source and target gNBs. In an alternative implementation (not shown in the figure), the UE context and profile can be stored in the serving node (first in gNB 112, then in gNB 110).

[0043] Although gNBs 110 and 112 are shown as a single entity, both can utilize a split architecture, where each (or only one) can include a centralized unit (CU) and a distributed unit (DU). In another implementation, the CU includes a user plane portion (CU-UP) and a control plane portion (CU-CP), although for simplicity... Figure 5 Not shown in the image.

[0044] In step 502, the configured criteria (e.g., A3 event) are met, thereby initiating a measurement report, and the UE sends a measurement report to the serving node gNB 112. In step 504, based on the measurement report, gNB 112 (e.g., CU-CP) decides to initiate a HO procedure.

[0045] Therefore, in step 506, gNB 112 sends a HO request to the target gNB 110 (e.g., to the CU-CP of gNB 110). This request includes at least the Profile-ID used in the source cell 102 (i.e., the ID of the source cell's RRC profile). In embodiments, the Profile-ID may also be another ID selected by the source cell, for example, based on measurements from the UE, and is not necessarily the ID currently used by the UE with the source node 112. The HO request may also include the ID of the UE 120 to be switched. Optionally, the source gNB 112 indicates the RRC configuration (i.e., RRC parameters) associated with the Profile-ID, which was used in the source cell prior to the HO.

[0046] In step 508, gNB 110 requests from the database the configuration of (multiple) profiles for the specific UE indicated by the UE-ID. This message may request all RRC profiles associated with the UE in the source cell (i.e., all second-cell RRC profiles) or only a subset. If the request only requests one RRC profile from the database, the request may include the RRC profile ID, which is included in the HO request.

[0047] If the RRC profile is stored in the access node (e.g., without a database), the gNB 112 may include the RRC parameters of the relevant source cell RRC profile in the handover request, or the gNB 112 may request the information separately from the gNB 110 after receiving the HO request.

[0048] In step 510, the DB provides configuration of multiple profiles associated with multiple Profile-IDs, and may also provide the remainder of the UE context, if stored.

[0049] In step 512, the target gNB (e.g., the CU-CP of gNB 110) derives (multiple) source cell RRC profiles to make them suitable for the target cell.

[0050] Optionally, the CU-CP sends a request to the DU of the gNB 110 to obtain any lower-layer (below RRC layer) and / or cell-specific configurations associated with the RRC profile(s)(s) included in the request sent to the DU. In an embodiment, an F1AP UE CONTEXT SETUP REQUEST message may be used for this request. If a request is sent to the DU, the DU may respond with a response message including the lower-layer / cell-specific configurations and parameters for the requested profile. The DU determines the lower-layer configuration of the requested profile as needed to match the target DU / cell configuration.

[0051] Using low-layer and / or cell-specific configurations, the source cell RRC profile(s) indicated in the HO request, and possibly some CU-specific information, gNB 110 (e.g., the CU of gNB 110) generates (multiple) first cell (=target cell) RRC profile(s) for the target cell in step 512. In this way, the target gNB 110 generates new target cell RRC profile(s), each corresponding to the source cell RRC profile(s) of the source gNB 112.

[0052] In one embodiment, multiple IDs of multiple RRC profiles are reserved for the generated / converted multiple first cell RRC profiles, such that the multiple IDs of the multiple first cell RRC profiles correspond to the multiple second cell (=source cell) RRC profiles used / stored during the connection in the source cell.

[0053] gNB 110 generates a HO command message for the UE and sends it to source gNB 112 in step 514. The HO command can be encapsulated in an RRC reconfiguration message. The HO command, transmitted to source gNB 112, includes the required access parameters (for the UE to access the target cell) and configuration parameters (and possibly the corresponding profile ID) of the derived / modified RRC profile to be activated in the target cell. In other words, the target gNB (e.g., CU) generates a HO command including a modified RRC profile, which can be modified based on the RRC profile used in the source cell (and obtained in the HO request). The associated profile ID of the target cell RRC profile is the same as in the HO request and is known to the UE. Alternatively, the profile ID can be included in the HO command to confirm that even if the source RRC configuration is modified, the profile ID associated with the RRC configuration of the HO command will still be the ID to be used in the target cell. This ensures that the same Profile-ID can be used for the same power-saving mode or service requirements, even if the RRC profile configuration is transformed.

[0054] For example, a HO request ACK is sent from the target gNB 110 to the source gNB 112, and this HO request ACK includes the generated HO command. The converted RRC profile configuration included in the HO command can also be an incremental configuration relative to the source cell's RRC profile configuration, rather than a full configuration, to reduce signaling. In step 516, the source gNB 112 sends an RRC reconfiguration message to the UE 120, which includes the HO command. In the case of a split architecture, the CU of gNB 112 first sends the HO command to the DU of gNB 112 in a DL RRC MESSAGETRANSFER message, and then the source DU transmits the HO command as an RRC reconfiguration message to the UE to trigger HO execution at the UE.

[0055] In one embodiment, while initiating UP data forwarding, a sequence number (SN) status transmission message is sent from the source gNB112 to the target gNB110.

[0056] In step 518, according to an embodiment, even if an HO command has been received and the UE is moving to another cell, the UE maintains / retains all configured source cell RRC profiles and multiple Profile-IDs. This can be beneficial for using incremental configuration, as explained later.

[0057] In step 520, a random access procedure is performed between the UE and the target gNB 110. For example, the UE initiates the access procedure by sending a RACH preamble (msg1) to the target cell. The target cell responds with a Random Access Response (RAR) message, which includes resource grants for subsequent UE uplink transmissions. The UE then sends an RRC reconfiguration complete (HO complete) message to gNB 110, which includes the Profile-ID to be activated. Note that the gNB-DU receiving the HO complete message may or may not be able to parse the RRC message to enable the profile configuration to be activated. The gNB-DU forwards the HO complete message to the CU of gNB 110. After decoding the RRC message, the CU can notify the DU of successful reception of the HO complete message. That is, the UE moves to the target cell, and after access, the UE begins using the indicated profile. The UE 120 can then communicate with the target gNB (current serving node) 110 using the indicated target cell RRC profile.

[0058] In step 522, the target gNB 110 sends a UE context release to the source gNB 112. Then, if the UE context information is stored at gNB 112, the source gNB (e.g., both CU and DU) releases the UE context information. Note that in some embodiments, the UE context and configuration file may be stored at the DB.

[0059] At this point, the HO procedure has been completed, and the UE connection has been moved to target cell 100 of gNB 110.

[0060] In one embodiment, for the user plane (UP), the target gNB can initiate a path handover procedure to the core network (CN). Furthermore, assuming a gNB function separation architecture, the UP portion of the gNB 110's CU can be configured for UE data path transmission, for example, by sending a bearer context establishment request to the CU-UP. In this case, the CU-UP can reply with a bearer context establishment response to confirm successful UP path configuration.

[0061] In step 524, gNB 110 can send the converted RRC profile and profile ID to the DB for storage. In this example, only the active profile is stored in the DB after the HO is completed. Additionally, the remaining portion of the UE context updated for the target cell is included in the information in the DB. The DB can confirm the storage of the new UE data (optional).

[0062] In step 526, at some point in time (the exact time may be determined by the implementation), the target gNB 110 may initiate the conversion of source cell RRC profiles that were not converted during the HO process (if any source cell RRC profiles were not converted). This may include retrieving other source cell RRC profiles from the DB (if this has not been completed in steps 508-510). Optionally, this step may also include sending these source cell RRC profiles and their IDs to the DU to adapt to the target cell configuration, and the DU responding with the adapted RRC profile configuration and profile ID, each adapted profile configuration and profile ID corresponding to a source cell RRC profile and an assigned source cell profile ID. For example, some parameters of the target cell are under the control of the DU, and these parameters may be provided by the DU. The CU can then form the entire RRC profile, since it can be assumed that the RRC resides in the CU.

[0063] gNB 110 can generate an RRC reconfiguration message to configure the remaining target cell RRC profiles for the UE, and send this RRC reconfiguration message to UE 120 in step 528. This message may include, for example, another target cell RRC profile and its profile ID. In an embodiment, incremental configuration relative to the source cell RRC profile (already retained at the UE) can be used instead of full RRC configuration. In step 530, the UE can acknowledge the received target cell RRC profile. At this step, the UE can release the source cell RRC profile. If needed, the CU of gNB 110 can indicate successful reception of the RRC reconfiguration completion message to the DU of gNB 110 (in the case of a split architecture). Following this negotiation, depending on the desired power savings or required service (e.g., UP data rate), the converted RRC profile can be used to quickly change the UE's operating mode in the target cell.

[0064] In step 532, gNB 110 can transfer the new target cell RRC profile configuration to the DB for storage. The DB can acknowledge receipt.

[0065] Next, let's look at a scenario where the UE is in an RRC inactive state and is moving or at least connected to a new cell that is different from the previous serving cell. Figure 6The signaling flowchart in the diagram illustrates this scenario, applicable to situations where the UE is in inactive mode and regains connection (reconnects). In other words, the UE has moved while inactive mode and is reselecting a new cell to connect to. Here, it is assumed that gNB 112 is the last serving node, and gNB 110 is the new node the UE is attempting to connect to.

[0066] exist Figure 6 In, with Figure 5 The same principle can be used for recovery during the HO process of the UE in an RRC connection. Figure 6 The example, as will be explained below, also shows the option to store the configuration file at the gNB (and the UE context). The principle is the same as when the UE context is stored in the DB, but the location of the storage and associated signaling differs.

[0067] In step 600, the UE decides to initiate connection establishment / recovery via another cell using the context of the stored (multiple) profiles to obtain the desired service. That is, in the described process, the UE initiates a connection in another cell (different from the cell where the UE previously connected via RRC) (after a pause). The UE may have retained the RRC profiles used / applied in the previously serving cell 102.

[0068] In this example, conventional (NR type) signaling is applied, where additional information is included in certain messages. For example, steps 602 and 604 may include the transmission and reception of random access (RA) messages Msg1 and Msg2, as in a conventional random access procedure.

[0069] In step 606, the UE transmits Msg3 of the RA procedure to the target gNB 110. Msg3 may include an indication of a requested profile with ID x, which may be any profile configured and stored in the UE and RAN during a previous RRC connected state in the previous serving cell. The requested profile may be based on the service the UE expects to use in the target cell (e.g., different RRC profiles may exist for different services). During the RA procedure, the network can also learn the identity of the UE. Msg3 may carry a recovery request message.

[0070] In one option, as indicated by reference numeral 607, the database stores the UE context, thereby storing the UE's RRC profile. In this case, in step 608, the gNB 110 may send a UE context request to the DB, which at least indicates the UE ID and may indicate the requested profile(s) ID(e.g., IDx). In step 610, the DB will return the requested RRC profile(s) to the gNB 110, and may also return the IDs of the RRC profile(s), at least if the RRC profile returned by the DB is not limited to the one corresponding to IDx.

[0071] In another option, as indicated by reference numeral 611 in the attached figure, the final service gNB 112 stores the UE context, thereby storing the UE's RRC profile. In this case, in step 612, gNB 110 may send a UE context request to gNB 112, which at least indicates the UE ID and may indicate the requested profile(s) ID (e.g., IDx). In step 614, gNB 112 returns the requested RRC profile(s)(s) to gNB 110, and may also return the IDs of the RRC profile(s), at least if the RRC profile returned by gNB 112 is not limited to the one corresponding to IDx.

[0072] At this point, due to options 607 or 611, gNB 110 knows the RRC profiles of (multiple) second cells (=last serving cell). Subsequently, in step 616, gNB 110 can modify these (multiple) second cell RRC profiles to the RRC profiles of (multiple) first cells (= target cell), similar to combining... Figure 5 As explained in steps 512 and / or 526. That is, in step 616, gNB 110 derives one or more first cell RRC profiles based on the corresponding one or more second cell RRC profiles, while retaining the RRC profile ID. This generation can also be based at least in part on the low-level configuration of the first cell 100 (controlled by gNB 110).

[0073] and Figure 5 Similar to China, also Figure 6 In the middle (although not shown), a path handover procedure can be initiated to the core network (CN). Furthermore, assuming a gNB function separation architecture, the UP portion of the gNB 110's CU can be configured for UE data path transmission by, for example, sending a bearer context establishment request to the CU-UP. In this case, the CU-UP can reply with a bearer context establishment response to confirm successful UP path configuration.

[0074] Then, in step 618, gNB 110 can generate a recovery message and transmit it to the UE. In an embodiment, this message includes all first cell RRC profiles (i.e., modified RRC profiles), the corresponding ID of the first cell RRC profile, and optionally, the IDx of the RRC profile that the UE will use with the target gNB 110, indicating to the UE. Figure 5 In the same manner, the (multiple) configurations can be (multiple) incremental configurations relative to the previous (multiple) serving cell RRC profiles (= (multiple) second cell RRC profiles). In one embodiment, the recovery message only indicates the RRC configuration corresponding to IDx to the UE, and the other first cell RRC configurations are notified to the UE later. The recovery message may be referred to as Msg4 of the RA procedure.

[0075] Subsequently, the UE can reactivate integrity protection and encryption using the new key based on the received RRC profile corresponding to profile IDx.

[0076] In step 620, the UE can respond to gNB 110 using an RRC establishment / recovery completion message (Msg5). The UE uses this RRC establishment / recovery completion message to confirm that it will use an RRC profile with IDx.

[0077] In step 622, if the DB is used to store the UE context, the gNB may store (multiple) target cell RRC profiles and their (multiple) IDs in the DB. The message may also include the UE's ID. The database may acknowledge receipt to the gNB 110 using an ACK message.

[0078] Such as combination Figure 3 As shown, gNB 110 can Figure 5 and Figure 6 The system performs at least the following functions: acquiring information about multiple second-cell RRC profiles associated with UE 120 in second cell 102; generating multiple first-cell RRC profiles for use in first cell based on the multiple second-cell RRC profiles; providing the UE with information about at least one first-cell RRC profile from the multiple first-cell RRC profiles; and communicating with the UE in the first cell based on at least one of the generated multiple first-cell RRC profiles. Acquiring information can occur at one point in time or at different points in time. Similarly, generating new RRC profiles for use in the first cell can occur at one point in time or at different points in time, such as... Figure 5 Steps 512 and 526 are shown.

[0079] In the embodiment, reference Figure 7 (Also as) Figure 5 and Figure 6 As shown in some steps), in step 700, gNB 110 can obtain information about the specific second cell RRC profile (e.g., Figure 5 HO request or Figure 6 (The indication of IDx in the recovery request). This specific RRC profile can be one of multiple second-cell RRC profiles. In an embodiment, the specific second-cell RRC profile is the latest RRC profile associated with the UE in the second cell.

[0080] Then, in step 702, gNB 110 can generate a specific first-cell RRC profile based on a specific second-cell RRC profile (and possibly based on the associated first-cell lower-level configuration, as described above). Alternatively, gNB 110 can select a specific first-cell RRC profile from among a plurality of generated first-cell RRC profiles, where the selection is based on a specific second-cell RRC profile. For example, gNB 110 can select a first-cell RRC profile associated with a certain ID, which corresponds to an ID associated with a specific second-cell RRC profile.

[0081] Then, in step 704, gNB 110 can provide the UE with information about the specific first cell RRC profile (e.g., in...). Figure 5 HO command or Figure 6 (In the RRC setup / recovery message). This information can be the ID of the RRC profile or the full / incremental RRC configuration. Then, the gNB 110 can communicate with the UE in the first cell based on the specific first cell RRC profile.

[0082] In one embodiment, an additional RRC profile associated with the UE in the second cell can be later used as the basis for generating the RRC profile for the first cell, and then instructed to the UE (e.g., not during handover or during RRC establishment / recovery). This can be more efficient because the UE can establish an RRC connection state with the gNB 110 with less signaling.

[0083] From the perspective of source gNB 112, Figure 8 An example method is described. This method can be implemented by a computer. This method can be executed by a network node (such as gNB 112) of the source cell during handover. Figure 8As shown, the source gNB 112 can perform at least the following functions. In step 800, the gNB 112 can include an identifier of a specific second-cell RRC profile in the handover request (to the target gNB 110). The gNB 112 can select the specific second-cell RRC profile to be included in the handover request, the selection being made from a plurality of second-cell RRC profiles and based on at least one of the following: measurement results received from the UE, profile ID in the measurement report, the service used by the UE in the source cell, and the latest second-cell RRC profile used by the UE in the second cell. For example, the measurement report that triggers the HO procedure can indicate an RRC profile ID that appears suitable for the target cell from the UE's perspective, and will, for example, provide the closest match to the service (or generally the operating mode) that the UE wishes to use in the first cell once handed over.

[0084] In step 802, gNB 112 may transmit a handover request to gNB 110. In step 804, gNB 112 may receive an identifier of a specific first cell RRC profile from the target gNB 110 in the handover command. In this embodiment, the first cell RRC profile may be determined by gNB 110 based on a specific second cell RRC profile. Then, in step 806, source gNB 112 may transmit / forward an HO command to UE 120, enabling the UE to access the target cell of the target gNB 110 based on the HO command.

[0085] Furthermore, from the perspective of source gNB 112, Figure 9 An example method is described. This method can be implemented by a computer. This method can be executed by a network node (such as gNB 112) of the source cell during handover. Figure 9 As shown, gNB 112 optionally stores (as shown in step 900) the source cell RRC profile (instead of DB or in addition to DB). In step 902, the source gNB 112 provides information on multiple second cell RRC profiles associated with the user equipment (UE) in the second cell to the (target / first cell) gNB 110. This provision may occur iteratively at multiple points in time or at a single point in time.

[0086] In an embodiment, this information may be, for example, a plurality of second cell RRC profiles and a profile-specific identifier for each of the plurality of second cell RRC profiles.

[0087] In one embodiment, the provision of step 902 may occur after receiving a request to provide information from the network node of the first cell (e.g., from gNB110). In one embodiment, the request includes the UE's identifier, and the acquisition includes obtaining the information based on the UE's identifier.

[0088] In one embodiment, gNB 112 retrieves information from a database accessible to gNB 112 before providing information to gNB 110.

[0089] Figure 10 An example method is described. This method can be implemented by a computer. This method can be performed by a user equipment such as UE 120. In step 1000, the UE stores multiple second-cell RRC profiles associated with the UE in the second cell. In step 1002, the UE retains the multiple stored profiles during mobility from the second cell to the first cell. In step 1004, the UE retrieves multiple first-cell RRC profiles associated with the UE in the first cell, the multiple first-cell RRC profiles being generated at least in part based on the multiple second-cell RRC profiles. The UE can retrieve the first-cell RRC profiles once or over a period of time (e.g., in…). Figure 5 In this embodiment, the UE acquires information about the RRC profile associated with the UE in the first cell in two steps (516 and 528). In one embodiment, acquisition is accomplished by receiving an HO command, which includes information about multiple first-cell RRC profiles. In another embodiment, acquisition is accomplished by receiving an RRC establishment / recovery message (also known as a connection recovery message, sent as a response to a connection recovery request message) from a network node in the first cell, which includes information about multiple first-cell RRC profiles. The UE can then communicate in the first cell based on at least one of the multiple first-cell RRC profiles.

[0090] Figure 11 Another example method is described. This method can be implemented by a computer. This method can be performed by a user equipment such as UE120. In step 1100, the UE provides the network node of the first cell with an indication of a specific second cell RRC profile. This indication can be included, for example, in an RRC establishment / recovery request (see...). Figure 6 In step 1102, the UE receives an indication of a specific first-cell RRC profile from the network node of the first cell. A specific first-cell RRC profile can be generated based on the specific second-cell RRC profile indicated in step 1100. This indication in step 1102 can be received, for example, in an RRC setup / restore message (see...). Figure 6In step 1104, the UE may apply a specific first cell RRC profile to communications within the first cell. Applying a given RRC profile to communications may include, for example, applying a corresponding set of parameters from the given RRC profile to at least one radio resource control configuration of the user equipment for current or subsequent connections / communications.

[0091] Figure 12 Another example method is described. This method can be implemented by a computer. This method can be performed by a user equipment such as UE 120. In step 1200, the UE to be switched to or connected to the first cell obtains information about multiple first-cell RRC profiles associated with the UE in the first cell. In an embodiment, this acquisition may occur in an HO command (e.g., the information is included in a handover command), and the user equipment receives the handover command via gNB 112 during a handover from a second cell to the first cell. In another embodiment, the acquisition occurs in an RRC establishment / recovery message (e.g., the information is included in a connection recovery message), and the user equipment receives a connection recovery message from gNB 110 during an attempt to recover the connection with gNB 110. For example, this information may include, for example, an RRC profile and an associated Profile-ID. In an embodiment, the UE sends information about a specific second-cell RRC profile to gNB 110 before acquiring the information (e.g., in a recovery request message). Then, in step 1202, the UE selects one of the multiple first-cell RRC profiles for communication in the first cell. In this embodiment, the selection is based on the UE's service requirements and / or power saving requirements in the first cell. In this embodiment, the UE indicates the selected profile (e.g., with Profile-ID) in the HO completion message.

[0092] The following lists some aspects of the above embodiments. According to one aspect, there exists an HO command indicating the RRC profile to be used when accessing a target cell, wherein the RRC profile is defined in a source (or previous)(multiple) cells, the profile to be used in the target cell is indicated in an HO request from the source gNB to the target gNB, and the target gNB adapts the requested profile using cell-specific parameters as needed to match the target cell configuration. In one aspect, the profile is indicated using a Profile-ID. In one aspect, the profile(s) configuration are included in the HO request, or are accessible by the target gNB using the UE ID and Profile-ID. In one aspect, other profile configurations are provided to the target gNB by the source gNB using a specific signaling procedure, or the target cell obtains the configuration from a public RAN database. In one aspect, each RRC profile includes a UE-specific portion and a cell-specific portion. In one aspect, the DU portion of the target gNB provides the low-layer or cell-specific parameters required to translate the RRC profile to match the target cell configuration. In one aspect, multiple or all configured profile configurations / profile IDs are included in the HO request, and the UE may consider the radio conditions on the target link and select the profile to be used in the target cell that best matches the desired service requirements and / or power saving level. In another aspect, the UE indicates the selected profile (Profile-ID) in the HO completion message.

[0093] like Figure 13 As shown, an embodiment provides an apparatus 10 including: a control circuitry system (CTRL) 12, such as at least one processor; and at least one memory 14 storing instructions that, when executed by the at least one processor, cause the apparatus to perform at least any of the processes described above. In the example, the at least one memory and computer program code (software) are configured, together with the at least one processor, to cause the apparatus to perform any of the processes described above. According to any embodiment, the control circuitry system 12 may include associated circuitry for performing functions.

[0094] Memory can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Memory may include databases for storing data.

[0095] In one embodiment, device 10 is or is included in a network node, such as gNB 110. The device can perform some functions of the above-described process, such as... Figure 3 and Figure 7 The steps of any one of them.

[0096] In another embodiment, device 10 is or is included in a network node, such as gNB 112. For example, the device can perform some of the functions described above, such as Figure 8 or Figure 9 The steps of any one of them.

[0097] In another embodiment, device 10 is or is included in a user equipment such as UE 120. For example, the device may be able to perform some of the functions described above, such as Figure 10 , Figure 11 or Figure 12 The steps of any one of them.

[0098] The device may also include a radio interface (TRX) 16, which includes hardware and / or software for establishing a communication connection according to one or more communication protocols. For example, the TRX can provide the device with the ability to communicate with user equipment and / or base stations.

[0099] The device may also include a user interface 18, which may include, for example, at least one keypad, microphone, touch display, display, speaker, etc. Users can use this user interface to control the device.

[0100] According to any embodiment, the control circuit system 12 may include associated circuitry for performing functions.

[0101] As used herein, the term "circuit" refers to all of the following: (a) hardware circuit implementations only, such as implementations in analog and / or digital circuits only; and (b) combinations of circuits and software (and / or firmware), such as (if applicable): (i) combinations of (multiple) processors or (ii) portions of (multiple) processors / software, including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device to perform various functions; and (c) circuits, such as (multiple) microprocessors or portions of (multiple) microprocessors, which require software or firmware to operate, even if the software or firmware is not physically present. This definition of circuit applies to all uses of the term in this application. As another example, as used herein, the term "circuit" will also cover implementations of processors (or multiple processors) or portions of processors and their accompanying software and / or firmware. For example, and if applicable to a particular element, the term "circuit" will also cover baseband integrated circuits or application processor integrated circuits for mobile phones or similar integrated circuits in servers, cellular network devices, or other network devices.

[0102] In one embodiment, at least some of the processes described may be performed by means including corresponding components for performing at least some of the processes described. Some example components for performing the processes may include at least one of the following: a detector, a processor (including dual-core and multi-core processors), a digital signal processor, a controller, a receiver, a transmitter, an encoder, a decoder, a memory, RAM, ROM, software, firmware, a display, a user interface, display circuitry, user interface circuitry, user interface software, display software, circuitry, an antenna, antenna circuitry, and circuitry.

[0103] As used herein, the term nontransient refers to a limitation on the medium itself (i.e., tangible, not signaling), rather than a limitation on the persistence of data storage (e.g., RAM vs. ROM).

[0104] As used herein, the term "component" should be interpreted in the singular form, referring to a single element, or in the plural form, referring to a combination of single elements. Therefore, the term "component for [performing A, B, C]" should be interpreted to encompass an arrangement in which only one component exists for performing A, B, and C, or in which separate components exist for performing A, B, and C, or in which partially or completely overlapping components exist for performing A, B, and C. Furthermore, the terms "component for performing A," "component for performing B," and "component for performing C" should be interpreted to encompass an arrangement in which only one component exists for performing A, B, and C, or in which separate components exist for performing A, B, and C, or in which partially or completely overlapping components exist for performing A, B, and C.

[0105] The techniques and methods described herein can be implemented by various means. For example, these techniques can be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or combinations thereof. For hardware implementation, the embodiments may be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or combinations thereof. For firmware or software, the implementation may be executed by a module (e.g., a process, function, etc.) of at least one chipset that performs the functions described herein. Software code may be stored in memory cells and executed by a processor. Memory cells may be implemented within or outside the processor. In the latter case, as is known in the art, it may be communicatively coupled to the processor via various means. Furthermore, as those skilled in the art will understand, the components of the systems described herein may be rearranged and / or supplemented by additional components to facilitate the implementation of the various aspects described herein, and they are not limited to the precise configurations illustrated in the given figures.

[0106] The described embodiments can also be performed as a computer process defined by a computer program or parts thereof. Embodiments of the described methods can be performed by executing at least one portion of a computer program including corresponding instructions. The computer program can be in source code form, object code form, or some intermediate form, and it can be stored in some kind of carrier, which can be any entity or device capable of carrying the program. For example, the computer program can be stored on a computer or processor-readable computer program distribution medium. The computer program medium can be, for example, but not limited to, recording media, computer memory, read-only memory, electrical carrier signals, telecommunication signals, and software distribution packages. The computer program medium can be a non-transitory medium. The coding of the software used to perform the embodiments shown and described is entirely within the scope of those skilled in the art.

[0107] The following is a list of some aspects of the present invention.

[0108] According to a first aspect, a method is provided performed by a network node of a first cell, the method comprising: obtaining information of a plurality of second cell radio resource control (RRC) profiles, the plurality of second cell RRC profiles being associated with user equipment in the second cells, wherein each RRC profile includes a set of parameters for at least RRC configuration of the user equipment; and generating a plurality of first cell RRC profiles for use in the first cell based on the plurality of second cell RRC profiles.

[0109] Various embodiments of the first aspect may include at least one feature from the following bulleted list: Based on at least one of the generated first cell RRC profiles, the UE communicates with the UE in the first cell.

[0110] Determine at least one first cell-specific configuration, which is associated with at least one layer below the RRC layer in the first cell; and further, based on the at least one first cell-specific configuration, generate a plurality of first cell RRC profiles for use in the first cell.

[0111] Determine at least one first cell-specific configuration, which is associated with at least one layer below the RRC layer in the first cell; and further, based on the at least one first cell-specific configuration, generate a plurality of first cell RRC profiles for use in the first cell.

[0112] The information acquisition includes obtaining multiple RRC configuration files of the second cell from the network nodes of the second cell or from the user equipment.

[0113] Receive the identifier of the user equipment from the network node of the second cell or from the user equipment; and obtain multiple RRC profiles of the second cell from a database accessible by the network node of the first cell based on the UE identifier.

[0114] The information acquisition includes acquiring at least one identifier of multiple second cell RRC configuration files and acquiring multiple second cell RRC configuration files based on at least one identifier.

[0115] Obtain information about a specific second cell RRC configuration file from multiple second cell RRC configuration files; determine a specific first cell RRC configuration file based on the specific second cell RRC configuration file; communicate with the user equipment in the first cell based on the specific first cell RRC configuration file.

[0116] The system retrieves information about the specific RRC configuration file of the second cell from the handover request from the network node of the second cell; generates a handover command, which includes information about the specific RRC configuration file of the first cell; and transmits the handover command to the user equipment.

[0117] Obtain information about the RRC profile of a specific second cell from the recovery request message from the user equipment; generate a connection recovery message, which includes information about the RRC profile of a specific first cell; and transmit the connection recovery message to the user equipment.

[0118] The specific second cell RRC profile is the latest RRC profile associated with the user equipment in the second cell.

[0119] Each of the multiple second-cell RRC profiles is identified by an identifier, wherein the identifiers of the multiple second-cell RRC profiles are retained in the multiple first-cell RRC profiles, such that a given first-cell RRC profile is assigned the same identifier as the identifier of the second-cell RRC profile, and the second-cell RRC profiles are used as the basis for generating a given first-cell RRC profile.

[0120] According to a second aspect, a method is provided performed by a network node of a second cell, the method comprising: providing information on a plurality of second cell RRC profiles to a network node of a first cell, the plurality of second cell RRC profiles being associated with user equipment in the second cell, wherein each RRC profile includes a set of parameters for at least RRC configuration of the user equipment.

[0121] Various embodiments of the second aspect may include at least one feature from the following bulleted list: Stores information from multiple second-cell RRC configuration files.

[0122] Information about multiple RRC configuration files for the second cell can be obtained from a database accessible to the network nodes of the second cell.

[0123] Receive a request to provide information from a network node in the first cell, wherein the request includes the identifier of the user equipment; and respond to the request by providing information to a network node in the first cell.

[0124] The information provided includes: providing the network nodes of the first cell with a set of parameters associated with multiple second cell RRC profiles and a profile-specific identifier for each of the multiple second cell RRC profiles.

[0125] According to a third aspect, a method performed by a user equipment is provided, the method comprising: receiving information from a network node of a first cell regarding a plurality of first cell radio resource control (RRC) profiles associated with a user equipment in the first cell, wherein each RRC profile includes a set of parameters for at least RRC configuration of the user equipment; and selecting one of the plurality of first cell RRC profiles for communication in the first cell.

[0126] Various embodiments of the third aspect may include at least one feature from the following bulleted list: The selection is based on at least one of the UE's service requirements or power saving requirements in the first cell.

[0127] The information is included in the handover command; and the method further includes receiving the handover command via a network node of the second cell during the handover of the user equipment from the second cell to the first cell.

[0128] The information is included in the connection restoration message; and the method further includes receiving the connection restoration message from the network node of the first cell during the connection restoration with the network node of the first cell.

[0129] Before obtaining information about multiple first cell RRC configuration files, information about a specific second cell RRC configuration file is transmitted to the network node of the first cell.

[0130] According to a fourth aspect, a network node for a first cell is provided, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network node to at least: acquire information of a plurality of second cell radio resource control (RRC) profiles associated with user equipment in the second cells, wherein each RRC profile includes a set of parameters for at least RRC configuration of the user equipment; and generate a plurality of first cell RRC profiles for use in the first cell based on the plurality of second cell RRC profiles. Various embodiments of the fourth aspect may include at least one feature from the bulleted list under the first aspect.

[0131] According to a fifth aspect, a network node for a second cell is provided, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network node to at least: provide information on a plurality of second-cell RRC profiles to a network node of a first cell, the plurality of second-cell RRC profiles being associated with user equipment in the second cell, wherein each RRC profile includes a set of parameters for at least RRC configuration of the user equipment. Various embodiments of the fifth aspect may include at least one feature from the bulleted list under the second aspect.

[0132] According to a sixth aspect, a user equipment is provided, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the user equipment to at least: receive information from a network node of a first cell regarding a plurality of first cell radio resource control (RRC) profiles associated with the user equipment in the first cell, wherein each RRC profile includes a set of parameters for at least RRC configuration of the user equipment; and select one of the plurality of first cell RRC profiles for communication in the first cell. Various embodiments of the sixth aspect may include at least one feature from the bulleted list under the third aspect.

[0133] According to a seventh aspect, a computer program product is provided, embodied on a distribution medium and including program instructions that, when executed by a device, cause the device to perform the method according to the first aspect, the second aspect, or the third aspect.

[0134] According to an eighth aspect, a computer program product is provided, including program instructions that, when executed by a device, cause the device to perform the method according to the first aspect or according to the first, second, or third aspect.

[0135] According to a ninth aspect, an apparatus is provided, including components for performing a method according to a first aspect, a second aspect, or a third aspect, and / or components configured to cause the apparatus to perform a method according to a first aspect, a second aspect, or a third aspect.

[0136] Although the invention has been described above with reference to examples in conjunction with the accompanying drawings, it is clear that the invention is not limited thereto, but can be modified in various ways within the scope of the appended claims. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate rather than limit the embodiments. It will be apparent to those skilled in the art that the inventive concept can be implemented in various ways as technology advances. Furthermore, it will be clear to those skilled in the art that the described embodiments can, but are not required to, be combined with other embodiments in various ways.

Claims

1. A network node for a first cell, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the network node to at least: Information is obtained about multiple second cell radio resource control (RRC) profiles associated with user equipment in the second cell, wherein each RRC profile includes a set of parameters for at least RRC configuration of the user equipment; as well as Based on the multiple second cell RRC configuration files, multiple first cell RRC configuration files are generated for use in the first cell.

2. The network node according to claim 1, wherein the network node is further configured to: Based on at least one of the generated first cell RRC profiles, the UE communicates with the UE in the first cell.

3. The network node according to any one of claims 1 to 2, wherein the network node is further configured to: Determine at least one first cell-specific configuration, said at least one first cell-specific configuration being associated with at least one layer below the RRC layer in the first cell; and Further, based on the specific configuration of the at least one first cell, generate the plurality of first cell RRC configuration files for use in the first cell.

4. The network node according to any one of claims 1 to 3, wherein obtaining the information includes: The plurality of second cell RRC configuration files are obtained from the network node of the second cell or from the user equipment.

5. The network node according to any one of claims 1 to 3, wherein the network node is further configured to: Receive the identifier of the user equipment from the network node of the second cell or from the user equipment; and Based on the identifier of the UE, the plurality of second cell RRC configuration files are obtained from a database accessible to the network node of the first cell.

6. The network node according to any one of claims 1 to 5, wherein obtaining the information includes: Obtain at least one identifier of the plurality of second cell RRC configuration files, and obtain the plurality of second cell RRC configuration files based on the at least one identifier.

7. The network node according to any one of claims 1 to 6, wherein the network node is further configured to: Obtain information about a specific second cell RRC configuration file from the plurality of second cell RRC configuration files; Based on the specific second cell RRC configuration file, determine the specific first cell RRC configuration file; Based on the specific first cell RRC configuration file, it communicates with the user equipment in the first cell.

8. The network node according to claim 7, wherein the network node is further configured to: Obtain the information from the specific second cell RRC configuration file in the handover request from the network node of the second cell; Generate a handover command, the handover command including information from the specific first cell's RRC configuration file; and The handover command is transmitted to the user equipment.

9. The network node of claim 7, wherein the network node is further configured to: Obtain the information from the recovery request message from the user equipment regarding the specific second cell's RRC configuration file; Generate a connection recovery message, the connection recovery message including information from the specific first cell's RRC configuration file; as well as The connection restoration message is transmitted to the user equipment.

10. The network node according to any one of claims 7 to 9, wherein the specific second cell RRC profile is the latest RRC profile associated with the user equipment in the second cell.

11. The network node according to any one of claims 1 to 10, wherein each of the plurality of second cell RRC profiles is identified by an identifier, wherein the identifier of the plurality of second cell RRC profiles is retained in the plurality of first cell RRC profiles such that a given first cell RRC profile is assigned the same identifier as the identifier of the second cell RRC profile, and the second cell RRC profile is used as the basis for generating the given first cell RRC profile.

12. A network node for a second cell, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the network node to at least: Information on multiple second-cell RRC profiles is provided to network nodes of the first cell. The multiple second-cell RRC profiles are associated with user equipment in the second cell, wherein each RRC profile includes a set of parameters for at least RRC configuration of the user equipment.

13. The network node of claim 12, wherein providing the information includes: The network node of the first cell is provided with the set of parameters associated with the plurality of second cell RRC profiles and a profile-specific identifier for each of the plurality of second cell RRC profiles.

14. A user equipment, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the user equipment to at least: Information on multiple first-cell radio resource control (RRC) profiles is received from a network node in a first cell. The multiple first-cell RRC profiles are associated with the user equipment in the first cell, wherein each RRC profile includes a set of parameters for at least RRC configuration of the user equipment. as well as Select one of the plurality of first cell RRC profiles for communication in the first cell.

15. The user equipment of claim 14, wherein one of the following: The information is included in the handover command, and the user equipment is also configured to receive the handover command via a network node of the second cell during the handover from the second cell to the first cell; or The information is included in the connection restoration message; and the user equipment is also configured to receive the connection restoration message from the network node of the first cell during the connection restoration with the network node of the first cell.