Successful PSCell report transfer

Abstract

A method and system for transmitting a Successful Primary Secondary Cell (PSCell) Report (SPR) and for indicating the availability of an SPR are described. In some embodiments, a first network node can receive SPR availability information from a UE. The first network node can then fetch the SPR from the UE and analyze whether the SPR should be shared with another network node. The SPR can then be shared if deemed necessary or appropriate.

Description

Technical Field

[0001] Cross - reference to related information This application claims the benefit of U.S. Priority Application No. 63 / 410,505, filed on September 27, 2022, entitled "Successful PSCell Report Transfer".

[0002] This disclosure generally relates to the field of wireless communication, and more particularly, to PSCell changes.

Background Art

[0003] Wireless communication system in 3GPP FIG. 1 shows a simplified wireless communication system in which there is a user equipment (UE) 102 that communicates with one or more access nodes 103 - 104, and the one or more access nodes 103 - 104 are connected to a network node 106. The access nodes 103 - 104 are part of a radio access network (RAN) 100.

[0004] In a wireless communication system that complies with the 3GPP evolved packet system (EPS) standard specifications (also called Long Term Evolution (LTE) or 4G) and related specifications as specified in 3GPP TS36.300, the access nodes 103 - 104 generally correspond to evolved Node Bs (eNBs), and the network node 106 generally corresponds to either a mobility management entity (MME) and / or a serving gateway (SGW). The eNB is part of the radio access network 100, and in this case, the radio access network 100 is an E - UTRAN (Evolved Universal Terrestrial Radio Access Network), and both the MME and the SGW are part of the EPC (Evolved Packet Core Network). The eNBs are interconnected via the X2 interface and connected to the EPC via the S1 interface, more specifically, connected to the MME via S1 - C and to the SGW via S1 - U.

[0005] On the other hand, in a radio communication system that conforms to the 3GPP 5G System (5GS) standard specification (also known as New Radio (NR) or 5G), and related specifications, as specified in 3GPP TS38.300, access nodes 103-104 generally correspond to 5G Node B (gNB), and network node 106 generally corresponds to either Access and Mobility Management Function (AMF) and / or User Plane Function (UPF). The gNB is part of the radio access network 100, which in this case is the NG-RAN (Next Generation Radio Access Network), and both the AMF and UPF are part of the 5G Core Network (5GC). The gNB is interconnected via the Xn interface, connected to the 5GC via the NG interface, and more specifically to the AMF via NG-C and to the UPF via NG-U.

[0006] To support high-speed mobility between NR and LTE and to avoid changes to the core network, LTE eNBs can also be connected to 5G-CN via NG-U / NG-C and support the Xn interface. eNBs connected to 5GC are called next-generation eNBs (ng-eNBs) and are considered part of NG-RAN. LTE connected to 5GC is not described further in this disclosure, but it should be noted that most of the solutions / features described for LTE and NR in this disclosure also apply to LTE connected to 5GC. In this disclosure, the term LTE refers to LTE-EPC when used unless further specified.

[0007] Self-organizing networks in 3GPP Self-organizing networks (SONs) are automated technologies designed to make planning, configuring, managing, optimizing, and repairing mobile radio access networks easier and faster. SON functions and behaviors are defined and specified in generally accepted mobile industry recommendations generated by organizations such as 3GPP (Third Generation Partnership Project) and NGMN (Next Generation Mobile Networks).

[0008] In 3GPP, processes within a SON area are classified into self-configured processes and self-optimized processes. Self-configured processes are those in which newly deployed nodes are configured by an automated installation procedure to obtain the necessary basic settings for system operation.

[0009] This process operates in a pre-operational state. The pre-operational state is understood as the state from when the eNB is powered on and has backbone connectivity until the RF transmitter is switched on.

[0010] As shown in Figure 2, the following functions handled in the pre-operation state, namely basic setup and initial wireless configuration, are covered by the self-configuration process.

[0011] The self-optimization process is defined as a process in which UE and access node measurements and performance measurements are used to automatically tune the network. The self-optimization process operates in the operational state, which is understood as a state in which the RF interface is further switched on.

[0012] As illustrated in Figure 2, the following functions handled in the operating state, namely optimization / adaptation, are covered by the self-optimization process.

[0013] LTE specifies support for self-configuration and self-optimization, as described in 3GPP TS36.300 Section 22.2, including features such as dynamic configuration, automatic neighbor relations (ANR), mobility load balancing, mobility robustness optimization (MRO), and RACH optimization and support for energy saving.

[0014] NR similarly specifies support for self-configuration and self-optimization, starting with self-configuration features such as dynamic configuration and automatic neighbor relations (ANR) in Rel-15, as described in 3GPP TS38.300 Section 15. NR Rel-16 specifies more SON features, including self-optimization features such as mobility robustness optimization (MRO).

[0015] Successful handover report The Successful Handover (HO) Report (SHR) is standardized as part of 3GPP Rel17 TS; see, for example, RRC Specification 38.331 (V17.0.0). The primary purpose of the Successful HO Report is to enable network nodes to infer the suboptimal performance of the underlying procedures performed during the HO procedure.

[0016] If a network node is interested in SHRs, it can configure the UE to report an SHR after a successful execution of an HO if at least one of the SHR trigger conditions / thresholds is met. The SHR trigger thresholds are defined as follows: • Whether the T304 timer value exceeded a certain threshold (thresholdPercentageT304) during a successful HO execution. • Whether the T310 timer value exceeded a certain threshold (thresholdPercentageT310) during a successful HO execution. • Whether the T312 timer value exceeded a certain threshold (thresholdPercentageT312) during a successful HO execution. • Whether the UE experienced an RLF on the source node while performing DAPS HO (sourceDAPS-FailureReporting).

[0017] When a successful handover report is recorded, the UE may include various pieces of information to help the network optimize the handover, such as neighbor cell measurements and the conditions that triggered the successful handover report (e.g., a threshold being exceeded for T310, or a specific RLF issue in the source while performing a DAPS HO).

[0018] An SHR can be set by a serving cell, and when the trigger conditions for SHR logging are met, the UE stores the information until the NW requests it. In particular, the UE may indicate the availability of SHR information in certain RRC messages such as RRCReconfigurationComplete, RRCReestablishmentComplete, RRCSetupComplete, and RRCResumeComplete, and the network may request such information via a UEInformationRequest message, at which point the UE sends the stored SHR in a UEInformationResponse message.

[0019] Multi-wireless dual connectivity Multi-radio dual connectivity (MR-DC), as described in TS37.340, describes a scenario in which a UE capable of connecting to multiple nodes utilizes multiple resources to increase throughput. This is a generalization of dual connectivity within E-UTRA (Extended Universal Terrestrial Radio Access), as described in TS36.300.

[0020] When the UE is in DC mode, one node acts as the master node (MN) and the other node acts as the secondary node (SN). The MN and SN are connected via a network interface, and at least the MN is connected to the core network. More details about MR-DC can be found in TS38.401. The primary cell in the MN is known as the PCell, and the primary cell in the SN is known as the PSCell.

[0021] Successful PSCell Reports (SPRs) The ongoing rel-18 work item, "New WID on Further Enhancements to Data Acquisition for SON (Self-Organizing Network) / MDT (Drive Test Minimization) in NR Standalone and MR-DC (Multi-Radio Dual Connectivity)," aims to support SON / MDT enhancements for successful PScell ​​change reporting.

[0022] A successful PScell ​​(change) report, or SPR, may have the same characteristics as an SHR described above, but is related to PSCell change / addition events. This means that if an event set up by the network is triggered during a PSCell change or addition, the UE will generate an SPR. The UE will provide the network with the existence of the SPR, and the network will fetch the SPR in return. Network signaling will then be used to send the SPR to the node that set up the event that triggered its creation. This SPR will ultimately be used by the network nodes to optimize PSCell changes / additions.

[0023] Currently, there are several issues. Contrary to SHR, SPR can be MN-initiated or SN-initiated for PSCell changes and thus can be useful for both MN optimization and SN optimization. Therefore, even when the SHR design is taken as the baseline for SPR, some questions still remain unresolved. It is not clear whether the SN will be able to fetch the SPR or how it will be able to do so. Also, if the SN will be able to fetch the SPR, it is not clear how the SPR will be sent to the MN. It is also not clear how the SPR availability will be signaled to the network. Further, when the SPR availability is signaled only to the SN at the completion of the RRC reconfiguration, it is not clear how the MN will know when / how to fetch the SPR. These questions need to be answered and the corresponding solutions need to be standardized.

Summary of the Invention

[0024] One embodiment under the present disclosure includes a method implemented by a UE for indicating the availability of an SPR. The method includes providing SPR availability information to a network node. The method also optionally includes transmitting the SPR to the network node.

