Search

EP-4736507-A1 - CONFIGURATIONS RELATING TO A MOBILITY OPERATION

EP4736507A1EP 4736507 A1EP4736507 A1EP 4736507A1EP-4736507-A1

Abstract

According to an aspect, there is provided a method performed by a user equipment (UE). The UE has a first configuration associated with a Master Node (MN) in a communication network and a second configuration associated with a Secondary Node (SN) in the communication network. The first configuration and the second configuration indicate information to be provided in a report relating to a mobility operation with respect to the SN. The method comprises, if the MN initiated the mobility operation, obtaining information (601) according to the first configuration for the mobility operation. If the SN initiated the mobility operation, obtaining (601) information according to the second configuration for the mobility operation; and generating (603) a report relating to the mobility operation, the report comprising the obtained information.

Inventors

  • PARICHEHREHTEROUJENI, Ali
  • BELLESCHI, Marco
  • RAMACHANDRA, PRADEEPA

Assignees

  • Telefonaktiebolaget LM Ericsson (publ)

Dates

Publication Date
20260506
Application Date
20240624

Claims (19)

  1. 1 . A method performed by a user equipment, UE, wherein the UE has a first configuration associated with a Master Node, MN, in a communication network and a second configuration associated with a Secondary Node, SN, in the communication network, wherein the first configuration and the second configuration indicate information to be provided in a report relating to a mobility operation with respect to the SN, the method comprising: if the MN initiated the mobility operation, obtaining (601) information according to the first configuration for the mobility operation, and if the SN initiated the mobility operation, obtaining (601) information according to the second configuration for the mobility operation; and generating (603) a report relating to the mobility operation, the report comprising the obtained information.
  2. 2. The method of claim 1 , wherein the communication network is a Self-Organising Network, SON, and the generated report is a SON report.
  3. 3. The method of claim 1 or 2, wherein the information to be provided in the report relating to the mobility operation comprises any one or more of: location information; radio measurement results; and a Conditional Handover, CHO, configuration.
  4. 4. The method of any of claims 1-3, wherein the first configuration and the second configuration are location configurations.
  5. 5. The method of any of claims 1-4, wherein the first configuration and the second configuration are part of a set of configurations associated with the MN and SN respectively.
  6. 6. The method of any of claims 1-5, wherein the UE has a first set of criteria relating to the first configuration, and wherein the step of obtaining (601) information and/orthe step of generating (603) the report is performed if the one or more of the first set of criteria are fulfilled.
  7. 7. The method of any of claims 1-6, wherein the method further comprises: sending the generated report to the MN.
  8. 8. The method of claim 7, wherein the generated report is sent to the MN in response to a request from the MN.
  9. 9. The method of any of claims 1-8, wherein the mobility operation is a handover to or from the SN.
  10. 10. The method of any of claims 1 -9, wherein the mobility operation is a handover between the SN and another network node in the communication network.
  11. 11. The method of any of claims 1-8, wherein the UE is using Dual Connectivity, DC, and the mobility operation is a Primary Secondary Cell Group Cell, PSCell, Addition or Change operation; wherein the SN is one of: (i) the SN providing the PSCell before the PSCell Change operation; and (ii) the SN providing the PSCell after the PSCell Addition or Change operation.
  12. 12. The method of claim 11 , wherein the MN provided the last used configuration to the UE.
  13. 13. The method of any of claims 1-12, wherein the first configuration and second configuration relate to a report to be generated if the mobility operation is successful.
  14. 14. The method of claim 13, wherein the report to be generated is a Successful Handover Report, SHR, or a Successful Primary Secondary Cell Group Cell, PSCell, Addition or Change Report, SPR.
  15. 15. The method of claim 13 or 14, wherein the UE has a first set of criteria relating to the first configuration and the second configuration, and wherein the step of generating (603) the report is performed if the mobility operation is successful and one or more of the first set of criteria are fulfilled.
  16. 16. The method of any of claims 9 or 10, wherein the first configuration relates to a report to be generated in the event of a failure of the handover.
  17. 17. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of claims 1-16.
  18. 18. A user equipment, UE, configured to perform the method of any of claims 1-16.
  19. 19. A user equipment, UE, comprising a processor and a memory, said memory containing instructions executable by said processor whereby said UE is operative to perform the method of any of claims 1-16.

Description

