PSCELL Change or Addition Success Report

Abstract

The method, performed by a UE (User Equipment), includes receiving a success report configuration including conditions for a PSCell (Primary Secondary Cell Group Cell) success report, and, during a PSCell modification procedure, storing information in the PSCell success report indicating which of a plurality of network nodes initiated the PSCell modification procedure based on satisfying the conditions defined by the PSCell success report configuration.

Description

[Technical Field]

[0001] FIELD OF THE DISCLOSURE The present disclosure relates generally to communications, and more particularly to communication methods and associated devices and nodes supporting wireless communications. [Background technology]

[0002] Multi-Radio Dual Connectivity (MR-DC) is a technology in which a multi-Rx / Tx capable UE can be configured to utilize resources provided by two different nodes connected via a non-ideal backhaul. One node acts as a Master Node (MN) and another node acts as a Secondary Node (SN). The MN and SN are connected via a network interface, with at least the MN being connected to the core network. A detailed architectural description of MR-DC can be found in TS 37.340 [1].

[0003] trout Tano The group of serving cells associated with a node is called a mass Tase A master cell group includes a primary cell (PCell) and, optionally, one or more secondary cells (SCells).

[0004] A group of serving cells associated with a secondary node is called a secondary cell group, and the secondary cell group may include a primary secondary cell (PSCell) and optionally one or more SCells. The PCell and PSCell are collectively referred to as SpCells.

[0005] A conditional PSCell change (CPC) is defined as a PSCell change performed by the UE when the execution condition(s) for the PSCell change are met. The UE starts evaluating the execution condition(s) when it receives a CPC configuration and stops evaluating the execution condition(s) when a PSCell change is triggered. Intra-SN CPC without MN involvement and inter-SN CPC initiated by either the MN or the SN are supported.

[0006] Similarly, conditional PSCell addition (CPA) is supported to be initiated by the MN only.

[0007] The Successful handover report (SHR) has been standardized as part of 3GPP Release 17 TS (see, for example, RRC Specification 38.331 (V17.0.0)). The main purpose of the Successful Handover (HO) report is to enable network nodes to estimate the suboptimal performance of the lower procedures executed during the HO procedure.

[0008] A network node interested in SHR may configure the user equipment (UE) to report SHR after a successful HO execution if at least one of the SHR trigger conditions / thresholds is met. The SHR trigger thresholds are defined as follows:

[0009] Whether the T304 timer value exceeded a certain threshold when HO execution was successful (thresholdPercentageT304)

[0010] Whether the T310 timer value exceeds a certain threshold when HO execution is successful (thresholdPercentageT310)

[0011] Whether the T312 timer value exceeds a certain threshold when HO execution is successful (thresholdPercentageT312)

[0012] Whether the UE experienced a radio link failure (RLF) at the source node while performing a dual active protocol stack (DAPS) HO (sourceDAPS-FailureReporting).

[0013] When saving the handover success report, the UE may include various information to assist the network in optimizing the handover, such as measurements of neighboring cells, the conditions met that triggered the handover success report (e.g., the threshold when T310 was exceeded, specific RLF issues at the source while performing DAPS HO), etc.

[0014] The SHR may be configured by a serving cell, and the UE stores this information until the network (NW) requests it when the trigger condition for SHR logging is met. In particular, the UE may indicate the availability of SHR information in specific Radio Resource Control (RRC) messages such as RRCReconfigurationComplete, RRCReestablishmentComplete, RRCSetupComplete, and RRCResumeComplete, and the network may request such information via a UEInformationRequest message, in response to which the UE sends the stored SHR in a UEInformationResponse message.

[0015] Upon receiving the Successful HO Report, the receiving node can analyze whether its mobility configuration requires adjustment. Such adjustment may result in a change to the mobility configuration, such as a change to the radio link monitoring (RLM) settings or a change to the mobility threshold between the source and target. Additionally, the target NG RAN node may further optimize the individual random access channel (RACH) beam resources during the performed handover based on the beam measurements reported during the successful handover.

[0016] In 3GPP Release 18, the above functionality will be extended to cover the case of successful PSCell modification / addition (SPR). Summary of the Invention

[0017] Some embodiments disclosed herein are directed to a method performed by a user equipment (UE), including receiving a PSCell success report configuration including conditions for a PSCell (primary secondary cell group cell) success report, and further including, during a PSCell modification procedure, storing, in the PSCell success report, information indicating which of a plurality of network nodes initiated the PSCell modification procedure based on satisfying the conditions defined by the PSCell success report configuration.

[0018] Some other embodiments are directed to a method performed by a network node of a plurality of network nodes, the method including sending a PSCell success reporting configuration to a UE, the PSCell success reporting configuration including conditions for a PSCell success reporting.

[0019] Some other embodiments are directed to a corresponding UE configured to receive a PSCell success report configuration including conditions for the PSCell success report, wherein the user equipment is further configured to store, during a PSCell modification procedure, information in the PSCell success report indicating which of a plurality of network nodes initiated the PSCell modification procedure based on meeting the conditions defined by the PSCell success report configuration.

[0020] Some other embodiments are directed to a corresponding UE comprising at least one processor and at least one memory storing instructions, the instructions executable by the at least one processor for performing operations including receiving a PSCell success report configuration including a condition for a PSCell (primary secondary cell group cell) success report, the instructions executable by the at least one processor for further performing operations including, during a PSCell modification procedure, storing in the PSCell success report information indicating which of a plurality of network nodes initiated the PSCell modification procedure based on satisfying the condition defined by the PSCell success report configuration.

[0021] Some other embodiments are directed to a computer program product including a non-transitory computer-readable medium storing instructions executable by at least one processor of a UE to perform operations including receiving a PSCell success report configuration including conditions for a PSCell (primary secondary cell group cell) success report, the instructions executable by the at least one processor of the UE for further performing operations including, during a PSCell modification procedure, storing in the PSCell success report information indicating which of a plurality of network nodes initiated the PSCell modification procedure based on satisfying the conditions defined by the PSCell success report configuration.

[0022] Some other embodiments are directed to a corresponding network node of the plurality of network nodes, wherein the network node is configured to send a PSCell success reporting configuration to the UE, the PSCell success reporting configuration including conditions for the PSCell success reporting.

[0023] Some other embodiments are directed to a network node of a plurality of network nodes, the network node comprising at least one processor and at least one memory storing instructions executable by the at least one processor to perform an operation of transmitting a PSCell success reporting configuration to a UE (User Equipment) including conditions for a PSCell success reporting.

[0024] Some other embodiments are directed to a computer program product that includes a non-transitory computer-readable medium storing instructions executable by at least one processor of a network node to perform an operation of sending a PSCell success reporting configuration to a UE, the PSCell success reporting configuration including conditions for a PSCell success reporting.

[0025] Some potential advantages of these embodiments include that the network node among multiple network nodes that originated / initiated the PSCell modification procedure that led to the PSCell success report may be identified in a quick and efficient manner by including an indication of which of the multiple network nodes initiated the PSCell modification procedure. Including an indication of which of the multiple network nodes initiated the PSCell modification procedure reduces the processing time and power required to determine which network node initiated the PSCell modification procedure or where the PSCell modification procedure originated from. Other potential advantages of these embodiments include saving processing time, processing power, and storage space in certain circumstances by storing measurements related to the PSCell modification procedure and information in the PSCell success report, for example, based on meeting conditions defined in a PSCell success report configuration during the PSCell modification procedure.

[0026] Other methods, network nodes, and related devices according to embodiments will be or become apparent to one of ordinary skill in the art upon examination of the following figures and detailed description, and all such additional methods, network nodes, and related devices are intended to be included within this description and protected by the accompanying claims. [Brief explanation of the drawings]

[0027] The accompanying drawings, which are included to provide a further understanding of the present disclosure, and which are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of the inventive concepts.

[0028] [Figure 1] FIG. 1 is a communication system according to some embodiments.

[0029] [Figure 2] FIG. 2 is a flowchart illustrating the operation of a UE in accordance with some embodiments of the inventive concept.

[0030] [Figure 3] FIG. 3 is a flowchart illustrating the operation of a network node in accordance with some embodiments of the inventive concept.

[0031] [Figure 4] FIG. 4 is a block diagram of a communication system according to some embodiments.

[0032] [Figure 5] FIG. 5 is a block diagram of a user device according to some embodiments.

[0033] [Figure 6] FIG. 6 is a block diagram of a network node according to some embodiments.

[0034] [Figure 7] FIG. 7 is a block diagram of a host computer in communication with a user device, according to some embodiments.

[0035] [Figure 8] FIG. 8 is a block diagram of a virtualized environment according to some embodiments.

[0036] [Figure 9] FIG. 9 is a block diagram of a host computer communicating with a user device over a partially wireless connection via a base station, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0037] Some of the embodiments discussed herein are described more fully below with reference to the accompanying drawings. The embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art. Example embodiments of the inventive concepts are shown. However, the inventive concepts may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. A component from one embodiment may be implicitly assumed to be present / used in another embodiment.

[0038] The current Release 18 SON / MDT WID document (RP-221825) identifies the need to consider PSCell success report collection and reporting to the network. However, the current behavior for enabling the UE to collect / log PSCell modification / addition success information and measurements and reporting to the network is not standardized. Furthermore, in the current 3GPP RRC TS Specification 38.331 (Version 17.1.0), the UE does not know the initiator of the PSCell modification procedure (MN-initiated SN change or SN-initiated SN change), and such information is not stored in the network. Therefore, upon receipt of a PSCell success report in the network, it is not possible to identify the node (MN or SN) involved in the RRC configuration that triggered the UE to generate the PSCell success report. Not knowing the initiator node of the PSCell modification creates ambiguity when analyzing the report and finding the root cause of the problem that resulted in suboptimal performance in the PSCell modification procedure.

