Patent Application
20240215095
Exemplary embodiments herein relate generally to wireless communication systems and, more specifically, relates to mobility robustness optimization (MRO) analysis.
In a wireless network such as a cellular network, there is a mechanism referred to as a Minimization of Driving Test (MDT). This mechanism allows User Equipment (UE, a wireless, typically mobile, device) to make certain reports to the cellular network, for use by the cellular network for capacity, coverage, and/or mobility optimization, along with, e.g., quality of service (QOS) verification. These can be important inputs for networks that are Self-Organizing Networks (SON), which can use this information for reconfiguration or other tasks.
In case of Multi-RAT Dual Connectivity (MR-DC, where RAT is radio access technology), a Master Node (MN) functions as the controlling entity that provides control plane connection to the core network, and utilizes an SN (secondary node) for additional resources to the UE. The MN and SN may be two different gNBs (5G, fifth generation, base stations). A Secondary Cell Group (SCG) refers to a group of serving cells associated with the SN, and comprises a Primary Secondary Cell (PSCell), which is the primary cell of the SCG. When a user-equipment (UE) detects a radio failure in the PSCell (i.e., an SCG failure), the UE transmits an SCG Failure Information message to the MN, including the SCG failure type and potential measurement reports that are configured by the MN and/or SN. This report is then used for Mobility Robustness Optimization (MRO) (e.g., with configuration changes to be made in corresponding nodes), among other use cases, e.g., failure detection and recovery.
Coordination of this information for analysis, including MRO analysis, could be improved.
This section is intended to include examples and is not intended to be limiting.
In an exemplary embodiment, a method is disclosed that includes, in a master node in wireless communication with a user equipment and in communication with one or more secondary nodes, after receiving an indication from the user equipment that a secondary cell group failure has occurred, determining by the master node which node of at least the master node or a last serving secondary node or another secondary node is responsible for the secondary cell group failure. The method includes, based on outcome of the determining, performing by the master node an analysis for mobility robustness for the secondary cell group failure where the master node was responsible for the secondary cell group failure.
An additional exemplary embodiment includes a computer program, comprising code for performing the method of the previous paragraph, when the computer program is run on a processor. The computer program according to this paragraph, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer. Another example is the computer program according to this paragraph, wherein the program is directly loadable into an internal memory of the computer.
An exemplary apparatus includes one or more processors and one or more memories including computer program code. The one or more memories and the computer program code are configured to, with the one or more processors, cause the apparatus at least to: in a master node in wireless communication with a user equipment and in communication with one or more secondary nodes, after receiving an indication from the user equipment that a secondary cell group failure has occurred, determine by the master node which node of at least the master node or a last serving secondary node or another secondary node is responsible for the secondary cell group failure; and based on outcome of the determining, perform by the master node an analysis for mobility robustness for the secondary cell group failure where the master node was responsible for the secondary cell group failure.
An exemplary computer program product includes a computer-readable storage medium bearing computer program code embodied therein for use with a computer. The computer program code includes: code for, in a master node in wireless communication with a user equipment and in communication with one or more secondary nodes, after receiving an indication from the user equipment that a secondary cell group failure has occurred, determining by the master node which node of at least the master node or a last serving secondary node or another secondary node is responsible for the secondary cell group failure; and code for based on outcome of the determining, performing by the master node an analysis for mobility robustness for the secondary cell group failure where the master node was responsible for the secondary cell group failure.
In another exemplary embodiment, an apparatus comprises means for performing: in a master node in wireless communication with a user equipment and in communication with one or more secondary nodes, after receiving an indication from the user equipment that a secondary cell group failure has occurred, determining by the master node which node of at least the master node or a last serving secondary node or another secondary node is responsible for the secondary cell group failure; and based on outcome of the determining, performing by the master node an analysis for mobility robustness for the secondary cell group failure where the master node was responsible for the secondary cell group failure.
In an exemplary embodiment, a method is disclosed that includes in a secondary node, of a secondary cell group, in wireless communication with a user equipment and in communication with a master node, determining whether or not the secondary node is responsible for a secondary cell group failure. The method also includes, in response to receiving from the master node a message corresponding to the secondary cell group failure, indicating to the master node by the secondary node whether or not the secondary node is responsible for the secondary cell group failure.
An additional exemplary embodiment includes a computer program, comprising code for performing the method of the previous paragraph, when the computer program is run on a processor. The computer program according to this paragraph, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer. Another example is the computer program according to this paragraph, wherein the program is directly loadable into an internal memory of the computer.
An exemplary apparatus includes one or more processors and one or more memories including computer program code. The one or more memories and the computer program code are configured to, with the one or more processors, cause the apparatus at least to: in a secondary node, of a secondary cell group, in wireless communication with a user equipment and in communication with a master node, determine whether or not the secondary node is responsible for a secondary cell group failure; and in response to receiving from the master node a message corresponding to the secondary cell group failure, indicate to the master node by the secondary node whether or not the secondary node is responsible for the secondary cell group failure.
An exemplary computer program product includes a computer-readable storage medium bearing computer program code embodied therein for use with a computer. The computer program code includes: code for, in a secondary node, of a secondary cell group, in wireless communication with a user equipment and in communication with a master node, determining whether or not the secondary node is responsible for a secondary cell group failure; and code for, in response to receiving from the master node a message corresponding to the secondary cell group failure, indicating to the master node by the secondary node whether or not the secondary node is responsible for the secondary cell group failure.
In another exemplary embodiment, an apparatus comprises means for performing: in a secondary node, of a secondary cell group, in wireless communication with a user equipment and in communication with a master node, determining whether or not the secondary node is responsible for a secondary cell group failure; and in response to receiving from the master node a message corresponding to the secondary cell group failure, indicating to the master node by the secondary node whether or not the secondary node is responsible for the secondary cell group failure.
In the attached Drawing Figures:
Abbreviations that may be found in the specification and/or the drawing figures are defined below, at the end of the detailed description section.
The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. All of the embodiments described in this Detailed Description are exemplary embodiments provided to enable persons skilled in the art to make or use the invention and not to limit the scope of the invention which is defined by the claims.
When more than one drawing reference numeral, word, or acronym is used within this description with “/”, and in general as used within this description, the “/” may be interpreted as “or”, “and”, or “both”.
The exemplary embodiments herein describe techniques for coordinating MRO analysis for PSCell change failure. Additional description of these techniques is presented after a system into which the exemplary embodiments may be used is described.
Turning to
The UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected through one or more buses 127. Each of the one or more transceivers 130 includes a receiver, Rx, 132 and a transmitter, Tx, 133. The one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. The UE 110 includes a control module 140, comprising one of or both parts 140-1 and/or 140-2, which may be implemented in a number of ways. The control module 140 may be implemented in hardware as control module 140-1, such as being implemented as part of the one or more processors 120. The control module 140-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the control module 140 may be implemented as control module 140-2, which is implemented as computer program code 123 and is executed by the one or more processors 120. For instance, the one or more memories 125 and the computer program code 123 may be configured to, with the one or more processors 120, cause the user equipment 110 to perform one or more of the operations as described herein. The UE 110 communicates with RAN node 170 via a wireless link 111 and with RAN node 170-1 via wireless link 111-1.
The RAN nodes 170, 170-1 are base stations that provides access by wireless devices such as the UE 110 to the wireless network 100. In the examples below, the RAN node 170 is assumed to be a Master Node (MN), and the RAN node 170-1 is assumed to be a Secondary Node (SN). The RAN node 170-1 is assumed to be SN #1, and there are or may be other SNs, which are not illustrated. The RAN nodes 170, 170-1 are assumed to be similar, so the internal configuration of only RAN node 170 is described. Additionally, both may be referred to as gNBs, though as described below, this is only one possibility.
The RAN node 170 may be, for instance, a base station for 5G, also called New Radio (NR). In 5G, the RAN node 170 may be a NG-RAN node, which is defined as either a gNB or an ng-eNB. A gNB is a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to a 5GC (e.g., the network element(s) 190). The ng-eNB is a node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. The NG-RAN node may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) 196 and distributed unit(s) (DUs) (gNB-DUs), of which DU 195 is shown. Note that the DU may include or be coupled to and control a radio unit (RU). The gNB-CU is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected with the gNB-DU. The F1 interface is illustrated as reference 198, although reference 198 also illustrates a link between remote elements of the RAN node 170 and centralized elements of the RAN node 170, such as between the gNB-CU 196 and the gNB-DU 195. The gNB-DU is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU. One gNB-CU supports one or multiple cells. One cell is supported by one gNB-DU. The gNB-DU terminates the F1 interface 198 connected with the gNB-CU. Note that the DU 195 is considered to include the transceiver 160, e.g., as part of an RU, but some examples of this may have the transceiver 160 as part of a separate RU, e.g., under control of and connected to the DU 195. The RAN node 170 may also be an eNB (evolved NodeB) base station, for LTE (long term evolution), or any other suitable base station.
The RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N/W I/F(s)) 161, and one or more transceivers 160 interconnected through one or more buses 157. Each of the one or more transceivers 160 includes a receiver, Rx, 162 and a transmitter, Tx, 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. The CU 196 may include the processor(s) 152, memories 155, and network interfaces 161. Note that the DU 195 may also contain its own memory/memories and processor(s), and/or other hardware, but these are not shown.
The RAN node 170 includes a control module 150, comprising one of or both parts 150-1 and/or 150-2, which may be implemented in a number of ways. The control module 150 may be implemented in hardware as control module 150-1, such as being implemented as part of the one or more processors 152. The control module 150-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the control module 150 may be implemented as control module 150-2, which is implemented as computer program code 153 and is executed by the one or more processors 152. For instance, the one or more memories 155 and the computer program code 153 are configured to, with the one or more processors 152, cause the RAN node 170 to perform one or more of the operations as described herein. Note that the functionality of the control module 150 may be distributed, such as being distributed between the DU 195 and the CU 196, or be implemented solely in the DU 195.
The one or more network interfaces 161 communicate over a network such as via the links 176 and 131. Two or more RAN nodes 170, 170-1 (and possibly other RAN nodes) communicate using, e.g., link 176. The link 176 may be wired or wireless or both and may implement, e.g., an Xn interface for 5G, an X2 interface for LTE, or other suitable interface for other standards.
The one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like. For example, the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for gNB implementation for 5G, with the other elements of the RAN node 170 possibly being physically in a different location from the RRH/DU, and the one or more buses 157 could be implemented in part as, e.g., fiber optic cable or other suitable network connection to connect the other elements (e.g., a central unit, gNB-CU) of the RAN node 170 to the RRH/DU 195. Reference 198 also indicates those suitable network link(s).
It is noted that description herein indicates that “cells” perform functions, but it should be clear that the base station that forms the cell will perform the functions. The cell makes up part of a base station. That is, there can be multiple cells per base station. For instance, there could be three cells for a single carrier frequency and associated bandwidth, each cell covering one-third of a 360-degree area so that the single base station's coverage area covers an approximate oval or circle. Furthermore, each cell can correspond to a single carrier and a base station may use multiple carriers. So, if there are three 120-degree cells per carrier and two carriers, then the base station has a total of six cells.
The wireless network 100 may include a network element or elements 190 that may include core network functionality, and which provides connectivity via a link or links 181 with a data network 191, such as a telephone network and/or a data communications network (e.g., the Internet). Such core network functionality for 5G may include access and mobility management function(s) (AMF(s)) and/or user plane functions (UPF(s)) and/or session management function(s) (SMF(s)). Such core network functionality for LTE may include MME (Mobility Management Entity)/SGW (Serving Gateway) functionality. These are merely exemplary functions that may be supported by the network element(s) 190, and note that both 5G and LTE functions might be supported. The RAN nodes 170, 170-1 are coupled via a link 131 to a network element 190. The link 131 may be implemented as, e.g., an NG interface for 5G, or an S1 interface for LTE, or other suitable interface for other standards. The network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N/W I/F(s)) 180, interconnected through one or more buses 185. The one or more memories 171 include computer program code 173. The one or more memories 171 and the computer program code 173 are configured to, with the one or more processors 175, cause the network element 190 to perform one or more operations.
The wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as either external, combining many networks, or parts of networks, into a virtual unit, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors 152 or 175 and memories 155 and 171, and also such virtualized entities create technical effects.
The computer readable memories 125, 155, and 171 may be of any type suitable to the local technical environment and may 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. The computer readable memories 125, 155, and 171 may be means for performing storage functions. The processors 120, 152, and 175 may be of any type suitable to the local technical environment, and may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples. The processors 120, 152, and 175 may be means for performing functions, such as controlling the UE 110, RAN nodes 170 and 170-1, and other functions as described herein.
In general, the various embodiments of the user equipment 110 can include, but are not limited to, cellular telephones such as smart phones, tablets, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, vehicles with a modem device for wireless V2X (vehicle-to-everything) communication, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances (including Internet of Things, IOT, devices) permitting wireless Internet access and possibly browsing. IoT devices with sensors and/or actuators for automation applications with wireless communication tablets with wireless communication capabilities, as well as portable units or terminals that incorporate combinations of such functions.
Having thus introduced one suitable but non-limiting technical context for the practice of the exemplary embodiments, the exemplary embodiments will now be described with greater specificity.
The development of SON/MDT is to include the support of data collection for SON features, involving coverage and capacity optimization, inter-system/inter-RAT energy saving, inter-system load balancing, 2-step RACH optimization, mobility enhancement optimization, PCI selection, successful handover reports, UE history information in EN-DC, load balancing enhancement, RACH optimization and mobility robustness optimization (MRO) for secondary node (SN) change failure. The inter-node information exchange of the aforementioned procedures, including possible enhancements to S1/NG, X2/Xn, and F1/E1 interfaces, may need to be specified.
Discussions on MRO for SN change failure have been held in 3GPP, and several agreements were made. The following relevant agreements were made in RAN3 #109-e meeting (sec R3-205900, “Agenda”, 3GPP TSG RAN3 meeting #110-c, 2-12 November, 2020):
As the last item above indicates, Rel-17 UEs may report an SCG failure information message that can include more elements than what is already in the report, in order for the MN to be able to identify if the last PSCell change was initiated by itself or an SN, and which SN it was that initiated. However, additional mechanisms are needed for the support of MRO for pre-Rel-17 UEs that would still send the conventional SCG failure information message in case of an SCG failure.
Furthermore, it has been also agreed that the MN performs initial analysis to identify the node that caused the failure. The node that caused the failure performs root cause analysis.
Based on the agreements provided above, the MN can forward the SCG failure information to the serving SN, or the SN initiating the last PSCell change, for the SN to make configuration changes (i.e., MRO), after an initial analysis to identify the node that caused the failure. On the other hand, the MN may directly use the SCG failure information and make its own configuration changes, in case for example the MN thinks that the MN is responsible for the SCG mobility and the SCG failure. More specifically, in case the MN finds out, after an initial MRO analysis after receiving the SCG failure information from the UE, that this is a “too early PSCell change” failure, or a “PSCell change failure to wrong PSCell”, and the SN is responsible for the PSCell change that caused the failure, then the MN forwards the SCG failure information to the source SN (not to the serving SN). On the other hand, in case the MN thinks that this is a “too late PSCell change” failure caused by the SN, then the MN forwards the SCG failure information to the serving SN.
Moreover, both MN and SN can be responsible for SCG mobility, and this responsibility is not officially reflected in the current specifications. In addition, the SN can change the PSCell of the UE without notifying the MN (e.g., an intra-SN PSCell change without MN involvement) using the dedicated signaling radio bearer between the SN and the UE (SRB3), in case of EN-DC, NG EN-DC and NR-DC. In that case, the MN is not aware of the PSCell change, although the MN still knows the correct SN to which the UE is connected. If the UE location is being tracked, however, intra-SN PSCell changes initiated by the SN are also reported to the MN by the SN. Intra-SN PSCell change without MN involvement is introduced in order to preserve SN autonomy, and the procedure aims to have a lowest amount of signaling towards the MN as is possible.
A focus is placed herein on the error in the understanding of the MN that occurs in case of intra-SN PSCell change without MN involvement, where the UE location tracking is disabled for the UE, which would eventually cause MRO problems.
In more detail, as described previously, the concept of intra-SN PSCell change without MN involvement was introduced to let the SN make autonomous decisions on the PSCell of the UE without any MN interaction, and avoid unnecessary signaling towards the MN. In case the location of the UE is being tracked by the MN, e.g., for lawful interception purposes, which is optional and applied only to selected UEs, then the SN notifies the MN in case of intra-SN PSCell change failure, but does so only after the PSCell is changed (to avoid any delay of the change).
Consider a scenario where the MN initiates a PSCell change for a UE that is successfully completed (inter-SN or intra-SN), or where the SN initiates an inter-SN PSCell change. In both cases, the MN would be aware of the change, since the MN is involved in those procedures. After a while, the serving SN may initiate independently another intra-SN PSCell change via, e.g., SRB3 without MN involvement. This may occur, even if it is assumed that only one of the nodes should be responsible for SCG mobility, because measurement-based mobility may not be the only trigger for PSCell changes. For example, if one layer (in this scenario, the SN) is responsible for “normal” mobility, the other layer (MN here) may decide to execute load-based or service-based SN change.
After the UE connects to the PSCell that is indicated by the SN, this PSCell may fail soon after the change. Based on the measurements reported from the UE, this scenario would conventionally be identified as a “PSCell change failure to wrong cell”, “too early PSCell change failure” or a “too late PSCell change failure” that is caused by the SN, and the SN would make its own configuration changes for MRO purposes.
However, since the MN is not aware of the intra-SN PSCell change initiated by the SN, upon reception of the SCG failure information sent by the UE, the MN would assume the failure is related to the PSCell change triggered by the MN itself, and would not forward the SCG failure information to the SN based on the current agreements described above. Even if the MN forwards the message to the SN for purposes other than MRO, the MN would make its own configuration changes for MRO, as the MN would think that the SCG failure was caused by itself. On top of that, the SN would also make own configuration changes for MRO. One of the two corrective actions are not necessary and may thus worsen the performance instead of improving the performance (also, the statistics, if collected, would be badly impacted). Thus, the current mechanisms are not sufficient for successful MRO operation under the given scenario.
In block 210, the UE is connected to the PSCell #1 206-1 of SN #x 170-x. In signaling 215, the MN 170 may send a PSCell change command, to cause the UE 110 to transition to PSCell #2 205-2 of SN #1 170-1. It is noted that this assumes the MN 170 performs an inter-node cell change, i.e., from PSCell #1 206-1 of SN #x to PSCell #2 205-2 of SN #1. However, it may also be possible for the MN 170 to perform an intra-node cell change, such as where the UE 110 is initially connected to PSCell #1 205-1 and the MN sends a cell change command to have the UE change from PSCell #1 205-1 to PSCell #205-2 in the SN #1. In block 220, the UE 110 is connected to the PSCell #2 205-2 of SN #1 170-1. As indicated by reference 225, the MN 170 may start a timer, such as T_SN_change. This timer may be started by the MN in response to the UE completing a PSCell change. This may be used to make an “initial analysis” on the MRO issue, and the value may be used to determine the cause of the failure. The dashed line 227 indicates the completion of the PSCell change initiated by the MN.
In signaling 230, the SN #1 170-1 may send a PSCell change command to UE 110, and this sending is performed without MN 170 involvement (such as for example via SRB 3 or other signaling). The SN can change the PSCell based on different reasons, such as load balancing, measurements, and the like. The UE 110 in block 235 is connected to the PSCell #1 205-1 of SN #1 170-1.
The UE 110 in reference 240 may determine there was an SCG failure and, in response, may send signaling 245 with indication of the SCG failure information to the MN 170. Block 250 indicates that the MN, in response to receiving the signaling 245, may still think the UE was connected to the PSCell #2 205-2 of SN #1 170-1.
Hence, one exemplary objective of the exemplary embodiments is to provide mechanisms to successfully perform MRO for SN change failure in case of a PSCell change without an MN involvement, which causes an SCG failure.
As an overview, it is proposed that, after an SCG failure is detected by the MN 170, the serving SN 170-1 may provide information to the MN 170 about a possible PSCell change that might have been initiated by the serving SN after the previous MN-initiated SN change (or a previous inter-SN PSCell change that was initiated by another SN). The information from the serving SN is assumed to be sent after an initiation by the MN by sending the information about PSCell change failure. The SN may respond to MN's information with a confirmation or denial that the SN is related to the SN-internal PSCell change, or may send a message in case the SN takes over the MRO handling.
As one example, the MN may select one of multiple options for performing an analysis for mobility robustness for a secondary cell group failure:
Two example implementation options are proposed for this coordination between the MN, last serving SN, and/or another SN.
The first option, Option 1, is described in reference to
In
The following are numbered notes about this first option and its process.
1. The MN 170 may forward the SCG failure information received (in signaling 245) from the UE to the serving SN, even in case the MN thinks the MN itself is responsible for the PSCell change failure.
2. The forwarded SCG failure information from the MN to the serving SN may be replied by the SN (see, e.g., signaling 330).
i. The reply message may indicate whether the SN has recently initiated a PSCell change without MN involvement, and possibly the serving PSCell ID in case the SN has initiated a recent PSCell change.
a) In another aspect, the SN 170-1 may only indicate the serving PSCell ID. The MN 170 can then compare this information with its own understanding of serving PSCell to decide on further steps. This would further decrease the size of the message from the SN to the MN.
3. Based on the information obtained from the serving SN with the message in signaling from the SN, the MN may additionally forward the SCG failure information to a source SN that had initiated the last inter-SN PSCell change (that is, a PSCell change from the source SN to the current serving SN), or the MN may make its own configuration changes for MRO purposes. See
A second option, Option 2, is described in reference to
In
The following are numbered notes about this second option and its process.
1. Upon reception (in signaling 245) of the SCG failure information from the UE, the MN 170 may send a message (see signaling 410) to the serving SN 170-1, asking whether the SN has recently initiated an intra-SN PSCell change or not.
a. The size of the message can be much smaller than the size of SCG failure information (even ˜1-bit).
2. The SN 170-1 may reply to the MN 170. The response may include an indication of a recently initiated PSCell change (or an indication of a no such change, see
3. Based on a positive reply from the SN 170-1 regarding a recent PSCell change and possibly the failed PSCell ID, SCG failure information can be forwarded to the serving SN 170-1 by the MN 170. This is illustrated by signaling 420.
4. If the MN receives a negative reply, which indicates that the serving SN has not initiated an intra-SN PSCell change, the MN 170 can follow conventional MRO procedures. See also
Further comments and details on these procedures are provided below.
Regarding Option 1—Note 1: In case the MN 170 determines (upon an initial MRO analysis) that the MN itself is the initiator of the last PSCell change, conventionally, the MN 170 would not send the SCG failure information received from the UE (in signaling 245) upon PSCell failure to the serving SN for MRO, based on the latest agreements described above. Instead, the MN would make its own configuration changes for MRO purposes. Furthermore, in case the MN determines that the initiator of the last PSCell change is a source SN other than the serving SN (upon an initial MRO analysis), based on agreements provided above, the MN would forward the SCG failure information to the source SN. What is proposed herein, by contrast, is that the MN forwards SCG failure information initially to the serving SN for MRO purposes, at least for Option 1.
Regarding Option 1—Note 2: If upon note 2-i-a the MN finds out that the last serving PSCell of the UE is different than what MN thinks as the last serving PSCell, then the MN would conclude that a PSCell change without MN involvement had been performed, which caused current PSCell change failure. If that is the case, the MN neither makes its own MRO re-configurations, nor forwards the SCG failure information to a source SN, as the serving SN would perform MRO root cause analysis.
If the MN finds out that the serving SN had not initiated an additional PSCell change without MN involvement, then the MN would perform MRO root cause analysis, and make its own configurations, in case the MN has initiated the last PSCell change. Refer to
Regarding Option 2—Note 4: Refer to
Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect and advantage of one or more of the example embodiments disclosed herein is that a possible misunderstanding of an MN on the initiator of the last PSCell change for a UE would be mitigated, paving the way to successful MRO for SN change failure.
The following are additional examples.
Example 1. A method, comprising:
Example 2. The method of example 1, wherein determining which node is responsible for the secondary cell group failure further comprises determining by the master node the last serving secondary node is the node responsible for the secondary cell group failure, based on communication with the last serving secondary node indicating the last serving secondary node was involved in an intra-node cell change that was not indicated to the master node.
Example 3. The method of example 2, further comprising:
Example 4. The method of example 2, further comprising:
Example 5. The method of one of examples 2 to 4, wherein the analysis by the master node for mobility robustness for the secondary cell group failure determines the secondary node is to perform an analysis for mobility robustness for the secondary cell group failure.
Example 6. The method of example 1, wherein determining which node is responsible for the secondary cell group failure further comprises determining by the master node the last serving secondary node is not the node responsible for the secondary cell group failure, based on communication with the secondary node indicating the last serving secondary node was not involved in an intra-node cell change that was not indicated to the master node.
Example 7. The method of example 6,
Example 8. The method of example 6, further comprising:
Example 9. The method of example 7 or 8, wherein determining by the master node which node of at least the master node or the last serving secondary node or another secondary node is responsible for the secondary cell group failure further comprises determining by the master node the other secondary node is responsible for the secondary cell group failure and sending by the master node failure information for the secondary cell group failure toward the other secondary node.
Example 10. A method, comprising:
Example 11. The method of example 10, wherein the indicating by the secondary node whether or not the secondary node sent the command for the intra-node cell change without notifying the master node further comprises performing by the secondary node communication with the master node indicating the secondary node was involved in the intra-node cell change that was not indicated to the master node.
Example 12. The method of example 11,
Example 13. The method of example 11,
Example 14. The method of example 10, wherein the indicating by the secondary node whether or not the secondary node sent the command for the intra-node cell change without notifying the master node further comprises performing communication by the secondary node with the master node indicating the secondary node was not involved in the intra-node cell change that was not indicated to the master node.
Example 15. The method of example 14,
Example 16. The method of example 14,
Example 17. A computer program, comprising code for performing the methods of any of examples 1 to 16, when the computer program is run on a computer.
Example 18. The computer program according to example 17, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with the computer.
Example 19. The computer program according to example 17, wherein the computer program is directly loadable into an internal memory of the computer.
Example 20. An apparatus, comprising means for performing:
Example 21. The apparatus of example 20, wherein determining which node is responsible for the secondary cell group failure further comprises determining by the master node the last serving secondary node is the node responsible for the secondary cell group failure, based on communication with the last serving secondary node indicating the last serving secondary node was involved in an intra-node cell change that was not indicated to the master node.
Example 22. The apparatus of example 21, wherein the means are further configured for performing:
Example 23. The apparatus of example 21, wherein the means are further configured for performing:
Example 24. The apparatus of one of examples 21 to 23, wherein the analysis by the master node for mobility robustness for the secondary cell group failure determines the secondary node is to perform an analysis for mobility robustness for the secondary cell group failure.
Example 25. The apparatus of example 20, wherein determining which node is responsible for the secondary cell group failure further comprises determining by the master node the last serving secondary node is not the node responsible for the secondary cell group failure, based on communication with the secondary node indicating the last serving secondary node was not involved in an intra-node cell change that was not indicated to the master node.
Example 26. The apparatus of example 25,
Example 27. The apparatus of example 25, wherein the means are further configured for performing:
Example 28. The apparatus of example 26 or 27, wherein determining by the master node which node of at least the master node or the last serving secondary node or another secondary node is responsible for the secondary cell group failure further comprises determining by the master node the other secondary node is responsible for the secondary cell group failure and sending by the master node failure information for the secondary cell group failure toward the other secondary node.
Example 29. An apparatus, comprising means for performing:
Example 30. The apparatus of example 29, wherein the indicating by the secondary node whether or not the secondary node sent the command for the intra-node cell change without notifying the master node further comprises performing by the secondary node communication with the master node indicating the secondary node was involved in the intra-node cell change that was not indicated to the master node.
Example 31. The apparatus of example 30,
Example 32. The apparatus of example 30,
Example 33. The apparatus of example 29, wherein the indicating by the secondary node whether or not the secondary node sent the command for the intra-node cell change without notifying the master node further comprises performing communication by the secondary node with the master node indicating the secondary node was not involved in the intra-node cell change that was not indicated to the master node.
Example 34. The apparatus of example 33,
Example 35. The apparatus of example 33,
Example 36. The apparatus of any preceding apparatus example, wherein the means comprises:
Example 37. An apparatus, comprising:
Example 38. A computer program product comprising a computer-readable storage medium bearing computer program code embodied therein for use with a computer, the computer program code comprising:
Example 39. An apparatus, comprising:
Example 40. A computer program product comprising a computer-readable storage medium bearing computer program code embodied therein for use with a computer, the computer program code comprising:
As used in this application, the term “circuitry” may refer to one or more or all of the following:
This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
Embodiments herein may be implemented in software (executed by one or more processors), hardware (e.g., an application specific integrated circuit), or a combination of software and hardware. In an example embodiment, the software (e.g., application logic, an instruction set) is maintained on any one of various conventional computer-readable media. In the context of this document, a “computer-readable medium” may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer, with one example of a computer described and depicted, e.g., in
If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined.
Although various aspects are set out above, other aspects comprise other combinations of features from the described embodiments, and not solely the combinations described above.
It is also noted herein that while the above describes example embodiments of the invention, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention.
The following abbreviations that may be found in the specification and/or the drawing figures are defined as follows:
3GPP third generation partnership project
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/IB2022/054174 | 5/5/2022 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63184974 | May 2021 | US |