CONFIGURATIONS RELATING TO A MOBILITY OPERATION Technical Field This disclosure relates to User Equipments (UEs) and methods performed by a UE when the UE has a configuration relating to a mobility operation. Background Overall Architecture of NG-RAN The current 5th Generation (5G) Radio Access Network (RAN) (NG-RAN) architecture is depicted in Fig. 1 and described in the 3rd Generation Partnership Project (3GPP) Technical Standard (TS) 38.401 v17.2.0 as follows: The NG-RAN consists of a set of gNBs connected to the 5G Core (5GC) through the Next Generation (NG) interface. As specified in 3GPP TS 38.300 v17.4.0, NG-RAN could also consist of a set of ng-eNBs, where an ng-eNB may consist of an ng-eNB-Central Unit (CU, eNB-CU) and one or more ng- eNB-Distributed Unit(s) (DU(s), eNB-DU(s)). An ng-eNB-CU and an ng-eNB-DU is connected via W1 interface. The general principle described in this clause also applies to ng-eNB and W1 interface, if not explicitly specified otherwise. • An gNB can support Frequency Division Duplex (FDD) mode, Time Division Duplex (TDD) mode or dual mode operation. • gNBs can be interconnected through the Xn interface. • A gNB may consist of a gNB-CU and one or more gNB-DU(s). A gNB-CU and a gNB-DU is connected via F1 interface. • One gNB-DU is connected to only one gNB-CU. • NG, Xn and F1 are logical interfaces. For NG-RAN, the NG and Xn-C interfaces for a gNB consist of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For E-UTRAN (Evolved-UTRA (UMTS Terrestrial Radio Access) Network) New Radio - Dual Connectivity (EN-DC), the S1-U and X2-C interfaces for a gNB consist of a gNB-CU and gNB-DUs terminating in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB. The node hosting the user plane (UP) part of New Radio (NR) Packet Data Convergence Protocol (PDCP) (e.g. gNB-CU, gNB-CU-UP, and for EN-DC, Master eNB (MeNB) or Secondary gNB (SgNB) depending on the bearer split) shall perform user inactivity monitoring and further informs its inactivity or (re)activation to the node having control plane (CP) connection towards the core network (e.g. over E1 , X2). The node hosting NR Radio Link Control (RLC) (e.g. gNB- DU) may perform user inactivity monitoring and further inform its inactivity or (re)activation to the node hosting control plane, e.g. gNB-CU or gNB-CU-CP. Uplink (UL) PDCP configuration (i.e. how the UE uses the UL at the assisting node) is indicated via X2-C (for EN-DC), Xn-C (for NG-RAN) and F1-C. Radio Link Outage/Resume for Downlink (DL) and/or UL is indicated via X2-U (for EN-DC), Xn-U (for NG-RAN) and F1-U. The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e. the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport, signalling transport. The architecture shown above is that defined by 3GPP for 5G. Other standardisation groups, such as Open RAN (ORAN), have further extended the architecture above and have, for example, split the gNB-DU into two further nodes connected by a fronthaul interface. The lower node of the split gNB-DU would contain the Physical (PHY) protocol and the Radio Frequency (RF) parts, the upper node of the split gNB-DU would host the RLC and Medium Access Control (MAC). In ORAN the upper node is called ORAN Distributed Unit (O-DU), while the lower node is called ORAN-Radio Unit (O-RU). At current state-of-art, the coordination across RAN and Transport domains is typically managed in a non-real-time mode (e.g. pre-planning and provisioning the Transport domain) with the alternative to coordinate Radio and Transport domains at Service Orchestration level, even though no products are yet available on the market. Self-Organising Networks (SON) in 3GPP A Self-Organising Network (SON) is an automation technology designed to make the planning, configuration, management, optimisation and healing of mobile radio access networks simpler and faster. SON functionality and behaviour has been defined and specified in generally accepted mobile industry recommendations produced by organisations such as 3GPP and the NGMN (Next Generation Mobile Networks). In 3GPP, the processes within the SON area are classified into a Self-configuration process and a Self-optimisation process. The Self-configuration process is the process where newly deployed nodes are configured by automatic installation procedures to get the necessary basic configuration for system operation. This process works in a pre-operational state. A pre-operational state is understood as the state from when the eNB is powered up and has backbone connectivity until the RF transmitter is switched on. Fig. 2 illustrates the ramifications of Self-Configuration/Self-Optimisation functionality, and corresponds to Figure 22.1-1 in