[0039] According to various embodiments of the present disclosure, the UE is configured to include the originator of the PSCell modification procedure in the PSCell success report. In addition, the network node may be configured to inform the UE about the originator of the PSCell modification procedure when configuring the PSCell success report configuration in the UE.

[0040] FIG. 1 illustrates a mass communication network (MCH) that can communicate with each other through one or more networks QQ 106 that provide backhaul communication. seeds 1 illustrates a communication system 100 including master network nodes QQ110A / QQ110B / QQ108 and secondary network nodes QQ110A / QQ110B / QQ108. The master network nodes QQ110A / QQ110B / QQ108 and secondary network nodes QQ110A / QQ110B / QQ108 may communicate with UEs QQ112A-D using multi-radio dual connectivity.

[0041] Various embodiments of the present disclosure relate to operations performed by a user equipment (UE) QQ112A-D to receive configuration from at least one network node (RAN node) (e.g., MN QQ110A / QQ110B / QQ108 and / or SN QQ110A / QQ110B / QQ108), evaluate PSCell modification or addition success reporting conditions, store configured parameters and measurements in a PSCell success report, and transmit the report to the network QQ160 (more specifically, to the network nodes Q110A / QQ110B / QQ108). One of The actions by the UE include:

[0042] Action (1): Receive a PSCell success report configuration from a network node, with an indication in the configuration indicating whether the PSCell modification procedure was initiated by the MN QQ110A / QQ110B / QQ108 or the SN QQ110A / QQ110B / QQ108.

[0043] Action (2): During and in response to the execution of a PSCell change procedure, evaluate the conditions set in the PSCell success report settings. Store / log information and measurements about the executed PSCell change performed according to the settings in a PSCell success report. Include information about the PSCell change initiator in the PSCell change success report.

[0044] Action (3): Report the availability of the PSCell success report to network node QQ106.

[0045] Action (4): Report a PSCell success report to network node QQ106.

[0046] Some other embodiments are directed to an operation by a network node to configure a PSCell success reporting configuration to UE QQ112A-D and to include an indication regarding the originator of the PSCell modification procedure.

[0047] In one embodiment, if the PSCell success report setting is set by the target SN, the operations include:

[0048] The source master network node (MN) provides the target secondary network node (SN) with an indicator to identify the originator / initiator of the PSCell modification procedure. In one embodiment, this indicator is included in the SN addition request message.

[0049] The target network node (SN) includes this indicator in the configuration sent to the UE QQ112A-D.

[0050] In one embodiment, when the PSCell success reporting configuration is configured by the MN, e.g., in the case of a PSCell change initiated by the MN, the operations include:

[0051] The master network node (MN) includes an indicator to identify the originator / initiator of the PSCell modification procedure (here, the MN) in the configuration sent to the UE QQ112A-D.

[0052] In one embodiment, if the PSCell success reporting setting is set by the source SN, e.g., in the case of a PSCell change initiated by an SN, the operations include:

[0053] A) (Optional) The source secondary network node (SN) provides an indicator to the source master network node (MN) to identify the originator / initiator of the PSCell modification procedure, which in this case is the source MN.

[0054] B) The source master network node (MN) includes this indicator in the configuration sent to the UE. In another embodiment, when the source MN receives the SPR configuration for PSCell modification from the source SN, the source MN adds an indicator to identify the originator / initiator of the PSCell modification procedure.

[0055] C) In one embodiment, the source SN includes this indicator in the configuration sent to the UE via SRB3.

[0056] When performing any of the above embodiments, the following operations for a network node (wherein a network node may refer to a source MN, a source SN, a target SN, or a different node) apply:

[0057] Action (1): A target network node (SN) or any other network node receives a PSCell success report from the UE.

[0058] Action (2): Based on the indicator, distribute a PSCell success report (201) to other network nodes.

[0059] Potential advantages of one or more embodiments of the present disclosure may include identifying the network node (MN or SN) that originated / initiated the PSCell modification procedure that led to the PSCell success report.

[0060] Throughout this disclosure, the terms network node and RAN node may be used interchangeably. Furthermore, the terms MN and SN may be different from the UE's perspective, i.e., the same network node may simultaneously act as an MN and an SN for different UEs. A Successful PSCell Report indicates a report from a UE according to the Successful PSCell report configuration and may have different names.

[0061] The corresponding actions by the UE are described in more detail below.

[0062] Disclosed herein is an operation in which a UE receives (one or more) PSCell success report configurations from a network node (e.g., a RAN node) for evaluating conditions for reporting a successful PSCell modification or addition, stores information and measurements based on the received configurations in a PSCell success report, and transmits the report to the network. The operations by the UE include:

[0063] Action (1): Receive a PSCell success report configuration from a network node.

[0064] The UE receives at least one PSCell success reporting configuration from the network node, the configuration(s) including different trigger options / conditions for the PSCell success reporting, the configuration(s) further including an indication regarding the initiator of the PSCell modification procedure.

[0065] FIG. 2 illustrates a flowchart of example operations that may be performed by a UE, according to some embodiments.

[0066] 2, in block 210, the UE may receive a Primary Secondary Cell (PSCell) success reporting configuration, the configuration including conditions for PSCell success reporting and indicating which of multiple network nodes initiated the PSCell modification procedure. In block 220, the UE may determine whether the conditions defined by the PSCell success reporting configuration are met during the PSCell modification procedure.

[0067] In some embodiments, the determination of whether the conditions defined by the PSCell success reporting configuration are met is determined elsewhere (other than by the UE), for example, at a network node. In these embodiments, an indication of whether the conditions are met may then be sent to and received by the UE. Thus, the operation of block 210 to determine whether the conditions are met may be optional for the UE.

[0068] In block 230, based on satisfying the conditions defined by the PSCell success report configuration during the PSCell modification procedure, the UE stores measurements related to the PSCell modification procedure in a PSCell success report, the measurements being performed according to the PSCell success report configuration.

[0069] Additionally, based on the above conditions being met, in block 240, the UE stores information indicating which of the multiple network nodes initiated the PSCell modification procedure in the PSCell success report.

[0070] Optionally, in block 250, the UE may report the availability of the PSCell success report to one of a plurality of network nodes.

[0071] In one embodiment, the indication is a flag indicating whether the PSCell modification procedure was initiated by the MN or the SN. In a non-limiting example, a value of 0 indicates that the PSCell modification procedure was initiated by the MN, and a value of 1 indicates that the PSCell modification procedure was initiated by the SN.

[0072] An exemplary corresponding action by the UE may include storing information in the PSCell success report indicating which of a plurality of network nodes initiated the PSCell modification procedure, including storing a flag in the PSCell success report indicating whether the PSCell modification procedure was initiated by a master node (MN) or a secondary node (SN) among the plurality of network nodes.

[0073] In another embodiment, the presence of the indication indicates that the PSCell change was initiated by the MN. The absence of the indication indicates that the PSCell change was initiated by the SN.

[0074] An example corresponding operation by the UE may include storing a flag in the PSCell success report based on the PSCell modification procedure being initiated by a predetermined one of a master node (MN) and a secondary node (SN) among a plurality of network nodes, where the presence of the flag in the PSCell success report indicates that a predetermined one of the MN and the SN initiated the PSCell modification procedure.

[0075] Another example corresponding action by the UE may include not storing a flag in the PSCell success report based on the PSCell modification procedure being initiated by the other of the MN and the SN, where the absence of a flag in the PSCell success report indicates that the other of the MN and the SN initiated the PSCell modification procedure.

[0076] Action (2): Evaluating the PSCell report trigger condition during the PSCell modification procedure.

[0077] The UE evaluates the PSCell success trigger conditions received as part of the last applied RRC reconfiguration, including reconfigurationWithSync, during the PSCell modification procedure, and logs the information required for the PSCell success report if the PSCell success report trigger conditions are met / satisfied. Non-limiting examples of the logged information include:

[0078] A) Source PSCell information, e.g., Source PSCell CGI (Cell Global Identity);

[0079] B) Target PSCell information, e.g., target PSCell CGI; and / or

[0080] C) Source PCell information, e.g., source PC ell CGI, where the source PCell is the PCell when performing the PSCell modify / add procedure.

[0081] An example corresponding action by the UE may include storing at least one of source PSCell information, target PSCell information, source primary cell (PCell) information, and information at the time of the PSCell change procedure in a PSCell success report based on satisfying the condition.

[0082] Furthermore, the UE logs a PSCell change initiator node indication in a report, i.e., to the MN or SN.

[0083] In one embodiment, the UE explicitly includes the received indication in the report.

[0084] In another embodiment, the UE does not explicitly include the indication in the report. In one embodiment, the UE includes the above-mentioned PCell information (e.g., PCell identity) only if the PSCell modification procedure is initiated by the MN. The absence of PCell information is an indirect indication that the procedure is initiated by the SN.

[0085] An exemplary corresponding action by the UE may include storing information in a PSCell success report indicating which of a plurality of network nodes initiated the PSCell modification procedure, performed in response to determining that the PSCell modification procedure was initiated by a master node (MN).

[0086] Another example corresponding operation by the UE may include storing information in the PSCell success report indicating which of a plurality of network nodes initiated the PSCell modification procedure, including storing source PSCell information and target PSCell information in the PSCell success report without storing source PCell information in response to determining that the PSCell modification procedure was initiated by a master node (MN).

[0087] In another embodiment, the UE includes the source PCell information and the source PSCell information both when the PSCell modification procedure is initiated by the MN or the SN. In one embodiment, the UE does not include the source PSCell information only in the case of a PSCell addition procedure. In this latter case, the network determines that the SHR is associated with a PSCell addition procedure when the SHR contains only the target PSCell information and the source PCell information.