[0025] Another embodiment of the method under the present disclosure is a method implemented by a first network node for transmitting an SPR. The method includes receiving SPR availability information from a UE, fetching the SPR from the UE, analyzing the received SPR and determining that the SPR needs to be transferred to a second network node. The method further optionally includes transmitting the SPR to the second network node.

[0026] Further embodiments below of the present disclosure include a method implemented by a first network node for indicating the availability of an SPR. The method includes receiving SPR availability information from a UE and sending an indication to a second network node that the SPR is available at the UE. The method may optionally further include receiving the SPR from the second network node.

[0027] Further embodiments below of the present disclosure include a method implemented by a first network node for receiving an SPR. The method includes receiving from a second network node an indication that the SPR is available at a UE, fetching the SPR from the UE, and analyzing the fetched SPR to detect whether the SPR should be sent to the second network node. The method may optionally further include sending the SPR to the second network node.

[0028] The summary of the present invention is provided to introduce, in a simplified form, a selection of concepts that are further described below in the detailed description for implementing the invention. The summary of the present invention is not intended to identify the key features or essential features of the claimed subject matter, nor is it intended to be used as an indication of the scope of the claimed subject matter.

[0029] For a more complete understanding of the present disclosure, reference is now made to the following description taken in conjunction with the accompanying drawings.

Brief Description of the Drawings

[0030] [Figure 1] A diagram showing a simplified wireless communication system. [Figure 2] A diagram showing self-configuration and self-optimization functions. [Figure 3] A flowchart of a method embodiment under the present disclosure. [Figure 4] A flowchart of a method embodiment under the present disclosure. [Figure 5]This is a flowchart of a method embodiment under the present disclosure. [Figure 6] This figure shows one embodiment of messaging under the present disclosure. [Figure 7] This is a flowchart of a method embodiment under the present disclosure. [Figure 8] This is a flowchart of a method embodiment under the present disclosure. [Figure 9] This is a flowchart of a method embodiment under the present disclosure. [Figure 10] This is a flowchart of a method embodiment under the present disclosure. [Figure 11] This is a flowchart of a method embodiment under the present disclosure. [Figure 12] This is a schematic diagram of an embodiment of a communication system under the present disclosure. [Figure 13] This is a schematic diagram of a user device embodiment under the present disclosure. [Figure 14] This is a schematic diagram of a network node embodiment under the present disclosure. [Figure 15] This is a schematic diagram of a host embodiment under the present disclosure. [Figure 16] This is a schematic diagram of an embodiment of a virtualization environment under this disclosure. [Figure 17] This figure shows a schematic representation of one embodiment of communication between a node, a host, and user equipment under this disclosure. [Modes for carrying out the invention]

[0031] Before describing in detail the various embodiments of this disclosure, it should be understood that this disclosure is not limited to the parameters of the systems, methods, apparatus, products, processes, and / or kits illustrated in detail, and that such parameters may, of course, vary. Therefore, while some embodiments of this disclosure are described in detail with respect to specific settings, parameters, components, elements, etc., the descriptions are illustrative and should not be construed as limiting the scope of the claimed embodiments. Furthermore, the terms used herein are for the purpose of describing embodiments and are not necessarily intended to limit the scope of the claimed embodiments.

[0032] Some aspects of this disclosure and their embodiments may provide solutions to the problems identified above or other problems. Some possible embodiments include: • If the SN fetches the SPR and the PSCell change was MN-initiated, it sends the SPR to the MN. • The UE instructs the MN on SPR availability in the following message: • SN signals to MN that SPR should be fetched, and • The MN fetches the SPR, and if the PSCell change was SN-initiated, it sends the SPR to the SN.

[0033] These embodiments, as well as some of the other embodiments and variations contemplated herein, will be described more thoroughly with reference to the accompanying drawings. The embodiments are provided, by example, to convey the scope of the subject to those skilled in the art.

[0034] Some embodiments may provide one or more of the following technical advantages. Under this disclosure and its embodiments, both the MN and SN should be able to receive the SPR when generated by the UE. Furthermore, the SHR design (where the UE notifies the network of SPR availability in the RRCReconfigurationComplete message and the MN fetches the SPR) may or may not be implemented by the user or network, as required.

[0035] In this disclosure, the terms network node and RAN node are used interchangeably. Furthermore, the terms MN and SN may differ from the UE's perspective, i.e., the same network node may act as both an MN and an SN simultaneously for different UEs. Successful PSCell reporting refers to reporting from a UE in response to a successful PSCell reporting configuration, and may have different names in some systems and embodiments.

[0036] SN fetches SPR (MN-initiated PSCell modification) In some embodiments, the SN fetches the SPR and sends it to the MN if the PSCell change was MN-initiated. The techniques taken under these embodiments include the possibility that the SN fetches and analyzes the SPR, for example, the part in which the SN determines whether the SPR should be forwarded by analyzing the triggers contained within the SPR. Another embodiment is a new inter-node signaling for forwarding the SPR from the SN to the MN, particularly via UE-related signaling. Figure 3 shows a possible method embodiment 400, including steps from the perspective of SN 402, UE 401, and MN 403.

[0037] Under Method 400, one aspect may include steps performed by a network node acting as an SN for the UE in dual connectivity operation. Step 410 is to receive SPR availability information from the UE. Step 420 is to fetch the SPR from the UE. Step 430 is to analyze the received SPR and determine that the SPR should be forwarded to the MN. Step 440 is to forward the SPR to the MN.

[0038] One alternative embodiment under Method 400 includes a step performed by a network node acting as the master node (MN) for the UE in dual connectivity operation. Step 480 is to receive the SPR from the SN.

[0039] Another aspect of Method 400 may include steps performed by the UE in dual connectivity operation. Step 460 is to provide SPR availability information to the SN. Step 470 is to send the SPR to the SN, or alternatively, to have the SN fetch the SPR.

[0040] Each of these method steps described above may include different variations.

[0041] Steps 410 / 460, receiving / providing SPR availability information from the UE to the SN, may include different variations. In one embodiment, SPR information availability is included in the RRCReconfigurationComplete message. In one variation, the RRCReconfigurationMessage may be sent directly from the UE to the SN (via SRB3). In another variation, the RRCReconfigurationMessage may be sent from the MN to the SN via the MN (if received by the MN via SRB1) in the S-node reconfiguration complete message. In another embodiment, SPR information availability is included in an RRC message, for example, the ULInformationTransferMRDC message. In one variation, the ULInformationTransferMRDC may be sent directly from the UE to the SN (via SRB3). In another variation, the ULInformationTransferMRDC may be sent from the MN to the SN via the MN (if received by the MN via SRB1) in the S-node reconfiguration complete message. In a further embodiment, SPR information availability is included in the UEAssistanceInformation message. In one variant, UEAssistanceInformation may be sent directly from the UE to the SN (via SRB3). In another variant, UEAssistanceInformation may be sent to the SN through the MN via SRB1. In an additional embodiment, the network node configures the UE how and on which signals, for example, on the RRCReconfigurationComplete message or the UEAssistanceInformation message, the SPR availability instruction should be sent. In one variant, the network requests the UE to send the SPR availability instruction to the SN via the RRCReconfigurationComplete message. In another variant, the network requests the UE to send the SPR availability instruction to the SN via the UEAssistanceInformation message, via SRB1, or via SRB3.

[0042] Step 430, analyzing the received SPR and determining whether the SPR needs to be forwarded to the MN, may include different variations. In one embodiment, the information that the SPR needs to be forwarded to the MN is represented by information that a PSCell change was triggered by the MN, and this information is contained within the SPR itself. In another embodiment, the information that the SPR needs to be forwarded to the MN is represented by one or more triggers contained within the SPR, and these triggers are set by the MN before the SPR is generated. In yet another embodiment, the information that the SPR needs to be forwarded to the MN is represented by a flag that triggers the SN to send the SPR to the MN upon receipt of the SPR via the SRB3.

[0043] Step 440 / 490, forwarding the SPR to the MN, can take on different forms. In one embodiment, UE-related signaling is used, which may include, for example, a new UE-related XnAP message, an XnAP S-Node Modification Required message, or an XnAP RRC forwarding message. In another embodiment, non-UE-related messages are used, which may include, for example, an XnAP access and mobility instruction message, or a new non-UE-related message.

[0044] An example of a possible implementation in TS38.423 of the method 400 shown in Figure 3, which incorporates RRC forwarding, is described below.

[0045] The purpose of the RRC forwarding procedure is to deliver a PDCP-C PDU, which encapsulates an LTE RRC message or an NR RRC message, to an S-NG-RAN node, which is then forwarded to the UE, or, if received from the UE, can be forwarded from the S-NG-RAN node. The delivery status may also be provided from the S-NG-RAN node to the M-NG-RAN node using RRC forwarding.

