WO2022086421A1 - Initiateur d'un rapport de changement d'un sn et de défaillance d'un scg lors de la suspension d'un mcg - Google Patents

Initiateur d'un rapport de changement d'un sn et de défaillance d'un scg lors de la suspension d'un mcg Download PDF

Info

Publication number
WO2022086421A1
WO2022086421A1 PCT/SE2021/051056 SE2021051056W WO2022086421A1 WO 2022086421 A1 WO2022086421 A1 WO 2022086421A1 SE 2021051056 W SE2021051056 W SE 2021051056W WO 2022086421 A1 WO2022086421 A1 WO 2022086421A1
Authority
WO
WIPO (PCT)
Prior art keywords
change
node
network node
failure
pscell
Prior art date
Application number
PCT/SE2021/051056
Other languages
English (en)
Inventor
Pradeepa Ramachandra
Angelo Centonza
Ioanna Pappa
Ali PARICHEHREHTEROUJENI
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2022086421A1 publication Critical patent/WO2022086421A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the present disclosure relates to handling of Secondary Cell Group (SCG) failures resulting from Secondary Node (SN) changes in a cellular communications system.
  • SCG Secondary Cell Group
  • SN Secondary Node
  • FIGs 1 and 2 excerpted from Figures 5.3.5.1-1 and 5.3.5.1-2 of 3GPP TS 38.331, version 16.2.0 (referred to hereinafter as "TS 38.331"), illustrate Radio Resource Control (RRC) configuration with a successful outcome and a failure outcome, respectively.
  • RRC Radio Resource Control
  • the purpose of this procedure is to modify an RRC connection, e.g., to establish/modify/release resource blocks (RBs), to perform reconfiguration with sync, to setup/modify/release measurements, to add/modify/release Secondary Cells (SCells) and cell groups, to add/modify/release conditional handover configuration, and/or to add/modify/release conditional Primary Serving Cell (PSCell) change configuration.
  • NAS Non-Access-Stratum
  • UE user equipment
  • RRC reconfiguration to perform reconfiguration with sync includes, but is not limited to, the following cases:
  • SRB3 can be used for measurement configuration and reporting, for UE assistance configuration/reconfiguration and reporting for power savings, to configure/reconfigure MAC, RLC, physical layer and Radio Link Failure (RLF) timers and constants of the SCG configuration, and to reconfigure PDCP for DRBs associated with the S-KQNB or SRB3, to reconfigure Service Data Adaptation Protocol (SDAP) for DRBs associated with S-KQNB in NGEN-DC and NR-DC, and to add/modify/release conditional PSCell change configuration, provided that the configuration/reconfiguration does not require any Master Node (MN) involvement.
  • MN Master Node
  • the Network may initiate the RRC reconfiguration procedure to a UE in RRC_CONNECTED.
  • the Network applies the procedure as follows: • the establishment of RBs (other than SRB1, which is established during RRC connection establishment) is performed only when Access Stratum (AS) security has been activated;
  • AS Access Stratum
  • CPC Continuous Packet Connectivity
  • conditionalReconfiguration for Conditional Handover (CHO) is included only when AS security has been activated, and SRB2 with at least one DRB or, for Integrated Access and Backhaul (IAB), SRB2, are setup and not suspended.
  • RRCReconfiguration is received by the UE the following applies for
  • S-RLF SCG RLF
  • the content of the SCG Failure report contains a failure type, MCG related measurements, and SCG related measurements.
  • the SCG related measurements are included in SN format, in a container, and the setting of the information is defined in 5.7.3. , as excerpted in Table 2 below:
  • MCG related measurements are included in MN format, and the setting of the information is defined in 5.7.3.5 directly, as shown in the excerpt in Table 3 below:
  • MCG measurements are included in the field measResultFreqList of IE MeasResultFreqList in MN format, in the SCGFaiiurelnformation message sent to the MN.
  • SCG measurement are included in the field measResultSCG-Failure of IE message OCTET STRING (CONTAINING MeasResultSCG-Failure) - i.e., it is transmitted in a container in SN format, as shown in the excerpt in Table 4:
  • the MN Upon reception of the MCG measurements, the MN can determine the actions to be performed (e.g., release the SN, change the SN, etc.). However, the SCG measurements could in principle be useful for further procedures. Hence, SCG measurements that have been received at the MN within an SCG Failure report (within SCGFailurelnformation message) can be forwarded e.g., when the MN releases and/or modifies the UE context at the SN within the RRC container CG-Configlnfo, as defined in TS 38.331, when the master eNB or gNB requests the SgNB or SeNB to perform certain actions e.g., to establish, modify or release an SCG, as described below in Table 5:
  • scgFailurelnfo contains SCG failure type and measurement results.
  • the sender may include one empty entry (i.e., without any optional fields present) in measResultPerMOList.
  • This field is used in (NG)EN-DC and NR-DC, and scgFailurelnfoEUTRA contains SCG failure type and measurement results of the E-UTRA secondary cell group. This field is only used in NE- DC.
  • the RRC container CG- Configlnfo can be included in the following messages from MN to SN:
  • the MN would typically send a S-NODE MODIFICATION REQUEST or a S-NODE RELEASE REQUEST, to modify or release the SN.
  • M-RLF MCG RLF
  • the SN can send an RRC transfer message to the MN, so the MN can take the appropriated actions.
  • the UE include an indication that an RLF report is available in the RRCReestablishmentComplete message so the node where the UE has Reestablished can retrieve the RLF report via UE Information request. Then, the RLF report can be included in an UEInformationResponse Once that message is received, the Re-establishment node can retrieve in the RLF report the information regarding the cell where the UE has failed, so that it can forward the RLF report to the source node.
  • the Failure Indication procedure is used for that purpose, as defined in TS 38.423 (see 8.4.7).
  • the purpose of the procedure is to transfer information regarding
  • RRC re-establishment attempts or received RLF Reports, between NG-RAN nodes.
  • the signalling takes place from the NG-RAN node at which a re-establishment attempt is made, or an RLF Report is received, to an NG-RAN node to which the UE concerned may have previously been attached prior to the connection failure. This may aid the detection of radio link failure, handover failure cases.
  • the procedure uses non UE- associated signalling and is illustrated in Figure 4.
  • NG-RAN node initiates the procedure by sending the FAILURE INDICATION message to NG-RAN nodei, following a re-establishment attempt or an RLF Report reception from a UE at NG-RAN node , when NG-RAN node considers that the UE may have previously suffered a connection failure at a cell controlled by NG-RAN nodei. If the UE RLF Report Container IE is included in the FAILURE INDICATION message, NG-RAN nodei shall use it to derive failure case information.
  • the FAILURE INDICATION message is illustrated below in Table 7:
  • Embodiments disclosed herein enable a cellular communications network to determine which network node initiates an SN change that led to SCG failure, and to correspondingly forward relevant information for further processing even if the Master Cell Group (MCG) is suspended and/or if there is no User Equipment (UE) signaling connection between the node receiving the SCG Radio Link Failure (S-RLF) information and the node where the failure may have originated.
  • MCG Master Cell Group
  • UE User Equipment
  • Embodiments of a method performed by a UE of a cellular communication system to provide reporting of SN change and SCG failure are disclosed herein.
  • the method comprises receiving an indication associated with an SN change or a Primary Serving Cell (PSCell) change, the indication indicating a node that initiated the SN change or the PSCell change.
  • the method further comprises declaring an SCG failure.
  • the method also comprises transmitting, to a network node, an indication of the node that initiated the SN change or the PSCell change.
  • Some embodiments disclosed herein provide that the method further comprises transmitting, to the network node, an S-RLF report containing information on an S-RLF event.
  • receiving the indication comprises receiving an RRCReconfiguration message comprising the indication.
  • the RRCReconfiguration message further comprises an indication of whether the SN change or the PSCell change is instructed by a Master Node (MN) or by the SN.
  • MN Master Node
  • the network node comprises a re-establishment node
  • transmitting the indication of the node that initiated the SN change or the PSCell change comprises detecting that an S-RLF has occurred; initiating a re-establishment procedure; receiving, from the re-establishment node, a request for an S-RLF report; and transmitting, to the re-establishment node, a UEInformationResponse message comprising the indication of the node that initiated the SN change or the PSCell change.
  • the method further comprises transmitting, to the re-establishment node, the S-RLF report and the indication of the node that initiated the SN change or the PSCell change.
  • the method further comprises transmitting, to a MN, an SCGFailurelnformation message comprising the indication of the node that initiated the SN change or the PSCell change.
  • the method further comprises transmitting, to the MN, the S-RLF report and the indication of the node that initiated the SN change or the PSCell change.
  • the re-establishment node comprises a network node associated with a cell selected by the UE during the re-establishment procedure.
  • the re-establishment node comprises a network node associated with a cell accessed by the UE upon applying a Conditional Reconfiguration configuration.
  • Some embodiments disclosed herein provide that the re-establishment node comprises a network node associated with a cell with which the UE performs a connection establishment or a connection setup when returning from an RRC_IDLE state after S-RLF.
  • the re-establishment node comprises a network node associated with a cell that sends an RRCReconfiguration message to the UE.
  • a UE for providing reporting of SN change and SCG failure are also disclosed herein.
  • the UE comprises one or more transmitters, one or more receivers, and processing circuitry associated with the one or more transmitters and the one or more receivers.
  • the processing circuitry is configured to cause the UE to receive an indication associated with an SN change or PSCell change, the indication indicating a node that initiated the SN change or the PSCell change.
  • the processing circuitry is further configured to cause the UE to declare an SCG failure.
  • the processing circuitry is also configured to cause the UE to transmit, to a network node, an indication of the node that initiated the SN change or the PSCell change. Some embodiments disclosed herein provide that the processing circuitry is further configured to cause the UE to perform the steps of any of the above-disclosed methods attributed to the UE.
  • Embodiments of a UE for providing reporting of SN change and SCG failure are also disclosed herein.
  • the UE is adapted to receive an indication associated with an SN change or PSCell change, the indication indicating a node that initiated the SN change or the PSCell change.
  • the UE is further adapted to declare an SCG failure.
  • the UE is also adapted to transmit, to a network node, an indication of the node that initiated the SN change or the PSCell change.
  • the UE is further adapted to perform the steps of any of the above-disclosed methods attributed to the UE.
  • Embodiments of a method performed by a first network node of a cellular communication system to provide reporting of SN change and SCG failure are also disclosed herein. Some embodiments disclosed herein provide that the method comprises transmitting, to a UE, an RRCReconfiguration message associated with an SN change or PSCell change, the RRCReconfiguration message comprising an indication indicating a node that initiated the SN change or the PSCell change. The method further comprises receiving, from the UE, information regarding an SCG failure. The method also comprises determining a second network node based on the information regarding the SCG failure. The method additionally comprises transmitting the information regarding the SCG failure to the second network node.
  • the second network node comprises an SN for which the UE was configured when the SCG failure was detected.
  • the second network node comprises an SN from which the UE successfully received an RRCReconfiguration message with a sync command whose execution failed.
  • Some embodiments disclosed herein provide that the second network node comprises a MN for which the UE was configured when the SCG failure was detected.
  • the method further comprises determining that an issue related to a too-early SN change is a cause of S-RLF.
  • the method also comprises determining that the SCG failure is a handover failure.
  • the method additionally comprises transmitting an S-RLF report to a network node serving a previous PSCell.
  • the method further comprises determining that an issue related to a too-early SN change is a cause of S-RLF.
  • the method also comprises determining that the SCG failure is a Radio Link Failure (RLF) while the UE is connected to a target PSCell.
  • the method additionally comprises transmitting an S-RLF report to a network node serving a PSCell in which the UE indicates the SCG failure.
  • RLF Radio Link Failure
  • the method further comprises determining that an issue related to a too-late SN change or a coverage hole is a cause of S-RLF.
  • the method also comprises transmitting an S-RLF report to a network node serving a previous PSCell.
  • the method further comprises forwarding the indication indicating the node that initiated the SN change or the PSCell change to an SN using a Failure Indication procedure.
  • the network node comprises a network interface, and processing circuitry associated with the network interface.
  • the processing circuitry is configured to cause the network node to transmit, to a UE, an RRCReconfiguration message associated with an SN change or PSCell change, the RRCReconfiguration message comprising a first indication indicating a node that initiated the SN change or the PSCell change.
  • the processing circuitry is further configured to cause the network node to receive, from the UE, information regarding an SCG failure.
  • the processing circuitry is also configured to cause the network node to determine a second network node based on the information regarding the SCG failure.
  • the processing circuitry is additionally configured to cause the network node to transmit the information regarding the SCG failure to the second network node.
  • Embodiments of a network node for a core network of a cellular communications system where the network node is enabled to provide reporting of SN change and SCG failure are also disclosed herein.
  • the network node is adapted to transmit, to a UE, an RRCReconfiguration message associated with an SN change or PSCell change, the RRCReconfiguration message comprising a first indication indicating a node that initiated the SN change or the PSCell change.
  • the network node is further adapted to receive, from the UE, information regarding an SCG failure.
  • the network node is also adapted to determine a second network node based on the information regarding the SCG failure.
  • the network node is additionally adapted to transmit the information regarding the SCG failure to the second network node.
  • the network node is further adapted to perform the steps of any of the above-disclosed methods attributed to the network node.
  • Embodiments of a method in a core network of a cellular communication system to provide reporting of SN change and SCG failure are also disclosed herein. Some embodiments disclosed herein provide that the method comprises transmitting, by a first network node, to a UE, an RRCReconfiguration message associated with an SN change or PSCell change, the RRCReconfiguration message comprising an indication indicating a node that initiated the SN change or the PSCell change.
  • the method further comprises receiving, by a second network node from the UE, information regarding an SCG failure.
  • the method also comprises determining, by the second network node, a third network node based on the information regarding the SCG failure.
  • the method additionally comprises transmitting, by the second network node, the information regarding the SCG failure to the third network node.
  • the core network comprises a first network node comprising a first network interface and first processing circuitry associated with the first network interface.
  • the first processing circuitry is configured to cause the first network node to transmit, to a UE, an RRCReconfiguration message associated with an SN change or PSCell change, the RRCReconfiguration message comprising a first indication indicating a node that initiated the SN change or the PSCell change.
  • the core network further comprises a second network node comprising a second network interface and second processing circuitry associated with the second network interface.
  • the second processing circuitry is configured to cause the second network node to receive, from the UE, information regarding an SCG failure.
  • the second processing circuitry is further configured to determine a third network node based on the information regarding the SCG failure.
  • the second processing circuitry is also configured to transmit the information regarding the SCG failure to the third network node.
  • the core network comprises a first network node adapted to transmit, to a UE, an RRCReconfiguration message associated with an SN change or PSCell change, the RRCReconfiguration message comprising a first indication indicating a node that initiated the SN change or the PSCell change.
  • the core network further comprises a second network node adapted to receive, from the UE, information regarding an SCG failure.
  • the second network node is further adapted to determine a third network node based on the information regarding the SCG failure.
  • the second network node is also adapted to transmit the information regarding the SCG failure to the third network node.
  • FIG. 1 illustrates Radio Resource Control (RRC) configuration with a successful outcome, according to some embodiments disclosed herein;
  • RRC Radio Resource Control
  • Figure 2 illustrates RRC configuration with a failure outcome, according to some embodiments disclosed herein;
  • FIG. 3 illustrates an example of the Secondary Cell Group (SCG) Failure Information procedure, according to some embodiments disclosed herein;
  • Figure 4 illustrates an example of the Failure Indication procedure using non-UE- associated signalling, according to some embodiments disclosed herein;
  • Figure 5 illustrates one example of a cellular communications system according to some embodiments disclosed herein;
  • Figures 6 and 7 illustrate example embodiments in which the cellular communication system of Figure 3 is a Fifth Generation (5G) System (5GS);
  • 5G Fifth Generation
  • 5GS Fifth Generation
  • FIG. 8 illustrates communications flows and operations for reporting of Secondary Node (SN) change and SCG failure, according to some embodiments disclosed herein;
  • Figure 9 illustrates communications flows and operations for reporting SN change and SCG failure, according to another embodiment disclosed herein;
  • Figure 10 is a schematic block diagram of a radio access node according to some embodiments disclosed herein;
  • Figure 11 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node of Figure 10 according to some embodiments disclosed herein;
  • Figure 12 is a schematic block diagram of the radio access node of Figure 10 according to some other embodiments disclosed herein;
  • Figure 13 is a schematic block diagram of a UE according to some embodiments disclosed herein.
  • Figure 14 is a schematic block diagram of the UE of Figure 13 according to some other embodiments disclosed herein.
  • a User Equipment configured with Multi-Radio Dual Connectivity (MR-DC) wherein a Secondary Cell Group Radio Link Failure (S-RLF) is triggered (i.e., Radio Link Failure (RLF) triggered at the Secondary Cell Group (SCG)), due to an SCG failure.
  • S-RLF Secondary Cell Group Radio Link Failure
  • MCG Master Cell Group
  • Some problems that emerge from such scenario include how the information the UE has logged would be retrieved in cases where the UE has both an RLF report (or an MCG failure report) and an SCG failure report, as well as the forwarding mechanisms from the node receiving the logged information to the node(s) where the failure may have originated for parameter tuning/settings, i.e., to be used as input of SelfOrganizing Networks (SON) functions, such as Mobility Robustness Optimization (MRO).
  • SON SelfOrganizing Networks
  • MRO Mobility Robustness Optimization
  • the solution proposed in the said prior art comprises a method performed by a wireless terminal (also called User Equipment) for reporting S-RLF information to a reestablishment node, the method comprising:
  • It also comprises a method on the network side, at a re-establishment or reconnection node, for receiving from a UE information of an SCG Failure Information message, that could not be transmitted by the UE in an SCG Failure Information message (because MCG was suspended e.g., due to M-RLF), the method comprising:
  • the invention comprises a method performed by a wireless terminal (also called User Equipment) for reporting which node initiated the SN change that led to the SCG failure, the method comprising:
  • the invention also comprises a method on the network side, at a network node, for receiving from a UE report associated to an SCG Failure Information message, that could not be transmitted by the UE in an SCG Failure Information message (because MCG was suspended, e.g., due to M-RLF), the method comprising:
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • the advantages disclosed herein consist of the network being able to know which node initiated an SN change that led to SCG failure and correspondingly forward the relevant information for further processing even if the MCG is suspended and/or when there is no UE signaling connection between the node receiving the S-RLF information and the node where the failure may have originated (e.g., the SN the UE was connected to when the failure occurred).
  • Radio Node As used herein, a "radio node” is either a radio access node or a wireless communication device.
  • Radio Access Node As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals.
  • RAN Radio Access Network
  • a radio access node examples include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.
  • a base station e.g., a New Radio (NR) base station (gNB)
  • a "core network node” is any type of node in a core network or any node that implements a core network function.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like.
  • MME Mobility Management Entity
  • P-GW Packet Data Network Gateway
  • SCEF Service Capability Exposure Function
  • HSS Home Subscriber Server
  • a core network node examples include a node implementing an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • NSSF Network Slice Selection Function
  • NEF Network Exposure Function
  • NRF Network Exposure Function
  • NRF Network Exposure Function
  • PCF Policy Control Function
  • UDM Unified Data Management
  • a "communication device” is any type of device that has access to an access network.
  • Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC).
  • the communication device may be a portable, hand-held, computer-comprised, or vehiclemounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.
  • One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network).
  • a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device.
  • UE User Equipment
  • MTC Machine Type Communication
  • LoT Internet of Things
  • Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC.
  • the wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection.
  • Network Node As used herein, a "network node” is any node that is either part of the RAN or the core network of a cellular communications network/system.
  • a TRP may be either a network node, a radio head, a spatial relation, or a Transmission Configuration Indicator (TCI) state.
  • TCI Transmission Configuration Indicator
  • a TRP may be represented by a spatial relation or a TCI state in some embodiments.
  • a TRP may be using multiple TCI states.
  • FIG. 5 illustrates one example of a cellular communications system 500 in which embodiments of the present disclosure may be implemented.
  • the cellular communications system 500 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC) or an Evolved Packet System (EPS) including an Evolved Universal Terrestrial RAN (E-UTRAN) and an Evolved Packet Core (EPC).
  • 5GS 5G system
  • NG-RAN Next Generation RAN
  • 5GC 5G Core
  • EPS Evolved Packet System
  • E-UTRAN Evolved Universal Terrestrial RAN
  • EPC Evolved Packet Core
  • the RAN includes base stations 502-1 and 502-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC) and in the EPS include eNBs, controlling corresponding (macro) cells 504-1 and 504-2.
  • the base stations 502- 1 and 502-2 are generally referred to herein collectively as base stations 502 and individually as base station 502.
  • the (macro) cells 504-1 and 504-2 are generally referred to herein collectively as (macro) cells 504 and individually as (macro) cell 504.
  • the RAN may also include a number of low power nodes 506-1 through 506-4 controlling corresponding small cells 508-1 through 508-4.
  • the low power nodes 506-1 through 506-4 can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like.
  • RRHs Remote Radio Heads
  • one or more of the small cells 508-1 through 508-4 may alternatively be provided by the base stations 502.
  • the low power nodes 506-1 through 506-4 are generally referred to herein collectively as low power nodes 506 and individually as low power node 506.
  • the small cells 508-1 through 508-4 are generally referred to herein collectively as small cells 508 and individually as small cell 508.
  • the cellular communications system 500 also includes a core network 510, which in the 5G System (5GS) is referred to as the 5GC.
  • the base stations 502 (and optionally the low power nodes 506) are connected to the core network 510.
  • the base stations 502 and the low power nodes 506 provide service to wireless communication devices 512-1 through 512-5 in the corresponding cells 504 and 508.
  • the wireless communication devices 512-1 through 512-5 are generally referred to herein collectively as wireless communication devices 512 and individually as wireless communication device 512.
  • the wireless communication devices 512 are oftentimes UEs, but the present disclosure is not limited thereto.
  • Figure 6 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point/interface.
  • Figure 6 can be viewed as one particular implementation of the system 500 of Figure 5.
  • NFs Network Functions
  • the 5G network architecture shown in Figure 6 comprises a plurality of UEs 512 connected to either a RAN 502 or an Access Network (AN) as well as an AMF 600.
  • the R(AN) 502 comprises base stations, e.g., such as eNBs or gNBs or similar.
  • the 5GC NFs shown in Figure 6 include a NSSF 602, an AUSF 604, a UDM 606, the AMF 600, a SMF 608, a PCF 610, and an Application Function (AF) 612.
  • the N1 reference point is defined to carry signaling between the UE 512 and AMF 600.
  • the reference points for connecting between the AN 502 and AMF 600 and between the AN 502 and UPF 614 are defined as N2 and N3, respectively.
  • N4 is used by the SMF 608 and UPF 614 so that the UPF 614 can be set using the control signal generated by the SMF 608, and the UPF 614 can report its state to the SMF 608.
  • N9 is the reference point for the connection between different UPFs 614, and N14 is the reference point connecting between different AMFs 600, respectively.
  • N15 and N7 are defined since the PCF 610 applies policy to the AMF 600 and SMF 608, respectively.
  • N12 is required for the AMF 600 to perform authentication of the UE 512.
  • N8 and N10 are defined because the subscription data of the UE 512 is required for the AMF 600 and SMF 608.
  • the 5GC network aims at separating UP and CP.
  • the UP carries user traffic while the CP carries signaling in the network.
  • the UPF 614 is in the UP and all Other NFS, i.e., the AMF 600, SMF 608, PCF 610, AF 612, NSSF 602, AUSF 604, and UDM 606, are in the CP.
  • Separating the UP and CP guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP functions in a distributed fashion.
  • UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and a Data Network (DN) 616 (which provides Internet access, operator services, and/or the like) for some applications requiring low latency.
  • RTT Round Trip Time
  • DN Data Network
  • the core 5G network architecture is composed of modularized functions.
  • the AMF 600 and SMF 608 are independent functions in the CP. Separated AMF 600 and SMF 608 allow independent evolution and scaling.
  • Other CP functions like the PCF 610 and AUSF 604 can be separated as shown in Figure 6.
  • Modularized function design enables the 5GC network to support various services flexibly.
  • Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF.
  • a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity.
  • the UP supports interactions such as forwarding operations between different UPFs.
  • Figure 7 illustrates a 5G network architecture using service-based interfaces between the NFs in the CP, instead of the point-to-point reference points/interfaces used in the 5G network architecture of Figure 6.
  • the NFs described above with reference to Figure 6 correspond to the NFs shown in Figure 7.
  • the service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface.
  • the service based interfaces are indicated by the letter "N" followed by the name of the NF, e.g., Namf for the service based interface of the AMF 600 and Nsmf for the service based interface of the SMF 608, etc.
  • the AMF 600 provides UE-based authentication, authorization, mobility management, etc.
  • a UE 512 even using multiple access technologies is basically connected to a single AMF 600 because the AMF 600 is independent of the access technologies.
  • the SMF 608 is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF 614 for data transfer. If a UE 512 has multiple sessions, different SMFs 608 may be allocated to each session to manage them individually and possibly provide different functionalities per session.
  • the AF 612 provides information on the packet flow to the PCF 610 responsible for policy control in order to support QoS.
  • the PCF 610 determines policies about mobility and session management to make the AMF 600 and SMF 608 operate properly.
  • the AUSF 604 supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM 606 stores subscription data of the UE 512.
  • the Data Network (DN) 616 not part of the 5GC network, provides Internet access or operator services and similar.
  • An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.
  • the term “re-establishment node” refers to a network node (or network element, or network function) associated to a cell the UE transmits the RLF for SCG information (radio link failure for SCG information).
  • MCG RLF while UE monitors CHO, or CHO execution failure, or HO failure while CHO is configured
  • some of the actions related to logging upon re-establishment could be equivalent in this CHO related case i.e., when the UE has stored S-RLF information and applies a stored RRC Reconfiguration that was part of CHO configuration upon failure detection, so that report is retrieved by network
  • this re-establishment node can be the network node associated to the cell the UE performs a connection establishment/setup coming from RRC_IDLE after the failure.
  • this re-establishment node can be the network node associated to the cell which sends the RRCReconfiguration message to the UE.
  • the term "indication for the initiating node” refers to information that clearly indicates which node initiated the SN change that led to SCG failure.
  • the example cases considering NR and the 5GC are only one instance of how the methods can be applied.
  • the methods can also be applied to other systems adopting the same multi connectivity solutions assumed in the methods, e.g., the methods can be applied to the E-UTRAN and EPS system, in which case they would affect the E-UTRAN interfaces and protocols.
  • step A Receiving (step A) an indication associated to SN change/ PSCell change, indicating which node initiated the SN change/PSCell change;
  • step C Transmitting (step C) to the network node an indication of which node initiated the SN change
  • the UE receives the RRCReconfiguration message associated to a SN change or PSCell change related configuration. Further in this RRC message, the network includes an indication as to whether this SN change or PSCell change is instructed by MN or by SN.
  • An example implementation is given below (this is just an example and the indication could be included in some of the other IES within the RRCReconfiguration e.g., MRDC-SecondaryCellGroupConfig).
  • the RRCReconfiguration message is the command to modify an RRC connection.
  • Signalling radio bearer SRB1 or SRB3
  • a set of UE embodiments related to the indication for the initiating node provide reporting mechanisms for the said indication.
  • the UE detects that S-RLF has occurred. If the MCG transmission is suspended (or an SCG Failure Information message cannot be transmitted via MCG for other reasons) the UE may initiate a re-establishment procedure. Consequently, the re-establishment node may request S- RLF report which the UE may send in the UEInformationResponse message. There, the UE indicates to the re-establishment node which node initiated the SN change.
  • the UEInformationResponse message is used by the UE to transfer information requested by the network, and has the following characteristics:
  • Signalling radio bearer SRB1 or SRB2 (when logged measurement information is included)
  • the UE includes the said indication about which node had initiated the SN change procedure, in the SCGFailurelnformation message which is included in the UEInformationResponse message.
  • the UE may also include the indication in a separate IE and send it together with the S-RLF Report (or SCGFailurelnformation).
  • the UE could use the method of this embodiment when the UE experiences a successive SCGFailure and MCGFailure before it could report the SCGFailurelnformation to the MN.
  • Contents of a UEInformationResponse message are shown in Table 12 below: Table 12
  • the UE includes the said indication about which node had initiated the SN change procedure, in the SCGFailurelnformation message which is directly sent to the MN.
  • the UE may also include the indication in a separate IE and send it together with the S-RLF Report (or SCGFailurelnformation).
  • SCGFailurelnformation This embodiment is useful in scenarios when the UE declares SCG failure and then successfully sends the SCGFailurelnformation message to the MN which directly looks into the contents of the message to realize which node (MN or SN) had initiated the SCG change/PSCell change procedure. Contents of such an SCGFailurelnformation message are shown below in Table 14:
  • the re-establishment node receives the indication e.g., in the UEInformationResponse/SCGFai/urelnformation message as described above.
  • the reestablishment node transmits the indication to a second network node.
  • that second network node is the Secondary Node the UE was configured with when the SCG Failure was detected.
  • that second network node is the Secondary Node in which the UE received the RRCReconfiguration with sync (HO) command successfully but whose execution failed.
  • that second network node is the Master Node the UE was configured with when the SCG Failure was detected. That is the Master Node associated to the MCG that was suspended when the UE tried to transmit the SCG Failure Information message.
  • the re-establishment node receives the SCGFailurelnformation and determines the MN the UE was connected to e.g., thanks to the PCell identifier included in the S-RLF information in the UE Information Response message.
  • the re-establishment node forwards the_S-RLF (or parts of it e.g., measurements, failure type, location, etc.) to a second network node (e.g., the MN the UE was connected to when the S-RLF was detected).
  • the re-establishment node can do one of the following actions.
  • the re-establishment node could further do the root cause analysis based on the S-RLF report information.
  • the re-establishment node sends the S-RLF report to (1) the node serving the previous PSCell (i.e., the source PSCell of the SN change procedure) included in the S-RLF report, if the failure is an handover Failure, e.g., failure at RACH access to the PSCell; and/or (2) the node serving the failure PSCell (i.e., the PSCell in which the UE declared SCG RLF) included in the S-RLF report, if the failure is an RLF while the UE is connected to the target PSCell
  • the re-establishment node could further do the root cause analysis based on the S-RLF report. If the RLF is determined to be a too-late SN change related issue or a coverage hole related issue, then the re-establishment node sends the S-RLF report to the previous PSCell (i.e., the source PSCell of the SN change procedure) included in the S-RLF. For the scenario wherein the re-establishment node sends the S-RLF report to the node associated to the PCell at the time of PSCell RLF (referred to as associated MN hereon), the associated MN can do one of the following actions. The associated MN could further do the root cause analysis based on the S-RLF report.
  • the associated MN sends the S-RLF report to (1) the node serving the previous PSCell (i.e., the source PSCell of the SN change procedure) included in the S-RLF report, if the failure is an handover Failure, e.g., failure at RACH access to the PSCell; and/or (2) the node serving the failure PSCell (i.e., the PSCell in which the UE declared SCG RLF) included in the S-RLF report, if the failure is an RLF while the UE is connected to the target PSCell.
  • the failure i.e., the source PSCell of the SN change procedure
  • the associated MN could further do the root cause analysis based on the S-RLF report. If the RLF is determined to be a too-late SN change related issue or a coverage hole related issue and the associated SN change was an SN initiated SN change, then the associated MN sends the S-RLF report to the node serving the failed PSCell (i.e., the PSCell in which the UE declared SCG RLF) included in the S-RLF.
  • the node serving the failed PSCell i.e., the PSCell in which the UE declared SCG RLF
  • the associated MN could further do the root cause analysis based on the S-RLF report. If the RLF is determined to be a too-late SN change related issue or a too-early SN change related issue and the associated SN change was an MN initiated SN change procedure, then the associated MN changes the mobility parameters associated to the SN change procedure.
  • the re-establishment node forwards the indication for the initiating node (reported by the UE) to the SN using a Failure Indication procedure, by transmitting a FAILURE INDICATION message over an inter-node interface (e.g., XnAP message, X2 message, etc.), which is a non-UE associated message.
  • a FAILURE INDICATION message e.g., XnAP message, X2 message, etc.
  • the SN receiving the indication for the initiating node uses a Failure Indication procedure to forward the indication for the initiating node to the MN the UE was connected to, by transmitting a FAILURE INDICATION message over an inter-node interface (e.g., XnAP message, X2 message, etc.), which is a non-UE associated message.
  • a FAILURE INDICATION message e.g., XnAP message, X2 message, etc.
  • Table 15 Below in Table 15 is shown an example of possible changes to TS 38.423 based on these embodiments: Table 15
  • embodiments related to how the re-establishment node decides on whether to forward the S-RLF report information directly to the corresponding SN or whether to send the S-RLF report information to the SN via the previous MN are captured, based also on the indication for the initiating node. This is applicable for the scenario when the UE includes the identities related to both the failed PSCell and the associated PCell in the said failure information. It is to be noted that the network actions mentioned here are just examples
  • the reestablishment node could forward the S-RLF report information to the node serving the previous PCell over X2/Xn connection and the node serving the PCell will forward this information to the node serving the previous PSCell. This avoids the core network related signaling.
  • the forwarding of this information by the node serving the PCell to the node serving the PSCell is optional for those scenarios when the node serving the PCell identifies the root cause of this failure to be a PSCell change which was initiated as part of MN initiated SN change procedure.
  • the re-establishment cell has the PCell included in S-RLF report information as one of the known neighbors (i.e., there is an X2/Xn connection between the reestablishment cell and the PCell included in S-RLF report information) and also the PSCell included in S-RLF report information is a known neighbor (i.e., there is X2/Xn connection between the node serving the reestablishment cell and the node serving the PSCell included in S-RLF report information).
  • the node serving the reestablishment cell could forward the S-RLF report information directly to the node serving the PSCell over X2/Xn connection. This is in a network solution wherein the network is implementing the SN initiated SN change procedures. This avoids the core network related signaling.
  • the reestablishment cell could forward the S-RLF report information to the node serving the PCell over X2/Xn connection. This is in a network solution wherein the network is implementing the MN initiated SN change procedures. This avoids the core network related signaling.
  • the reestablishment cell could forward the S-RLF report information to both the PSCell and PCell over X2/Xn connection. This avoids the core network related signaling.
  • Figure 8 provides a message flow diagram 800.
  • the message flow diagram 800 show a network node 802, a UE 804, and a network node 806 represented by vertical lines, with communications between these elements represented by captioned arrows and operations performed by these elements represented by captioned blocks.
  • Each of the network nodes 802 and 806 may be, e.g., a base station 502 or 506 or a network node that implements all or part of the functionality of the base station 502 or 506.
  • operations begin with the UE 804 receiving an indication associated with an SN change or PSCell change, the indication indicating a node that initiated the SN change or PSCell change, as indicated by arrow 810.
  • the indication 808 may be received as part of an RRCReconfiguration message 810 received by the UE 804.
  • the UE 804 next declares an SCG failure, as indicated by block 814.
  • the UE 804 then transmits, to the network node 806, an indication 816 of the node that initiated the SN change or PSCell change, as indicated by arrow 818.
  • the UE 804 may also transmit, to the network node 806, an S-RLF report 820 containing information on an S-RLF event, as indicated by arrow 822.
  • Figure 9 provides a message flow diagram 900 to illustrate communications flows and operations for reporting SN change and SCG failure according to another embodiment.
  • the message flow diagram 900 show a first network node 902, a UE 904, and a second network node 906 represented by vertical lines, with communications between these elements represented by captioned arrows and operations performed by these elements represented by captioned blocks.
  • Each of the first network node 902 and the second network node 906 may be, e.g., a base station 502 or 506 or a network node that implements all or part of the functionality of the base station 502 or 506.
  • Operations in Figure 9 begin with the first network node 902 transmitting, to the UE 904, an RRCReconfiguration message 908 associated with an SN change or PSCell change, the RRCReconfiguration message 908 comprising an indication 910 indicating a node that initiated the SNChange or PSCell change, as indicated by arrow 912.
  • the first network node 902 receives, from the UE 904, information 904 regarding an SCG failure, as indicated by arrow 916.
  • the first network node 902 determines the second network node 906 based on the information 914 regarding the SCG failure, as indicated by block 918.
  • the first network node 902 transmits the information 914 regarding the SCG failure to the second network node, as indicated by arrow 920.
  • FIG. 10 is a schematic block diagram of a radio access node 1000 according to some embodiments of the present disclosure.
  • the radio access node 1000 may be, for example, a base station 502 or 506 or a network node that implements all or part of the functionality of the base station 502 or gNB described herein.
  • the radio access node 1000 includes a control system 1002 that includes one or more processors 1004 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 1006, and a network interface 1008.
  • the one or more processors 1004 are also referred to herein as processing circuitry.
  • the radio access node 1000 may include one or more radio units 1010 that each includes one or more transmitters 1012 and one or more receivers 1014 coupled to one or more antennas 1016.
  • the radio units 1010 may be referred to or be part of radio interface circuitry.
  • the radio unit(s) 1010 is external to the control system 1002 and connected to the control system 1002 via, e.g., a wired connection (e.g., an optical cable).
  • the radio unit(s) 1010 and potentially the antenna(s) 1016 are integrated together with the control system 1002.
  • the one or more processors 1004 operate to provide one or more functions of a radio access node 1000 as described herein.
  • the function(s) are implemented in software that is stored, e.g., in the memory 1006 and executed by the one or more processors 1004.
  • FIG 11 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node 1000 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes.
  • a "virtualized" radio access node is an implementation of the radio access node 1000 in which at least a portion of the functionality of the radio access node 1000 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)).
  • the radio access node 1000 may include the control system 1002 and/or the one or more radio units 1010, as described above.
  • the control system 1002 may be connected to the radio unit(s) 1010 via, for example, an optical cable or the like.
  • the radio access node 1000 includes one or more processing nodes 1100 coupled to or included as part of a network(s) 1102. If present, the control system 1002 or the radio unit(s) are connected to the processing node(s) 1100 via the network 1102.
  • Each processing node 1100 includes one or more processors 1104 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1106, and a network interface 1108.
  • functions 1110 of the radio access node 1000 described herein are implemented at the one or more processing nodes 1100 or distributed across the one or more processing nodes 1100 and the control system 1002 and/or the radio unit(s) 1010 in any desired manner.
  • some or all of the functions 1110 of the radio access node 1000 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environ ment(s) hosted by the processing node(s) 1100.
  • additional signaling or communication between the processing node(s) 1100 and the control system 1002 is used in order to carry out at least some of the desired functions 1110.
  • the control system 1002 may not be included, in which case the radio unit(s) 1010 communicate directly with the processing node(s) 1100 via an appropriate network interface(s).
  • a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node 1000 or a node (e.g., a processing node 1100) implementing one or more of the functions 1110 of the radio access node 1000 in a virtual environment according to any of the embodiments described herein is provided.
  • a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
  • Figure 12 is a schematic block diagram of the radio access node 1000 according to some other embodiments of the present disclosure.
  • the radio access node 1000 includes one or more modules 1200, each of which is implemented in software.
  • the module(s) 1200 provide the functionality of the radio access node 1000 described herein. This discussion is equally applicable to the processing node 1100 of Figure 11 where the modules 1200 may be implemented at one of the processing nodes 1100 or distributed across multiple processing nodes 1100 and/or distributed across the processing node(s) 1100 and the control system 1002.
  • FIG. 13 is a schematic block diagram of a wireless communication device 1300 according to some embodiments of the present disclosure.
  • the wireless communication device 1300 includes one or more processors 1302 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1304, and one or more transceivers 1306 each including one or more transmitters 1308 and one or more receivers 1310 coupled to one or more antennas 1312.
  • the transceiver(s) 1306 includes radio-front end circuitry connected to the antenna(s) 1312 that is configured to condition signals communicated between the antenna(s) 1312 and the processor(s) 1302, as will be appreciated by on of ordinary skill in the art.
  • the processors 1302 are also referred to herein as processing circuitry.
  • the transceivers 1306 are also referred to herein as radio circuitry.
  • the functionality of the wireless communication device 1300 described above may be fully or partially implemented in software that is, e.g., stored in the memory 1304 and executed by the processor(s) 1302.
  • the wireless communication device 1300 may include additional components not illustrated in Figure 13 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 1300 and/or allowing output of information from the wireless communication device 1300), a power supply (e.g., a battery and associated power circuitry), etc.
  • user interface components e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 1300 and/or allowing output of information from the wireless communication device 1300
  • a power supply e.g., a battery and associated power circuitry
  • a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 1300 according to any of the embodiments described herein is provided.
  • a carrier comprising the aforementioned computer program product is provided.
  • the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
  • FIG 14 is a schematic block diagram of the wireless communication device 1300 according to some other embodiments of the present disclosure.
  • the wireless communication device 1300 includes one or more modules 1400, each of which is implemented in software.
  • the module(s) 1400 provide the functionality of the wireless communication device 1300 described herein.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • Embodiment 1 A method performed by a User Equipment (UE) of a cellular communication system to provide reporting of Secondary Node (SN) change and Secondary Cell Group (SCG) failure, the method comprising: • receiving an indication associated with an SN change or Primary Serving Cell (PSCell) change, the indication indicating a node that initiated the SN change or PSCell change;
  • UE User Equipment
  • SCG Secondary Cell Group
  • Embodiment 2 The method of embodiment 1, further comprising transmitting, to the network node, an SCG Radio Link Failure (S-RLF) report containing information on an S-RLF event.
  • S-RLF SCG Radio Link Failure
  • Embodiment 3 The method of embodiment 1, wherein receiving the indication comprises receiving an RRCReconfiguration message comprising the indication.
  • Embodiment 4 The method of embodiment 1, wherein transmitting the indication of the node that initiated the SN change or PSCell change comprises:
  • Embodiment 5 A User Equipment (UE), comprising:
  • processing circuitry associated with the one or more transmitters and the one or more receivers, the processing circuitry configured to cause the UE to:
  • Embodiment 6 The UE of embodiment 5, wherein the processing circuitry is further configured to cause the UE to perform the method of any one of embodiments 2 to 4.
  • Embodiment 7 A method performed by a first network node of a cellular communication system to provide reporting of Secondary Node (SN) change and Secondary Cell Group (SCG) failure, the method comprising:
  • UE User Equipment
  • PSCell Primary Serving Cell
  • Embodiment 8 The method of embodiment 7, wherein the second network node comprises an SN for which the UE was configured when the SCG failure was detected.
  • Embodiment 9 The method of embodiment 7, wherein the second network node comprises an SN from which the UE successfully received an RRCReconfiguration message with a sync (HO) command whose execution failed.
  • the second network node comprises an SN from which the UE successfully received an RRCReconfiguration message with a sync (HO) command whose execution failed.
  • Embodiment 10 The method of embodiment 7, wherein the second network node comprises a Master Node (MN) for which the UE was configured when the SCG failure was detected.
  • MN Master Node
  • Embodiment 11 A network node for a core network of a cellular communications system where the network node is enabled to provide reporting of Secondary Node (SN) change and Secondary Cell Group (SCG) failure, the network node comprising:
  • processing circuitry associated with the network interface, the processing circuitry configured to cause the network node to:
  • the RRCReconfiguration message comprising a first indication indicating a node that initiated the SNChange or PSCell change;
  • Embodiment 12 The network node of embodiment 11, wherein the processing circuitry is further configured to cause the network node to perform the method of any one of embodiments 8 to 10.