[0088] Exemplary corresponding actions by the UE may include storing information in the PSCell success report indicating which of a plurality of network nodes initiated the PSCell modification procedure, including storing source PSCell information and target PSCell information in the PSCell success report without storing source PCell information in response to determining that the PSCell modification procedure was initiated by a master node (MN) or a secondary node (SN).

[0089] In a different embodiment, the UE includes the source PSCell information only if it is available, so during the first PSCell addition procedure, the source PSCell information is unavailable.

[0090] In another embodiment, the UE added the PSCell success report to a list of PSCell success reports.

[0091] Action (3): Report the availability of the PSCellreport to the network.

[0092] The UE reports the availability of a PSCell change success report to the network.

[0093] In one embodiment, the UE sends a PSCell success report availability indication to the serving MN after the PSCell change procedure.

[0094] In another embodiment, the UE sends a PSCell success report availability indication to the target SN.

[0095] In yet another embodiment, the UE sends the PSCell success report availability indication to a third network SN different from the target SN and the serving MN.

[0096] In an independent embodiment, the UE includes an explicit capability indication to the target MN, target SN, or third network to which the PSCell success report can be reported via a PSCell success report or other RRC message (e.g., RRCSetup complete, RRC Resume complete, etc.). The capability can be further separated with respect to RAT type (e.g., capability indication related to EUTRA or NR MCG).

[0097] Action (4): Report a PSCell success report to the network.

[0098] Upon receiving the report request from the network, the UE reports a PSCell success report to the network. Current standardized UE information request and response mechanisms / procedures may be used in this regard.

[0099] Corresponding actions by the network nodes are described in more detail below.

[0100] Another embodiment of the present disclosure relates to an operation by a network node to configure a PSCell success report configuration in a UE and a PSCell modification procedure. Origin The scope of this document is to include an indication of the originator / initiator of the protocol.

[0101] 3 illustrates a flowchart of exemplary operations that may be performed by a network node according to some embodiments. Referring to FIG. 3, at block 320, the network node sends a Primary Secondary Cell (PSCell) success reporting configuration to the UE, the configuration including conditions for the PSCell success reporting and indicating which of a plurality of network nodes initiated the PSCell modification procedure.

[0102] In a further embodiment, if the network node is a target secondary node (SN), the network node may optionally receive (at block 310) an indication from the source master node (MN) of which of the multiple network nodes initiated the PSCell modification procedure. Further, the network node may generate a PSCell success report configuration to include an indication of which of the multiple network nodes initiated the PSCell modification procedure.

[0103] Optionally, in some embodiments, the network node may receive (at block 330) an indication from the UE that a PSCell success report is available.

[0104] Optionally, in some embodiments, the network node may fetch (at block 340) a PSCell success report from the UE.

[0105] Optionally, in some embodiments, the network node may distribute (at block 350) the PSCell success report to another network node based on an indication in the PSCell success report of which of multiple network nodes initiated the PSCell modification procedure. Additionally or alternatively, the PSCell success report may include PCell information, and the other network node is selected to receive distribution of the PSCell success report based on the PCell information.

[0106] Further related actions by the network node may include the following five numbered actions (1)-(5) described below:

[0107] Action (1): The source master network node (MN) provides the target secondary network node (SN) with an indicator for identifying the originator of the PSCell modification procedure.

[0108] In one embodiment, the indicator is a flag that indicates whether the PSCell change is initiated / initiated by the MN or the SN, e.g., a value of 0 indicates that the PSCell change procedure is initiated by the MN, and a value of 1 indicates that the PSCell change procedure is initiated by the SN.

[0109] For example, the indication received from the source MN (at block 310) includes a flag indicating whether the PSCell modification procedure was initiated by the MN or by a secondary node (SN) among multiple network nodes.

[0110] In another embodiment, the presence of the indication indicates that the PSCell change was initiated by the MN. The absence of the indication indicates that the PSCell change was initiated by the SN.

[0111] In some embodiments, a network node may perform operations including determining that the PSCell modification procedure was initiated by a predetermined one of a master node (MN) and a secondary node (SN) among a plurality of network nodes, which may be based on receiving a flag from a source master node (MN), and determining that the PSCell modification procedure was initiated by the other of the MN and SN based on not receiving a flag from the source MN.

[0112] In yet another embodiment, an indication is included in the SN addition request, for example, an indication of which of multiple network nodes initiated the PSCell modification procedure may be received by the network node from the source MN in a Source Node (SN) Addition Request message.

[0113] Action (2): The target network node (SN) includes this indicator (301) in the configuration (101) sent to the UE. Thus, as described above, the network node operates to send to the UE a PSCell success report configuration that includes the conditions for the PSCell success report and indicates which of multiple network nodes initiated the PSCell modification procedure.

[0114] The target network node (SN) includes an indication in the RRC configuration including reconfiguration with synchronization sent to the UE.

[0115] In one embodiment, for an intra-SN PSCell modification procedure, an indication is included by the SN indicating which SN will be the initiator of the procedure.

[0116] In an alternative embodiment, if the PSCell success report configuration is configured by the source MN, e.g., in the case of a PSCell change initiated by the MN, the operation includes the source master network node (MN) including this indicator in the configuration sent to the UE.

[0117] In one embodiment, if the PSCell success reporting setting is set by the source SN, e.g., in the case of a PSCell change initiated by an SN, the operations further include:

[0118] A) (Optional) The source secondary network node (SN) provides an indicator to the source master network node (MN) to identify the originator / initiator of the PSCell modification procedure, which in this case is the source MN; and / or

[0119] B) The source master network node (MN) includes this indicator in the configuration sent to the UE. In another embodiment, when the source MN receives the SHR configuration for PSCell modification from the source SN, the source MN adds an indicator to identify the originator / initiator of the PSCell modification procedure (in this case, the source MN or source SN).

[0120] For example, if the network node is a source master network node (MN), the network node may generate the PSCell success report configuration to include an indicator identifying the source master node (MN) that initiated the PSCell modification procedure. Further, if the PSCell success report configuration is configured by a source secondary node (SN), the source MN receives an indication from the source SN that the source SN initiated the PSCell modification procedure.

[0121] Action (3): The target network node (SN) or any other network node receives an indication from the UE regarding the availability of a PSCell success report.

[0122] The target network node (SN) or any other network node receives an indication from the UE regarding the availability of the PSCell success report. Corresponding actions by the network node include receiving an indication from the UE that the PSCell success report is available.

[0123] Action (4): The target network node (SN) or any other network node receives a PSCell success report from the UE.

[0124] The target network node (SN) fetches the PSCell report from the UE, which may be performed using standardized UE information request and response procedures. Corresponding actions by the network node include fetching the PSCell success report from the UE.

[0125] Action (5): Based on the indicator, distribute the PSCell success report to other network nodes.

[0126] The target network node (SN) or any other network node distributes the PSCell report to other network nodes based on the initiator indicator indicated in the PSCell success report. Corresponding actions by the network node include distributing the PSCell success report to other network nodes based on an indication in the PSCell success report of which of multiple network nodes initiated the PSCell modification procedure.

[0127] In one embodiment, if the UE includes the PCell information, it is an implicit indicator that the PSCell modification procedure is initiated by the MN, and the target SN forwards it to the source MN. The absence of such PCell information indicates an SN-initiated PSCell modification procedure, and the target SN provides this information only to the source SN.

[0128] In another embodiment, if the UE includes an explicit indicator regarding the initiator of the PSCell modification procedure, the target SN sends the report only to the initiating node, and therefore forwards the report to the source MN or SN.

[0129] In yet another embodiment, if the UE includes an explicit indicator regarding the initiator of the PSCell modification procedure, regardless of the initiator, the target SN forwards the report only to the source MN.

[0130] In a subembodiment, the source MN forwards the report to the source SN.

[0131] In some instances, the node receiving the PSCell success report from the UE is neither the MN nor the SN (i.e., a third network node), in such instances the node receiving the PSCell success report forwards the report to the target SN of the PSCell modification, to the initiator of the PSCell modification procedure, or to both.

[0132] The operation of the communication device QQ200 (implemented using the configuration of the block diagram of FIG. 5) is described above with reference to the flowchart of FIG. 2, according to some embodiments of the inventive concepts. For example, modules may be stored in the memory QQ210 of FIG. 5, and these modules may provide instructions such that when the instructions of the modules are executed by the processing circuitry QQ202 of the respective communication device, the processing circuitry QQ202 performs the respective operations of the flowchart.

[0133] Various operations from the flowchart of Figure 2 may be optional for some embodiments of the communications device and associated methods, for example, one or more of the operations of blocks 230 and 250 of Figure 2 may be optional.

[0134] The operation of RAN node QQ300 (implemented using the configuration of FIG. 6) is described above with reference to the flowchart of FIG. 3, in accordance with some embodiments of the inventive concepts. For example, modules may be stored in memory QQ304 of FIG. 6, and these modules may provide instructions such that the RAN node QQ300 performs the respective operations of the flowchart when the instructions of the modules are executed by the processing circuitry QQ220 of the respective RAN node.

[0135] Various operations from the flowchart of Figure 3 may be optional for some embodiments of the RAN node and associated methods, for example, one or more of the operations in blocks 310, 330, 340, and 350 of Figure 3 may be optional.

[0136] The operation of core network (CN) node QQ300 (implemented using the configuration of FIG. 6) is described above with reference to the flowchart of FIG. 3, in accordance with some embodiments of the inventive concepts. For example, modules may be stored in memory QQ304 of FIG. 6, and these modules may provide instructions such that the CN node QQ300 performs the respective operations of the flowchart when the instructions of the modules are executed by the processing circuitry QQ302 of the respective CN node.

[0137] FIG. 4 illustrates an example of a communication system QQ100 according to some embodiments.