[0046] The procedure is also used to enable the forwarding of one of the following messages from the M-NG-RAN node to the S-NG-RAN node when received from the UE. • NR RRC message container with NR measurement values, • E-UTRA RRC message container with E-UTRA measurement values, • NR RRC message container containing NR failure information, • NR RRC message container with RRCReconfigurationComplete message, • NR RRC message container with UE support information, • NR RRC message container with PSCell change reporting.

[0047] In the case of RACH-based SDT without UE context relocation, this procedure is also used to deliver PDCP-C PDUs that encapsulate NR RRC messages between the new and old NG-RAN nodes. The procedure can utilize UE-related signaling.

[0048] UE indicates SPR availability. As described above, another embodiment includes the UE instructing the MN on SPR availability in the following message. The technique taken under this embodiment may focus on the UE using an RRC message (e.g., UEInformationTransferMRDC) sent to the MN to notify the MN that an SPR is available. Another embodiment may include the MN analyzing the SPR and determining whether the SPR should be transferred by analyzing the triggers contained within the SPR. Figure 4 shows a possible method embodiment 600, including steps from the perspective of SN602, UE601, and MN603.

[0049] Under one embodiment of Method 600, one aspect may include steps performed by a network node acting as an MN for the UE in dual connectivity operation. Step 610 is to receive SPR availability information from the UE. Step 620 is to fetch the SPR from the UE. Step 630 is to analyze the received SPR and determine that the SPR needs to be transferred to the SN. Step 640 is to transfer the SPR to the SN. Step 610 may include different variations. In one embodiment, the SPR information availability is included in the next RRCReconfigurationComplete message sent to the MN. In another embodiment, the SPR information availability is included in an RRC message, for example, a UEInformationTransferMRDC message. Step 630 may include different variations. In one embodiment, the information that the SPR needs to be transferred to the SN is represented by information that a PSCell change was triggered by the SN, and this information is included in the SPR itself. In another embodiment, the information that an SPR needs to be forwarded to an SN is represented by one or more triggers included in the SPR, which are set by the SN before the SPR is generated. Step 640 may include different variations. In one embodiment, UE-related signaling is used, such as a new UE-related XnAP message, an XnAP S-node modification request message, or an XnAP RRC forwarding message. In another embodiment, a non-UE-related message is used, such as an XnAP access and mobility instruction message, or a new non-UE-related message.

[0050] Another embodiment under Method 600 may include steps performed by the UE in dual connectivity operation. Step 660 is to provide SPR availability information to the MN. Step 670 may be the UE sending the SPR to the MN (or alternatively, allowing the MN to fetch the SPR). Step 660 may include multiple variations. In one embodiment, the SPR information availability is included in the next RRCReconfigurationComplete message sent to the MN. In another embodiment, the SPR information availability is included in an RRC message, for example, a UEInformationTransferMRDC message.

[0051] Another embodiment under Method 600 may include steps performed by a network node acting as an SN for the UE in dual connectivity operation. Step 690 is to receive an SPR from the MN. In one embodiment of step 690, UE-related signaling is used, such as a new UE-related XnAP message, an XnAP S-node correction required message, or an XnAP RRC forwarding message. In another embodiment, a non-UE-related message is used, such as an XnAP access and mobility instruction message, or a new non-UE-related message.

[0052] SN signals MN to fetch SPR. Another embodiment may include the SN signaling to the MN that the SPR should be fetched. The technique under this embodiment may include new internode signaling sent by the SN to inform the MN that the SPR is available in the UE. Alternative embodiments and variations may include, for example, UE-related signaling such as S node modification needed, or the addition of a UE identifier, or internode signaling in which the MN forwards the SPR to the SN along with the UE identifier. Figure 5 shows a possible method embodiment 800, including steps from the perspective of SN802, UE801, and MN803.

[0053] One embodiment under Method 800 includes steps performed by a network node acting as SN802 for UE801 in dual connectivity operation. Step 810 is to receive SPR availability information from the UE. Step 820 is to notify the MN that the SPR is available at the UE. An optional step 830 is to receive the SPR from the MN.

[0054] Another embodiment under Method 800 may include steps performed by a network node acting as an MN for the UE in dual connectivity operation. Step 840 is to receive an instruction from the SN that the SPR is available at the UE. Step 850 is to fetch the SPR from the UE. Step 860 is to analyze the received SPR and determine that the SPR needs to be forwarded to the SN. Step 870 is to forward the SPR to the SN.

[0055] Another embodiment under Method 800 may include steps performed by the UE in dual connectivity operation. Step 880 is to provide SPR availability information to the SN. An optional step 890 may be to send the SPR to the MN in response to an MN request / retrieval.

[0056] Steps 810 / 880 can take various embodiments or variations. In one embodiment, SPR information availability is included in the RRCReconfigurationComplete message. In some variations, the RRCReconfigurationMessage may be sent directly from the UE to the SN (via SRB3), or the RRCReconfigurationMessage may be sent from the MN to the SN via the MN (if received by the MN via SRB1) in the S-node reconfiguration complete message.

[0057] Steps 820 / 840 can take various embodiments or variations. SPR availability notifications / instructions can take multiple forms. In one embodiment, the SPR availability instruction is included in an S-node modification required message. In an alternative embodiment, the SPR availability instruction is included in an access and mobility instruction message along with an identifier that uniquely identifies the UE for which an SPR is available. In yet another alternative embodiment, the SPR availability instruction is included in a new XnAP message sent to the MN (e.g., SON reporting availability). In another embodiment, the SN requests the MN to collect SPRs for a list of UEs that have SPRs. The SN includes a list of UE identifiers in its request to the MN.

[0058] Steps 830 / 870 can take various embodiments or variations. In one embodiment, the SPR is included in the S-node correction confirmation message. In an alternative embodiment, the SPR is included in the access and mobility instruction message along with an identifier that uniquely identifies the UE that generated the SPR.

[0059] Step 860 can take various embodiments or variations. In one embodiment, the information that an SPR needs to be transferred to the SN is represented by the information that a PSCell change was triggered by the SN, and this information is contained within the SPR itself. In another embodiment, the information that an SPR needs to be transferred to the SN is represented by one or more triggers contained within the SPR, and these triggers are set by the SN before the SPR is generated.

[0060] An example of a possible implementation of Method 800 in TS38.423 is shown in Figure 6. Figure 6 shows one embodiment of the access and mobility instruction 1000. This message is sent by NG-RAN node 1 to transfer access and mobility relationship information to NG-RAN node 2. The direction is from NG-RAN node 1 to NG-RAN node 2.

[0061] MN fetches SPR (SN-initiated PSCell modification) Another embodiment may include the MN fetching an SPR and sending it to the SN if necessary, and sending the SPR to the SN if the PSCell change was SN-initiated. Such an embodiment may include the MN focusing on analyzing the SPR and determining whether the SPR needs to be forwarded by analyzing the triggers contained within the SPR. Figure 7 shows a possible method embodiment 1200, including steps from the perspective of SN1202, UE1201, and MN1203.

[0062] One embodiment under Method 1200 includes steps performed by a network node acting as a master node (MN) for a UE in dual connectivity operation. Step 1210 is to receive SPR availability information from the UE. Step 1220 is to fetch the SPR from the UE. Step 1230 is to analyze the received SPR and determine that the SPR needs to be forwarded to the SN. Step 1240 is to forward the SPR to the SN.

[0063] Another embodiment under Method 1200 includes steps performed by a network node acting as an SN. Step 1250 is to receive the SPR from the MN.

[0064] Another embodiment under Method 1200 includes steps performed by the UE. Step 1280 is to provide / notify the MN of SPR availability. An optional step 1290 is to respond to the MN fetching the SPR or to send the SPR to the MN.

[0065] Steps 1210 / 1280 may include different embodiments or variations. In one embodiment, SPR information availability is included in the RRCReconfigurationComplete message. The RRCReconfigurationMessage may be sent directly from the UE to the MN (via SRB1). In another embodiment, SPR information availability is included in an RRC message, for example, the UEInformationTransferMRDC message. The UEInformationTransferMRDC may be sent directly from the UE to the MN (via SRB1).

[0066] Step 1230 may include different embodiments or variations. In one embodiment, the information that an SPR needs to be forwarded to the SN is represented by information that a PSCell change was triggered by the SN, and this information is contained within the SPR itself. In another embodiment, the information that an SPR needs to be forwarded to the SN is represented by one or more triggers contained within the SPR, and these triggers are set by the SN before the SPR is generated. In yet another embodiment, the information that an SPR needs to be forwarded to the SN is represented by a flag that triggers the MN to send the SPR to the SN upon receiving the SPR via the SRB1.