Landscapes

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

Abstract

L'invention concerne des procédés et un appareil permettant de fournir un rapport de changement d'un nœud secondaire (SN) et de défaillance d'un groupe de cellules secondaires (SCG). Dans un mode de réalisation, un procédé mis en œuvre par un UE consiste à : recevoir une indication associée à un changement de SN ou un changement cellule de desserte primaire (PSCell) et indiquant un nœud qui a initié le changement de SN/PSCell ; déclarer une défaillance de SCG ; et transmettre, à un nœud de réseau, une indication du nœud qui a initié le changement de SN/PSCell. Dans un autre mode de réalisation, un procédé mis en œuvre par un premier nœud de réseau consiste à : transmettre, à un UE, un message RRCReconfiguration associé à un changement de SN ou un changement de PSCell et comprenant une indication indiquant un nœud qui a initié le changement de SN/PSCell ; recevoir, de l'UE, des informations concernant une défaillance de SCG ; déterminer un second nœud de réseau d'après les informations ; et transmettre les informations au second nœud de réseau.
PCT/SE2021/051056 2020-10-22 2021-10-21 Initiateur d'un rapport de changement d'un sn et de défaillance d'un scg lors de la suspension d'un mcg WO2022086421A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063104311P 2020-10-22 2020-10-22
US63/104,311 2020-10-22