[0138] In this example, communication system QQ100 includes a telecommunications network QQ102 including an access network QQ104, such as a radio access network (RAN), and a core network QQ106 including one or more core network nodes QQ108. Access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network node QQ110), or any other similar 3GPP access node or non-3GPP access point. Network node QQ110 facilitates direct or indirect connectivity of user equipment (UE), such as connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UE QQ112), to core network QQ106 over one or more wireless connections.

[0139] Exemplary wireless communications over wireless connections include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for carrying information without the use of wires, cables, or other material conductors. Moreover, in various embodiments, communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via wired or wireless connections. Communication system QQ100 may include and / or interface with any type of communication, telecommunications, data, cellular, wireless network, and / or other similar types of systems.

[0140] UEQQ112 may be any of a wide variety of communication devices, including wireless devices, that are positioned, configured, and / or operable to communicate wirelessly with network node QQ110 and other communication devices. Similarly, network node QQ110 is positioned, capable, configured, and / or operable to communicate, directly or indirectly, with UEQQ112 and / or with other network nodes or equipment within telecommunications network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as management, within telecommunications network QQ102.

[0141] In the illustrated example, core network QQ106 connects network node QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect through one or more intermediate networks or devices. In other examples, a network node may be directly coupled to a host. Core network QQ106 includes one or more core network nodes (e.g., core network node QQ108) structured with hardware and software components. The functionality of these components may be substantially similar to that described with respect to UEs, network nodes, and / or hosts, and therefore, these descriptions are generally applicable to the corresponding components of core network node QQ108. Exemplary core network nodes include one or more of a Mobile Switching Center (MSC), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Subscription Identifier Deciphering Function (SIDF), a Unified Data Management (UDM), a Security Edge Protection Proxy (SEPP), a Network Publishing Function (NEF), and / or a User Plane Function (UPF).

[0142] Host QQ116 ,a access network QQ104 and / or telecommunications network QQ102 Business operator or Provider Service providers other than may be owned or controlled by the service provider or The service provider For The host QQ 116 may host a variety of applications and provide one or more services. Examples of such applications include live and pre-recorded audio / video content, various ambient signals detected by multiple UEs, and situationThis includes data collection services such as obtaining and compiling data about, analytics functionality, social media, functionality for controlling or otherwise interacting with remote devices, functionality for alarm and monitoring centers, or any other such functionality performed by the server.

[0143] 4 enables connectivity between UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as a particular standard, including, but not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G), a wireless local area network (WLAN) standard, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi), and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standard, such as LoRa and Sigfox.

[0144] In some examples, the telecommunications network QQ 102 is a cellular network that implements functions standardized by 3GPP. Thus, the telecommunications network QQ 102 provides various logical services to various devices connected to the telecommunications network QQ 102. targetThe network may support network slicing for providing a network, for example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communications (URLLC) services to some UEs while providing enhanced Mobile Broadband (eMBB) services to other UEs. and / or It may also provide Massive Machine Type Communication (mMTC) / Massive IoT services to additional UEs.

[0145] In some examples, the UE QQ 112 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to the access network QQ 104 on a predetermined schedule, when triggered by an internal or external event, or in response to a request from the access network QQ 104. Additionally, the UE may be configured to operate in a single or multi-RAT or multi-standard mode. For example, the UE may be configured and operate in any one or combination of Wi-Fi, NR (New Radio), and LTE, i.e., for Multi-Radio Dual Connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0146] In the above example, the hub QQ 114 communicates with the access network QQ 104 to facilitate indirect communication between one or more UEs (e.g., UEs QQ 112c and / or QQ 112d) and a network node (e.g., network node QQ 110b). In some examples, the hub QQ 114 may be a controller, a router, a content source and analytics, or any of the other communication devices described herein with respect to a UE. For example, the hub QQ 114 may be a broadband router that enables access to the core network QQ 106 for the UE. As another example, the hub QQ 114 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE or the network node QQ 110, or Hub QQ114 Executable code, scripts, processes, and Other As another example, the hub QQ 114 may be a data collector that acts as a temporary storage for UE data and, in some embodiments, analyzes that data. or Other processing may be performed. As another example, Hub QQ 114 may be a content source. For example, for UEs that are VR headsets, displays, loudspeakers, or other media delivery devices, Hub QQ 114 may obtain media or data related to VR assets, video, audio, or other sensory information via a network node, and then provide it to the UE either directly, after performing local processing, and / or after adding additional local content. In yet another example, Hub QQ 114 acts as a proxy server or orchestrator for the UEs, particularly if one or more of the UEs are low-energy IoT devices.

[0147] Hub QQ 114 may have a constant / permanent or intermittent connection to network node QQ 110b. Hub QQ 114 also has a for example,The hub QQ114 may enable different communication schemes and / or schedules between the UEs QQ112c and / or QQ112d, and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to other UEs over a direct connection. In some scenarios, a UE may establish a wireless connection with the network node QQ110b while still being connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub, i.e., a hub whose primary function is to route communications between UEs and the network node QQ110b. In other embodiments, hub QQ114 may be a non-dedicated hub, i.e., a device that is operable to route communications between UEs and network node QQ110b, but that is also operable as a communication origination and / or termination point for any data channel.

[0148] 5 illustrates a UE QQ 200 according to some embodiments. As used herein, a UE refers to a device capable of, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smartphone, a mobile phone, a cell phone, a Voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless camera, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a smart device, a wireless customer premises equipment (CPE), an in-vehicle or vehicle embedded / integrated wireless device, etc. Other examples include a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. Third Generation Partnership Project ( 3GPP ) This includes any UE identified by

[0149] The UE may communicate via, for example, sidelink communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) or vehicle-to-everything (V2 X In another example, a UE may support device-to-device (D2D) communications by implementing 3GPP standards for device-to-device (D2D) communications. In another example, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but that may not, at least initially, be associated with a particular human user. Alternatively, a UE may represent a device that is intended for sale to or operation by an end user. Although , may represent a device (e.g., a smart power meter) that may be associated with or operated for the benefit of a user.

[0150] UEQQ200 is an input / output interface QQ206 , power supply QQ208, memory QQ210, communication interface QQ212, and / or any other components, or any combination thereof. Processing circuit QQ20 operably coupled via bus QQ204 to 2 5. A given UE may utilize all or a subset of the components shown in FIG. 5. The level of integration between components may vary from one UE to another. Furthermore, a given UE may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0151] Processing circuit QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operable to execute instructions stored as a machine-readable computer program in memory QQ210. Processing circuit QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.), programmable logic with appropriate firmware, one or more stored computer programs, a general-purpose processor such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, processing circuit QQ202 may include multiple central processing units (CPUs).

[0152] In the above example, the input / output interface QQ 206 may be an input device, an output device, or one or more Input and / or OutputThe UEQQ 200 may be configured to provide one or more interfaces to devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, emitters, smart cards, other output devices, or any combination thereof. Input devices may enable a user to capture information for the UEQQ 200. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, webcams, etc.), microphones, sensors, mice, trackballs, directional Examples of such sensors include pads, trackpads, scroll wheels, and smart cards. Presence-sensitive displays may include capacitive or resistive touch sensors for sensing input from a user. The sensors may be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetic sensors, optical sensors, proximity sensors, biometric sensors, etc., or any combination thereof. Output devices may use the same type of interface port as the input devices. For example, a Universal Serial Bus (USB) port may be used to provide input and output devices.

[0153] In some embodiments, the power source QQ208 is structured as a battery or battery pack; an external power source (e.g., an electrical outlet); solar Other types of power sources, such as photovoltaic devices or batteries but The power supply QQ208 may be used in various applications. The power supply QQ208 may further include power circuitry for transferring power from the power supply QQ208 itself and / or from an external power source to various portions of the UEQQ200 via an interface, such as an input circuit or a power cable. The transfer of power may be for charging the power supply QQ208, for example. The power circuitry may perform some shaping, conversion, or other modification of the power from the power supply QQ208 to make it suitable for the respective components of the UEQQ200 that it powers.

[0154] Memory QQ210 supports Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read Only Memory (PROM), Erasable Programmable Read Only Memory (EPROM), Electrical Target Erasable Programmable Read-Only Memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, and flash drives memory In one example, the memory QQ 210 includes one or more application programs QQ 214, such as an operating system, a web browser application, a widget, a gadget engine, or other applications, and corresponding data QQ 216. The memory QQ 210 may be a UEQQ 2 Any of a wide variety of operating systems or combinations of operating systems may be stored for use by the 00.

[0155] The QQ210 memory is configured with RAID (Redundant Array of Independent Disks) )、 Flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, HD-DVD (High-Density Digital Versatile Disc), optical disk drive, internal hard disk drive, Blu-Ray optical disk drive, HDDS (Holographic Digital Data Storage) optical disk drive, external mini DI MM (Dual In-Line Memory Module), SDRAM (Synchronous Dynamic Random Access Memory), external micro DIMM SDRAM, smart card memory such as a tamper-resistant module in the form of a UICC (universal integrated circuit card) containing one or more SIMs (subscriber identity modules) such as USIM and / or ISIM, other memory, or any combination thereof Multiple physical drive units such asThe UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card." The memory QQ210 may enable the UEQQ200 to access instructions, application programs, and the like stored on a temporary or non-temporary storage medium to offload or upload data. An item of product, such as one utilizing a communication system, may be tangibly embodied as or in the memory QQ210, which may be or include a device-readable storage medium.

[0156] The processing circuit QQ202 may be configured to communicate with an access network or other networks using a communication interface QQ212. The communication interface QQ212 may include one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of other devices capable of wireless communication (e.g., other UEs or network nodes in the access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate for providing network communications (e.g., optical, electrical, frequency allocation, etc.). Moreover, the transmitter QQ218 and the receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222), which may share circuit components, software, or firmware, or may alternatively be implemented separately.

[0157] In the illustrated embodiment, the communication capabilities of communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using the Global Positioning System (GPS) for determining location, other similar communication capabilities, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as, for example, IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.