[0067] Steps 1240 / 1250 may include different embodiments or variations. In one embodiment, UE-related signaling is used, such as a new UE-related XnAP message, an XnAP S-node modification request message, or an XnAP RRC forwarding message. In other embodiments, non-UE-related messages are used, such as an XnAP access and mobility instruction message, or a new non-UE-related message.

[0068] Additional Embodiments Possible method embodiments under this disclosure are shown in Figure 8. Method 1400 includes a method implemented by the UE for indicating the availability of SPRs. Step 1410 is to provide SPR availability information to the network node. Method 1400 also optionally includes step 1420, transmitting the SPR to the network node. Method 1400 may include a plurality of variations and embodiments, as well as / or additional and / or alternative steps.

[0069] Another possible embodiment of the method under this disclosure is shown in Figure 9. Method 1600 is a method performed by a first network node for transmitting an SPR. Step 1610 is to receive SPR availability information from the UE. Step 1620 is to fetch the SPR from the UE. Step 1630 is to analyze the received SPR and determine that the SPR should be forwarded to a second network node. Method 1600 further optionally includes step 1640, transmitting the SPR to the second network node. Method 1600 may include a plurality of variations and embodiments, as well as / or additional and / or alternative steps.

[0070] Further possible embodiments under this disclosure are shown in Figure 10. Method 1800 includes a method implemented by a first network node for indicating the availability of an SPR. Step 1810 is to receive SPR availability information from the UE. Step 1820 is to send an indication to a second network node that the SPR is available at the UE. Method 1800 may optionally further include step 1830, receiving the SPR from the second network node. Method 1800 may include a plurality of variations and embodiments, as well as additional and / or alternative steps.

[0071] Further embodiments under this disclosure are shown in Figure 11. Method 2000 includes a method implemented by a first network node for receiving an SPR. Step 2010 is to receive an instruction from a second network node that an SPR is available at the UE. Step 2020 is to fetch the SPR from the UE. Step 2030 is to analyze the fetched SPR and determine whether the SPR should be sent to the second network node. Method 2000 may optionally further include step 2040, sending the SPR to the second network node. Method 2000 may include a plurality of variations and embodiments, as well as / or additional and / or alternative steps. One or more re-selection priorities may be included.

[0072] Figure 12 shows an example of a communication system 2100 according to several embodiments. In this example, the communication system 2100 includes a communication network 2102 which includes an access network 2104 such as a RAN and a core network 2106 which includes one or more core network nodes 2108. The access network 2104 includes one or more access network nodes (one or more of which may generally be referred to as network nodes 2110), such as network nodes 2110a and 2110b, or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Network nodes 2110 facilitate direct or indirect connectivity of UEs, such as by connecting UEs 2112a, 2112b, 2112c, and 2112d (one or more of which may generally be referred to as UE2112) to the core network 2106 over one or more wireless connections.

[0073] Exemplary wireless communication over a wireless connection involves transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without using wires, cables, or other material conductors. Furthermore, in different embodiments, the communication system 1100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals, whether via a wired or wireless connection. The communication system 2100 may include and / or interface with any type of communication, telecommunication, data, cellular, wireless network, and / or other similar types of systems.

[0074] UE2112 may be any of a wide variety of communication devices, including a wireless device configured, set up, and / or operable to communicate wirelessly with network node 2110 and other communication devices. Similarly, network node 2110 is configured, capable, set up, and / or operable to communicate directly or indirectly with UE2112 and / or with other network nodes or devices in communication network 2102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in communication network 2102.

[0075] In the illustrated example, the core network 2106 connects network node 2110 to one or more hosts, such as host 2116. These connections may be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 2106 includes one or more core network nodes (e.g., core network node 2108) structured with hardware and software components. The characteristics of these components may be substantially similar to those described for UEs, network nodes, and / or hosts, and therefore their descriptions are generally applicable to the corresponding components of core network node 2108. An exemplary core network node includes one or more of the following functions: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protected Proxy (SEPP), Network Exposure Function (NEF), and / or User Plane Function (UPF).

[0076] Host 2116 may be owned or under the control of a service provider other than the operator or provider of the access network 2104 and / or the communication network 2102, and may be operated by or on behalf of the service provider. Host 2116 may host a variety of applications to provide one or more services. Examples of such applications include data collection services such as extracting and compiling live and pre-recorded audio / video content, data on various ambient conditions detected by multiple UEs, analytical functions, social media, functions for controlling or possibly interacting with remote devices, functions for alarms and surveillance centers, or any other such functions performed by the server.

[0077] Overall, the communication system 2100 in Figure 12 enables connectivity between the UE, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, including, but not limited to, any other suitable wireless communication standards, such as GSM (Global System for Mobile Communications), 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), wireless local area network (WLAN) standards such as the IEEE 802.11 standard (WiFi), and / or any other suitable wireless communication standards such as global interoperability for microwave access (WiMAX), Bluetooth, Z-Wave, near-field communications (NFC) ZigBee, LiFi, and / or LoRa and Sigfox, or any low-power wide area network (LPWAN) standards.

[0078] In some examples, the communication network 2102 is a cellular network implementing 3GPP standardized features. Therefore, the communication network 2102 may support network slicing to provide different logical networks to different devices connected to the communication network 2102. For example, the communication network 2102 may provide ultra-high reliability low-latency communication (URLLC) services to some UEs while providing extended mobile broadband (eMBB) services to other UEs, and / or also provide massive machine-type communication (mMTC) / massive IoT services to further UEs.

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

[0080] In this example, hub 2114 communicates with access network 2104 to facilitate indirect communication between one or more UEs (e.g., UE2112c and / or 2112d) and a network node (e.g., network node 2110b). In some examples, hub 2114 may be a controller, router, content source and content analysis, or any other communication device described herein with respect to the UE. For example, hub 2114 may be a broadband router that enables access to the core network 2106 for the UE. In another example, hub 2114 may be a controller that sends commands or instructions to one or more actuators in the UE. Commands or instructions may be received from the UE, network node 2110, or by executable code, scripts, processes, or other instructions in hub 2114. In yet another example, hub 2114 may be a data collector acting as temporary storage for UE data, and in some embodiments may perform data analysis or other processing. In yet another example, hub 2114 may be a content source. For example, with respect to a UE that is a VR headset, display, loudspeaker, or other media distribution device, the hub 2114 can retrieve VR assets, video, audio, or other media or data related to sensory information via network nodes, which the hub 2114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In yet another example, the hub 2114 acts as a proxy server or orchestrator for the UE, particularly when one or more of the UEs are low-energy IoT devices.

[0081] Hub 2114 may have always-on / persistent or intermittent connectivity to network node 2110b. Hub 2114 may also enable different communication methods and / or schedules between Hub 2114 and UEs (e.g., UE2112c and / or 2112d), and between Hub 2114 and the core network 2106. In other examples, Hub 2114 connects to the core network 2106 and / or one or more UEs via wired connections. Furthermore, Hub 2114 may be configured to connect to an M2M service provider on the access network 1104 and / or another UE via a direct connection. In some scenarios, a UE may establish a wireless connection with network node 2110 while still being connected via wired or wireless connections through Hub 2114. In some embodiments, Hub 2114 may be a dedicated hub, i.e., a hub whose primary function is to route communications from the UE to network node 2110b and from network node 2110b to the UE. In other embodiments, the hub 2114 may be a non-dedicated hub, i.e., a device that can operate to route communication between the UE and the network node 2110b, but can also operate as a communication start and / or end point for several data channels.

[0082] Figure 13 shows the UE2200 in several embodiments. As used herein, UE refers to a device that is capable of, configured, and / or operable of communicating wirelessly with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), and vehicle-mounted or vehicle-embedded / integrated wireless devices. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine-type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0083] A UE may support device-to-device (D2D) communication by implementing 3GPP standards for sidelink communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE does 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 to be sold to or operated by a human user, but may not be associated with a particular human user, or may not be associated with a particular human user in the first place. Alternatively, a UE may represent a device (e.g., a smart electricity meter) that is not intended to be sold to or operated by an end user, but may be associated with or operate for the benefit of a user.

[0084] The UE2200 includes processing circuitry 2202 operably coupled via bus 2204 to input / output interface 2206, power supply 2208, memory 2210, communication interface 2212, and / or any other components, or any combination thereof. Some UEs may utilize all or a subset of the components shown in Figure 10. The level of integration between components may vary from UE to UE. Furthermore, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, and receivers.

[0085] The processing circuit 2202 is configured to process instructions and data and may be configured to implement any sequential state machine capable of executing instructions stored in memory 2210 as a machine-readable computer program. The processing circuit 2202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.), programmable logic with appropriate firmware, a microprocessor or digital signal processor (DSP) with appropriate software, one or more stored computer programs, a general-purpose processor, or any combination of the above. For example, the processing circuit 2202 may include multiple central processing units (CPUs).

