Search

EP-4736506-A1 - CONFIGURATIONS FOR DETERMINING WHEN TO GENERATE REPORTS

EP4736506A1EP 4736506 A1EP4736506 A1EP 4736506A1EP-4736506-A1

Abstract

There is provided a method performed by a user equipment, UE. The UE has a first Successful Primary Secondary Cell Group Cell (PSCell) Report (SPR) configuration and a second SPR configuration for determining when to generate SPRs. The method comprises, based on the occurrence of an event or procedure, releasing (301) at least part of the first SPR configuration and/or releasing at least part of the second SPR configuration.

Inventors

  • PARICHEHREHTEROUJENI, Ali
  • BELLESCHI, Marco
  • RAMACHANDRA, PRADEEPA
  • BIN REDHWAN, Sakib

Assignees

  • Telefonaktiebolaget LM Ericsson (publ)

Dates

Publication Date
20260506
Application Date
20240624

Claims (20)

  1. 1. A method performed by a user equipment, UE, wherein the UE has a first Successful Primary Secondary Cell Group Cell, PSCell, Report, SPR, configuration and a second SPR configuration for determining when to generate SPRs, the method comprising: based on the occurrence of an event or procedure, releasing (301) at least part of the first SPR configuration and/or releasing at least part of the second SPR configuration.
  2. 2. The method of Claim 1 , wherein, based on the occurrence of the event or procedure, releasing only a part of the first SPR configuration.
  3. 3. The method of Claim 2, wherein the other part of the first SPR configuration is kept.
  4. 4. The method of Claim 1 , wherein, based on the occurrence of the event or procedure, releasing the first SPR configuration in full.
  5. 5. The method of any of Claims 1-4, wherein the first SPR configuration and/or the second SPR configuration comprises a plurality of timer thresholds.
  6. 6. The method of any of claims 1-5, wherein, based on the occurrence of the event or procedure, not releasing the first SPR configuration and releasing the second SPR configuration.
  7. 7. The method of any of claims 1-5, wherein, based on the occurrence of the event or procedure, not releasing the first SPR configuration and releasing a part of the second SPR configuration.
  8. 8. The method of any of claims 1-5, wherein, based on the occurrence of the event or procedure, releasing the first SPR configuration and releasing a part of the second SPR configuration.
  9. 9. The method of any of claims 1-5, wherein, based on the occurrence of the event or procedure, releasing the first SPR configuration and releasing the second SPR configuration.
  10. 10. The method of any of Claims 1-9, wherein the first SPR configuration was received from, or configured by, a Primary Cell, PCell, a source PSCell or a target PSCell.
  11. 11. The method of any of Claims 1-9, wherein the first SPR configuration was received from, or configured by, a Primary Cell, PCell, a source PSCell or a target PSCell, and the second SPR configuration was received from, or configured by, a different one of the PCell, source PSCell and target PSCell.
  12. 12. The method of claim 11 , wherein the UE has a third SPR configuration that was received from, or configured by, the remaining one of the PCell, source PSCell and target PSCell.
  13. 13. The method of Claim 12, wherein, based on the occurrence of the event or procedure, not releasing one of the SPR configurations and releasing at least part or all of the other two SPR configurations.
  14. 14. The method of Claim 12, wherein, based on the occurrence of the event or procedure, not releasing two of the SPR configurations and releasing at least part of the othSPRSPR configuration.
  15. 15. The method of Claim 12, wherein, based on the occurrence of the event or procedure, releasing the first SPR configuration, the second SPR configuration and the third SPR configuration.
  16. 16. The method of any of Claims 1-15, wherein the event or procedure is a Radio Resource Control, RRC, event or procedure.
  17. 17. The method of any of Claims 1-16, wherein the event or procedure is one of: • receiving the SPR configuration from a Primary Cell, PCell, and/or source PSCell, and/or target PSCell; • successfully performing a PSCell change/addition procedure using a PSCell change/addition configuration provided by the PCell or PSCell; • failure of a PSCell change/addition procedure using a PSCell change/addition configuration provided by the PCell or PSCell; • performing a Multi-Radio Dual Connectivity, MR-DC, release procedure; • successfully performing a PCell handover; • successfully performing a simultaneous PCell handover and PSCell change/addition; • successfully performing a PCell handover without PSCell change/addition; • performing a re-establishment procedure following a Radio Link Failure in the PCell; • performing a re-establishment procedure following a Handover Failure, HOF, in the PCell; • performing a Radio Resource Control, RRC, resume procedure; • performing RRC resume without Secondary Cell Group, SCG, restoration; • performing RRC resume with SCG restoration; • RLF in the PCell; • HOF in the PCell; • RLF in the PSCell; • HOF in the PSCell; or • performing fast Master Cell Group, MCG, link recovery following RLF in the PCell.
  18. 18. 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-17.
  19. 19. A user equipment, UE, configured to perform the method of any of claims 1-17.
  20. 20. 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 claim 1-17.

Description

CONFIGURATIONS FOR DETERMINING WHEN TO GENERATE REPORTS Technical Field This disclosure relates to reporting configurations that are used for determining when to generate reports. Background Overall Architecture of NG-RAN The current 5th Generation (5G) Radio Access Network (RAN) (NG-RAN) architecture is depicted and described in the 3rd Generation Partnership Project (3GPP) Technical Standard (TS) 38.401 V17.2.0 as shown in Fig. 1. 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 some of the ramifications of Self-Configuration/Self-Optimisation functionality. Fig. 2 corresponds to Figure 22.1-1 in 3GPP TS 36.300 v17.