[0158] Regardless of the type of sensor, the UE may provide an output of data captured by its sensors to a network node via a wireless connection through its communication interface QQ212. Data captured by the UE's sensors may be communicated via other UEs to the network node via a wireless connection. The output may be periodic (e.g., once every 15 minutes when reporting sensed temperature), random (e.g., to balance the load of notifications from multiple sensors), in response to a triggering event (e.g., moisture is detected and an alert is sent), on request (e.g., a user-initiated request), or as a continuous stream (e.g., a live video feed of a patient).

[0159] As another example, the UE may include an actuator, motor, or switch associated with a communications interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch may change in response to the received wireless input. For example, the UE may include a motor that adjusts a control surface or rotor of a drone in flight in accordance with the received input, or a robotic arm that performs a medical procedure in accordance with the received input.

[0160] When the UE is in the form of an Internet of Things (IoT) device, it may be a device for use in one or more application domains, including but not limited to wearable technology in the city, extended industrial applications, and healthcare. Type Refrigerator or freezer, TV, connected Type Lighting fixtures, electricity meters, robot vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / moisture sensors, electricity formula Door lock, Connected Doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, Electric vehicles Charging stations, smart watches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearables for haptic augmentation or sensory enhancement, water sprinklers, animal or object tracking device UE may be or be integrated into devices such as sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any type of medical device such as a heart rate monitor or remote-controlled surgical robot. A UE in the form of an IoT device may comprise other components such as those described in connection with the UEQQ 200 shown in FIG. 5, in addition to circuitry and / or software depending on the intended application of the IoT device.

[0161] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to other UEs and / or network nodes. The UE may in this case be an M2M device, which may also be referred to as an MTC device in the 3GPP context. specific As an example, the UE may implement the 3GPP NB-IoT standard. a vehicle such as a car, truck, boat, or aircraft; or The ability to monitor and / or report on its operational status or other functions associated with its operation Other may represent the equipment.

[0162] In practice, any number of UEs may be used together for a single use case. For example, a first UE may be a drone or integrated into a drone and provide drone speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When a user makes changes from the remote controller, the first UE may adjust the drone's throttle (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE may also include more than one of the above-described functionalities. For example, a UE may include a sensor and an actuator and handle communication of data for both the speed sensor and the actuator.

[0163] 6 illustrates a network node QQ300 according to some embodiments. As used herein, a network node refers to a device that is capable of, configured, arranged, and / or operable to communicate directly or indirectly with UEs and / or other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points) and base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0164] Base stations may be categorized based on the amount of coverage they provide (or, alternatively, their transmit power levels) and may therefore be referred to as femto, pico, micro, or macro base stations depending on the amount of coverage provided. A base station may also be a relay node or a relay donor node that controls a relay. Also, A network node may be a centralized digital unit, and / or sometimes Remote Radio Head (RRH) and be called It may include one or more (or all) parts of a distributed radio base station, such as a remote radio unit (RRU), which may or may not be integrated with an antenna, such as an antenna-integrated radio. Also, Some of the distributed radio base stations may be referred to as nodes in a distributed antenna system (DAS).

[0165] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as an MSR BS, a network controller such as a radio network controller (RNC) or base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile location center (E-SMLC) and / or a minimized drive test (MDT).

[0166] Network node QQ300 includes processing circuitry QQ302, memory QQ304, communication interface QQ306, and power supply QQ308. Network node QQ300 may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component), each of which may have its own respective components. In some scenarios in which network node QQ300 comprises multiple separate components (e.g., a BTS and a BSC component), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such scenarios, each unique pair of Node B and RNC may, in some examples, be considered a single separate network node. In some embodiments, network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be redundant (e.g., separate memories QQ304 for different RATs) and some components may be reused (e.g., the same antenna QQ310 may be shared by different RATs). Network node QQ300 may also include multiple sets of various illustrated components for different wireless technologies integrated into network node QQ300, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, RFID (Radio Frequency Identification), or Bluetooth wireless technologies. The wireless technologies may be integrated into the same or different chips or chipsets and other components within network node QQ300.

[0167] The processing circuitry QQ302 may include one or more combinations of microprocessors, controllers, microcontrollers, central processing units, digital signal processors, application specific integrated circuits, field programmable gate arrays or other suitable computing devices, resources or combinations of hardware, software and / or coded logic operable, alone or in conjunction with other network node QQ300 components, such as memory QQ304, to provide the functionality of network node QQ300.

[0168] In some embodiments, the processing circuit QQ302 comprises a system-on-chip (SOC). In some embodiments, the processing circuit QQ302 includes one or more of a radio frequency (RF) transceiver circuit QQ312 and a baseband processing circuit QQ314. In some embodiments, the radio frequency (RF) transceiver circuit QQ312 and the baseband processing circuit QQ314 may be on separate chips (or chipsets), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit QQ312 and the baseband processing circuit QQ314 may be on the same chip or chipset, board, or unit.

[0169] The memory QQ304 may include any type of volatile or non-volatile computer-readable memory, including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disks), removable storage media (e.g., flash drives, compact discs (CDs), or digital video discs (DVDs)), and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory device, that stores information, data, and / or instructions that may be used by the processing circuit QQ302. The memory QQ304 may store any suitable instructions, data, or information, including applications, including one or more of computer programs, software, logic, rules, codes, tables, and / or other instructions, that are executable by the processing circuit QQ302 and usable by the network node QQ300. The memory QQ304 may store any computational results produced by the processing circuit QQ302 and / or communication It may be used to store any data received via the interface QQ 306. In some embodiments, the processing circuit QQ 302 and the memory QQ 304 are integrated.

[0170] The communication interface QQ306 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, the communication interface QQ306 includes a port / terminal QQ316 for transmitting and receiving data to and from a network over a wired connection, for example. The communication interface QQ306 also includes a radio front-end circuit QQ318 that is coupled to the antenna QQ310 or, in some embodiments, may be part of the antenna QQ310. The radio front-end circuit QQ318 includes a filter QQ320 and an amplifier QQ322. The radio front-end circuit QQ318 may be connected to the antenna QQ310 and the processing circuit QQ302. The radio front-end circuit may be configured to condition signals communicated between the antenna QQ310 and the processing circuit QQ302. The radio front-end circuit QQ318 may accept digital data to be sent to another network node or UE via a wireless connection. The radio front-end circuit QQ318 may convert the digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of a filter QQ320 and / or an amplifier QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when data is received, the antenna QQ310 collects the radio signal, which may then be converted into digital data by the radio front-end circuit QQ318. The digital data may be passed to the processing circuit QQ302. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0171] In an alternative embodiment, the network node QQ300 includes a separate radio front-end circuit QQ318. figure Rather, the processing circuit QQ302 includes a radio front-end circuit. fruit , connected to the antenna QQ310 RSimilarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In yet another embodiment, the communication interface QQ306 includes one or more ports or terminals QQ316, radio front-end circuitry QQ318, and RF transceiver circuitry QQ312 as part of a radio unit (not shown), and the communication interface QQ306 communicates with baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0172] Antenna QQ310 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna QQ310 may be coupled to radio front-end circuit QQ318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna QQ310 is separate from network node QQ300 and connectable to network node QQ300 through an interface or port.

[0173] The antenna QQ310, the communication interface QQ306, and / or the processing circuit QQ302 may be configured to perform any receiving operation and / or any acquiring operation described herein as being performed by a network node. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuit QQ302 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0174] Power supply QQ308 provides power to the various components of network node QQ300 in a manner appropriate for each component (e.g., at the voltage and current levels required by each component). Power supply QQ308 includes power management circuitry to provide power to the components of network node QQ300 to perform the functionality described herein. moreover The power management circuitry may include or be coupled to the network node QQ300. For example, the network node QQ300 may be connectable to an external power source (e.g., a power grid, an electrical outlet) via an input circuit or interface, such as an electrical cable, so that the external power source provides power to the power circuitry of the power source QQ308. As a further example, the power source QQ308 may include a source of power in the form of a battery or battery pack connected to or integrated into the power circuitry. The battery may provide backup power in case of failure of the external power source.

[0175] Embodiments of network node QQ300 may include additional components other than those shown in Figure 6 to provide certain aspects of the network node's functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node QQ300 may include user interface devices that allow information to be input into network node QQ300 and information to be output from network node QQ300. This may enable a user to perform diagnostic, maintenance, repair, and other management functions on network node QQ300.

[0176] 7 is a block diagram of a host QQ 400, which may be an embodiment of the host QQ 116 of FIG. 4, in accordance with various aspects described herein. As used herein, the host QQ 400 may be or include hardware and / or software in various combinations, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or processing resources within a server farm. The host QQ 400 may provide one or more services to one or more UEs.

[0177] The host QQ400 has an input / output interface QQ406 , network interface QQ408, power supply QQ410, and memory QQ412 Processing circuit QQ40 operably coupled via bus QQ404 to 2 In other embodiments, other components may be included, the functionality of which may be substantially similar to those described with respect to the devices in previous figures, such as Figures 5 and 6, and therefore those descriptions are generally applicable to the corresponding components of host QQ400.