Publications (1)

Publication Number Publication Date
WO2022086421A1 true WO2022086421A1 (fr) 2022-04-28

Family

ID=78463877

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2021/051056 WO2022086421A1 (fr) 2020-10-22 2021-10-21 Initiateur d'un rapport de changement d'un sn et de défaillance d'un scg lors de la suspension d'un mcg

Country Status (1)

Country Link
WO (1) WO2022086421A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024035304A1 (fr) * 2022-08-08 2024-02-15 Telefonaktiebolaget Lm Ericsson (Publ) Signalisation de réseau de rapport de pscell réussie
WO2024051375A1 (fr) * 2022-09-08 2024-03-14 中国电信股份有限公司 Procédé et appareil d'optimisation de changement de cellule primaire-secondaire, et dispositif, support et produit-programme
WO2024078974A1 (fr) * 2022-10-10 2024-04-18 Nokia Technologies Oy Accès conditionnel

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.331
3GPP TS 38.423
CHINA TELECOM: "Support on MRO for SN Change Failure", vol. RAN WG3, no. Online; 20200817 - 20200828, 6 August 2020 (2020-08-06), XP051911286, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_109-e/Docs/R3-204896.zip R3-204896 Discussion on SN Change Failure-CT.doc> [retrieved on 20200806] *
NOKIA ET AL: "C122, C123, C124 and C150 - TPs for inter-RAT handover via SRB3 upon MCG failure recovery", vol. RAN WG2, no. Elbonia; 20200601 - 20200611, 21 May 2020 (2020-05-21), XP051887465, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_110-e/Docs/R2-2004838.zip R2-2004838 C122, C123, C124 and C150 - TPs for inter-RAT handover via SRB3 upon MCG failure recovery.docx> [retrieved on 20200521] *
ZTE CORPORATION ET AL: "Further issues on MCG fast recovery", vol. RAN WG2, no. Online; 20200224 - 20200306, 14 February 2020 (2020-02-14), XP051849576, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_109_e/Docs/R2-2001266.zip R2-2001266 Further issues on MCG fast recovery.docx> [retrieved on 20200214] *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024035304A1 (fr) * 2022-08-08 2024-02-15 Telefonaktiebolaget Lm Ericsson (Publ) Signalisation de réseau de rapport de pscell réussie
WO2024051375A1 (fr) * 2022-09-08 2024-03-14 中国电信股份有限公司 Procédé et appareil d'optimisation de changement de cellule primaire-secondaire, et dispositif, support et produit-programme
WO2024078974A1 (fr) * 2022-10-10 2024-04-18 Nokia Technologies Oy Accès conditionnel