[0086] In this example, the input / output interface 2206 may be configured to provide an input device, an output device, or one or more interfaces to one or more input and / or output 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 allow a user to capture information to the UE2200. 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 pads, trackpads, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors for detecting user input. Sensors may include, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, light sensors, proximity sensors, biosensors, or any combination thereof. Output devices may use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port may be used to provide input and output devices.

[0087] In some embodiments, the power supply 2208 is structured as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The power supply 2208 may further include a power circuit for distributing power from the power supply 2208 itself and / or from an external power source via an interface such as an input circuit or power cable. Distributing power may, for example, be for charging the power supply 2208. The power circuit may perform any formatting, conversion, or other modifications to the power from the power supply 2208 to make that power suitable for each component of the UE2200 to which it is supplied.

[0088] Memory 2210 may be memory, or configured to contain memory, such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, etc. In one example, memory 2210 may contain one or more application programs 2214, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and corresponding data 2216. Memory 2210 may store any of a variety of operating systems or combinations of operating systems for use by UE2200.

[0089] Memory 2210 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), flash memory, USB flash drives, external hard disk drives, thumb drives, pen drives, key drives, high-density digital versatile disk (HD-DVD) optical disk drives, internal hard disk drives, Blu-ray optical disk drives, holographic digital data storage (HDDS) optical disk drives, external mini dual in-line memory modules (DIMMs), synchronous dynamic random access memory (SDRAM), external microDIMM SDRAM, smart card memory such as a tamper-proof module in the form of a universal integrated circuit card (UICC) containing one or more subscriber identification modules (SIMs) such as USIM and / or ISIM, other memory, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card". Memory 2210 may enable UE 2200 to access instructions, application programs, etc., stored in temporary or non-temporary memory media, to offload data, or to upload data. Products such as products utilizing communication systems may be tangibly embodied as or within memory 2210, and memory 2210 may be a device-readable storage medium or comprise a device-readable storage medium.

[0090] The processing circuit 2202 may be configured to communicate with an access network or other networks using a communication interface 2212. The communication interface 2212 may comprise one or more communication subsystems, including or communicatively coupled to an antenna 2222. The communication interface 2212 may include one or more transceivers used for communication, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or network node in the access network). Each transceiver may include a transmitter 2218 and / or receiver 2220 suitable for providing network communication (e.g., optical, electrical, frequency-allocated, etc.). Furthermore, the transmitter 2218 and receiver 2220 may be coupled to one or more antennas (e.g., antenna 2222), share circuit components, software or firmware, or alternatively, be implemented separately.

[0091] In the embodiments shown, the communication functions of the communication interface 2212 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 the use of the Global Positioning System (GPS) to determine location, other similar communication functions, or any combination thereof. The communication may be implemented in accordance with one or more communication protocols and / or standards, such as 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.

[0092] Regardless of the sensor type, the UE may provide the output of data captured by the UE's sensors to network nodes via a wireless connection through the UE's communication interface 2212. The data captured by the UE's sensors may be communicated to network nodes via another UE through a wireless connection. The output may be periodic (e.g., once every 15 minutes if reporting detected temperature), in response to a triggering event (e.g., an alarm is sent when humidity is detected), in response to a request (e.g., a user-initiated request), random (e.g., to equalize the load from reports from several sensors), or a continuous stream (e.g., a live video feed of a patient).

[0093] As another example, the UE may include an actuator, motor, or switch relating to a communication interface configured to receive radio input from a network node via a wireless connection. In response to the received radio input, the state of the actuator, motor, or switch may change. For example, the UE may include a motor that adjusts the control surface or rotor of a drone in flight according to the received input, or a robotic arm that performs a medical procedure according to the received input.

[0094] A UE, in the form of an Internet of Things (IoT) device, can be a device for use in one or more application areas, which include, but are not limited to, urban wearable technology, augmented industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices that are connected refrigerators or freezers, TVs, connected lighting devices, energy meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearables for haptic augmentation or perceptual augmentation, water sprinklers, animal or product tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device such as a heart rate monitor or remotely controlled surgical robot, or devices embedded in them. The UE in the form of an IoT device includes, in addition to the other components described with respect to the UE2200 shown in Figure 10, circuitry and / or software depending on the intended application of the IoT device.

[0095] In another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE could be an M2M device, which is sometimes called an MTC device in a 3GPP context. In one specific example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, the UE may represent a vehicle, such as a car, bus, truck, ship, and airplane, or other equipment capable of monitoring its operational status and / or reporting on its operational status, or performing other functions related to its operation.

[0096] In practice, any number of UEs can be used together for a single use case. For example, the first UE may be the drone itself, or integrated within the drone, providing the drone's speed information (obtained through a speed sensor) to the second UE, which is the remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (for example, by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UEs may also include two or more of the functions described above. For example, the UE may have sensors and actuators and handle the communication of data about both the speed sensor and the actuator.

[0097] Figure 14 shows a network node 3300 according to several embodiments. As used herein, a network node refers to a device that is configured, set up, and / or operable to communicate directly or indirectly with UEs in a communication network and / or with other network nodes or devices. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, node Bs, evolved node Bs (eNBs), and NR node Bs (gNBs)).

[0098] Base stations can be categorized based on the amount of coverage they provide (or, in other words, the base station's transmit power level), and are therefore sometimes called femto base stations, pico base stations, micro base stations, or macro base stations, depending on the amount of coverage they provide. A base station can be a relay node or relay donor node that controls relays. Network nodes can also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or remote radio unit (RRU), sometimes called a remote radio head (RRH). Such remote radio units may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station are sometimes called nodes in a distributed antenna system (DAS).

[0099] Other examples of network nodes include multiple transmit point (multi-TRP) 5G access nodes, MSR equipment such as multi-standard radio (MSR) BS, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base station transceiver stations (BTSs), transmit points, transmit nodes, multi-cell / multicast cooperative entities (MCEs), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., evolved serving mobile location centers (E-SMLCs)), and / or drive test minimization (MDT).

[0100] Network node 3300 includes a processing circuit 3302, a memory 3304, a communication interface 3306, and a power supply 3308. Network node 3300 can be assembled from multiple physically distinct components (e.g., node B components and RNC components, or BTS components and BSC components), each of which may have its own respective components. In some scenarios where network node 3300 has multiple distinct components (e.g., BTS components and BSC components), one or more of the distinct components may be shared among several network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, each unique node B-RNC pair may, in some cases, be considered a single distinct network node. In some embodiments, network node 1300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 3304 for different RATs), and some components may be reused (e.g., the same antenna 3310 may be shared by different RATs). Network node 3300 may also include multiple sets of various indicated components for different wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID), or Bluetooth wireless technologies, which are integrated into network node 1300. These wireless technologies may be integrated into the same or different chips or sets of chips, and other components within network node 1300.

[0101] The processing circuit 3302 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 any other suitable computing devices, resources, or combinations of hardware, software, and / or encoded logic, which are capable of operating to provide network node 3300 functionality, either on its own or in combination with other network node 3300 components such as memory 3304.

[0102] In some embodiments, the processing circuit 3302 includes a system-on-a-chip (SOC). In some embodiments, the processing circuit 3302 includes one or more of the radio frequency (RF) transceiver circuit 3312 and the baseband processing circuit 3314. In some embodiments, the radio frequency (RF) transceiver circuit 3312 and the baseband processing circuit 3314 may be on separate chips (or sets of chips), boards, or units such as radio and digital units. In alternative embodiments, some or all of the RF transceiver circuit 3312 and the baseband processing circuit 3314 may be on the same chip or set of chips, board, or unit.

[0103] Memory 3304 may include, but is not limited to, any form of volatile or non-volatile computer-readable memory, including persistent storage, solid memory, remote-mount memory, magnetic media, optical media, random-access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD), or digital video disc (DVD)), and / or any other volatile or non-volatile, non-temporary device-readable and / or computer-executable memory device for storing information, data, and / or instructions that may be used by the processing circuit 3302. Memory 3304 may store any suitable instructions, data, or information, including other instructions that may be executed by the processing circuit 3302 and utilized by the network node 3300, including applications that include one or more computer programs, software, logic, rules, code, and tables. Memory 3304 may be used to store calculations performed by the processing circuit 3302 and / or data received via the communication interface 3306. In some embodiments, the processing circuit 3302 and the memory 3304 are integrated.