[0178] Memory QQ412 may include one or more computer programs, including one or more host application programs QQ414, and data QQ416, which may include user data, such as data generated by a UE for host QQ400 or data generated by host QQ400 for a UE. An embodiment of host QQ400 may utilize only a subset or all of the illustrated components. Host application programs QQ414 may be implemented in a container-based architecture and may support video codecs (e.g., CODECs), including transcoding for different UE classes, types, or implementations (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). for example,The host application program QQ414 may provide support for Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9, ​​and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711). The host application program QQ414 may also provide user authentication and license checks, and may periodically report health, route, and content availability to a central node, such as a device in or at the edge of the core network. Thus, the host QQ400 may select and / or point to different hosts for over-the-top services for the UE. The host application program QQ414 may support a variety of protocols, such as HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0179] FIG. 8 is a block diagram illustrating a virtualization environment QQ500 in which functionality implemented in some embodiments may be virtualized. In this context, virtualization means for creating a virtual version of an apparatus or device may include a virtualized hardware platform, storage devices, and networking resources. As used herein, virtualization may apply to any device or component described herein and refers to an implementation in which at least a portion of its functionality is implemented as one or more virtual components. Some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented within one or more virtual environments QQ500 hosted by one or more hardware nodes, such as a network node, a UE, a core network node, or a hardware computing device acting as a host. Furthermore, in embodiments in which a virtualized node does not require wireless connectivity (e.g., a core network node or host), the node may be virtualized in its entirety.

[0180] Application QQ502 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in virtualized environment QQ500 to implement some of the features, functionality and / or benefits of some of the embodiments disclosed herein.

[0181] The hardware QQ504 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or hardware devices as described herein, such as network interfaces and input / output interfaces. The software is executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide VMQQ508a and VMQQ508b (one or more of which may be collectively referred to as VMQQ508), and / or perform any of the functions, features, and / or benefits described in connection with some embodiments described herein. The virtualization layer QQ506: VM It may present a virtual operating platform that appears to the QQ508 as networking hardware.

[0182] VMQQ 508 may include virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be executed by a corresponding virtualization layer QQ 506. Various embodiments of an instance of virtual appliance QQ 502 may be implemented in one or more of VMQQ 508, and the implementation may be done in various ways. Hardware virtualization is referred to in some contexts as network functions virtualization (NFV). NFV may be used to aggregate many network equipment types into industry-standard, high-capacity server hardware, physical switches, and physical storage that may be located in data centers and customer premises equipment.

[0183] In the context of NFV, a VMQQ 508 may be a software implementation of a physical machine that runs programs as if they were running on a physical, non-virtualized machine. Each VMQQ 508 and the portion of the hardware QQ 504 that runs that VM, whether on hardware dedicated to that VM and / or shared by that VM with other VMs, forms a separate virtual network element. Also in the context of NFV, a virtual network function is responsible for handling specific network functions running in one or more VMQQs 508 on top of a hardware QQ 504 and corresponds to an application QQ 502.

[0184] Hardware QQ504 is General-purpose Alternatively, the hardware QQ504 may be implemented in a standalone network node with its own components. The hardware QQ504 may implement some functions via virtualization. Alternatively, the hardware QQ504 may be part of a larger hardware cluster (e.g., in a data center or CPE) where multiple hardware nodes cooperate and are managed via a management and orchestration QQ510, which oversees, among other things, the lifecycle management of the application QQ502. In some embodiments, the hardware QQ504 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces or may be used in combination with virtual components, such as radio access nodes or base stations, to provide wireless capabilities to virtual nodes. In some embodiments, some signaling may be provided using the control system QQ512, which may alternatively be used for communication between the hardware nodes and the radio units.

[0185] FIG. 9 illustrates a host computer communicating with a network node QQ 604 over a partially wireless connection in accordance with some embodiments. ToQ 9 illustrates a communication diagram for UE QQ 602. Exemplary implementations according to various embodiments of the UE (UE QQ 112a of FIG. 4 and / or UE QQ 200 of FIG. 5), network node (network node QQ 110a of FIG. 4 and / or network node QQ 300 of FIG. 6), and host (host QQ 116 of FIG. 4 and / or host QQ 400 of FIG. 7) discussed in the preceding paragraphs will now be described with reference to FIG.

[0186] Similar to host QQ 400, an embodiment of host QQ 602 includes hardware such as communication interfaces, processing circuitry, and memory. , Ho The present invention also includes software stored within or accessible by the host QQ 602 that is executable by the processing circuitry. 6th grade and a host computer QQ 602. During the provision of the service to the remote user, the host application may provide user data that is transmitted using the OTT connection QQ 650.

[0187] Network node QQ 604 includes hardware that enables communication with hosts QQ 602 and UEQQ 606. Connection QQ 660 may be direct or may pass through one or more other intermediate networks, such as a core network (such as core network QQ 106 of FIG. 4) and / or one or more public, private, or hosted networks. For example, the intermediate network may be a backbone network or the Internet.

[0188] UEQQ 606 is software stored within or accessible by UEQQ 606 that is executable by the processing circuitry of the UE. Including The software includes a client application, such as a web browser or operator-specific "app," that may be operable to provide services to a human or non-human user via the UE QQ 606, with support from the host QQ 602. A host application running on the host QQ 602 may communicate with a client application running on the UE via the UE QQ 606 and an OTT connection QQ 650 that terminates at the host QQ 602. During the provision of services to the user, the client application on the UE may receive request data from the host application on the host and provide user data in response to the request data. The OTT connection QQ 650 may transport both the request data and user data. The client application on the UE may interact with the user to generate user data that it provides to the host application through the OTT connection QQ 650.

[0189] OTT connection QQ650 may extend via connection QQ660 between host QQ602 and network node QQ604 and via wireless connection QQ670 between network node QQ604 and UEQQ606, providing connectivity between host QQ602 and UEQQ606. Connection QQ660 and wireless connection QQ670 over which OTT connection QQ650 may be provided are depicted abstractly to illustrate communication between host QQ602 and UEQQ606 via network node QQ604 without explicit reference to any intermediate devices and the precise routing of messages through those devices.

[0190] As an example of transmitting data over the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be done by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with the UEQQ606. In other embodiments, the user data is associated with the UEQQ606 sharing data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission to the UEQQ606 carrying user data. The host QQ602 may initiate the transmission in response to a request sent by the UEQQ606. The request may be triggered by human interaction with the UEQQ606 or by the operation of a client application running on the UEQQ606. The transmission may pass through the network node QQ604 in accordance with the teachings of embodiments described throughout this disclosure. In response, in step QQ612, network node QQ604 transmits the user data carried in the transmission initiated by host QQ602 to UEQQ606, in accordance with the teachings of embodiments described throughout this disclosure. In step QQ614, UEQQ606 receives the user data carried in the transmission, which may be done by a client application running on UEQQ606 that is associated with a host application executed by host QQ602.

[0191] In some examples, UEQQ606 executes a client application, which provides user data destined for host QQ602. The user data may be provided in reaction or response to receiving the data from host QQ602. In response, UEQQ606 may provide the user data in step QQ616, which may be done by executing the client application. While providing the user data, the client application may further consider user input received from the user via an input / output interface of UEQQ606. Regardless of the specific manner in which the user data is provided, UEQQ606 initiates transmission of the user data to host QQ602 via network node QQ604 in step QQ618. In step QQ620, network node QQ604 receives the user data from UEQQ606 and initiates transmission of the received user data to host QQ602, in accordance with the teachings of embodiments described throughout this disclosure. In step QQ622, host QQ602 receives the user data carried in the transmission initiated by UEQQ606.

[0192] One or more of the various embodiments improve the performance of the OTT service provided to the UEQQ 606 using the OTT connection QQ 650, of which the wireless connection QQ 670 forms the final segment.

[0193] In an exemplary scenario, factory status information may be collected and analyzed by the host QQ 602. As another example, the host QQ 602 may process audio and video data, possibly obtained from UEs, for use in generating maps. As another example, the host QQ 602 may collect and analyze real-time data to assist in vehicular congestion control (e.g., traffic light control). As another example, the host QQ 602 may store surveillance video uploaded by UEs. As another example, the host QQ 602 may store or control access to media content, such as video, audio, VR, or AR, that can be broadcast, multicast, or unicast to UEs. As another example, the host QQ 602 may provide energy pricing, remote control of non-time-critical power loads for balancing power generation needs, location services, presentation services (using data collected from remote devices), and other services. Diagram (e.g., editing of a website), or any other function that collects, retrieves, stores, analyzes, and / or transmits data.

[0194] In some examples, measurement procedures may be provided to monitor data rates, latency, and other factors that may be improved by one or more embodiments. There may also be optional network functionality for reconfiguring the OTT connection QQ650 between host QQ602 and UEQQ606 in response to fluctuations in the measurements. The measurement procedures and / or network functionality for reconfiguring the OTT connection may be implemented in software and hardware in host QQ602 and / or UEQQ606. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection QQ650 passes, and these sensors may participate in the measurement procedures by providing values ​​for the monitored quantities exemplified above or other physical quantities from which the monitored quantities may be calculated or estimated by software. Reconfiguration of the OTT connection QQ650 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not directly alter the operation of network node QQ604. Such procedures and functionality may be known or practiced in the art. In one embodiment, the measurements may involve proprietary UE signaling that facilitates measurements by the host QQ 602 of throughput, propagation time, latency, etc. The measurements may be implemented by software using the OTT connection QQ 650 to send messages, specifically empty or "dummy" messages, while monitoring propagation time, errors, etc.

[0195] While the computing devices (e.g., UEs, network nodes, hosts) described herein may include combinations of the illustrated hardware components, other embodiments may include computing devices with different combinations of components. It should be understood that the computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, transforming the obtained information into other information, comparing the obtained or transformed information with information stored at a network node, and / or performing one or more operations based on the obtained or transformed information, and making a decision as a result of that processing. Moreover, while components are depicted as a single box located within a larger box or nested within multiple boxes, in reality, the computing device may include multiple different physical components that make up the illustrated single component, and functionality may be partitioned among the separate components. For example, a communication interface may be configured to include any of the components described herein, and the functionality of those components may be partitioned between the processing circuitry and the communication interface. In other examples, the computationally less intensive functions of any of these components may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0196] In some embodiments, some or all of the functionality described herein may be provided by a processing circuit executing instructions stored in a memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by a processing circuit, such as in a hardwired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of these specific embodiments, the processing circuit can be configured to perform the described functionality regardless of whether it executes instructions stored on a non-transitory computer-readable storage medium. Benefits provided by such functionality are not limited to just the processing circuit or other components of the computing device, but are enjoyed by the computing device as a whole and / or by end users and wireless networks in general.