Similar Documents

Publication Publication Date Title
JP7189126B2 (ja) 無線通信システムにおけるサービス要求手順の実行方法とそのための装置
JP2020123992A (ja) 無線通信システムにおけるネットワーク間の相互連動方法及びそのための装置
KR102048046B1 (ko) 무선 통신 시스템에서 ladn 이용 방법 및 이를 위한 장치
JP2020506620A (ja) 要求に対する応答方法及びネットワーク装置
US10681637B2 (en) Method and apparatus for transmitting and receiving data, by terminal, in wireless communication system
US20200120561A1 (en) 5GSM Handling on Invalid PDU Session
US10805938B2 (en) Data transmission/reception method and apparatus for terminal in wireless communication system
WO2022086421A1 (fr) Initiateur d&#39;un rapport de changement d&#39;un sn et de défaillance d&#39;un scg lors de la suspension d&#39;un mcg
EP3410814B1 (fr) Procédé de déclenchement de mise à jour de zone de suivi et équipement d&#39;utilisateur
US20220286881A1 (en) Recovery over sidelink
US20240064863A1 (en) Ue controlled pdu sessions on a network slice
US20210345434A1 (en) Method for Handling a Mobility Management State Transition After Fallback to RRC Establishment
EP4176688A1 (fr) Distribution de rapport de mesure de qoe dans une architecture ran divisée
US20170111879A1 (en) Resource control for wireless device detach
WO2021037583A1 (fr) Gestion de rlf en liaison latérale
US20240080787A1 (en) Redirection and retry of registration
US20230403623A1 (en) Managing sidelink information, configuration, and communication
US20220124869A1 (en) Emergency calls with service request triggered fallback
KR20230092912A (ko) Mr-dc 시나리오에서의 scg 비활성화 메커니즘 및 scg 활성화 메커니즘을 위한 방법들 및 장치들
WO2020254968A1 (fr) Systèmes et procédés se rapportant à une suspension de connexion initiée par un réseau et à une libération initiale de rrc
US20240073990A1 (en) Systems and methods for ue context retrieval and data forwarding to support small data transmission
US20220287126A1 (en) Sidelink transmission continuity
US20230300607A1 (en) Handling ue parameters update data set types which may be unsupported in ue parameters update via udm control plane procedure
US20230133792A1 (en) Handling of collision between pdu session establishment and modification procedure
US20240023182A1 (en) Handling the unknown rrc establishment cause value in nr

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21801253

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21801253

Country of ref document: EP

Kind code of ref document: A1