[0104] The communication interface 3306 is used in wired or wireless signaling and / or data between network nodes, access networks, and / or UEs. As shown, the communication interface 3306 includes (one or more) ports / (one or more) terminals 3316 for sending and receiving data to and from the network, for example, over a wired connection. The communication interface 3306 also includes a wireless front-end circuit 3318, which is coupled to or, in some embodiments, may be part of the antenna 3310. The wireless front-end circuit 3318 includes a filter 3320 and an amplifier 3322. The wireless front-end circuit 3318 may be connected to the antenna 3310 and the processing circuit 3302. The wireless front-end circuit may be configured to adjust signals communicated between the antenna 3310 and the processing circuit 3302. The wireless front-end circuit 3318 may receive digital data to be sent to other network nodes or UEs via the wireless connection. The wireless front-end circuit 3318 can convert digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filter 3320 and / or amplifier 3322. The radio signal can then be transmitted via antenna 3310. Similarly, when receiving data, antenna 3310 can collect a radio signal, which is then converted into digital data by the wireless front-end circuit 3318. The digital data can then be passed to processing circuit 3302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0105] In some alternative embodiments, the network node 3300 does not include a separate radio front-end circuit 3318; instead, the processing circuit 3302 includes the radio front-end circuit and is connected to the antenna 3310. Similarly, in some embodiments, all or part of the RF transceiver circuit 3312 is part of the communication interface 3306. In yet another embodiment, the communication interface 3306, as part of a radio unit (not shown), includes one or more ports or terminals 3316, the radio front-end circuit 3318, and the RF transceiver circuit 3312, and the communication interface 3306 communicates with a baseband processing circuit 3314, which is part of a digital unit (not shown).

[0106] Antenna 3310 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 3310 may be coupled to the wireless front-end circuit 3318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 3310 is separate from the network node 3300 and can be connected to the network node 3300 through an interface or port.

[0107] The antenna 3310, the communication interface 3306, and / or the processing circuit 3302 may be configured to perform any receiving operations and / or certain acquisition operations as described herein as being performed by a network node. Any information, data, and / or signals may be received from the UE, another network node, and / or any other network equipment. Similarly, the antenna 3310, the communication interface 3306, and / or the processing circuit 3302 may be configured to perform any transmitting operations as described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to the UE, another network node, and / or any other network equipment.

[0108] The power supply 3308 provides power to the various components of the network node 3300 in a form suitable for each component (for example, at the voltage and current levels required for each respective component). The power supply 3308 may further include, or be coupled to, a power management circuit for supplying power to the components of the network node 3300 to perform the functions described herein. For example, the network node 3300 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, thereby the external power source supplying power to the power circuit of the power supply 3308. As a further example, the power supply 3308 may include a power source in the form of a battery or battery pack, connected to or integrated into the power circuit. The battery may provide backup power in the event of an external power failure.

[0109] Embodiments of the network node 3300 may include additional components other than those shown in Figure 14 to provide several aspects of the network node's functionality, including any of the functions described herein and / or functions necessary to support the subject matter described herein. For example, the network node 3300 may include user interface equipment for enabling information input to and output from the network node 3300. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 3300.

[0110] Figure 15 is a block diagram of host 4400, which may be one embodiment of host 2116 in Figure 12, according to various aspects described herein. Host 4400 as used herein may be a variety of combinations of hardware and / or software, or comprise a variety of combinations of hardware and / or software, including standalone servers, blade servers, cloud implementation servers, distributed servers, virtual machines, containers, or processing resources in a server farm. Host 4400 may provide one or more services to one or more UEs.

[0111] The host 4400 includes a processing circuit 4402 operably coupled to an input / output interface 4406, a network interface 4408, a power supply 4410, and memory 4412 via a bus 4404. Other embodiments may include other components. The characteristics of these components may be substantially the same as those described with respect to the devices in previous figures, such as Figures 13 and 14, and therefore their descriptions are generally applicable to the corresponding components of the host 4400.

[0112] Memory 4412 may include one or more computer programs, each containing one or more host application programs 4414 and data 4416, the data 4416 of which may include user data, for example, data generated by the UE for host 4400, or data generated by host 4400 for the UE. Embodiments of host 4400 may utilize only a subset or all of the components shown. Host application programs 4414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Multipurpose 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), including transcoding for multiple different classes, types, or implementations of the UE (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application program 4414 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 the core network or a device at the edge of the core network. Thus, host 4400 may select and / or direct different hosts for over-the-top services for the UE. The host application program 4414 may support various protocols, including HTTP Live Streaming (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), and Dynamic Adaptive Streaming over HTTP (MPEG-DASH).

[0113] Figure 16 is a block diagram showing a virtualization environment 5500 in which functions implemented by several embodiments can be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include virtualizing hardware platforms, storage devices, and networking resources. The virtualization used herein may apply to any device or its components described herein and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components, executed by one or more virtual machines (VMs) implemented in one or more virtualization environments 5500 hosted by one or more hardware nodes, such as network nodes, UEs, core network nodes, or hardware computing devices acting as hosts. Furthermore, in embodiments in which the virtual nodes do not require wireless connectivity (e.g., core network nodes or hosts), the nodes may be fully virtualized.

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

[0115] Hardware 5504 includes processing circuits, memory for storing software and / or instructions executable by the hardware processing circuits, and / or other hardware devices described herein, such as network interfaces and input / output interfaces. The software is executed by the processing circuits to instantiate one or more virtualization layers 5506 (also called hypervisors or virtual machine monitors (VMMs)), providing VM5508a and 5508b (one or more of which may commonly be referred to as VM5508), and / or may implement any of the functions, features, and / or benefits described with respect to some embodiments described herein. The virtualization layer 5506 may present VM5508 with a virtual operating platform that looks like networking hardware.

[0116] VM5508 features virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be powered by the corresponding virtualization layer 5506. Different embodiments of the virtual appliance 5502 example may be implemented on one or more of the VM5508s, and the implementation may be carried out in different ways. Hardware virtualization is referred to as network function virtualization (NFV) in several contexts. NFV can be used to consolidate many types of network equipment onto industry-standard high-volume server hardware, physical switches, and physical storage, which may reside in data centers and customer premises equipment.

[0117] In the context of NFV, VM5508 can be a software implementation of a physical machine, where programs run as if they were running on a physical, non-virtualized machine. Each VM5508 and its portion of the hardware 5504 on which it runs, whether that hardware is dedicated to that VM and / or shared by that VM with other VMs in the VM, form a separate virtual network element. Furthermore, in the context of NFV, the virtual network function is responsible for handling specific network functions running in one or more VM5508s on the hardware 5504 and corresponds to application 5502.

[0118] Hardware 5504 may be implemented in a standalone network node with general or specific components. Hardware 5504 may implement some functions through virtualization. Alternatively, hardware 5504 may be part of a larger cluster of hardware (such as in a data center or CPE) where many hardware nodes cooperate and are managed via management and orchestration 5510, which oversees the lifecycle management of applications 5502. In some embodiments, hardware 5504 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 suitable network interfaces and may be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station. In some embodiments, some signaling may be provided using a control system 5512, which may be used alternatively for communication between hardware nodes and radio units.

[0119] Figure 17 shows a communication diagram of host 6602 communicating with UE 6606 via network node 6604 over a partial wireless connection, according to several embodiments. Next, exemplary implementations of various embodiments of the UEs (such as UE 2112a in Figure 12 and / or UE 2200 in Figure 13), network nodes (such as network node 2110a in Figure 12 and / or network node 3300 in Figure 14), and hosts (such as host 2116 in Figure 12 and / or host 4400 in Figure 15), as described in the previous paragraph, will be described with reference to Figure 17.

[0120] Similar to host 4400, embodiments of host 6602 include hardware such as a communication interface, processing circuitry, and memory. Host 6602 also includes software that is stored in or accessible by host 6602 and executable by the processing circuitry. The software includes a host application that may be capable of operating to serve a remote user, such as UE6606 connected via an over-the-top (OTT) connection 6650 extending between UE6606 and host 6602. When serving a remote user, the host application may provide user data transmitted using the OTT connection 6650.

[0121] Network node 6604 includes hardware that enables network node 6604 to communicate with host 6602 and UE6606. The connection 6660 may be direct or pass through a core network (similar to core network 2106 in Figure 12) and / or one or more other intermediate networks, such as one or more public networks, private networks, or hosted networks. For example, the intermediate network could be a backbone network or the internet.

[0122] The UE6606 includes hardware and software that is stored in or accessible by the UE6606 and executable by the UE's processing circuitry. The software includes client applications, such as a web browser or operator-specific “app,” which may be capable of operating to serve human or non-human users through the UE6606, with the support of the host 6602. On the host 6602, the running host application may communicate with the running client application via an OTT connection 6650 that terminates in the UE6606 and host 6602. When serving a user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 6650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate user data that the UE's client application provides to the host application via the OTT connection 6650.

[0123] The OTT connection 6650 may extend via connection 6660 between host 6602 and network node 6604, and via wireless connection 6670 between network node 6604 and UE6606, in order to provide a connection between host 6602 and UE6606. Connections 6660 and wireless connection 6670, which the OTT connection 6650 may provide, are depicted abstractly to illustrate communication between host 6602 and UE6606 via network node 6604, without explicit reference to intermediary devices and the precise routing of messages through these devices.

[0124] As an example of transmitting data via the OTT connection 6650, in step 6608, host 6602 provides user data, which may be done by running a host application. In some embodiments, the user data relates to a specific human user interacting with UE6606. In other embodiments, the user data relates to UE6606 sharing data with host 6602 without explicit human interaction. In step 6610, host 6602 initiates a transmission to carry the user data toward UE6606. Host 6602 may initiate a transmission in response to a request sent by UE6606. The request may be triggered by human interaction with UE6606 or by the operation of a client application running on UE6606. The transmission may proceed through network node 6604 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 6612, the network node 6604 transmits the user data carried in the transmission initiated by host 6602 to UE 6606, in accordance with the teachings of the embodiments described throughout this disclosure. In step 6614, UE 6606 receives the user data carried in the transmission, which may be done by a client application running on UE 6606 related to a host application run by host 6602.

[0125] In some examples, UE6606 runs a client application that provides user data to host 6602. User data may be provided in response to or in reaction to data received from host 6602. Thus, in step 6616, UE6606 may provide user data, which may be done by running a client application. When providing user data, the client application may further consider user input received from the user via the input / output interface of UE6606. Regardless of the particular form in which the user data is provided, UE6606 initiates a transmission of the user data to host 6602 via network node 6604 in step 6618. In step 6620, in accordance with the teachings of embodiments described throughout this disclosure, network node 6604 receives user data from UE6606 and initiates a transmission of the received user data to host 6602. In step 6622, host 6602 receives the user data carried in the transmission initiated by UE6606.

[0126] One or more of the various embodiments improve the performance of the OTT service provided to the UE6606 by using the OTT connection 6650, in which the wireless connection 6670 forms the final segment. More precisely, the teachings of these embodiments may improve data rate, latency, and / or power consumption, thereby providing benefits such as reduced user latency, relaxed file size limitations, improved content resolution, enhanced responsiveness, and / or extended battery life.

[0127] In an exemplary scenario, factory status information may be collected and analyzed by host 6602. As another example, host 6602 may process audio and video data that may be extracted from the UE for use in creating maps. As yet another example, host 6602 may collect and analyze real-time data to help control vehicle congestion (e.g., control traffic signals). As yet another example, host 6602 may store surveillance video uploaded by the UE. As yet another example, host 6602 may store or control access to media content, such as video, audio, VR or AR, which host 6602 can broadcast, multicast, or unicast to the UE. As yet another example, host 6602 may be used for energy pricing, remote control of non-time-constrained electrical loads to balance generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, extracting, storing, analyzing, and / or transmitting data.

[0128] In some embodiments, measurement procedures may be provided for the purpose of monitoring data rate, latency, and other factors, which are improved by one or more embodiments. Further optional network functions may be provided for reconfiguring the OTT connection 6650 between host 6602 and UE6606 in response to variations in measurement results. Measurement procedures and / or network functions for reconfiguring the OTT connection may be implemented in software and hardware on host 6602 and / or UE6606. In some embodiments, sensors (not shown) may be deployed in or in relation to other devices through which the OTT connection 6650 passes, and the sensors may participate in the measurement procedure by supplying values ​​for the monitored quantities exemplified above, or values ​​for other physical quantities that the software can calculate or estimate the monitored quantities for. Reconfiguring the OTT connection 6650 may include message formatting, retransmission settings, preferred routing, etc., and the reconfiguration does not require a direct change in the operation of network node 6604. Such procedures and functions are known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling by host 6602 to facilitate measurements such as throughput, propagation time, and latency. The measurements may be implemented in which software uses OTT connection 6650 to cause messages, particularly empty or "dummy" messages, to be sent while monitoring propagation time, errors, etc.

[0129] The computing devices described herein (e.g., UEs, network nodes, hosts) may include the shown combinations of hardware components, but other embodiments may comprise computing devices with different combinations of components. It should be understood that these computing devices may comprise any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determining, calculating, acquiring, or similar operations described herein may be performed by processing circuits, which may process information by, for example, converting acquired information to other information, comparing acquired or converted information to information stored in a network node, and / or performing one or more operations based on the acquired or converted information and as a result of the processing making decisions. Furthermore, although components are illustrated as a single box located within a larger box, or as a single box nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that constitute a single shown component, and functions may be separated between the distinct components. For example, a communication interface may be configured to include any of the components described herein, and / or the functions of those components may be separated between the processing circuit and the communication interface. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0130] In some embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in memory, which in some embodiments may be a computer program product in the form of a non-temporary computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by a processing circuit without executing instructions stored in a separate or individual device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, whether or not it executes instructions stored in a non-temporary computer-readable storage medium, the processing circuit may be configured to perform the functions described. The benefits provided by such functions are enjoyed by the processing circuit alone, or by the computing device as a whole, but not limited to other components of the computing device, and / or generally by the end user and the wireless network.