[0197] A list of embodiments is provided below. 1. A method performed by a UE (User Equipment), comprising: It includes the condition for PSCell (Primary Secondary Cell) success report, and which of multiple network nodes performs the PSCell change procedure. start receiving a PSCell success report setting indicating whether the PSCell has been successfully During the PSCell modification procedure, based on satisfying a condition defined by the PSCell success report configuration (220), storing (230) measurements related to the PSCell modification procedure in a PSCell success report, the measurements being performed according to the PSCell success report configuration; storing information in the PSCell success report indicating which of the plurality of network nodes initiated the PSCell modification procedure (240); A method comprising:

[0198] 2. The method of embodiment 1, comprising: The method further includes reporting (250) the availability of the PSCell success report to one of the plurality of network nodes.

[0199] 3. The method of embodiment 1 or 2, A method wherein storing (240) the information indicating which of the plurality of network nodes initiated the PSCell change procedure in the PSCell success report is performed in response to determining that the PSCell change procedure was initiated by a MN (master node).

[0200] 4. The method of embodiment 1 or 2, The method wherein storing (240) the information indicating which of the plurality of network nodes initiated the PSCell modification procedure in the PSCell success report includes storing a flag in the PSCell success report indicating whether the PSCell modification procedure was initiated by an MN (master node) or an SN (secondary node) of the plurality of network nodes.

[0201] 5. The method of any one of embodiments 1 to 4, further comprising: storing a flag in the PSCell success report based on the PSCell modification procedure being initiated by a predetermined one of an MN (master node) and an SN (secondary node) of the plurality of network nodes, wherein the presence of the flag in the PSCell success report indicates that the predetermined one of the MN and the SN has initiated the PSCell modification procedure; not storing the flag in the PSCell success report based on the PSCell modification procedure being initiated by the other of the MN and SN, wherein the absence of the flag in the PSCell success report indicates that the other of the MN and SN has initiated the PSCell modification procedure; The method further comprises:

[0202] 6. The method of any one of embodiments 1 to 5, further comprising: The method further includes storing (240) at least one of source PSCell information, target PSCell information, and source PCell (primary cell) information at the timing of the PSCell change procedure in the PSCell success report based on satisfying the condition.

[0203] 7. The method of embodiment 6, comprising: Storing the information indicating which of the plurality of network nodes initiated the PSCell modification procedure in the PSCell success report (240), A method comprising, in response to determining that the PSCell change procedure is initiated by an MN (master node), storing source PSCell information and target PSCell information in the PSCell success report without storing source PCell information.

[0204] 8. The method of embodiment 6, comprising: Storing the information indicating which of the plurality of network nodes initiated the PSCell modification procedure in the PSCell success report (240), A method comprising, in response to determining that the PSCell change procedure is initiated by an MN (master node) or an SN (secondary node), storing source PCell information in the PSCell success report without storing source PSCell information and target PSCell information.

[0205] 9. A method performed by a network node of a plurality of network nodes, the method comprising: sending (320) a PSCell success report configuration to a UE (User Equipment), the PSCell success report configuration including a condition for a PSCell (Primary Secondary Cell) success report and indicating which of the plurality of network nodes initiated a PSCell modification procedure; A method comprising:

[0206] 10. The method of embodiment 9, comprising: The network node is a target SN (secondary node), and the method comprises: receiving (310) an indication from a source MN (master node) of which of the plurality of network nodes initiated the PSCell modification procedure; generating (320) the PSCell success report configuration to include the indication of which of the plurality of network nodes initiated the PSCell modification procedure; The method further comprises:

[0207] 11. The method of embodiment 10, further comprising: The method, wherein the indication received (310) from the source MN includes a flag indicating whether the PSCell change procedure was initiated by an MN or an SN (secondary node) among the plurality of network nodes.

[0208] 12. The method of any of embodiments 9-11, further comprising: determining that the PSCell change procedure has been initiated by a selected one of the MN (master node) and the SN (secondary node) of the plurality of network nodes based on receiving a flag from a source MN (master node); determining that the PSCell change procedure has been initiated by the other of the MN and the SN based on not receiving the flag from the source MN; The method further comprises:

[0209] 13. The method of any of embodiments 9-12, further comprising: The method, wherein an indication of which of the plurality of network nodes initiated the PSCell modification procedure is received from a source MN in a SN (Source Node) Addition Request message.

[0210] 14. The method of any of embodiments 9-13, further comprising: The method, wherein the PSCell success report configuration is sent in an RRC (Radio Resource Control) configuration message.

[0211] 15. The method of any of embodiments 9-14, further comprising: The network node is a source MN (master network node), and the method comprises: The method further includes generating the PSCell success report configuration to include an indicator that identifies the source MN (master node) that initiated the PSCell modification procedure.

[0212] 16. The method of any of embodiments 9-14, further comprising: The network node is a source MN (master network node), and the method comprises: The method further includes, when the PSCell success report setting is set by a source SN (secondary node), the source MN receiving an indication from the source SN that the source SN has initiated the PSCell change procedure.

[0213] 17. The method of any of embodiments 9 to 16, further comprising: The method further includes receiving (330) an indication from the UE that the PSCell success report is available.

[0214] 18. The method of any of embodiments 9 to 17, further comprising: The method further includes fetching (340) the PSCell success report from the UE.

[0215] 19. The method of embodiment 18, further comprising: The method further includes distributing (350) the PSCell success report to other network nodes based on an indication in the PSCell success report of which of the plurality of network nodes initiated the PSCell modification procedure.

[0216] 20. The method of embodiment 19, The method, wherein the PSCell success report includes PCell information, and the other network node is selected to receive delivery of the PSCell success report based on the PCell information.

[0217] 21. A UE (User Equipment) (QQ112A-QQ112D), It includes the condition of PSCell (Primary Secondary Cell) success report, and which of multiple network nodes (QQ110A, QQ110B, QQ108) performs the PSCell change procedure. start receiving a PSCell success report setting indicating whether the During a PSCell change procedure, based on satisfying the conditions defined by the PSCell success report configuration, storing measurements related to the PSCell modification procedure in a PSCell success report, the measurements being performed according to the PSCell success report configuration; storing information in a PSCell success report indicating which of the plurality of network nodes initiated the PSCell modification procedure; The UE is configured to:

[0218] 22. The UE (QQ112A-QQ112D) of embodiment 21, A UE further configured to perform the method of any of embodiments 2 to 8.

[0219] 23. A UE (User Equipment) (QQ112A-QQ112D), At least one processor (QQ202) and and at least one memory (QQ210) storing instructions executable by said at least one processor to perform operations, said operations comprising: It includes the condition of PSCell (Primary Secondary Cell) success report, and which of multiple network nodes (QQ110A, QQ110B, QQ108) performs the PSCell change procedure. start receiving a PSCell success report setting indicating whether the During a PSCell change procedure, based on satisfying the conditions defined by the PSCell success report configuration, storing measurements related to the PSCell modification procedure in a PSCell success report, the measurements being performed according to the PSCell success report configuration; storing information in a PSCell success report indicating which of the plurality of network nodes initiated the PSCell modification procedure; The UE is what performs this.

[0220] 24. The UE (QQ112A-QQ112D) of embodiment 23, The UE, wherein the operation further performs the method of any one of embodiments 2 to 8.

[0221] 25. A computer program product including a non-transitory computer-readable medium (QQ210) storing instructions executable by at least one processor of a UE (User Equipment) (QQ112A-QQ112D) to perform operations, said operations including: and at least one memory (QQ210) storing instructions executable by said at least one processor to perform operations, said operations comprising: It includes the condition of PSCell (Primary Secondary Cell) success report, and which of multiple network nodes (QQ110A, QQ110B, QQ108) performs the PSCell change procedure. start receiving a PSCell success report setting indicating whether the During a PSCell change procedure, based on satisfying the conditions defined by the PSCell success report configuration, storing measurements related to the PSCell modification procedure in a PSCell success report, the measurements being performed according to the PSCell success report configuration; storing information in a PSCell success report indicating which of the plurality of network nodes initiated the PSCell modification procedure; A computer program product that performs the following:

[0222] 26. The computer program product of embodiment 25, 9. A computer program product, wherein the operations further perform the method of any of embodiments 2 to 8.

[0223] 27. A network node (QQ110A, QQ110B, QQ108) among a plurality of network nodes, wherein the network node: and a condition for a PSCell (Primary Secondary Cell) success report, wherein any of the plurality of network nodes performs a PSCell change procedure. start A network node configured to send a PSCell success report configuration to a UE (User Equipment) (QQ112A-QQ112D) indicating whether the PSCell has been successfully configured.

[0224] 28. A network node (QQ110A, QQ110B, QQ108) according to embodiment 27, 21. A network node further configured to perform the method of any of embodiments 10 to 20.

[0225] 29. A network node (QQ110A, QQ110B, QQ108) among a plurality of network nodes, wherein the network node: At least one processor (QQ302) and and at least one memory (QQ304) storing instructions executable by said at least one processor to perform operations, said operations comprising: and a condition for a PSCell (Primary Secondary Cell) success report, wherein any of the plurality of network nodes performs a PSCell change procedure. start A network node that transmits a PSCell success report configuration to a UE (User Equipment) (QQ112A-QQ112D) indicating whether the PSCell has been successfully configured.

[0226] 30. A network node (QQ110A, QQ110B, QQ108) according to embodiment 29, 21. A network node further configured to perform the method of any of embodiments 10 to 20.

[0227] 31. A computer program product including a non-transitory computer-readable medium (QQ304) storing instructions executable by at least one processor of a network node (QQ110A, QQ110B, QQ108) to perform operations, said operations comprising: It includes conditions for PSCell (Primary Secondary Cell) success reporting, and which of multiple network nodes performs the PSCell change procedure start A computer program product for transmitting a PSCell success report setting to a UE (User Equipment) (QQ112A-QQ112D) indicating whether the PSCell has been successfully configured.

[0228] 32. The computer program product of embodiment 31, 21. A computer program product, the operations of which further perform the method of any of embodiments 10 to 20.

[0229] Various terms used herein are listed below along with their abbreviations. CPC Conditional PSCell Change CGI Cell Global Identity MN Master Node PCell Primary Cell PSCell Primary Secondary Cell Group Cell RAN Radio Access Network SCell Secondary Cell SHR Successful Handover Report SN Secondary Node UE User Equipment

Claims

1. A method performed by a UE (User Equipment), comprising: receiving (210) a PSCell (primary secondary cell group cell) success reporting configuration including a condition for a PSCell (primary secondary cell group cell) success reporting; During a PSCell modification procedure, based on satisfying a condition defined by the PSCell success reporting configuration (220), storing (240) information in a PSCell success report indicating which of a plurality of network nodes initiated the PSCell modification procedure; A method comprising:

2. 10. The method of claim 1, The method further includes storing (230) measurements related to the PSCell change procedure in the PSCell success report.

3. 3. The method of claim 1 or 2, The received PSCell report configuration indicates which of a plurality of network nodes initiated a PSCell modification procedure.

4. 4. The method according to any one of claims 1 to 3, The method further includes reporting (250) the availability of the PSCell success report to one of the plurality of network nodes.

5. 5. The method according to any one of claims 1 to 4, Storing (240) the information indicating which of the plurality of network nodes initiated the PSCell change procedure in the PSCell success report is performed in response to determining that the PSCell change procedure was initiated by a MN (master node).

6. 5. The method according to any one of claims 1 to 4, Storing (240) the information indicating which of the plurality of network nodes initiated the PSCell change procedure in the PSCell success report includes storing a flag in the PSCell success report indicating whether the PSCell change procedure was initiated by a MN (master node) or an SN (secondary node) of the plurality of network nodes.

7. 7. The method according to any one of claims 1 to 6, storing a flag in the PSCell success report based on the PSCell change procedure being initiated by a predetermined one of a MN (master node) and a SN (secondary node) of the plurality of network nodes, wherein the presence of the flag in the PSCell success report indicates that the predetermined one of the MN and SN has initiated the PSCell change procedure; not storing the flag in the PSCell success report based on the PSCell change procedure being initiated by the other of the MN and SN, wherein the absence of the flag in the PSCell success report indicates that the other of the MN and SN has initiated the PSCell change procedure; The method further comprises:

8. 10. The method of claim 1, Storing (240) the information indicating which of the plurality of network nodes initiated the PSCell modification procedure in the PSCell success report, In response to determining that the PSCell change procedure was initiated by a MN (master node), the method includes storing source PSCell information and target PSCell information in the PSCell success report without storing source PCell information.

9. 10. The method of claim 1, Storing (240) the information indicating which of the plurality of network nodes initiated the PSCell modification procedure in the PSCell success report, The method includes, in response to determining that the PSCell change procedure was initiated by a MN (master node) or an SN (secondary node), storing source PSCell information and target PSCell information in the PSCell success report without storing source PCell information.

10. 1. A method performed by a network node of a plurality of network nodes, the method comprising: sending (320) a PSCell (Primary Secondary Cell Group Cell) success reporting configuration to a UE (User Equipment), the PSCell success reporting configuration including conditions for a PSCell (Primary Secondary Cell Group Cell) success reporting; A method comprising:

11. 11. The method of claim 10, The method, wherein the PSCell success report configuration indicates which of the plurality of network nodes initiated a PSCell modification procedure.

12. 12. The method of claim 10 or 11, The network node is a target SN (Secondary Node), and the method comprises: receiving (310) an indication from a source MN (master node) of which of the plurality of network nodes initiated the PSCell change procedure; generating (320) the PSCell success report configuration to include the indication of which of the plurality of network nodes initiated the PSCell modification procedure; The method further comprises:

13. 13. The method of claim 12, The method, wherein the indication received (310) from the source MN includes a flag indicating whether the PSCell change procedure was initiated by an MN or by a secondary node (SN) among the plurality of network nodes.

14. 14. The method according to any one of claims 10 to 13, determining that the PSCell change procedure has been initiated by a selected one of the MN (master node) and the SN (secondary node) of the plurality of network nodes based on receiving a flag from a source MN (master node); determining that the PSCell change procedure has been initiated by the other of the MN and the SN based on not receiving the flag from the source MN; The method further comprises:

15. 15. The method of any one of claims 10 to 14, The method, wherein an indication of which of the plurality of network nodes initiated the PSCell modification procedure is received from a source MN in an SN (Source Node) Addition Request message.

16. 16. The method of any one of claims 10 to 15, The PSCell success report configuration is sent in an RRC (Radio Resource Control) configuration message.

17. 17. The method of any one of claims 10 to 16, The network node is a source MN (master network node), and the method comprises: The method further includes generating the PSCell success report configuration to include an indicator that identifies the source MN (master node) that initiated the PSCell change procedure.

18. 17. The method of any one of claims 10 to 16, The network node is a source MN (master network node), and the method comprises: The method further includes, when the PSCell success report setting is set by a source SN (secondary node), the source MN receiving an indication from the source SN that the source SN has initiated the PSCell change procedure.

19. 19. The method of any one of claims 10 to 18, The method further includes receiving (330) an indication from the UE that the PSCell success report is available.

20. 20. The method of any one of claims 10 to 19, The method further includes fetching (340) the PSCell success report from the UE.

21. 21. The method of claim 20, The method further includes: delivering (350) the PSCell success report to other network nodes based on an indication in the PSCell success report of which of the plurality of network nodes initiated the PSCell modification procedure.

22. 22. The method of claim 21, The method, wherein the PSCell success report includes PCell information, and the other network node is selected to receive delivery of the PSCell success report based on the PCell information.

23. A UE (User Equipment) (QQ112A-QQ112D), receiving a PSCell (Primary Secondary Cell Group cell) success reporting configuration including a condition for a PSCell (Primary Secondary Cell Group cell) success reporting; During a PSCell modification procedure, based on satisfying the conditions defined by the PSCell success reporting configuration, storing information in a PSCell success report indicating which of a plurality of network nodes initiated the PSCell modification procedure; The UE is configured to:

24. 24. The UE (QQ112A-QQ112D) of claim 23, 10. A UE further configured to perform the method of any one of claims 2 to 9.

25. A UE (User Equipment) (QQ112A-QQ112D), At least one processor (QQ202); and at least one memory (QQ210) storing instructions executable by said at least one processor to perform operations, said operations comprising: receiving a PSCell (Primary Secondary Cell Group cell) success reporting configuration including a condition for a PSCell (Primary Secondary Cell Group cell) success reporting; During a PSCell modification procedure, based on satisfying the conditions defined by the PSCell success reporting configuration, storing information in a PSCell success report indicating which of a plurality of network nodes initiated the PSCell modification procedure; The UE performs the above.

26. 26. The UE (QQ112A-QQ112D) of claim 25, The UE, wherein the operation further comprises performing a method according to any one of claims 2 to 9.

27. A computer program product including a non-transitory computer-readable medium (QQ210) storing instructions executable by at least one processor of a UE (User Equipment) (QQ112A-QQ112D) to perform operations, said operations comprising: and at least one memory (QQ210) storing instructions executable by said at least one processor to perform operations, said operations comprising: receiving a PSCell (Primary Secondary Cell Group cell) success reporting configuration including a condition for a PSCell (Primary Secondary Cell Group cell) success reporting; During a PSCell modification procedure, based on satisfying the conditions defined by the PSCell success reporting configuration, storing information in a PSCell success report indicating which of a plurality of network nodes initiated the PSCell modification procedure; A computer program product that performs the following:

28. 28. A computer program product according to claim 27, comprising:

10. A computer program product, the operations of which further comprise performing the method of any one of claims 2 to 9.

29. A network node (QQ110A, QQ110B, QQ108) among a plurality of network nodes, wherein the network node is A network node configured to send a PSCell (Primary Secondary Cell Group Cell) success reporting configuration to a UE (User Equipment) (QQ112A-QQ112D), the PSCell success reporting configuration including conditions for a PSCell (Primary Secondary Cell Group Cell) success reporting.

30. A network node (QQ110A, QQ110B, QQ108) according to claim 29, A network node further configured to perform the method of any one of claims 11 to 21.

31. A network node (QQ110A, QQ110B, QQ108) among a plurality of network nodes, wherein the network node is At least one processor (QQ302); and at least one memory (QQ304) storing instructions executable by said at least one processor to perform operations, said operations comprising: A network node that transmits a PSCell (Primary Secondary Cell Group Cell) success report configuration including conditions for a PSCell (Primary Secondary Cell Group Cell) success report to a UE (User Equipment) (QQ112A-QQ112D).

32. A network node (QQ110A, QQ110B, QQ108) according to claim 31, A network node further configured to perform the method of any one of claims 11 to 21.

33. A computer program product including: a non-transitory computer-readable medium (QQ304) storing instructions executable by at least one processor of a network node (QQ110A, QQ110B, QQ108) to perform operations, said operations comprising: A computer program product for transmitting a PSCell (Primary Secondary Cell Group Cell) success report configuration including conditions for a PSCell (Primary Secondary Cell Group Cell) success report to a UE (User Equipment) (QQ112A-QQ112D).

34. 34. A computer program product according to claim 33, comprising:

22. A computer program product, the operations of which further comprise performing the method of any one of claims 11 to 21.

Images