[0131] It will be understood that computer systems take on an increasingly diverse range of forms. In this description and in the claims, the terms “controller,” “computer system,” or “computing system” are broadly defined to include any device or system, or any combination thereof, comprising at least one physical and tangible processor and physical and tangible memory capable of having computer-executable instructions that can be executed by the processor. Not limited to, but as used herein, the terms “computer system” or “computing system” are intended to include personal computers, desktop computers, laptop computers, tablets, handheld devices (e.g., mobile phones, PDAs, pagers), microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, multiprocessor systems, network PCs, distributed computing systems, data centers, message processors, routers, switches, and even devices not previously considered computing systems, such as wearables (e.g., eyeglasses).

[0132] A computing system also has several structures on which it rests, often referred to as “executable components.” For example, the memory of a computing system may contain executable components. The term “executable component” is a name for a structure that is well understood by those skilled in the art of computing as a structure that may be software, hardware, or a combination thereof. For example, when implemented in software, those skilled in the art will understand that the structure of an executable component may include software objects, routines, methods, etc., that can be executed by one or more processors on the computing system, regardless of whether such executable components reside in the heap of the computing system or on a computer-readable storage medium. The structure of an executable component exists on a computer-readable medium in such a form that, when executed by one or more processors of the computing system, it is operable to cause the computing system to perform one or more functions, such as the functions and methods described herein. Such a structure may be directly computer-readable by the processor, as is the case when the executable component is a binary. Alternatively, the structure may be structured and / or compiled in an interpretable manner, whether in a single step or in multiple steps, to produce a binary that is directly interpretable by the processor.

[0133] The terms “components,” “services,” “engines,” “modules,” “controls,” and “generators” may also be used in this description. These terms, as used in this description and in this context, are intended to be synonymous with the term “executable components,” whether expressed with or without modifying clauses, and therefore have the same structure as will be well understood by those skilled in the art of computing.

[0134] In terms of computer implementations, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer, processor, and controller may be used interchangeably. When provided by a computer, processor, or controller, the functionality may be provided by a single dedicated computer or processor or controller, a single shared computer or processor or controller, or by multiple individual computers or processors or controllers, some of which may be shared or distributed. Furthermore, the terms “processor” or “controller” may also refer to other hardware capable of performing such functionality and / or running software, such as the exemplary hardware described above.

[0135] In general, various exemplary embodiments may be implemented in hardware or dedicated chips, circuits, software, logic, or any combination thereof. For example, some embodiments may be implemented in hardware, while others may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, but this disclosure is not limited thereto. Various embodiments of the exemplary embodiments of this disclosure may be shown and described as block diagrams, flowcharts, or using any other graphical representation, but it should be understood that these blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof, as non-limiting examples.

[0136] Not all computing systems require a user interface, but in some embodiments, a computing system includes a user interface for use in communicating information with a user. The user interface may include output and input mechanisms. The principles described herein are not limited to strict output or input mechanisms and therefore depend on the nature of the device. However, output mechanisms may include, for example, speakers, displays, haptic outputs, projections, holograms, etc. Examples of input mechanisms may include, for example, microphones, touchscreens, projections, holograms, cameras, keyboards, styluses, mice, or other pointer inputs, any type of sensor, etc.

[0137] Abbreviations and defined terms To aid in understanding the scope and content of this specification and the appended claims, several selected terms are defined below directly. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this disclosure relates.

[0138] As used herein, the terms “approximately,” “about,” and “substantially” refer to an amount or condition that is close to a specific stated amount or condition that still performs the desired function or achieves the desired result. For example, the terms “approximately,” “about,” and “substantially” may refer to an amount or condition that deviates by less than 10%, or less than 5%, or less than 1%, or less than 0.1%, or less than 0.01%, from the specifically stated amount or condition.

[0139] Various aspects of the Disclosure, including devices, systems, and methods, may be shown with respect to one or more embodiments or implementations that are essentially illustrative. As used herein, the term “exemplary” means “acting as an example, case, or illustration” and should not necessarily be construed as being preferable or advantageous to other embodiments disclosed herein. Furthermore, references to “implementations” of the Disclosure or embodiments include specific references to one or more embodiments thereof, and vice versa, and are intended to provide illustrative examples without limiting the scope of the Disclosure as directed not by this Specified Publication but by the appended claims.

[0140] Unless implicitly or explicitly understood otherwise or otherwise stated, a word appearing in the singular form as used herein includes its plural equivalent, and a word appearing in the plural form includes its singular equivalent. Therefore, note that the singular forms “a,” “an,” and “the” as used herein and in the appended claims include plural referents unless the context explicitly specifies otherwise. For example, a reference to a singular referent (e.g., “a widget”) includes one, two, or more referents unless implicitly or explicitly understood otherwise or otherwise stated. Similarly, a reference to multiple referents should be interpreted as including one referent and / or multiple referents unless the content and / or context explicitly specifies otherwise. For example, a reference to a plural referent (e.g., “widgets”) does not necessarily require multiple such referents. Instead, unless otherwise stated, it should be understood that one or more referents are intended herein, regardless of the presumed number of referents.

[0141] References herein to “one embodiment,” “an embodiment,” and “exemplary embodiment” indicate that the embodiments described may include certain features, structures, or characteristics, but not all embodiments necessarily include such features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when certain features, structures, or characteristics are described in relation to an embodiment, it is known to those skilled in the art that such features, structures, or characteristics will be affected in relation to other embodiments, whether or not they are explicitly described.

[0142] Terms such as “first” and “second” may be used herein to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are used merely to distinguish one element from another. For example, without departing from the scope of exemplary embodiments, a first element may be called a second element, and similarly, a second element may be called a first element. The terms “and / or” as used herein include any and all combinations of one or more of the relevant enumerated terms.

[0143] As used herein, the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” specify the presence of the described features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0144] conclusion This disclosure includes any novel features or combinations thereof of the features expressly disclosed herein, or any generalization thereof. Various modifications and adaptations to the exemplary embodiments of this disclosure may become apparent to those skilled in the art in view of the above description when read together with the accompanying drawings. However, any and all modifications still fall within the scope of the non-limiting and exemplary embodiments of this disclosure.

[0145] With respect to any given component or embodiment described herein, it should be understood that any of the possible candidate or alternative forms listed for that component may be used individually or in combination with each other, unless implicitly or explicitly understood otherwise or otherwise stated. Furthermore, it should be understood that the list of such candidate or alternative forms is illustrative and not limiting, unless implicitly or explicitly understood otherwise or otherwise stated.

[0146] Furthermore, unless otherwise indicated, numbers representing quantities, components, distances, or other measurements used herein and in the claims should be understood to be modified by the term “approximately” when the term is defined herein. Therefore, unless otherwise indicated, the numerical parameters described herein and in the appended claims are approximations that may vary depending on the desired properties to be obtained by the subject matter presented herein. At a minimum, and not as an attempt to limit the application of the doctrine of equivalents to the claims, each numerical parameter should be interpreted at least in light of the number of significant figures reported and by applying ordinary rounding techniques. While the numerical ranges and parameters describing a wide range of the subject matter presented herein are approximations, the numbers described in specific examples are reported as accurately as possible. However, any numerical value inherently contains some error, which inevitably arises from the standard deviation found in their respective test measurements.

[0147] Any headings and subheadings used herein are for organizational purposes only and are not intended to limit the scope of this specification or the claims. The terms and expressions used herein are descriptive, not restrictive, and in the use of such terms and expressions, no equivalents or parts thereof of the features shown and described are excluded, and various modifications are possible within the scope of this disclosure. Therefore, although this disclosure is specifically disclosed in part by some embodiments and optional features, modifications and variations of the concepts disclosed herein may be used by those skilled in the art, and such modifications and variations are considered to be within the scope of this specification.

[0148] Furthermore, it will be understood that some embodiments of the present disclosure may include, incorporate, or otherwise possess properties or features (e.g., components, members, elements, parts, and / or portions) described in other embodiments disclosed and / or described herein. Accordingly, various features of some embodiments may be compatible with, combined with, included in, and / or incorporated into other embodiments of the present disclosure. Accordingly, the disclosure of some features for a particular embodiment of the present disclosure should not be construed as limiting the application or inclusion of such features to that particular embodiment. Rather, it will be understood that other embodiments may also include such features, members, elements, parts, and / or portions without necessarily departing from the scope of the present disclosure.

[0149] Furthermore, unless a feature is described as requiring another feature to be combined with it, any feature herein may be combined with any other feature of the same or different embodiments disclosed herein. Moreover, various well-known embodiments, such as exemplary systems, methods, and apparatus, are not described herein in particular detail in order to avoid obscuring the embodiments of the exemplary models. However, such embodiments are also contemplated herein.

[0150] It will be apparent to those skilled in the art that methods, devices, device elements, materials, procedures, and techniques other than those specifically described herein can be applied to the practices of the embodiments described herein as broadly disclosed herein, without relying on excessive experimentation. All technically known functional equivalents of the methods, devices, device elements, materials, procedures, and techniques specifically described herein are intended to be encompassed by this disclosure.

[0151] When a group of materials, compositions, components, or compounds is disclosed herein, it should be understood that all individual members of those groups and all of their subgroups are disclosed separately. When a Markush group or other grouping is used herein, all individual members of that group, as well as all possible combinations and partial combinations of that group, are intended to be individually included in this disclosure.

[0152] The embodiments described above are merely examples. Modifications, alterations, and variations of specific embodiments can be made by those skilled in the art without departing from the scope of this description, as defined solely by the appended claims.

Claims

1. A method performed by a user device (UE) for indicating the availability of a successful primary / secondary cell (PSCell) report (SPR), wherein the method is Providing SPR availability information to network nodes Includes, A method in which the SPR availability information is included in the S node reconfiguration completion message from the master node to the secondary node, or in the UE assistance information message.

2. The method according to claim 1, further comprising transmitting the SPR to the network node.

3. The method according to claim 1, wherein the network node includes at least one of a secondary node (SN) and a master node (MN).

4. The method according to claim 1, wherein the SPR availability information is sent directly from the UE to the secondary node via the signaling radio bearer 3 (SRB3).

5. The method according to claim 1, wherein the SPR availability information is sent directly from the UE to the master node via the signaling radio bearer 1 (SRB1).

6. The method according to claim 1, wherein when the SPR availability information is received by the master node (MN) via the signaling radio bearer 1 (SRB1), the SPR availability information is sent from the MN to the secondary node via the MN in an S-node reconfiguration completion message.

7. The method according to claim 1, further comprising receiving the setting of the SPR availability information from one or more of the master node (MN) and secondary nodes (SN).

8. The method according to claim 1, further comprising receiving a request to send the SPR availability information.

9. The method according to claim 7, wherein the reception is performed for at least one of the following: a Radio Resource Control (RRC) message, an RRC Reconfiguration Complete message, or a UE Assistance Information message.

10. A method performed by a first network node to indicate the availability of a successful primary / secondary cell (PSCell) report (SPR), the method being: Receiving SPR availability information from UE, To send an instruction to the second network node that the SPR is available in the UE. Includes, A method in which the SPR availability information is included in the S node reconfiguration completion message from the master node to the secondary node, or in the UE assistance information message.

11. The method according to claim 10, further comprising receiving the SPR from the second network node.

12. A method performed by a first network node for receiving a successful primary / secondary cell (PSCell) report (SPR), the method being: The second network node transmits the SPR availability information received from the user equipment (UE), Receiving an instruction from the second network node that SPR is available in UE, From the aforementioned UE, fetch the aforementioned SPR, The fetched SPR is analyzed to determine whether the SPR should be sent to the second network node. Includes, A method in which the SPR availability information is included in the S node reconfiguration completion message from the master node to the secondary node, or in the UE assistance information message.

13. The method according to claim 12, further transmitting the SPR to the second network node.

14. A user device (UE) for indicating the availability of successful primary / secondary cell (PSCell) reports (SPRs), A processing circuit configured to perform any of the steps described in any one of claims 1 to 9, A power supply circuit configured to supply power to the aforementioned processing circuit and User equipment (UE) equipped with these features.

15. A network node for indicating the availability of a successful primary / secondary cell (PSCell) report (SPR) or for transmitting such SPR, wherein the network node A processing circuit configured to perform any of the steps described in any one of claims 10 to 13, A power supply circuit configured to supply power to the aforementioned processing circuit and A network node equipped with these features.

Images