WO2025211790A1

WO2025211790A1 - Method and apparatus for supporting data collection in a wireless communication system

Info

Publication number: WO2025211790A1
Application number: PCT/KR2025/004431
Authority: WO
Inventors: Yanru Wang; Lixiang Xu; Hong Wang
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2024-04-03
Filing date: 2025-04-03
Publication date: 2025-10-09
Anticipated expiration: 2026-10-03

Abstract

The disclosure relates to a fifth generation (5G) or sixth generation (6G) communication system for supporting higher data rates. The invention provides a node and a user equipment in a wireless communication system and methods performed by the same. Embodiments of the present disclosure provide a method performed by a secondary node in a wireless communication system, which includes: performing an initiation procedure to report a data collection and to configure to collect requested information of the data collection; receiving, from a master node (MN), an addition request message to request the data collection for a user equipment (UE), the addition request message including collection identifier (ID) information; and as a response to the addition request message, transmitting, to the MN, an addition request acknowledge message to report a result of the data collection, wherein the data collection is associated with a dual-connectivity.

Description

METHOD AND APPARATUS FOR SUPPORTING DATA COLLECTION IN A WIRELESS COMMUNICATION SYSTEM

The present disclosure relates to a technical field of wireless communication, and more specifically, to a node and a user equipment in a wireless communication system and methods performed by the same.

5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

Moreover, there has been ongoing standardization in air interface architecture/protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture/service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

The present disclosure relates to wireless communication systems and, more specifically, the present disclosure relates to supporting data collection in a wireless communication.

Embodiments of the present disclosure provide a method performed by a second node in a wireless communication system, which includes: receiving a first message from a first node, wherein the first message includes a first collection configuration and a first reporting configuration for multi-hop data collection of a user equipment (UE); and transmitting a seventh message to a third node, wherein the seventh message includes a second collection configuration for the multi-hop data collection, wherein the second collection configuration is determined based on the first collection configuration and data collection information of the UE at the second node, wherein the first message further includes at least one of: a node identifier of an initial configuration node of the multi-hop data collection, a UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the first collection configuration is a start configuration for the multi-hop data collection, and wherein the seventh message further includes at least one of: the node identifier of the initial configuration node, the UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the second collection configuration is a subsequent configuration for the multi-hop data collection.

According to embodiments of the present disclosure, the first collection configuration includes at least one of: a first collection time corresponding to the multi-hop data collection, a first maximum number of accessed/visited nodes corresponding to the multi-hop data collection, a first maximum hop number corresponding to the multi-hop data collection, and a third maximum number of accessed/visited cells corresponding to the multi-hop data collection; wherein the second collection configuration includes at least one of: a second collection time corresponding to the multi-hop data collection, a second maximum number of accessed/visited nodes corresponding to the multi-hop data collection, a second maximum hop number corresponding to the multi-hop data collection, and a fourth maximum number of accessed/visited cells corresponding to the multi-hop data collection; and wherein the second collection time is determined based on the first collection time and a data collection time of the UE at the second node; the second maximum number is determined based on the first maximum number and a number of accessed/visited nodes of the UE at the second node; the second maximum hop number is determined based on the first maximum hop number and a number of accessed/visited hops of the UE at the second node; the fourth maximum number is determined based on the third maximum number and the number of accessed/visited cells of the UE at the second node.

According to embodiments of the present disclosure, the UE identifier assigned for the UE by the initial configuration node is a UE Xn-interface Application Protocol (UE XnAP) identifier.

According to embodiments of the present disclosure, the method further includes receiving a handover request message from the first node, wherein the handover request message includes at least one of: a node identifier of an initial configuration node of the multi-hop data collection and a UE identifier assigned for the UE by the initial configuration node.

According to embodiments of the present disclosure, the method further includes transmitting an eighth message to the third node, wherein the eighth message includes a second reporting configuration for the multi-hop data collection.

According to embodiments of the present disclosure, the seventh message further includes a second reporting configuration for the multi-hop data collection.

According to embodiments of the present disclosure, the method further includes receiving a ninth message from the third node, wherein the ninth message includes information about whether the third node can be able to transmit a collection result of the multi-hop data collection to the initial configuration node of the multi-hop data collection directly.

According to embodiments of the present disclosure, the method further includes receiving a third message from the third node, wherein the third message includes a collection result of the multi-hop data collection of the third node; and transmitting the collection result to the first node.

Embodiments of the present disclosure provide a method performed by a first node in a wireless communication system, which includes: transmitting a first message to a second node, wherein the first message includes a first collection configuration and a first reporting configuration for multi-hop data collection of a user equipment (UE); and receiving a second message from the second node, wherein the second message includes a first response for the first message, wherein a seventh message is transmitted by the second node to a third node, wherein the seventh message includes a second collection configuration for the multi-hop data collection, wherein the second collection configuration is determined based on the first collection configuration and data collection information of the UE at the second node, wherein the first message further includes at least one of: a node identifier of an initial configuration node of the multi-hop data collection, a UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the first collection configuration is a start configuration for the multi-hop data collection, and wherein the seventh message further includes at least one of: the node identifier of the initial configuration node, the UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the second collection configuration is a subsequent configuration for the multi-hop data collection.

According to embodiments of the present disclosure, the method further includes transmitting a handover request message to the second node, wherein the handover request message includes at least one of: a node identifier of an initial configuration node of the multi-hop data collection and a UE identifier assigned for the UE by the initial configuration node.

According to embodiments of the present disclosure, the method further includes receiving a collection result of the multi-hop data collection of the third node from at least one of the second node, the third node and a core network node.

Embodiments of the present disclosure provide a method performed by a third node in a wireless communication system, which includes: receiving a seventh message from a second node, wherein the seventh message includes a second collection configuration for multi-hop data collection of a user equipment (UE), wherein the second collection configuration is determined based on a first collection configuration for the multi-hop data collection and data collection information of the UE at the second node, wherein the first collection configuration is received by the second node from a first node; and transmitting a ninth message to the second node, wherein the ninth message includes information about whether the third node can be able to transmit a collection result of the multi-hop data collection to the initial configuration node of the multi-hop data collection directly, wherein the seventh message further includes at least one of: a node identifier of an initial configuration node of the multi-hop data collection, a UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the second collection configuration is a subsequent configuration for the multi-hop data collection.

According to embodiments of the present disclosure, the method further includes receiving an eighth message from the second node, wherein the eighth message includes a second reporting configuration for the multi-hop data collection.

According to embodiments of the present disclosure, the method further includes transmitting a collection result of the multi-hop data collection of the third node to at least one of the first node, the second node and a core network node.

Embodiments of the present disclosure provide a method performed by a user equipment (UE) in a wireless communication system, including: receiving a radio resource control (RRC) reconfiguration message from a first node; and transmitting an RRC reconfiguration complete message to the first node, wherein a first message is transmitted by the first node to a second node, wherein the first message includes a first collection configuration and a first reporting configuration for multi-hop data collection of the UE; and wherein a seventh message is transmitted by the second node to a third node, wherein the seventh message includes a second collection configuration for the multi-hop data collection, wherein the second collection configuration is determined based on the first collection configuration and data collection information of the UE at the second node, wherein the first message further includes at least one of: a node identifier of an initial configuration node of the multi-hop data collection, a UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the first collection configuration is a start configuration for the multi-hop data collection, and wherein the seventh message further includes at least one of: the node identifier of the initial configuration node, the UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the second collection configuration is a subsequent configuration for the multi-hop data collection.

Embodiments of the present disclosure provide a first node device in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform methods performed by a first node in a wireless communication system according to embodiments of the present disclosure.

Embodiments of the present disclosure provide a second node device in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform methods performed by a second node in a wireless communication system according to embodiments of the present disclosure.

Embodiments of the present disclosure provide a third node device in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform methods performed by a third node in a wireless communication system according to embodiments of the present disclosure.

Embodiments of the present disclosure provide a user equipment (UE) in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform methods performed by a user equipment (UE) in a wireless communication system according to embodiments of the present disclosure.

Embodiments of the present disclosure provide a computer-readable medium having stored thereon computer-readable instructions which, when executed by a processor, perform methods performed by a first node and/or a second node and/or a third node and/or a user equipment in a wireless communication system according to embodiments of the present disclosure.

The methods performed by the first node and/or the second node and/or the third node and/or the user equipment in the wireless communication system provided by the present disclosure can effectively support the nodes and/or the user equipment to perform data collection in a multi-hop case and/or a dual-connectivity case by exchanging information related to multi-hop and/or dual-connectivity data collection between the nodes and/or the user equipment.

Embodiments of the present disclosure provide a method performed by a secondary node (SN) in a communication system, the method comprising: performing an initiation procedure to report a data collection and to configure to collect requested information of the data collection; receiving, from a master node (MN), an addition request message to request the data collection for a user equipment (UE), the addition request message including collection identifier (ID) information; and as a response to the addition request message, transmitting, to the MN, an addition request acknowledge message to report a result of the data collection, wherein the data collection is associated with a dual-connectivity.

Embodiments of the present disclosure provide a method performed by a master node (MN) in a communication system, the method comprising: performing an initiation procedure to report a data collection and to configure to collect requested information of the data collection; transmitting, to a secondary node (SN), an addition request message to request the data collection for a user equipment (UE), the addition request message including collection identifier (ID) information; and as a response to the addition request message, receiving, from the SN, an addition request acknowledge message to report a result of the data collection, wherein the data collection is associated with a dual-connectivity.

Embodiments of the present disclosure provide a secondary node (SN) in a communication system, the SN comprising: a transceiver; and a controller coupled with the transceiver, wherein the controller is configured to: perform an initiation procedure to report a data collection and to configure to collect requested information of the data collection; receive, from a master node (MN), an addition request message to request the data collection for a user equipment (UE), the addition request message including collection identifier (ID) information; and as a response to the addition request message, transmit, to the MN, an addition request acknowledge message to report a result of the data collection, wherein the data collection is associated with a dual-connectivity.

Embodiments of the present disclosure provide a master node (MN) in a communication system, the MN comprising: a transceiver; and a controller coupled with the transceiver, wherein the controller is configured to: perform an initiation procedure to report a data collection and to configure to collect requested information of the data collection; transmit, to a secondary node (SN), an addition request message to request the data collection for a user equipment (UE), the addition request message including collection identifier (ID) information; and as a response to the addition request message, receive, from the SN, an addition request acknowledge message to report a result of the data collection, wherein the data collection is associated with a dual-connectivity.

According to an embodiment of the disclosure, a wireless communication can be performed efficiently. Especially, supporting data collection can be performed efficiently.

The above and other aspects, features and advantages of certain embodiments of the present disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

FIG. 1 is an exemplary system architecture 100 of System Architecture Evolution (SAE);

FIG. 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure;

FIG. 3A shows schematic diagrams of an aspect of a method for supporting data collection according to embodiments of the present disclosure;

FIG. 3B shows schematic diagrams of an aspect of a method for supporting data collection according to embodiments of the present disclosure;

FIG. 3C shows schematic diagrams of an aspect of a method for supporting data collection according to embodiments of the present disclosure;

FIG. 3D shows schematic diagrams of an aspect of a method for supporting data collection according to embodiments of the present disclosure;

FIG. 3E shows schematic diagrams of an aspect of a method for supporting data collection according to embodiments of the present disclosure;

FIG. 3F shows schematic diagrams of an aspect of a method for supporting data collection according to embodiments of the present disclosure;

FIG. 3G shows schematic diagrams of an aspect of a method for supporting data collection according to embodiments of the present disclosure;

FIG. 3H shows schematic diagrams of an aspect of a method for supporting data collection according to embodiments of the present disclosure;

FIG. 3I shows schematic diagrams of an aspect of a method for supporting data collection according to embodiments of the present disclosure;

FIG. 4A shows schematic diagrams of an aspect of a method for supporting data collection according to embodiments of the present disclosure;

FIG. 4B shows schematic diagrams of an aspect of a method for supporting data collection according to embodiments of the present disclosure;

FIG. 4C shows schematic diagrams of an aspect of a method for supporting data collection according to embodiments of the present disclosure;

FIG. 5 shows a flowchart of a method performed by a second node in a wireless communication system according to embodiments of the present disclosure;

FIG. 6 shows a flowchart of a method performed by a first node in a wireless communication system according to embodiments of the present disclosure;

FIG. 7 shows a flowchart of a method performed by a third node in a wireless communication system according to embodiments of the present disclosure;

FIG. 8 shows a flowchart of a method performed by a user equipment (UE) in a wireless communication system according to embodiments of the present disclosure;

FIG. 9 shows a schematic diagram of a node according to embodiments of the present disclosure; and

FIG. 10 shows a schematic diagram of a user equipment (UE) according to embodiments of the present disclosure.

In order to meet an increasing demand for wireless data communication services since a deployment of 4G communication system, efforts have been made to develop an improved 5G or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called “beyond 4G network” or “post LTE system”.

Wireless communication is one of the most successful innovations in modern history. Recently, a number of subscribers of wireless communication services has exceeded 5 billion, and it continues growing rapidly. With the increasing popularity of smart phones and other mobile data devices (such as tablet computers, notebook computers, netbooks, e-book readers and machine-type devices) in consumers and enterprises, a demand for wireless data services is growing rapidly. In order to meet rapid growth of mobile data services and support new applications and deployments, it is very important to improve efficiency and coverage of wireless interfaces.

In the prior art, research on data collection in a multi-hop case and data collection in a dual-connectivity case is insufficient.

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustration purpose only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.

The term “include” or “may include” refers to the existence of a corresponding disclosed function, operation or component which can be used in various embodiments of the present disclosure and does not limit one or more additional functions, operations, or components. The terms such as “include” and/or “have” may be construed to denote a certain characteristic, number, step, operation, constituent element, component or a combination thereof, but may not be construed to exclude the existence of or a possibility of addition of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.

The term “or” used in various embodiments of the present disclosure includes any or all of combinations of listed words. For example, the expression “A or B” may include A, may include B, or may include both A and B.

Unless defined differently, all terms used herein, which include technical terminologies or scientific terminologies, have the same meaning as that understood by a person skilled in the art to which the present disclosure belongs. Such terms as those defined in a generally used dictionary are to be interpreted to have the meanings equal to the contextual meanings in the relevant field of art, and are not to be interpreted to have ideal or excessively formal meanings unless clearly defined in the present disclosure.

Figures discussed below and various embodiments for describing the principles of the present disclosure in this patent document are only for illustration and should not be interpreted as limiting the scope of the present disclosure in any way. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.

FIG. 1 is an exemplary system architecture 100 of system architecture evolution (SAE). User equipment (UE) 101 is a terminal device for receiving data. An evolved universal terrestrial radio access network (E-UTRAN) 102 is a radio access network, which includes a macro base station (eNodeB/NodeB) that provides UE with interfaces to access the radio network. A mobility management entity (MME) 103 is responsible for managing mobility context, session context and security information of the UE. A serving gateway (SGW) 104 mainly provides functions of user plane, and the MME 103 and the SGW 104 may be in the same physical entity. A packet data network gateway (PGW) 105 is responsible for functions of charging, lawful interception, etc., and may be in the same physical entity as the SGW 104. A policy and charging rules function entity (PCRF) 106 provides quality of service (QoS) policies and charging criteria. A general packet radio service support node (SGSN) 108 is a network node device that provides routing for data transmission in a universal mobile telecommunications system (UMTS). A home subscriber server (HSS)109 is a home subsystem of the UE, and is responsible for protecting user information including a current location of the user equipment, an address of a serving node, user security information, and packet data context of the user equipment, etc.

FIG. 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of the present disclosure.

User equipment (UE) 201 is a terminal device for receiving data. A next generation radio access network (NG-RAN) 202 is a radio access network, which includes a base station (a gNB or an eNB connected to 5G core network 5GC, and the eNB connected to the 5GC is also called ng-gNB) that provides UE with interfaces to access the radio network. An access control and mobility management function entity (AMF) 203 is responsible for managing mobility context and security information of the UE. A user plane function entity (UPF) 204 mainly provides functions of user plane. A session management function entity SMF 205 is responsible for session management. A data network (DN) 206 includes, for example, services of operators, access of Internet and service of third parties.

Nodes mentioned in the present disclosure may include: gNB, gNB Central Unit (gNB-CU), gNB Distributed Unit (gNB-DU), gNB Central Unit Control Plane (gNB-CU-CP), gNB Central Unit User Plane (gNB CU-UP), en-gNB, eNB, ng-eNB, UE, Access and Mobility Management Function (AMF), Session Management Function (SMF), Mobility Management Entity (MME) and other network entities or network logic units, and cells and/or beams managed by them, etc.

The information and/or field described in the present disclosure may be an average value, an instantaneous value, a maximum value, a minimum value, etc., which is not limited in the present disclosure.

The information and/or field described in the present disclosure may be used to represent one or more of the following situations: uplink, downlink, uplink and downlink, uplink or downlink.

The information and/or fields described in the present disclosure may be a measured value and/or an actual value, or may be a predicted value.

The signal strength and/or signal quality and/or measurement report result and/or measurement result mentioned in the present disclosure may be a Received Signal Strength Indicator (RSSI), a Reference Signal Receiving Power, RSRP), a Reference Signal Receiving Quality (RSRQ), and a Signal to Interference plus Noise Ratio (SINR), etc.

In the present disclosure, a slice identification may be identified by one or more Single Network Slice Selection Assistance Information (S-NSSAI).

In the present disclosure, a failure type and/or problem type may also be referred to as a report type.

In the present disclosure, reports related to a Self-Optimization Network (SON) may include one or more of the following: a Connection Establishment Failure (CEF) report, or a Random Access report, or a Successful Handover report, or a Radio Link Failure (RLF) report, or a measurement report, or other reports related to wireless connection.

In the present disclosure, radio link failure contains radio link failure and handover failure.

In the present disclosure, a TA value obtained in advance and a TA value in an LTM command may refer to each other.

The network self-optimization decision mentioned in the present disclosure may include network energy saving, load balancing, coverage and/or capacity optimization, mobility optimization and/or management, making and/or updating configuration, etc.

In the present disclosure, a result and a report may refer to each other.

In the present disclosure, time can be represented by one or more of the following: timestamp, time point, time interval, timer, period of time, time length, time period, time spacing, etc. The time length may be the length of time from a certain time point, which may be the current time. The time may be a relative time or an absolute time. In some implementations, the period of time may be represented by separate fields, for example, by a combination of a start time and an end time, or by a combination of a start time and a time period.

In the present disclosure, Quality of Experience (QoE) parameters and/or user experience parameters may include one or more of the following: Round-trip time, Jitter duration, Corruption duration, Average throughput, Initial playout delay, Playout Delay at Initial Startup, Device information, Rendered viewports, Codec information, Buffer level, Representation switch events, Play List, Media presentation description (MPD) information, Interactivity Summary, Interactivity Event List, etc.

In the present disclosure, Quality of Service (QoS) parameters and/or QoS parameters may include at least one of: packet loss rate, delay, throughput, data rate, etc.

In the present disclosure, load condition and/or load information may include one or more of the following: PRB usage ratio, available PRB number, allocated PRB number, scheduling PDCCH CCE usage, Transport Network Layer (TNL) capacity indication, radio resource status, comprehensive available capacity group, comprehensive available resource group, number of active user terminals, Radio Resource Control (RRC) connection number, slice available capacity, hardware capacity indication, S1 TNL load indication, hardware load indication, Almost Blank Subframe (ABS) status, Reference Signal Received Power (RSRP) measurement report list, Reference Signal Receiving Quality (RSRQ) measurement report, Signal to Interference plus Noise Ratio (SINR) measurement report, Channel State Information (CSI) report, cell report indication, Channel Occupancy time ratio, Energy Detection threshold, signal strength and/or signal quality, channel busy ratio, data volume, and Jitter of the various parameters, etc.

In the present disclosure, load condition and/or load information may refer to the resource status.

In the present disclosure, capacity information may be one or more of the following: QoS requirement, QoS level, capacity status, average QoS requirement, average QoS level, average capacity status identification, proportion of one or more QoS requirements, proportion of one or more QoS levels, proportion of one or more capacity status identifications, etc. Herein, the capacity status is represented by an identification, where one identification represents one capacity configuration. The QoS level may be represented by an identification, for example, it may be a mapped 5G QoS Identifier (5QI) or a QoS Class Identifier (QCI).

In the present disclosure, capacity prediction information may be a predicted value of the capacity information.

In the present disclosure, coverage information may be one or more of the following: coverage status, information on coverage increase and/or decrease, ratio of coverage increase and/or decrease, load information at cell edge, information of load that changes from within coverage to outside coverage due to coverage change, and so on. Herein, the coverage status may be represented by an identification, where one identification represents one coverage configuration.

In the present disclosure, coverage prediction information may be a predicted value of the coverage information.

In the present disclosure, coverage and/or capacity, coverage change, coverage and/or capacity optimization may refer to each other.

In the present disclosure, a coverage and/or capacity policy (information) may include one or more of the following: cell identification, cell status, cell deployment status indication, replacing cell information, beam coverage change information, reasons for coverage change, etc. Herein, the replacing cell information may include one or more of the following: identification of a replacing cell, identification of a replaced cell, proportion of replacing cells that can replace the replaced cells, etc. The beam coverage change information may include one or more of the following: beam identification, beam coverage status, etc.

In the present disclosure, a beam may refer to a Synchronization Signal and Physical Broadcast Channel (PBCH) block (SSB) beam, or any other beam.

In the present disclosure, a location range may be referred to by one or more of the following: coordinates, areas, cell identification, beam identification, identification for indicating a location and/or area, and the like. Herein, the cell identification may be one or more of the following: accessed/visited cell identification, connecting cell identification, serving cell identification, etc. The beam identification may be one or more of the following: accessed/visited beam identification, connecting beam identification, accessed/visited beam identification, etc. Herein, the identification for indicating a location and/or area is used to represent one or more locations and/or one or more areas. In some implementations, for example, it may be an area with a distance greater than and/or equal to and/or less than a threshold, which is represented by an identification. In some other implementations, for example, it may be an area with a signal quality greater than and/or equal to and/or less than a threshold, which is represented by an identification.

In the present disclosure, a target node may also be a candidate target node, a target master node, a target secondary node, a candidate target master node, a candidate target secondary node, and the like.

In the present disclosure, a source node may also be a source master node, a source secondary node, and the like.

In the present disclosure, data collection may be Minimization of Drive Tests (MDT) or any other data collection, which is not limited in the present disclosure. The MDT may be a Logged MDT or an Immediate MDT; the MDT may be a Signaling-based MDT or a Management-based MDT.

In the present disclosure, data collection may be used to collect user trajectory information and/or user performance information, and may also be used for collection of any other data.

In the present disclosure, a secondary cell may be a Primary Secondary Cell (PSCell) or a Secondary Cell (SCell).

In the present disclosure, collection/collect may be used interchangeably with measurement/measure.

In the present disclosure, data corresponding to the data collection may include one or more of the following:

- User trajectory related data, which may include one or more of the following:

* user identifier/identification (ID)

* identifier of an accessed/visited cell

* identifier of an accessed/visited primary cell

* identifier of an accessed/visited secondary cell

* identifier of an accessed/visited primary cell and identifier of an accessed/visited secondary cell, which indicate an accessed/visited primary cell and an accessed/visited secondary cell in a dual-connectivity case.

* node where an accessed/visited cell is located, which may be a node identifier or a node name.

* node where an accessed/visited primary cell is located, which may be a node identifier or a node name.

* node where an accessed/visited secondary cell is located, which may be a node identifier or a node name.

* accessing time and/or resident time

* coordinate

* information of an accessed/visited beam, which may be a beam identifier.

- User performance related data, which may include one or more of the following:

* user identifier

* time for user performance collection

* node corresponding to user performance collection, which may be a node identifier or a node name.

* cell identifier corresponding to user performance

* user performance, which may include one or more of the following: uplink and/or downlink data rate, uplink and/or downlink throughput, uplink and/or downlink delay, uplink and/or downlink packet loss rate, uplink and/or downlink QoE parameters.

- User measurement result information, which may include one or more of the following:

* user identifier

* node identifier and/or cell identifier corresponding to a user measurement result

* measurement result

* measurement time

- Sensing related result information, which may include one or more of the following:

* user identifier

* node identifier and/or cell identifier corresponding to a user sensing related measurement result

* sensing related measurement result

* sensing related measurement time

Example 1

An aspect of the present disclosure provides a method for supporting data collection, which may include: a first node transmits a first message including a request for single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection to a second node to inform the second node of a collection configuration and/or reporting configuration corresponding to single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection that needs to be performed. Herein, single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection may also be referred to as data collection for short.

In some implementations, the first message may be included in one or more of the following:

a Handover Request message or an S-NODE ADDITION REQUEST message or an S-NODE MODIFICATION REQUEST message or an S-NODE MODIFICATION REQUIRED message or an S-NODE CHANGE REQUIRED message or a RESOURCE STATUS REQUEST message or an NG-RAN NODE CONFIGURATION UPDATE message or an NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message or an XN SETUP REQUEST message or an XN SETUP RESPONSE message or a DATA COLLECTION REQUEST message of Xn;

or an NG SETUP REQUEST message or an NG SETUP RESPONSE message or a RAN CONFIGURATION UPDATE message or a RAN CONFIGURATION UPDATE ACKNOWLEDGE message or an AMF CONFIGURATION UPDATE message or an AMF CONFIGURATION UPDATE ACKNOWLEDGE message or an AMF STATUS INDICATION message or an OVERLOAD START message or an OVERLOAD STOP message of NG;

or an F1 SETUP REQUEST message or an F1 SETUP RESPONSE message or a GNB-DU CONFIGURATION UPDATE message or a GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-CU CONFIGURATION UPDATE message or a GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-DU STATUS INDICATION message or a RESOURCE STATUS REQUEST message of F1;

or a GNB-CU-UP E1 SETUP REQUEST message or a GNB-CU-UP E1 SETUP RESPONSE message or a GNB-CU-CP E1 SETUP REQUEST message or a GNB-CU-CP E1 SETUP RESPONSE message or a GNB-CU-UP CONFIGURATION UPDATE message or a GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-CU-CP CONFIGURATION UPDATE message or a GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-CU-UP STATUS INDICATION message or a RESOURCE STATUS REQUEST message of E1;

or an RRCReconfiguration message or an RRCReconfigurationComplete message or a UEInformationRequest message of RRC;

or an other and/or newly defined RRC and/or Xn and/or X2 and/or F1 and/or E1 and/or NG message and/or RRC container and/or MAC CE, etc.

In some implementations, the first message may include one or more of the following information and/or fields:

- transmitting node ID: used to identify a node that transmits the message.

- receiving node ID: used to identify a node that receives the message.

- request ID: used to identify the request.

- measurement ID: used to identify the measurement request. For example, the measurement ID may be assigned by a message transmitting node and/or a message receiving node.

- collection ID: used to identify the data collection. For example, the collection ID may be assigned by a message transmitting node and/or a message receiving node.

- configuration ID: used to identify a configuration of the data collection. This ID can uniquely identify a data collection configuration.

- data collection start indication (identification): it may also be called an identification indicating that the configuration corresponding to the message (for example, collection configuration and/or reporting configuration) is a start configuration for data collection, which is used to indicate that the collection configuration and/or reporting configuration are the start of the data collection. In some implementations, for example, the indication informs the message receiving node that this configuration is the start configuration for data collection. If the UE needs to be handed over, the message receiving node needs to decide whether to request a (candidate) handover target node to perform data collection for the UE according to the configuration, and/or request the (candidate) target node to perform configuration of data collection for the UE. In other implementations, for example, the indication informs the message receiving node that this configuration is a start configuration for data collection. If a secondary node needs to be added and/or changed for the UE, the message receiving node needs to decide whether to request a (candidate) target secondary node to perform data collection for the UE according to the configuration, and/or request the (candidate) target secondary node to perform configuration of data collection for the UE. In still other implementations, the message receiving node can know that a data collection result needs to be transmitted to the message transmitting node of the message through the indication.

- information of a node and/or cell that is initially configured for data collection (information of initial configuration node/cell of data collection): in some implementations, for example, this information may be used to uniquely identify a data collection among multiple nodes. In other implementations, for example, this information may be used to uniquely identify data collection for a UE among multiple nodes. In still other implementations, for example, this information may inform the node to which data collection results ultimately need to be transmitted. For example, in a multi-hop case, a data collection node may directly transmit the results to the node that is initially configured for the data collection, so as to avoid the need for intermediate nodes to perform forwarding in a multi-hop case and achieve an effect of signaling saving. For example, in a multi-hop case, a data collection node uniquely identifies a data collection and/or data collection for the same UE among multiple nodes by using the information of the node and/or cell that is initially configured for the data collection, which may avoid a case where other nodes except the node that is initially configured for the data collection still need to keep the UE context after the UE is handed over to another node in a multi-hop case, resulting in too much information stored by the nodes, and/or a case where the identifier assigned for the UE for which the data collection is targeted cannot be allocated to other UEs for a long time. This information may include one or more of the following:

* identifier of a node that is initially configured for the data collection

* identifier of a cell that is initially configured for the data collection

* UE identifier assigned by the node that is initially configured for the data collection. In some implementations, for example, it may be an XnAP (Xn-interface Application Protocol) UE ID assigned for a UE by node that is initially configured for the data collection.

* identifier assigned for the data collection by the node that is initially configured the data collection. It may include one or more of the following: a request ID, a measurement ID, a collection ID, a configuration ID, etc.

* identifier assigned for the data collection by a message receiving node of an initial configuration for the data collection. It may include one or more of the following: a request ID, a measurement ID, a collection ID, a configuration ID, etc.

- measurement configuration: a configuration corresponding to a measurement. The measurement configuration may include one or more of the following: frequency domain information of the measurement, time information of the measurement, start time of the measurement, end time of the measurement, period of the measurement, time of the measurement, type of the measurement, signal for the measurement, frequency domain information of the signal for the measurement, type of the signal for the measurement, configuration corresponding to the signal for the measurement, etc. Types of the measurement may include one or more of the following: periodic measurement, continuous measurement, single measurement, etc. The frequency domain information of the measurement and/or the frequency domain information of the signal for the measurement may include one or more of the following: starting frequency, center frequency of the measurement, frequency hopping information, subcarrier interval, etc.

- number of accessed/visited nodes: which indicates the maximum number of accessed/visited nodes. The accessed/visited node may be one or more of the following: a connected node, an accessed/visited master node, an accessed/visited secondary node, etc. In some implementations, for example, when the number of actually accessed/visited nodes reaches the number of accessed/visited nodes, data collection is stopped and/or data reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of collected data (for example, situation of current data collection of a corresponding UE, which will not be described in detail below). For example, the number of nodes in this configuration should be the number of nodes in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of nodes corresponding to the collected data.

- hop number: used to indicate the maximum number of hops to be accessed/visited. The hops may include one or more of the following: the UE jumps from one connecting node to another connecting node, the UE jumps from one master node to another master node, the UE changes from connecting to a (primary) node to connecting to a master node plus a secondary node, the UE jumps from one secondary node to another secondary node, and the UE changes from not having a secondary node to connecting to a secondary node, etc. In some implementations, for example, when the actual hop number reaches the hop number, data collection is stopped and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the hop number in this configuration should be the number of hops in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of hops corresponding to the collected data.

- number of accessed/visited cells: which indicates the maximum number of accessed/visited cells. In some implementations, for example, the accessed/visited cells may be accessed/visited cells corresponding to multiple accessed/visited nodes in a multi-hop case. In still other implementations, for example, the accessed/visited cell may be an accessed/visited primary cell, an accessed/visited secondary cell, an accessed/visited primary cell and an accessed/visited secondary cell. In some implementations, for example, when the number of actually accessed/visited cells reaches the number of accessed/visited cells, data collection is stopped and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the configured cell number should be the number of cells in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of cells corresponding to the collected data.

- number of accessed/visited cells corresponding to an accessed/visited node: which indicates the number of accessed/visited cells in an accessed/visited node. In some implementations, for example, in a multi-hop case, a plurality of nodes is accessed/visited, and when the number of accessed/visited cells in one accessed/visited node reaches the number of accessed/visited cells corresponding to the accessed/visited node, data collection is stopped, and/or collection of other accessed/visited cells of the accessed/visited node is stopped, and/or reporting is started.

number of accessed/visited secondary nodes: which indicates the maximum number of accessed/visited secondary nodes. In some implementations, for example, when the number of actually accessed/visited secondary nodes reaches the number of accessed/visited secondary nodes, data collection is stopped and/or data reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the number of nodes in this configuration should be the number of nodes in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of nodes corresponding to the collected data.

- number of accessed/visited secondary cells: which indicates the maximum number of accessed/visited secondary cells. In some implementations, for example, when the number of actually accessed/visited secondary cells reaches the number of accessed/visited secondary cells, data collection is stopped and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the configured cell number should be the number of cells in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of cells corresponding to the collected data.

- number of accessed/visited master nodes: which indicates the maximum number of accessed/visited master nodes. In some implementations, for example, when the number of actually accessed/visited master nodes reaches the number of accessed/visited master nodes, data collection is stopped and/or data reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the number of nodes in this configuration should be the number of nodes in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of nodes corresponding to the collected data.

- number of accessed/visited primary cells: which indicates the maximum number of accessed/visited primary cells. In some implementations, for example, when the number of actually accessed/visited primary cells reaches the number of accessed/visited primary cells, data collection is stopped and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the configured cell number should be the number of cells in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of cells corresponding to the collected data.

- number of accessed/visited secondary cells corresponding to an accessed/visited secondary node: which indicates the number of accessed/visited secondary cells in an accessed/visited secondary node. In some implementations, for example, when a plurality of secondary nodes are accessed/visited, when the number of actually accessed/visited secondary cells in one of the accessed/visited secondary nodes reaches the number of accessed/visited secondary cells corresponding to the accessed/visited secondary node, data collection is stopped, and/or corresponding data collection of subsequent other accessed/visited secondary cells of the accessed/visited secondary node is stopped, and/or reporting is started.

- number of accessed/visited primary cells corresponding to an accessed/visited master node: which indicates the number of accessed/visited primary cells in an accessed/visited master node. In some implementations, for example, when a plurality of master nodes are accessed/visited, when the number of actually accessed/visited primary cells in one of the master nodes reaches the number of accessed/visited primary cells corresponding to the accessed/visited master node, data collection is stopped, and/or corresponding data collection of subsequent other accessed/visited primary cells of the master node is stopped, and/or reporting is started.

- number of accessed/visited primary cells and/or secondary cells corresponding to an accessed/visited master node: which indicates the maximum number of primary cells and/or secondary cells in an accessed/visited master node. In some implementations, for example, when the number of accessed/visited primary cells and/or the number of accessed/visited secondary cells reaches the number of accessed/visited primary cells and/or secondary cells corresponding to an accessed/visited master node in the accessed/visited master node, data collection is stopped, and/or data collection corresponding to subsequent other accessed/visited cells in the accessed/visited master node is stopped, and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the configured number of accessed/visited primary cells and/or secondary cells corresponding to an accessed/visited master node should be the number of secondary cells in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of secondary cells corresponding to the collected data.

- indication (identification) of subsequent multi-hop data collection: it may also be called an identification indicating that the configuration corresponding to the message (for example, collection configuration and/or reporting configuration) is a subsequent configuration for data collection, which is used to indicate that the collection configuration and/or reporting configuration is data collection on the second hop and/or after the second hop. This indication informs the message receiving node that this configuration is a configuration for subsequent multi-hop data collection. In some implementations, for example, the message receiving node needs to obtain all and/or part of the data collection configuration in a subsequent message. For example, this configuration message only contains a reporting configuration, and a collection configuration is included in a subsequent message. In other implementations, for example, the message receiving node needs to obtain more data collection configurations in subsequent messages. In still other implementations, for example, if the message receiving node receives a data collection configuration in a subsequent message, the data collection configuration received subsequently shall prevail. In still other implementations, for example, the data reporting configured by the data collection configuration may be used to carry multi-hop data collection results. For example, the message receiving node needs to obtain a multi-hop data collection configuration in a subsequent message. The subsequent message may be a handover request message, a secondary node addition request message, or a secondary node modification request message.

- receiving node and/or cell corresponding to data collection and reporting: used to indicate which node and/or cell the data collection needs to be reported to. This information may be represented by an identifier of the node and/or the cell. In the case of multi-hop, the data collection node may directly transmit the collected data to the receiving node and/or cell corresponding to the data collection and reporting, so as to avoid forwarding by an intermediate node in a multi-hop case and achieve an effect of signaling saving.

- collection time: the collection time corresponding to data collection. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the collection time in this configuration should be the collection time in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the collection time corresponding to the collected data.

- event for stopping collection: when the event is met, data collection will be stopped. It may include one or more of the following:

* UE leaves the currently connected node.

* UE is handed over to another node.

* The actual collection time reaches the collection time.

* UE changes from an RRC Connected state to an RRC Idle state or RRC Inactive state.

* UE changes from an RRC Idle state or RRC Inactive state to an RRC Connected state.

* the RRC state of the UE changes.

* UE accesses and/or leaves one or more slices. This event may include one or more of the following: event type, event, slice identification and/or identification list, etc.

* the measurement report of UE is less than and/or equal to a predetermined threshold. The event configuration includes one or more of the following: event type, event, predetermined threshold, hysteresis and/or meeting time. For example, the event may imply that the UE needs to be handed over, so the UE will access to a next node and/or cell, and the data collection at the node and/or cell would be stopped.

- event for starting collection: when the event is met, data collection will be started. It may include one or more of the following:

* UE accesses the message receiving node.

* UE is handed over to the message receiving node.

* the RRC state of the UE changes.

* the measurement report of UE is greater than and/or equal to a predetermined threshold. The event configuration includes one or more of the following: event type, event, predetermined threshold, hysteresis and/or meeting time. For example, the event may indicate that the measurement result of the UE at the node and/or cell is good, so the UE will not be handed over for the moment, so corresponding data collection at the node and/or cell may be started.

* the message receiving node receives information related to artificial intelligence (AI)/Machine learning (ML): the AI/ML related information may include one or more of the following: measurement result prediction, trajectory prediction result, load prediction result, AI/ML related decision, etc. In some implementations, for example, the AI/ML related decision may be an AI/ML related self-optimization decision.

- reporting configuration: it may include one or more of the following:

* reporting time: reporting will be performed within the reporting time.

* reporting type: it may include one or more of the following: single reporting, on-demand * reporting, periodic reporting and event-triggered reporting.

* reporting period: the time interval between two reporting. In some implementations, it may be the time interval between two reporting in a case of periodic reporting.

* trigger event: when the following conditions are met, reporting will be triggered. It may include one or more of the following:

- UE leaves the currently connected node.

- UE is handed over to another node.

- The actual collection time reaches the collection time.

- UE enters an RRC Idle state or RRC Inactive state. For example, the UE changes from an RRC Idle state or RRC Inactive state to an RRC Connected state.

- The UE changes from an RRC Connected state to an RRC Idle state or RRC Inactive state.

- the RRC state of the UE changes.

- UE accesses and/or leaves one or more slices. This event may include one or more of the following: event type, event, slice identification and/or identification list, etc.

- The measurement report of the UE is less than and/or equal to a predetermined threshold. The event configuration includes one or more of the following: event type, event, predetermined threshold and meeting time. For example, the event may imply that the UE needs to be handed over, so the UE will access to a next node and/or cell, so the data collection at this node and/or cell will be reported.

Optionally, after receiving the first message of a request for single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection transmitted by the first node, the second node transmits a second message of a response for the single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection to the first node, so as to inform the first node whether the second node can perform reporting and/or collection.

In some implementations, the second message may be included in one or more of the following:

a HANDOVER REQUEST ACKNOWLEDGE message or an S-NODE ADDITION REQUEST ACKNOWLEDGE message or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message or an S-NODE MODIFICATION CONFIRM message or an S-NODE CHANGE CONFIRM message or a RESOURCE STATUS RESPONSE message or a RESOURCE STATUS FAILURE message or an NG-RAN NODE CONFIGURATION UPDATE message or an NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message or an XN SETUP REQUEST message or an XN SETUP RESPONSE message or a DATA COLLECTION RESPONSE message or a DATA COLLECTION FAILURE message of Xn;

or an F1 SETUP REQUEST message or an F1 SETUP RESPONSE message or a GNB-DU CONFIGURATION UPDATE message or a GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-CU CONFIGURATION UPDATE message or a GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-DU STATUS INDICATION message or a RESOURCE STATUS RESPONSE message or a RESOURCE STATUS FAILURE message of F1;

or a GNB-CU-UP E1 SETUP REQUEST message or a GNB-CU-UP E1 SETUP RESPONSE message or a GNB-CU-CP E1 SETUP REQUEST message or a GNB-CU-CP E1 SETUP RESPONSE message or a GNB-CU-UP CONFIGURATION UPDATE message or a GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-CU-CP CONFIGURATION UPDATE message or a GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-CU-UP STATUS INDICATION message or a RESOURCE STATUS RESPONSE message or a RESOURCE STATUS FAILURE of E1;

or an RRCReconfiguration message or an RRCReconfigurationComplete message or a MeasurementReport message or a UEInformationResponse message;

In some implementations, the second message may include one or more of the following information and/or fields:

- transmitting node ID: used to identify a node that transmits the message.

- receiving node ID: used to identify a node that receives the message.

- request ID: used to identify the request. The ID may be consistent with the request ID in the first message to match the response message with the request message.

- measurement ID: used to identify the measurement request. For example, the ID may include a measurement ID assigned by a message transmitting node and/or a measurement ID assigned by a message receiving node. For example, the ID may include a measurement ID assigned by the second node and/or a measurement ID assigned by the first node. The ID may be consistent with the measurement ID in the first message to match the response message with the request message. The ID may be consistent with the measurement ID in the first message to match the response message with the request message.

- collection ID: used to identify the data collection. For example, the ID may include a collection ID assigned by a message transmitting node and/or a collection ID assigned by a message receiving node. For example, the ID may include a collection ID assigned by the second node and/or a collection ID assigned by the first node. The ID may be consistent with the collection ID in the first message to match the response message with the request message. For example, the collection ID may be consistent with the collection ID in the first message to match the response message with the request message.

- configuration ID: used to identify a configuration corresponding to the data collection response. This ID can uniquely identify a data collection configuration.

- configuration available for collection, which may include one or more of the following:

* number of accessed/visited nodes available for collection: which indicates the maximum number of accessed/visited nodes available for a collection. The accessed/visited node may be one or more of the following: a connected node, an accessed/visited master node, an accessed/visited secondary node, etc. In some implementations, for example, when the number of actually accessed/visited nodes reaches the number of accessed/visited nodes, data collection is stopped and/or data reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the number of nodes in this configuration should be the number of nodes in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of nodes corresponding to the collected data.

* number of hops available for collection: used to indicate the maximum number of hops available for a collection. The hops may include one or more of the following: the UE jumps from one connecting node to another connecting node, the UE jumps from one master node to another master node, the UE changes from connecting to a (primary) node to connecting to a master node plus a secondary node, the UE jumps from one secondary node to another secondary node, and the UE changes from not having a secondary node to connecting to a secondary node, etc. In some implementations, for example, when the actual hop number reaches the hop number, data collection is stopped and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the hop number in this configuration should be the number of hops in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of hops corresponding to the collected data.

* number of accessed/visited cells available for collection: which indicates the maximum number of accessed/visited cells available for a collection. In some implementations, for example, the accessed/visited cells may be accessed/visited cells corresponding to multiple accessed/visited nodes in a multi-hop case. In still other implementations, for example, the accessed/visited cell may be an accessed/visited primary cell, an accessed/visited secondary cell, an accessed/visited primary cell and an accessed/visited secondary cell. In some implementations, for example, when the number of actually accessed/visited cells reaches the number of accessed/visited cells, data collection is stopped and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the configured cell number should be the number of cells in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of cells corresponding to the collected data.

* number of accessed/visited cells corresponding to an accessed/visited node available for collection: which indicates the number of accessed/visited cells available for a collection in an accessed/visited node. In some implementations, for example, in a multi-hop case, a plurality of nodes is accessed/visited, and when the number of accessed/visited cells in one accessed/visited node reaches the number of accessed/visited cells corresponding to the accessed/visited node, data collection is stopped, and/or collection of other accessed/visited cells of the accessed/visited node is stopped, and/or reporting is started.

* number of accessed/visited secondary nodes available for collection: which indicates the maximum number of accessed/visited secondary nodes available for a collection. In some implementations, for example, when the number of actually accessed/visited secondary nodes reaches the number of accessed/visited secondary nodes, data collection is stopped and/or data reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the number of nodes in this configuration should be the number of nodes in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of nodes corresponding to the collected data.

* number of accessed/visited secondary cells available for collection: which indicates the maximum number of accessed/visited secondary cells available for a collection. In some implementations, for example, when the number of actually accessed/visited secondary cells reaches the number of accessed/visited secondary cells, data collection is stopped and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the configured cell number should be the number of cells in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of cells corresponding to the collected data.

* number of accessed/visited master nodes available for collection: which indicates the maximum number of accessed/visited master nodes available for a collection. In some implementations, for example, when the number of actually accessed/visited master nodes reaches the number of accessed/visited master nodes, data collection is stopped and/or data reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the number of nodes in this configuration should be the number of nodes in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of nodes corresponding to the collected data.

* number of accessed/visited primary cells available for collection: which indicates the maximum number of accessed/visited primary cells corresponding to collection that can be performed. In some implementations, for example, when the number of actually accessed/visited primary cells reaches the number of accessed/visited primary cells, data collection is stopped and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the configured cell number should be the number of cells in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of cells corresponding to the collected data.

* number of accessed/visited secondary cells corresponding to an accessed/visited secondary node available for collection: which indicates the number of accessed/visited secondary cells available for a collection in an accessed/visited secondary node. In some implementations, for example, when a plurality of secondary nodes are accessed/visited, when the number of actually accessed/visited secondary cells in one of the accessed/visited secondary nodes reaches the number of accessed/visited secondary cells corresponding to the accessed/visited secondary node, data collection is stopped, and/or corresponding data collection of subsequent other accessed/visited secondary cells of the accessed/visited secondary node is stopped, and/or reporting is started.

* number of accessed/visited primary cells corresponding to an accessed/visited master node available for collection: which indicates the number of accessed/visited primary cells for a collection that can be performed in an accessed/visited master node. In some implementations, for example, when a plurality of master nodes are accessed/visited, when the number of actually accessed/visited primary cells in one of the master nodes reaches the number of accessed/visited primary cells corresponding to the accessed/visited master node, data collection is stopped, and/or corresponding data collection of subsequent other accessed/visited primary cells of the master node is stopped, and/or reporting is started.

* number of accessed/visited primary cells and/or secondary cells corresponding to an accessed/visited master node available for collection: which indicates the maximum number of accessed/visited primary cells and/or secondary cells available for a collection in an accessed/visited master node. In some implementations, for example, when the number of accessed/visited primary cells and/or the * number of accessed/visited secondary cells reaches the number of accessed/visited primary cells and/or secondary cells corresponding to an accessed/visited master node in the accessed/visited master node, data collection is stopped, and/or data collection corresponding to subsequent other accessed/visited cells in the accessed/visited master node is stopped, and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the configured number of accessed/visited primary cells and/or secondary cells corresponding to an accessed/visited master node should be the number of secondary cells in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of secondary cells corresponding to the collected data.

* indication about whether subsequent multi-hop data collection can be performed: used to indicate whether data collection at the second hop and/or after the second hop can be performed.

* available collection time: the collection time that can be used for data collection.

* information about whether a data collection result can be reported to a requested corresponding receiving node and/or cell: which may be used to indicate whether a data collection result can be reported to the receiving node and/or cell corresponding to data collection and reporting in the first message. It may also be used to indicate whether a data collection result can be reported to a node and/or cell corresponding to the Information of initial configuration node/cell of data collection in the first message.

* collection stop events available for data collection: the events may be one or more of the events for stopping collection in the first message.

* collection start events available for data collection: the events may be one or more of the events for starting collection in the first message.

* measurement configuration available for data collection: the measurement configuration may include one or more of the following: frequency domain information of the measurement, time information of the measurement, start time of the measurement, end time of the measurement, period of the measurement, time of the measurement, type of the measurement, signal for the measurement, frequency domain information of the signal for the measurement, type of the signal for the measurement, configuration corresponding to the signal for the measurement, etc. Types of the measurement may include one or more of the following: periodic measurement, continuous measurement, single measurement, etc. The frequency domain information of the measurement and/or the frequency domain information of the signal for the measurement may include one or more of the following: starting frequency, center frequency of the measurement, frequency hopping information, etc.

- configuration available for reporting: it may include one or more of the following:

* available reporting time: reporting can be performed within the reporting time.

* available reporting type: it may include one or more of the following: single reporting, on-demand reporting, periodic reporting and event-triggered reporting.

* available reporting period: the time interval between two reporting. In some implementations, it may be the time interval between two reporting in a case of periodic reporting.

* trigger events available for reporting: the events may be one or more trigger events in the reporting configuration in the first message.

- configuration unavailable for collection: it may include one or more of the following:

* number of accessed/visited nodes unavailable for collection: which indicates the maximum number of accessed/visited nodes unavailable for a collection. The accessed/visited node may be one or more of the following: a connected node, an accessed/visited master node, an accessed/visited secondary node, etc. In some implementations, for example, when the number of actually accessed/visited nodes reaches the number of accessed/visited nodes, data collection is stopped and/or data reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the number of nodes in this configuration should be the number of nodes in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of nodes corresponding to the collected data.

* number of hops unavailable for collection: used to indicate the maximum number of hops unavailable for a collection. The hops may include one or more of the following: the UE jumps from one connecting node to another connecting node, the UE jumps from one master node to another master node, the UE changes from connecting to a (primary) node to connecting to a master node plus a secondary node, the UE jumps from one secondary node to another secondary node, and the UE changes from not having a secondary node to connecting to a secondary node, etc. In some implementations, for example, when the actual hop number reaches the hop number, data collection is stopped and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the hop number in this configuration should be the number of hops in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of hops corresponding to the collected data.

* number of accessed/visited cells unavailable for collection: which indicates the maximum number of accessed/visited cells unavailable for a collection. In some implementations, for example, the accessed/visited cells may be accessed/visited cells corresponding to multiple accessed/visited nodes in a multi-hop case. In still other implementations, for example, the accessed/visited cell may be an accessed/visited primary cell, an accessed/visited secondary cell, an accessed/visited primary cell and an accessed/visited secondary cell. In some implementations, for example, when the number of actually accessed/visited cells reaches the number of accessed/visited cells, data collection is stopped and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the configured cell number should be the number of cells in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of cells corresponding to the collected data.

* number of accessed/visited cells corresponding to an accessed/visited node unavailable for collection: which indicates the number of accessed/visited cells unavailable for a collection in an accessed/visited node. In some implementations, for example, in a multi-hop case, a plurality of nodes is accessed/visited, and when the number of accessed/visited cells in one accessed/visited node reaches the number of accessed/visited cells corresponding to the accessed/visited node, data collection is stopped, and/or collection of other accessed/visited cells of the accessed/visited node is stopped, and/or reporting is started.

* number of accessed/visited secondary nodes unavailable for collection: which indicates the maximum number of accessed/visited secondary nodes unavailable for a collection. In some implementations, for example, when the number of actually accessed/visited secondary nodes reaches the number of accessed/visited secondary nodes, data collection is stopped and/or data reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the number of nodes in this configuration should be the number of nodes in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of nodes corresponding to the collected data.

* number of accessed/visited secondary cells unavailable for collection: which indicates the maximum number of accessed/visited secondary cells unavailable for a collection. In some implementations, for example, when the number of actually accessed/visited secondary cells reaches the number of accessed/visited secondary cells, data collection is stopped and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the configured cell number should be the number of cells in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of cells corresponding to the collected data.

* number of accessed/visited master nodes unavailable for collection: which indicates the maximum number of accessed/visited master nodes unavailable for a collection. In some implementations, for example, when the number of actually accessed/visited master nodes reaches the number of accessed/visited master nodes, data collection is stopped and/or data reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the number of nodes in this configuration should be the number of nodes in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of nodes corresponding to the collected data.

* number of accessed/visited primary cells unavailable for collection: which indicates the maximum number of accessed/visited primary cells unavailable for a collection. In some implementations, for example, when the number of actually accessed/visited primary cells reaches the number of accessed/visited primary cells, data collection is stopped and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the configured cell number should be the number of cells in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of cells corresponding to the collected data.

* number of accessed/visited secondary cells corresponding to an accessed/visited secondary node unavailable for collection: which indicates the number of accessed/visited secondary cells unavailable for a collection in an accessed/visited secondary node. In some implementations, for example, when a plurality of secondary nodes are accessed/visited, when the number of actually accessed/visited secondary cells in one of the accessed/visited secondary nodes reaches the number of accessed/visited secondary cells corresponding to the accessed/visited secondary node, data collection is stopped, and/or corresponding data collection of subsequent other accessed/visited secondary cells of the accessed/visited secondary node is stopped, and/or reporting is started.

* number of accessed/visited primary cells corresponding to an accessed/visited master node unavailable for collection: which indicates the number of accessed/visited primary cells unavailable for a collection in an accessed/visited master node. In some implementations, for example, when a plurality of master nodes are accessed/visited, when the number of actually accessed/visited primary cells in one of the master nodes reaches the number of accessed/visited primary cells corresponding to the accessed/visited master node, data collection is stopped, and/or corresponding data collection of subsequent other accessed/visited primary cells of the master node is stopped, and/or reporting is started.

* number of accessed/visited primary cells and/or secondary cells corresponding to an accessed/visited master node unavailable for collection: which indicates the maximum number of accessed/visited primary cells and/or accessed/visited secondary cells unavailable for a collection in an accessed/visited master node. In some implementations, for example, when the number of accessed/visited primary cells and/or the number of accessed/visited secondary cells reaches the number of accessed/visited primary cells and/or secondary cells corresponding to an accessed/visited master node in the accessed/visited master node, data collection is stopped, and/or data collection corresponding to subsequent other accessed/visited cells in the accessed/visited master node is stopped, and/or reporting is started. For data collection of a second hop and/or after a second hop, this information needs to be set in consideration of the collected data. For example, the configured number of accessed/visited primary cells and/or secondary cells corresponding to an accessed/visited master node should be the number of secondary cells in the configuration and/or initial configuration contained in the request corresponding to the first hop and/or the previous hop minus the number of secondary cells corresponding to the collected data.

* unavailable collection time: the collection time that cannot be used for data collection.

* collection stop events unavailable for data collection: the events may be one or more of the events for stopping collection in the first message.

* collection start events unavailable for data collection: the events may be one or more of the events for starting collection in the first message.

* measurement configuration unavailable for data collection: the measurement configuration may include one or more of the following: frequency domain information of the measurement, time information of the measurement, start time of the measurement, end time of the measurement, period of the measurement, time of the measurement, type of the measurement, signal for the measurement, frequency domain information of the signal for the measurement, type of the signal for the measurement, configuration corresponding to the signal for the measurement, etc. Types of the measurement may include one or more of the following: periodic measurement, continuous measurement, single measurement, etc. The frequency domain information of the measurement and/or the frequency domain information of the signal for the measurement may include one or more of the following: starting frequency, center frequency of the measurement, frequency hopping information, etc.

- configuration unavailable for reporting: it may include one or more of the following:

* unavailable reporting time: reporting cannot be performed within the reporting time.

* unavailable reporting type: it may include one or more of the following: single reporting, on-demand reporting, periodic reporting and event-triggered reporting.

* unavailable reporting period: the time interval between two reporting. In some implementations, it may be the time interval between two reporting in a case of periodic reporting.

* trigger events unavailable for reporting: the events may be one or more trigger events in the reporting configuration in the first message.

- cause/reason: the reason why collection and/or reporting cannot be performed.

In some implementations, the second node may transmit a third message of a result of single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection to the first node according to its own situation and/or a first message including a request for single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection received from the first node, so as to transmit the data collected by the second node to the first node.

It may also be that node A (e.g., an accessed/visited node in the multi-hop and/or a node at which the data collection is completed) transmits a third message of a result of single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection to the first node to the first node according to its own situation and/or a first message including a request for single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection received from node B (e.g., a node before node A in the multi-hop and/or a node before the node at which the data collection is completed), so as to transmit the data collected by node A to the first node.

In some implementations, for example, after the first node receives the result of the data collection, it may train an AI/ML model based on the received data collection result. In other implementations, for example, after the first node receives the data collection result, it may evaluate the output result of the AI/ML model and/or the accuracy of the AI/ML model. Herein, the evaluation of the output result of the AI/ML model may be an evaluation of the accuracy of the output result of the AI/ML model. For example, when the result of data collection deviates greatly from the output result of the model, it indicates that the output result of the AI/ML model is inaccurate and/or the accuracy of the AI/ML model is low. Nodes may trigger updating and/or retraining of the AI/ML model.

In some implementations, the third message may be included in one or more of the following:

a HANDOVER REQUEST ACKNOWLEDGE message or an S-NODE ADDITION REQUEST ACKNOWLEDGE message or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message or an S-NODE MODIFICATION CONFIRM message or an S-NODE CHANGE CONFIRM message or a RESOURCE STATUS UPDATE message or an NG-RAN NODE CONFIGURATION UPDATE message or an NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message or an XN SETUP REQUEST message or an XN SETUP RESPONSE message or a DATA COLLECTION UPDATE message of Xn;

or an F1 SETUP REQUEST message or an F1 SETUP RESPONSE message or a GNB-DU CONFIGURATION UPDATE message or a GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-CU CONFIGURATION UPDATE message or a GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-DU STATUS INDICATION message or a RESOURCE STATUS UPDATE message of F1;

or a GNB-CU-UP E1 SETUP REQUEST message or a GNB-CU-UP E1 SETUP RESPONSE message or a GNB-CU-CP E1 SETUP REQUEST message or a GNB-CU-CP E1 SETUP RESPONSE message or a GNB-CU-UP CONFIGURATION UPDATE message or a GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-CU-CP CONFIGURATION UPDATE message or a GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-CU-UP STATUS INDICATION message or a RESOURCE STATUS UPDATE message of E1;

In some implementations, the third message may include one or more of the following information and/or fields:

- transmitting node ID: used to identify a node that transmits the message.

- receiving node ID: used to identify a node that receives the message.

- request ID: used to identify the request. The ID may be consistent with the request ID in the first message and/or the second message, so as to match the result reporting message with the request message.

- measurement ID: used to identify the measurement request. The ID may be consistent with the measurement ID in the first message and/or the second message, so as to match the result reporting message with the request message. For example, the ID may include a measurement ID assigned by a message transmitting node and/or a measurement ID assigned by a message receiving node. For example, the ID may include a measurement ID assigned by the second node and/or a measurement ID assigned by the first node. The ID may be consistent with the measurement ID in the first message and/or the second message, so as to match the result reporting message with the request message. The ID may be consistent with the measurement ID in the first message and/or the second message, so as to match the result reporting message with the request message.

- collection ID: used to identify the data collection. For example, the ID may include a collection ID assigned by a message transmitting node and/or a collection ID assigned by a message receiving node. For example, the ID may include a collection ID allocated by the first node, and/or a collection ID allocated by the second node. The ID may be consistent with the collection ID in the first message, so as to match the result reporting message with the request message. For example, the ID assigned by the first node may be consistent with the ID assigned by the first node in the first message and/or the second message, and/or the ID assigned by the second node may be consistent with the ID assigned by the second node in the second message, so as to match the result reporting message with the request message.

- configuration ID: used to identify the configuration corresponding to the data collection result. This ID can uniquely identify a data collection configuration.

- information of a node and/or cell that is initially configured for data collection (information of initial configuration node/cell of data collection): in some implementations, for example, this information may be used to uniquely identify a data collection among multiple nodes. In other implementations, for example, this information may be used to uniquely identify data collection for a UE among multiple nodes. In still other implementations, for example, this information may inform the node to which data collection result ultimately need to be transmitted. For example, in a multi-hop case, a data collection node may directly transmit the results to the node that is initially configured for the data collection, so as to avoid the need for intermediate nodes to perform forwarding in a multi-hop case and achieve an effect of signaling saving. For example, in a multi-hop case, a data collection node uniquely identifies a data collection and/or data collection for the same UE among multiple nodes by using the information of the node and/or cell that is initially configured for the data collection, which may avoid a case where other nodes except the node that is initially configured for the data collection still need to keep the UE context after the UE is handed over to another node in a multi-hop case, resulting in too much information stored by the nodes, and/or a case where the identifier assigned for the UE for which the data collection is targeted cannot be allocated to other UEs for a long time. This information may include one or more of the following:

* identifier of a node that is initially configured for the data collection

* identifier of a cell that is initially configured for the data collection

- collected data: which indicates the data corresponding to the data collection.

- collection time corresponding to the collected data.

- number of hops corresponding to the collected data: this information is used to indicate the number of hops corresponding to the collected data. For example, this information may be used to indicate data collection of which hop the collected data corresponds to. In some implementations, for example, the hop number may be used for a node to correlate and/or integrate multiple data collection results.

- identification corresponding to the collected data: this information is used to identify the collected data. In some implementations, for example, the identification may be used for a node to correlate and/or integrate multiple data collection results.

Example 2

An aspect of the present disclosure provides a method for supporting data collection, which may include: a third node transmits a fourth message including a request for prediction of handover related auxiliary/assistance information to a fourth node to inform the fourth node that it needs to predict handover related auxiliary/assistance information and/or report the predicted handover related auxiliary/assistance information.

The prediction of handover related auxiliary/assistance information may include one or more of the following: measurement result prediction, trajectory prediction, etc.

In some implementations, the fourth message may be included in one or more of the following:

In some implementations, the fourth message may include one or more of the following information and/or fields:

- transmitting node ID: used to identify a node that transmits the message.

- receiving node ID: used to identify a node that receives the message.

- request ID: used to identify the request.

- configuration ID: used to identify the configuration of the measurement result prediction. The ID may uniquely identify a measurement result configuration.

- identification of a request for measurement result prediction: used to indicate that the measurement result is requested to be predicted.

- prediction registration request, which may include one or more of the following: start, end, update, increase, decrease, etc.

- prediction time: the prediction time corresponding to the measurement result requested to be predicted.

- Applicable/valid time: the applicable/valid time corresponding to the measurement result requested to be predicted.

- prediction type: it may include one or more of the following: single prediction, on-demand prediction, periodic prediction and event-triggered prediction.

- prediction period: the time interval between two predictions. In some implementations, in the case of periodic prediction, it may be the time interval between two predictions.

- trigger event corresponding to the prediction: when the trigger event is met, prediction is performed. The trigger event may include one or more of the following, or it may be that the following events are met at the same time:

* the measurement result is greater than and/or less than and/or equal to a threshold, where the event configuration includes one or more of the following: event type, event, threshold and meeting time.

* user (trajectory) enters a predetermined scope, where the event configuration includes one or more of the following: event type, event, predetermined threshold and meeting time. The predetermined scope may include one or more of the following: the scope covered by one or more cells (for example, it may be indicated by cell identifier and/or cell identifier list), the scope covered by one or more nodes (for example, it may be indicated by node identifier and/or node identifier list), and the scope covered by one or more beams (for example, it may be indicated by cell identifier and/or beam identifier, and/or cell identifier list and/or beam identifier list), a geographic area, etc.

* load condition is greater than and/or less than and/or equal to a threshold, where the event configuration includes one or more of the following: event type, event, threshold and meeting time.

* predicted load condition is greater than and/or less than and/or equal to a threshold, where the event configuration includes one or more of the following: event type, event, threshold and meeting time.

it is predicted that overload will occur.

overload occurs.

* it is predicted that the load will be too low.

* load is too low.

* there is a trend that the load is increasing and/or decreasing.

- information of node and/or cell corresponding to the requested prediction result of the handover related auxiliary/assistance information, which may include one or more of the following:

* node identifier corresponding to the prediction result

* node name corresponding to the prediction result

* cell identifier corresponding to the prediction result

* beam identifier corresponding to the prediction result

- reporting configuration: it may include one or more of the following:

* reporting time: reporting will be performed within the reporting time.

* reporting type: it may include one or more of the following: single reporting, on-demand reporting, periodic reporting and event-triggered reporting.

* trigger event: when the trigger event is met, reporting will be performed. The trigger event may include one or more of the following, or it may be that the following events are met at the same time:

- the predicted measurement result is greater than and/or less than and/or equal to a threshold, where the event configuration includes one or more of the following: event type, event, threshold and meeting time.

- the measurement result is greater than and/or less than and/or equal to a threshold, where the event configuration includes one or more of the following: event type, event, threshold and meeting time.

- predicted user (trajectory) enters a predetermined scope, where the event configuration includes one or more of the following: event type, event, predetermined threshold and meeting time. The predetermined scope may include one or more of the following: the scope covered by one or more cells (for example, it may be indicated by cell identifier and/or cell identifier list), the scope covered by one or more nodes (for example, it may be indicated by node identifier and/or node identifier list), and the scope covered by one or more beams (for example, it may be indicated by cell identifier and/or beam identifier, and/or cell identifier list and/or beam identifier list), a geographic area, etc.

- user (trajectory) enters a predetermined scope, where the event configuration includes one or more of the following: event type, event, predetermined threshold and meeting time. The predetermined scope may include one or more of the following: the scope covered by one or more cells (for example, it may be indicated by cell identifier and/or cell identifier list), the scope covered by one or more nodes (for example, it may be indicated by node identifier and/or node identifier list), and the scope covered by one or more beams (for example, it may be indicated by cell identifier and/or beam identifier, and/or cell identifier list and/or beam identifier list), a geographic area, etc.

- load condition is greater than and/or less than and/or equal to a threshold, where the event configuration includes one or more of the following: event type, event, threshold and meeting time.

- predicted load condition is greater than and/or less than and/or equal to a threshold, where the event configuration includes one or more of the following: event type, event, threshold and meeting time.

- it is predicted that overload will occur.

- overload occurs.

- it is predicted that the load will be too low.

- load is too low.

- there is a trend that the load is increasing and/or decreasing.

Optionally, after receiving the fourth message of a request for prediction of handover related auxiliary/assistance information transmitted by the third node, the fourth node transmits a fifth message containing a response for the prediction of handover related auxiliary/assistance information to the third node, so as to inform the third node whether the fourth node can perform prediction.

In some implementations, the fifth message may be included in one or more of the following:

or a GNB-CU-UP E1 SETUP REQUEST message or a GNB-CU-UP E1 SETUP RESPONSE message or a GNB-CU-CP E1 SETUP REQUEST message or a GNB-CU-CP E1 SETUP RESPONSE message or a GNB-CU-UP CONFIGURATION UPDATE message or a GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-CU-CP CONFIGURATION UPDATE message or a GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message or a GNB-CU-UP STATUS INDICATION message or a RESOURCE STATUS RESPONSE message or a RESOURCE STATUS FAILURE message of E1;

In some implementations, the fifth message may include one or more of the following information and/or fields:

- transmitting node ID: used to identify a node that transmits the message.

- receiving node ID: used to identify a node that receives the message.

- request ID: used to identify the request. The ID may be consistent with the request ID in the fourth message to match the response message with the request message.

- measurement ID: used to identify the measurement request. For example, the ID may include a measurement ID assigned by a message transmitting node and/or a measurement ID assigned by a message receiving node. For example, the ID may include a measurement ID assigned by the fourth node and/or a measurement ID assigned by the third node. The ID may be consistent with the measurement ID in the fourth message to match the response message with the request message. The ID may be consistent with the measurement ID in the fourth message to match the response message with the request message.

- collection ID: used to identify the data collection. For example, the ID may include a collection ID assigned by a message transmitting node and/or a collection ID assigned by a message receiving node. For example, the ID may include a collection ID assigned by the fourth node and/or a collection ID assigned by the third node. The ID may be consistent with the collection ID in the fourth message to match the response message with the request message. For example, the collection ID may be consistent with the collection ID in the fourth message to match the response message with the request message.

- information on whether measurement result prediction can be performed: used to indicate whether measurement result prediction can be performed.

- information on whether prediction of handover related auxiliary/assistance information can be performed: used to indicate whether prediction of handover related auxiliary/assistance information can be performed.

- information on whether trajectory information prediction can be performed: used to indicate whether trajectory information prediction can be performed.

* available prediction type: it may include one or more of the following: single prediction, on-demand prediction, periodic prediction and event-triggered prediction.

* available prediction period: available time interval between two predictions. In some implementations, in a case of periodic prediction, it may be the time interval between two predictions.

* trigger events available for prediction: which may include one or more of the trigger events corresponding to the prediction in the fourth message.

* reporting configuration available for reporting: it may include one or more of the following:

- reporting time available for reporting: reporting may be performed within the reporting time.

- reporting type available for reporting: it may include one or more of the following: single reporting, on-demand reporting, periodic reporting and event-triggered reporting.

- reporting period available for reporting: available time interval between two reporting. In some implementations, in a case of periodic reporting, it may be the time interval between two reporting.

- trigger event available for reporting: which may include one or more of the trigger events in the reporting configuration in the fourth message.

* unavailable prediction type: it may include one or more of the following: single prediction, on-demand prediction, periodic prediction and event-triggered prediction.

* unavailable prediction period: unavailable time interval between two predictions. In some implementations, in the case of periodic prediction, it may be the time interval between two predictions.

* trigger event unavailable for prediction: it may include one or more of the trigger events corresponding to the prediction in the fourth message.

* reporting configuration unavailable for reporting: it may include one or more of the following:

- reporting time unavailable for reporting: reporting cannot be performed within the reporting time.

- reporting type unavailable for reporting: it may include one or more of the following: single reporting, on-demand reporting, periodic reporting and event-triggered reporting.

- reporting period unavailable for reporting: unavailable time interval between two reporting. In some implementations, in a case of periodic reporting, it may be the time interval between two reporting.

- trigger event unavailable for reporting: which may include one or more of the trigger events in the reporting configuration in the fourth message.

In some implementations, the fourth node may transmit a sixth message including a prediction result of handover related auxiliary/assistance information to the third node according to its own situation and/or the fourth message including a request for prediction of handover related auxiliary/assistance information received from the third node, so as to transmit the handover related auxiliary/assistance information predicted by the fourth node to the third node.

After the third node receives the prediction result of the handover related auxiliary/assistance information, in some implementations, for example, it may make subsequent mobility decisions based on the prediction result of the handover related auxiliary/assistance information. In another implementation, for example, the third node may select a target node for (conditional) handover and/or (conditional) secondary node addition and/or (conditional) secondary node change, and/or set a time for related handover and/or secondary node addition and/or secondary node change based on the handover related auxiliary/assistance information prediction result.

In some implementations, the sixth message may be included in one or more of the following:

a Handover Request message or an S-NODE ADDITION REQUEST message or an S-NODE MODIFICATION REQUEST message or an S-NODE MODIFICATION REQUIRED message or an S-NODE CHANGE REQUIRED message or a HANDOVER REQUEST ACKNOWLEDGE message or an S-NODE ADDITION REQUEST ACKNOWLEDGE message or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message or an S-NODE MODIFICATION CONFIRM message or an S-NODE CHANGE CONFIRM message or an NG-RAN NODE CONFIGURATION UPDATE message or an NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message or an XN SETUP REQUEST message or an XN SETUP RESPONSE message or a RESOURCE STATUS UPDATE message or a DATA COLLECTION UPDATE message;

or a UE CONTEXT RELEASE REQUEST message or a UE CONTEXT MODIFICATION REQUEST message or a UE CONTEXT MODIFICATION RESPONSE message or an INITIAL CONTEXT SETUP REQUEST message or an NG SETUP REQUEST message or an NG SETUP RESPONSE message or a RAN CONFIGURATION UPDATE message or a RAN CONFIGURATION UPDATE ACKNOWLEDGE message or an AMF CONFIGURATION UPDATE message or an AMF CONFIGURATION UPDATE ACKNOWLEDGE message or an AMF STATUS INDICATION message or an OVERLOAD START message or an OVERLOAD STOP message of NG;

or an other and/or newly defined RRC message and/or Xn message and/or X2 message and/or F1 message and/or E1 message and/or NG message and/or RRC container and/or MAC CE, etc.

In some implementations, the sixth message may include one or more of the following information and/or fields:

- transmitting node ID: used to identify a node that transmits the message.

- receiving node ID: used to identify a node that receives the message.

- request ID: used to identify the request. The ID may be consistent with the request ID in the fourth message and/or the fifth message, so as to match the result reporting message with the request message.

- measurement ID: used to identify the measurement request. The ID may be consistent with the measurement ID in the fourth message and/or the fifth message, so as to match the result reporting message with the request message.

- collection ID: used to identify the data collection. For example, the ID may include a collection ID assigned by a message transmitting node and/or a collection ID assigned by a message receiving node. For example, the ID may include a collection ID assigned by the fourth node and/or a collection ID assigned by the third node. The ID may be consistent with the collection ID in the first message, so as to match the result reporting message with the request message. For example, the ID assigned by the first node may be consistent with the ID assigned by the first node in the fourth message and/or the fifth message, and/or the ID assigned by the fourth node may be consistent with the ID assigned by the fourth node in the fifth message, so as to match the result reporting message with the request message.

- predicted trajectory information, which may include one or more of the following:

* user identifier

* identifier of an accessed/visited cell

* identifier of an accessed/visited primary cell

* identifier of an accessed/visited secondary cell

* accessing time and/or resident time

* coordinate

* information of an accessed/visited beam, which may be a beam identifier.

- predicted measurement result information, which may include one or more of the following:

* user identifier

* measurement result

* measurement time

Exemplary embodiments of the present disclosure are further described below with reference to the accompanying drawings.

The text and drawings are provided as examples only to help understand the present disclosure. They should not be construed as limiting the scope of the present disclosure in any way. Although certain embodiments and examples have been provided, based on the disclosure herein, it is obvious to those skilled in the art that changes can be made to the illustrated embodiments and examples without departing from the scope of the present disclosure.

FIG. 3A shows a schematic diagram of an aspect of a method for supporting data collection according to embodiments of the present disclosure. Specifically, FIG. 3A shows a process of exchanging single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection between two nodes, so that the second node can support AI/ML related functions and/or operations by using the single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection result.

In an implementation, for example, the first node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the second node may be a UE. In an implementation, for example, the first node may be a UE, and the second node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the first node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the second node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In yet another implementation, for example, the first node may be an AMF or an SMF or an MME, and the second node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In yet another implementation, for example, the first node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the second node may be an AMF or an SMF or an MME. Alternatively, for example, the first node is a master node and the second node is a secondary node; for example, the first node is a secondary node and the second node is a master node; for example, the first node is a source node and the second node is a target node; for example, the first node is a target node and the second node is a source node.

Step 301A: the second node transmits a result of single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection to the first node. The result of the single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection may be the aforementioned third message.

Step 302A: the first node may perform analysis based on the result of single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection. In some implementations, for example, after the first node receives the result of the data collection, it may train an AI/ML model based on the received data collection result. In other implementations, for example, after the first node receives the data collection result, it may evaluate the output result of the AI/ML model and/or the accuracy of the AI/ML model. Herein, the evaluation of the output result of the AI/ML model may be an evaluation of the accuracy of the output result of the AI/ML model. For example, when the result of data collection deviates greatly from the output result of the model, it indicates that the output result of the AI/ML model is inaccurate and/or the accuracy of the AI/ML model is low. Nodes may trigger updating and/or retraining of the AI/ML model.

FIG. 3B shows a schematic diagram of an aspect of a method for supporting data collection according to embodiments of the present disclosure. Specifically, FIG. 3B shows a process of exchanging single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection between two nodes, so that the second node can support AI/ML related functions and/or operations by using the single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection result.

Step 301B: the first node transmits a request for single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection to the second node to request the second node to collect and/or report the single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection result. The request for single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection may be the aforementioned first message.

Step 302B: optionally, the second node transmits a response for single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection to the first node to inform the first node whether the second node can perform the requested collection and/or reporting. The response for single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection may be the aforementioned second message.

Step 303B: the second node transmits a result of single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection to the first node. The result of the single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection may be the aforementioned third message.

Step 304B: the first node may perform analysis based on the result of single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection. In some implementations, for example, after the first node receives the result of the data collection, it may train an AI/ML model based on the received data collection result. In other implementations, for example, after the first node receives the data collection result, it may evaluate the output result of the AI/ML model and/or the accuracy of the AI/ML model. Herein, the evaluation of the output result of the AI/ML model may be an evaluation of the accuracy of the output result of the AI/ML model. For example, when the result of data collection deviates greatly from the output result of the model, it indicates that the output result of the AI/ML model is inaccurate and/or the accuracy of the AI/ML model is low. Nodes may trigger updating and/or retraining of the AI/ML model.

In some implementations, for example, step 302B may be omitted.

FIG. 3C shows a schematic diagram of an aspect of a method for supporting data collection according to embodiments of the present disclosure. Specifically, FIG. 3C shows a process of exchanging multi-hop and/or dual-connectivity data collection between nodes, so that the nodes can support AI/ML related functions and/or operations by using the results of multi-hop and/or dual-connectivity data collection.

Step 301C: gNB1 transmits a request for multi-hop and/or dual-connectivity data collection (for example, it may be called a first request) to gNB2 to request it to collect and/or report a result of the multi-hop and/or dual-connectivity data collection. The request for multi-hop and/or dual-connectivity data collection may be the aforementioned first message. The message may be transmitted through a DATA COLLECTION REQUEST message. As mentioned above, the first message may include a first collection configuration and/or a first reporting configuration for multi-hop and/or dual-connectivity data collection for a UE.

Step 302C: optionally, gNB2 transmits a response for multi-hop and/or dual-connectivity data collection to gNB1 to inform gNB1 whether gNB2 can perform the requested collection and/or reporting. The response for the multi-hop and/or dual-connectivity data collection may be the aforementioned second message. The message may be transmitted through a DATA COLLECTION RESPONSE message and/or a DATA COLLECTION FAILURE message.

Step 303C: gNB1 transmits a handover request message to gNB2. The message carries an identification in step 301C and/or step 302C to request gNB2 to perform data collection for the UE (for example, the UE targeted by the handover request). The identification may include one or more of the following: request ID, measurement ID, collection ID, configuration ID, information of the node and/or cell that is initially configured for the data collection, etc.

Step 304C: gNB2 transmits a handover request confirmation message to gNB1.

Step 305C: gNB1 transmits an RRC reconfiguration message to the UE. In some implementations, for example, after receiving the RRC reconfiguration message, the UE transmits an RRC reconfiguration complete message to gNB1.

Step 306C: UE accesses gNB2.

Step 307C: gNB2 performs data collection.

The gNB2 transmitting the request for multi-hop and/or dual-connectivity data collection to gNB3 can be implemented by Mode 1-1 or Mode 1-2.

Mode 1-1:

Step 308C.11a: gNB2 transmits a request for multi-hop and/or dual-connectivity data collection (for example, it may be called a third request) to gNB3 to request gNB3 to collect and/or report a result of the multi-hop and/or dual-connectivity data collection. The request for multi-hop and/or dual-connectivity data collection may be the aforementioned first message. In order to be distinguished in the flow, this message may also be called an eighth message. In an implementation, the message may include the identifiers/identification, report configuration part, and/or indication of subsequent multi-hop data collection in the first message. The identification may include one or more of the following: request ID, measurement ID, collection ID, configuration ID, information of the node and/or cell that is initially configured for the data collection, etc. The message may be transmitted through a DATA COLLECTION REQUEST message.

Step 308C.11b: optionally, gNB3 transmits a response for multi-hop and/or dual-connectivity data collection to gNB2 (for example, it may be called a tenth message) to inform gNB2 whether gNB3 can perform the requested collection and/or reporting. The response for the multi-hop and/or dual-connectivity data collection may be the aforementioned second message. The message may be transmitted through a DATA COLLECTION RESPONSE message and/or a DATA COLLECTION FAILURE message.

Step 308.11c: gNB2 transmits a request for multi-hop and/or dual-connectivity data collection (for example, it may be called a second request) to gNB3 to request gNB3 to collect and/or report a result of the multi-hop and/or dual-connectivity data collection for one or some UE. The request for multi-hop and/or dual-connectivity data collection may be the aforementioned first message. In order to be distinguished in the flow, this message may also be called a seventh message. The seventh message may include a second collection configuration corresponding to the multi-hop and/or dual-connectivity data collection for the UE, and the second collection configuration may be determined based on the first collection configuration and the current data collection situation or data collection information for the UE at gNB2. In an implementation, the message may include the identifiers/identification in the aforementioned first message, and/or other information in addition to the information in step 308C.11a, etc. The identification may include one or more of the following: request ID, measurement ID, collection ID, configuration ID, information of the node and/or cell that is initially configured for the data collection, etc. In another implementation, if the information contained in this step is inconsistent with the information in step 308C.11a, the data collection for the UE is to be performed based on the information in this message. The message may be transmitted through a DATA COLLECTION REQUEST message and/or a HANDOVER REQUEST message and/or an S-NODE ADDITION REQUEST message.

Mode 1-2:

Step 308C.12: gNB2 transmits a request for multi-hop and/or dual-connectivity data collection (for example, it may be called a second request) to gNB3, so as to request gNB3 to collect and/or report a result of the multi-hop and/or dual-connectivity data collection for one or some UE. The request for multi-hop and/or dual-connectivity data collection may be the aforementioned first message. In order to be distinguished in the flow, this message may also be called a seventh message. The seventh message may include a second collection configuration corresponding to the multi-hop and/or dual-connectivity data collection for the UE, and the second collection configuration may be determined based on the first collection configuration and the current data collection situation for the UE. In addition, the seventh message may also include a second reporting configuration corresponding to the multi-hop and/or dual-connectivity data collection for the UE. The message may be transmitted through a DATA COLLECTION REQUEST message and/or a HANDOVER REQUEST message and/or an S-NODE ADDITION REQUEST message.

Step 309C: gNB3 transmits a message (for example, it may be called a ninth message) including information about whether gNB3 may directly transmit the collection result to the node that is initially configured for the data collection and/or a receiving node and/or cell corresponding to the reporting of the data collection. The message may be transmitted through a HANDOVER REQUEST ACKNOWLEDGE message and/or an S-NODE ADDITION REQUEST ACKNOWLEDGE message. The message may also be transmitted from gNB3 to gNB2 along with (or included in) the response for the multi-hop and/or dual-connectivity data collection in the above step 308C.11b.

Step 310C: gNB2 transmits an RRC reconfiguration message to the UE. In some implementations, for example, after receiving the RRC reconfiguration message, the UE transmits an RRC reconfiguration complete message to gNB2.

Step 311C: UE accesses gNB3.

Step 312C: gNB3 performs data collection.

The gNB3 transmitting the results of multi-hop and/or dual-connectivity data collection to gNB1 can be implemented by Mode 2-1 or Mode 2-2 or Mode 2-3. The results of multi-hop and/or dual-connectivity data collection transmitted by gNB3 to gNB1 may be the result of multi-hop and/or dual-connectivity data collection collected by gNB3, or the results of multi-hop and/or dual-connectivity data collection collected by gNB2 and gNB3. In some implementations, for example, the results of multi-hop and/or dual-connectivity data collection transmitted by gNB3 to gNB1 only include the results of multi-hop and/or dual-connectivity data collection collected by gNB3, and gNB2 needs to transmit the results of multi-hop and/or dual-connectivity data collection collected by gNB2 to gNB1, which occurs after step 307C. For example, it may occur at the same time with and/or after and/or before step 307C in the diagram.

Mode 2-1:

Step 313C.21a: gNB3 transmits results of multi-hop and/or dual-connectivity data collection to gNB2. The results of the multi-hop and/or dual-connectivity data collection may be the aforementioned third message. The message may be transmitted through a DATA COLLECTION UPDATE message and/or a new message.

Step 313C.21b: gNB2 transmits results of multi-hop and/or dual-connectivity data collection to gNB1. The results of the multi-hop and/or dual-connectivity data collection may be the aforementioned third message. The message may be transmitted through a DATA COLLECTION UPDATE message and/or a new message. In some implementations, for example, the results of the multi-hop and/or dual-connectivity data collection may be a result of the multi-hop and/or dual-connectivity data collection which is a combination of the data collected by gNB2 and the result of the multi-hop and/or dual-connectivity data collection received from gNB3 in step 313C.21a.

This mode can solve the problem that the last data collection node (for example, gNB3) has no communication interface with the node that is initially configured for the data collection (gNB1 in the diagram) and/or the receiving node and/or cell (for example, gNB1) corresponding to the reporting of the data collection.

Mode 2-2:

Step 313C.22: gNB3 transmits results of multi-hop and/or dual-connectivity data collection to gNB1. The results of the multi-hop and/or dual-connectivity data collection may be the aforementioned third message. The message may be transmitted through a DATA COLLECTION UPDATE message and/or a new message. GNB3 may obtain information that it needs to transmit the collection results to gNB1 by the information in step 308C.11a and/or step 308.11c and/or step 308C.12. In some implementations, for example, if it is indicated in step 309 that gNB3 may directly transmit the collection results to the node that is initially configured for the data collection (gNB1 in the diagram) and/or the receiving node and/or cell (for example, gNB1) corresponding to the reporting of the data collection, Mode 2-2 can be adopted.

This mode can reduce the signaling for transmission of the collection results.

Mode 2-3:

Step 313C.23a: gNB3 transmits results of multi-hop and/or dual-connectivity data collection to AMF. The results of the multi-hop and/or dual-connectivity data collection may be the aforementioned third message. The message may be transmitted through a DATA COLLECTION UPDATE message and/or a new message.

Step 313C.23b: AMF transmits results of multi-hop and/or dual-connectivity data collection to gNB1. The results of the multi-hop and/or dual-connectivity data collection may be the aforementioned third message. The message may be transmitted through a DATA COLLECTION UPDATE message and/or a new message.

In some implementations, for example, Mode 2-2 or Mode 2-3 requires gNB2 to transmit data collection results to gNB3, and gNB3 combines its own data collection result with the data collection results received from gNB2 to form a data collection result transmitted by gNB3.

GNB1 may perform analysis based on the results of multi-hop and/or dual-connectivity data collection. In some implementations, for example, after gNB1 receives the result of the data collection, it may train an AI/ML model based on the received data collection result. In other implementations, for example, after receiving the data collection result, gNB1 may evaluate the output result of the AI/ML model and/or the accuracy of the AI/ML model. Herein, the evaluation of the output result of the AI/ML model may be an evaluation of the accuracy of the output result of the AI/ML model. For example, when the result of data collection deviates greatly from the output result of the model, it indicates that the output result of the AI/ML model is inaccurate and/or the accuracy of the AI/ML model is low. Nodes may trigger updating and/or retraining of the AI/ML model.

In FIG. 3C, gNB2 is used as an example to illustrate the behavior of a node in an intermediate hop, and gNB3 is used as an example to illustrate the behavior of a node in an intermediate hop and/or the behavior of a node at which the data collection is completed.

FIG. 3D shows a schematic diagram of an aspect of a method for supporting data collection according to embodiments of the present disclosure. Specifically, FIG. 3D shows a process of exchanging dual-connectivity data collection between nodes, so that the nodes can support AI/ML related functions and/or operations by using the results of dual-connectivity data collection.

Step 301D: the master node transmits a request for dual-connectivity data collection to the secondary node 1 to request the secondary node 1 to collect and/or report a result of the dual-connectivity data collection. The request for dual-connectivity data collection may be the aforementioned first message. The message may be transmitted through a DATA COLLECTION REQUEST message.

Step 302D: optionally, the secondary node 1 transmits a response for dual-connectivity data collection to the master node to inform the master node whether the secondary node 1 can perform the requested collection and/or reporting. The response for the dual-connectivity data collection may be the aforementioned second message. The message may be transmitted through a DATA COLLECTION RESPONSE message and/or a DATA COLLECTION FAILURE message.

Step 303D: the master node transmits a request for dual-connectivity data collection to the secondary node 1, so as to request the secondary node 1 to collect and/or report the results of dual-connectivity data collection for one or some UE. For example, through this step, the secondary node 1 may be informed that data collection for the UE is needed. The request for dual-connectivity data collection may be the aforementioned first message. In an implementation, the message may include the identification/identifiers in the aforementioned first message. The identification may include one or more of the following: request ID, measurement ID, collection ID, configuration ID, information of the node and/or cell that is initially configured for the data collection, etc., to inform the secondary node 1 to perform data collection for the UE according to the request in step 301D. The message may be transmitted through an S-NODE ADDITION REQUEST message. The message may also be transmitted through an S-NODE MODIFICATION REQUEST message.

Step 304D: the secondary node 1 transmits an S-NODE ADDITION REQUEST ACKNOWLEDGE message and/or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message to the master node.

Step 305D: the master node transmits an RRC reconfiguration message to the UE. In some implementations, for example, after receiving the RRC reconfiguration message, the UE transmits an RRC reconfiguration complete message to the master node.

Step 306D: UE accesses the secondary node 1.

Step 307D: the secondary node 1 performs data collection.

Step 308D: the secondary node 1 transmits a result of the dual-connectivity data collection to the master node. The result of the dual-connectivity data collection may be the aforementioned third message. The message may be transmitted through a DATA COLLECTION UPDATE message.

FIG. 3E shows a schematic diagram of an aspect of a method for supporting data collection according to embodiments of the present disclosure. Specifically, FIG. 3E shows a process of exchanging dual-connectivity data collection between nodes, so that the nodes can support AI/ML related functions and/or operations by using the results of dual-connectivity data collection.

Step 301E: the master node transmits a request for dual-connectivity data collection to the secondary node 1 to request the secondary node 1 to collect and/or report a result of the dual-connectivity data collection. The request for dual-connectivity data collection may be the aforementioned first message. The message may be transmitted through an S-NODE ADDITION REQUEST message. The message may also be transmitted through an S-NODE MODIFICATION REQUEST message.

Step 302E: optionally, the secondary node 1 transmits a response for dual-connectivity data collection to the master node to inform the master node whether the secondary node 1 can perform the requested collection and/or reporting. The response for the dual-connectivity data collection may be the aforementioned second message. The message may be transmitted through an S-NODE ADDITION REQUEST ACKNOWLEDGE message and/or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.

Step 303E: the master node transmits an RRC reconfiguration message to the UE. In some implementations, for example, after receiving the RRC reconfiguration message, the UE transmits an RRC reconfiguration complete message to the master node.

Step 304E: UE accesses the secondary node 1.

Step 305E: the secondary node 1 performs data collection.

Step 306E: the secondary node 1 transmits a result of the dual-connectivity data collection to the master node. The result of the dual-connectivity data collection may be the aforementioned third message. The message may be transmitted through a DATA COLLECTION UPDATE message and/or a new message.

The master node may perform analysis based on the result of single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection. In some implementations, for example, after receiving the data collection result, the master node may train an AI/ML model based on the received data collection result. In other implementations, for example, after receiving the data collection result, the master node may evaluate the output result of the AI/ML model and/or the accuracy of the AI/ML model. Herein, the evaluation of the output result of the AI/ML model may be an evaluation of the accuracy of the output result of the AI/ML model. For example, when the result of data collection deviates greatly from the output result of the model, it indicates that the output result of the AI/ML model is inaccurate and/or the accuracy of the AI/ML model is low. Nodes may trigger updating and/or retraining of the AI/ML model.

FIG. 3F shows a schematic diagram of an aspect of a method for supporting data collection according to embodiments of the present disclosure. Specifically, FIG. 3F shows a process of exchanging dual-connectivity data collection between nodes, so that the nodes can support AI/ML related functions and/or operations by using the results of dual-connectivity data collection.

Step 300F: exchange between the master node, the secondary node 1 and the UE is performed, which may refer to FIG. 3D or FIG. 3E.

The exchange between the master node and the secondary node 2 may be performed by Mode 1 or Mode 2.

Mode 1:

Step 301F.1a: the master node transmits a request for dual-connectivity data collection to the secondary node 2 to request the secondary node 2 to collect and/or report a result of the dual-connectivity data collection. The request for dual-connectivity data collection may be the aforementioned first message. The message may be transmitted through a DATA COLLECTION REQUEST message.

Step 301F.1b: optionally, the secondary node 2 transmits a response for dual-connectivity data collection to the master node to inform the master node whether the secondary node 2 can perform the requested collection and/or reporting. The response for the dual-connectivity data collection may be the aforementioned second message. The message may be transmitted through a DATA COLLECTION RESPONSE message and/or a DATA COLLECTION FAILURE message.

Step 301F.1c: the master node transmits a request for dual-connectivity data collection to the secondary node 2, so as to request the secondary node 2 to collect and/or report the results of dual-connectivity data collection for one or some UE. For example, through this step, the secondary node 2 may be informed that data collection for the UE is needed. The request for dual-connectivity data collection may be the aforementioned first message. In an implementation, the message may include the identification/identifiers in the aforementioned first message. The identification may include one or more of the following: request ID, measurement ID, collection ID, configuration ID, information of the node and/or cell that is initially configured for the data collection, etc., to inform the secondary node 2 to perform data collection for the UE according to the request in step 301D. The message may be transmitted through an S-NODE ADDITION REQUEST message. The message may also be transmitted through an S-NODE MODIFICATION REQUEST message.

Step 301F.1d: the secondary node 2 transmits an S-NODE ADDITION REQUEST ACKNOWLEDGE message and/or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message to the master node.

Mode 2:

Step 301F.2a: the master node transmits a request for dual-connectivity data collection to the secondary node 2 to request the secondary node 2 to collect and/or report a result of the dual-connectivity data collection. The request for dual-connectivity data collection may be the aforementioned first message. The message may be transmitted through an S-NODE ADDITION REQUEST message. The message may also be transmitted through an S-NODE MODIFICATION REQUEST message.

Step 301F.2b: optionally, the secondary node 2 transmits a response for dual-connectivity data collection to the master node, so as to inform the master node whether the secondary node 2 can perform the requested collection and/or reporting. The response for the dual-connectivity data collection may be the aforementioned second message. The message may be transmitted through an S-NODE ADDITION REQUEST ACKNOWLEDGE message and/or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message.

Step 303F: the master node transmits an RRC reconfiguration message to the UE. In some implementations, for example, after receiving the RRC reconfiguration message, the UE transmits an RRC reconfiguration complete message to the master node.

Step 304F: UE accesses the secondary node 2.

Step 305F: the secondary node 2 performs data collection.

Step 306F: the secondary node 2 transmits a result of the dual-connectivity data collection to the master node. The result of the dual-connectivity data collection may be the aforementioned third message. The message may be transmitted through a DATA COLLECTION UPDATE message or a new message.

FIG. 3G shows a schematic diagram of an aspect of a method for supporting data collection according to embodiments of the present disclosure. Specifically, FIG. 3G shows a process of exchanging multi-hop and/or dual-connectivity data collection between nodes, so that the nodes can support AI/ML related functions and/or operations by using the results of multi-hop and/or dual-connectivity data collection.

Step 300G: exchange between the master node 1, the secondary node 1 and the UE is performed, which may refer to FIG. 3D or FIG. 3E.

Step 301G: the master node 1 transmits a request for multi-hop and/or dual-connectivity data collection to the master node 2 to request the master node 2 to collect and/or report a result of the multi-hop and/or dual-connectivity data collection. The request for multi-hop and/or dual-connectivity data collection may be the aforementioned first message. In an implementation, the message may include the identifiers/identification, report configuration part, and/or indication of subsequent multi-hop data collection in the first message. The identification may include one or more of the following: request ID, measurement ID, collection ID, configuration ID, information of the node and/or cell that is initially configured for the data collection, etc. The message may be transmitted through a DATA COLLECTION REQUEST message.

Step 302G: optionally, the master node 2 transmits a response for multi-hop and/or dual-connectivity data collection to the master node 1 to inform the master node 1 whether the master node 2 can perform the requested collection and/or reporting. The response for the multi-hop and/or dual-connectivity data collection may be the aforementioned second message. The message may be transmitted through a DATA COLLECTION RESPONSE message and/or a DATA COLLECTION FAILURE message.

Step 303G: the master node 1 transmits a request for multi-hop and/or dual-connectivity data collection to the master node 2, so as to request the master node 2 to collect and/or report a result of the multi-hop and/or dual-connectivity data collection to one or some UE. The request for multi-hop and/or dual-connectivity data collection may be the aforementioned first message. In an implementation, the message may include the identifiers/identification in the aforementioned first message, and/or other information in addition to the information in step 301G. The identification may include one or more of the following: request ID, measurement ID, collection ID, configuration ID, information of the node and/or cell that is initially configured for the data collection, etc. In another implementation, if the information contained in this step is inconsistent with the information in step 301G, the data collection for the UE is to be performed based on the information in this message. The message may be transmitted through a DATA COLLECTION REQUEST message and/or a HANDOVER REQUEST message and/or an S-NODE ADDITION REQUEST message.

The exchange between the master node 2 and the secondary node 2 in step 304G may refer to steps 301D to 304D in FIG. 3D or steps 301E to 302E in FIG. 3E.

Step 305G: the master node 2 transmits a message to the master node 1, including information about whether the master node 2 may directly transmit the collection result to the node that is initially configured for the data collection and/or a receiving node and/or cell corresponding to the reporting of the data collection. The message may be transmitted through a HANDOVER REQUEST ACKNOWLEDGE message. The message may also be transmitted from the master node 2 to the master node 1 along with (or included in) the response for the multi-hop and/or dual-connectivity data collection in the above step 302G.

Step 306G: the master node 1 transmits an RRC reconfiguration message to the UE. In some implementations, for example, after receiving the RRC reconfiguration message, the UE transmits an RRC reconfiguration complete message to the master node 1.

Step 307G: UE accesses the master node 2 and the secondary node 2.

Step 308G: the master node 2 and the secondary node 2 perform data collection.

Step 309G: the secondary node 2 transmits results of multi-hop and/or dual-connectivity data collection to the master node 2. The results of the multi-hop and/or dual-connectivity data collection may be the aforementioned third message. The message may be transmitted through a DATA COLLECTION UPDATE message and/or a new message.

Step 310G: the master node 2 transmits a request for multi-hop and/or dual-connectivity data collection to the master node 3 to request the master node 3 to collect and/or report a result of the multi-hop and/or dual-connectivity data collection. The request for multi-hop and/or dual-connectivity data collection may be the aforementioned first message. In an implementation, the message may include the identifiers/identification, report configuration part, and/or indication of subsequent multi-hop data collection in the first message. The identification may include one or more of the following: request ID, measurement ID, collection ID, configuration ID, information of the node and/or cell that is initially configured for the data collection, etc. The message may be transmitted through a DATA COLLECTION REQUEST message.

Step 311G: optionally, the master node 3 transmits a response for multi-hop and/or dual-connectivity data collection to the master node 2 to inform the master node 2 whether the master node 3 can perform the requested collection and/or reporting. The response for the multi-hop and/or dual-connectivity data collection may be the aforementioned second message. The message may be transmitted through a DATA COLLECTION RESPONSE message and/or a DATA COLLECTION FAILURE message.

Step 312G: the master node 2 transmits a request for multi-hop and/or dual-connectivity data collection to the master node 3, so as to request the master node 3 to collect and/or report a result of the multi-hop and/or dual-connectivity data collection for one or some UE. The request for multi-hop and/or dual-connectivity data collection may be the aforementioned first message. In an implementation, the message may include the identifiers/identification in the aforementioned first message, and/or other information in addition to the information in step 309G. The identification may include one or more of the following: request ID, measurement ID, collection ID, configuration ID, information of the node and/or cell that is initially configured for the data collection, etc. In another implementation, if the information contained in this step is inconsistent with the information in step 309G, the data collection for the UE is to be performed based on the information in this message. The message may be transmitted through a DATA COLLECTION REQUEST message and/or a HANDOVER REQUEST message and/or an S-NODE ADDITION REQUEST message.

The exchange between the master node 3 and the secondary node 3 in step 313G may refer to steps 301D to 304D in FIG. 3D or steps 301E to 302E in FIG. 3E.

Step 314G: the master node 3 transmits a message to the master node 2, including information about whether the master node 3 may directly transmit the collection result to the node that is initially configured for the data collection and/or a receiving node and/or cell corresponding to the reporting of the data collection. The message may be transmitted through a HANDOVER REQUEST ACKNOWLEDGE message. The message may also be transmitted from the master node 3 to the master node 2 along with (or included in) the response for the multi-hop and/or dual-connectivity data collection in the above step 311G.

Step 315G: the master node 2 transmits an RRC reconfiguration message to the UE. In some implementations, for example, after receiving the RRC reconfiguration message, the UE transmits an RRC reconfiguration complete message to the master node 2.

Step 316G: UE accesses the master node 3 and the secondary node 3.

Step 317G: the master node 3 and the secondary node 3 perform data collection.

Step 318G: the secondary node 3 transmits results of multi-hop and/or dual-connectivity data collection to the master node 3. The results of the multi-hop and/or dual-connectivity data collection may be the aforementioned third message. The message may be transmitted through a DATA COLLECTION UPDATE message and/or a new message.

Step 319G: the master node 3 transmits the collected results of the multi-hop and/or dual-connectivity data collection to the master node 1. The specific mode thereof may refer to Mode 2-1 or Mode 2-2 or Mode 2-3 in FIG. 3C, where the master node 1 may correspond to gNB1 in FIG. 3C; the master node 2 may correspond to gNB2 in FIG. 3C; and the master node 3 may correspond to gNB3 in FIG. 3C.

The master node 1 may perform analysis based on the result of single-hop data collection and/or multi-hop data collection and/or dual-connectivity data collection. In some implementations, for example, after receiving the data collection result, the master node 1 may train an AI/ML model based on the received data collection result. In other implementations, for example, after receiving the data collection result, the master node 1 may evaluate the output result of the AI/ML model and/or the accuracy of the AI/ML model. Herein, the evaluation of the output result of the AI/ML model may be an evaluation of the accuracy of the output result of the AI/ML model. For example, when the result of data collection deviates greatly from the output result of the model, it indicates that the output result of the AI/ML model is inaccurate and/or the accuracy of the AI/ML model is low. Nodes may trigger updating and/or retraining of the AI/ML model.

In FIG. 3G, the master node 2 is used as an example to illustrate the behavior of a node in an intermediate hop, and the master node 3 is used as an example to illustrate the behavior of a node in an intermediate hop and/or the behavior of a node at which the data collection is completed.

FIG. 3H shows a schematic diagram of an aspect of a method for supporting data collection according to embodiments of the present disclosure. Specifically, FIG. 3H shows a process of exchanging multi-hop and/or dual-connectivity data collection between nodes, so that the nodes can support AI/ML related functions and/or operations by using the results of multi-hop and/or dual-connectivity data collection.

Step 300H: the exchange between the master node 1, the secondary node 1, and the UE may refer to FIG. 3D or FIG. 3E.

Step 301H: the master node 1 transmits a request for multi-hop and/or dual-connectivity data collection to the master node 2 to request the master node 2 to collect and/or report a result of the multi-hop and/or dual-connectivity data collection. The request for multi-hop and/or dual-connectivity data collection may be the aforementioned first message. The message may be transmitted through a HANDOVER REQUEST message.

The exchange between the master node 2 and the secondary node 2 in step 302H may refer to steps 301D to 304D in FIG. 3D or steps 301E to 302E in FIG. 3E.

Step 303H: optionally, the master node 2 transmits a response for multi-hop and/or dual-connectivity data collection to the master node 1 to inform the master node 1 whether the master node 2 can perform the requested collection and/or reporting. The response for the multi-hop and/or dual-connectivity data collection may be the aforementioned second message. The message may be transmitted through a HANDOVER REQUEST ACKNOWLEDGE message.

Step 304H: the master node 1 transmits an RRC reconfiguration message to the UE. In some implementations, for example, after receiving the RRC reconfiguration message, the UE transmits an RRC reconfiguration complete message to the master node 1.

Step 305H: UE accesses the master node 2 and the secondary node 2.

Step 306H: the master node 2 and the secondary node 2 perform data collection.

Step 307H: the secondary node 2 transmits results of multi-hop and/or dual-connectivity data collection to the master node 2. The results of the multi-hop and/or dual-connectivity data collection may be the aforementioned third message. The message may be transmitted through a DATA COLLECTION UPDATE message and/or a new message.

Step 308H: the master node 2 transmits a request for multi-hop and/or dual-connectivity data collection to the master node 3 to request the master node 2 to collect and/or report a result of the multi-hop and/or dual-connectivity data collection. The request for multi-hop and/or dual-connectivity data collection may be the aforementioned first message. The message may be transmitted through a HANDOVER REQUEST message.

The exchange between the master node 3 and the secondary node 3 in step 309H may refer to steps 301D to 304D in FIG. 3D or steps 301E to 302E in FIG. 3E.

Step 310H: optionally, the master node 3 transmits a response for multi-hop and/or dual-connectivity data collection to the master node 2 to inform the master node 2 whether the master node 3 can perform the requested collection and/or reporting. The response for the multi-hop and/or dual-connectivity data collection may be the aforementioned second message. The message may be transmitted through a HANDOVER REQUEST ACKNOWLEDGE message.

Step 311H: the master node 2 transmits an RRC reconfiguration message to the UE. In some implementations, for example, after receiving the RRC reconfiguration message, the UE transmits an RRC reconfiguration complete message to the master node 2.

Step 312H: UE accesses the master node 3 and the secondary node 3.

Step 313H: the master node 3 and the secondary node 3 perform data collection.

Step 314H: the secondary node 3 transmits results of multi-hop and/or dual-connectivity data collection to the master node 3. The results of the multi-hop and/or dual-connectivity data collection may be the aforementioned third message. The message may be transmitted through a DATA COLLECTION UPDATE message and/or a new message.

Step 315H: the master node 3 transmits the collected results of the multi-hop and/or dual-connectivity data collection to the master node 1. The specific mode thereof may refer to Mode 2-1 or Mode 2-2 or Mode 2-3 in FIG. 3C, where the master node 1 may correspond to gNB1 in FIG. 3C; the master node 2 may correspond to gNB2 in FIG. 3C; and the master node 3 may correspond to gNB3 in FIG. 3C.

In FIG. 3H, the master node 2 is used as an example to illustrate the behavior of a node in an intermediate hop, and the master node 3 is used as an example to illustrate the behavior of a node in an intermediate hop and/or the behavior of a node at which the data collection is completed.

FIG. 3I shows a schematic diagram of an aspect of a method for supporting data collection according to embodiments of the present disclosure. Specifically, FIG. 3I shows a process of exchanging multi-hop and/or dual-connectivity data collection between nodes, so that the nodes can support AI/ML related functions and/or operations by using the results of multi-hop and/or dual-connectivity data collection.

Step 301I: the secondary node 1 transmits a request for multi-hop and/or dual-connectivity data collection to the master node to request the master node to collect and/or report a result of the multi-hop and/or dual-connectivity data collection. The request for multi-hop and/or dual-connectivity data collection may be the aforementioned first message. The message may be transmitted through a DATA COLLECTION REQUEST message.

Step 302I: optionally, the master node transmits a response for multi-hop and/or dual-connectivity data collection to the secondary node 1 to inform the master node whether the secondary node 1 can perform the requested collection and/or reporting. The response for the multi-hop and/or dual-connectivity data collection may be the aforementioned second message. The message may be transmitted through a DATA COLLECTION RESPONSE message and/or a DATA COLLECTION FAILURE message.

Step 303I: the exchange between UE, master node, secondary node 1, other master nodes and/or secondary nodes may refer to steps 301F to 316F in FIG. 3F, or steps 301G to 319G in FIG. 3G, or steps 301H to 315H in FIG. 3H, where the master node in FIG. 3I corresponds to the master node 1 in FIG. 3G or 3H.

Step 304I: the master node transmits the collected results of the multi-hop and/or dual-connectivity data collection to the secondary node 1. The results of the multi-hop and/or dual-connectivity data collection may be the aforementioned third message. The message may be transmitted through a DATA COLLECTION UPDATE message.

FIG. 4A shows a schematic diagram of an aspect of a method for supporting data collection according to embodiments of the present disclosure. Specifically, FIG. 4A shows a process of exchanging a prediction result of handover related auxiliary/assistance information between two nodes, so that the first node can make (subsequent) mobility-related decisions based on the prediction result of the handover related auxiliary/assistance information, or it may forward the prediction result of the handover related auxiliary/assistance information to other nodes for the other nodes to make (subsequent) handover decisions.

After the first node receives the prediction result of handover related auxiliary/assistance information, in some implementations, for example, it may make subsequent mobility decisions based on the prediction result of handover related auxiliary/assistance information. In another implementation, for example, the first node may select a target node for (conditional) handover and/or (conditional) secondary node addition and/or (conditional) secondary node change, and/or set a time for related handover and/or secondary node addition and/or secondary node change based on the handover related auxiliary/assistance information prediction result.

In an implementation, for example, the first node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB, and the second node may be a UE. In an implementation, for example, the first node may be a UE, and the second node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In another implementation, for example, the first node may be a gNB or a gNB-CU or a gNB-CP or an en-gNB or an eNB or an ng-eNB, and the second node may be a gNB or a gNB-CU or a gNB-DU or a gNB CU-CP or a gNB CU-UP or an en-gNB or an eNB or an ng-eNB. In yet another implementation, for example, the first node may be an AMF or an SMF or an MME, and the second node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB. In yet another implementation, for example, the first node may be a gNB or a gNB-CU or a gNB CU-CP or an en-gNB or an eNB or an ng-eNB, and the second node may be an AMF or an SMF or an MME. Alternatively, for example, the first node is a master node and the second node is a secondary node; for example, the first node is a secondary node and the second node is a master node; for example, the first node is a source node and the second node is a target node; for example, the first node is a target node and the second node is a source node.

Step 401A: the second node transmits a prediction result of handover related auxiliary/assistance information to the first node. The prediction result of handover related auxiliary/assistance information may be the aforementioned sixth message.

Step 402A: the first node may make (subsequent) mobility-related decisions based on the prediction result of the handover related auxiliary/assistance information, or it may forward the prediction result of the handover related auxiliary/assistance information to other nodes for the other nodes to make (subsequent) handover decisions.

After the first node receives the prediction result of handover related auxiliary/assistance information, in some implementations, for example, it may make subsequent mobility decisions based on the prediction result of handover related auxiliary/assistance information. In another implementation, for example, the third node may select a target node for (conditional) handover and/or (conditional) secondary node addition and/or (conditional) secondary node change, and/or set a time for related handover and/or secondary node addition and/or secondary node change based on the handover related auxiliary/assistance information prediction result.

FIG. 4B shows a schematic diagram of an aspect of a method for supporting data collection according to embodiments of the present disclosure. Specifically, FIG. 4B shows a process of exchanging a prediction result of handover related auxiliary/assistance information between two nodes, so that the first node can make (subsequent) mobility-related decisions based on the prediction result of the handover related auxiliary/assistance information, or it may forward the prediction result of the handover related auxiliary/assistance information to other nodes for the other nodes to make (subsequent) handover decisions.

Step 401B: the first node transmits a request for prediction of handover related auxiliary/assistance information to the second node to request the second node to predict and/or report the prediction result of handover related auxiliary/assistance information. The request for prediction of handover related auxiliary/assistance information may be the aforementioned fourth message.

Step 402B: optionally, the second node transmits a response for the prediction of the handover related auxiliary/assistance information to the first node, so as to inform the first node whether the second node can predict and/or report the handover related auxiliary/assistance information. The response for the prediction of the handover related auxiliary/assistance information may be the aforementioned fifth message.

Step 403B: the second node transmits a prediction result of handover related auxiliary/assistance information to the first node. The prediction result of handover related auxiliary/assistance information may be the aforementioned sixth message.

Step 404B: the first node may make (subsequent) mobility-related decisions based on the prediction result of the handover related auxiliary/assistance information, or it may forward the prediction result of the handover related auxiliary/assistance information to other nodes for the other nodes to make (subsequent) handover decisions.

In some implementations, for example, step 402B may be omitted.

FIG. 4C shows a schematic diagram of an aspect of a method for supporting data collection according to embodiments of the present disclosure. Specifically, FIG. 4C shows a process of exchanging prediction results of handover related auxiliary/assistance information, so that the nodes can make (subsequent) mobility-related decisions based on the prediction results of handover related auxiliary/assistance information.

After the node receives the prediction result of handover related auxiliary/assistance information, in some implementations, for example, it may make subsequent mobility decisions based on the prediction result of handover related auxiliary/assistance information. In another implementation, for example, a node can select a target node for (conditional) handover and/or (conditional) secondary node addition and/or (conditional) secondary node change based on the prediction result of handover related auxiliary/assistance information, and/or set a time for the relevant handover and/or secondary node addition and/or secondary node change.

In an implementation, for example, the fifth node may be a target master node and/or a (candidate) target secondary node and/or other nodes.

Step 401C: optionally, the fifth node transmits a request for prediction of handover related auxiliary/assistance information to the master node, so as to request the master node to predict and/or report a prediction result of the handover related auxiliary/assistance information. The request for prediction of handover related auxiliary/assistance information may be the aforementioned fourth message. The message may be transmitted through a DATA COLLECTION REQUEST message. If the fifth node is the target master node and/or other nodes, for example, the message in step 401C may be transmitted through a HANDOVER REQUEST ACKNOWLEDGE message.

Step 402C: optionally, the master node transmits a request for prediction of handover related auxiliary/assistance information to the secondary node, so as to request the secondary node to predict and/or report a prediction result of the handover related auxiliary/assistance information. The request for prediction of handover related auxiliary/assistance information may be the aforementioned fourth message. The message may be transmitted through a DATA COLLECTION REQUEST message.

Step 403C: optionally, the secondary node transmits a response for the prediction of the handover related auxiliary/assistance information to the master node, so as to inform the master node whether the secondary node can predict and/or report the handover related auxiliary/assistance information. The response for the prediction of the handover related auxiliary/assistance information may be the aforementioned fifth message. The message may be transmitted through a DATA COLLECTION RESPONSE message and/or a DATA COLLECTION FAILURE message. If the message indicates that the secondary node cannot predict and/or report all the requested handover related auxiliary/assistance information, then steps 405C and 406C will not be performed.

Step 404C: optionally, the master node transmits a response for the prediction of the handover related auxiliary/assistance information to the fifth node, so as to inform the fifth node whether the master node can predict and/or report handover related auxiliary/assistance information. The response for the prediction of the handover related auxiliary/assistance information may be the aforementioned fifth message. The message may be transmitted through a DATA COLLECTION RESPONSE message and/or a DATA COLLECTION FAILURE message. If the message indicates that the secondary node cannot predict and/or report all the requested handover related auxiliary/assistance information, then steps 405C and 406C will not be performed.

Step 405C: the secondary node transmits a prediction result of handover related auxiliary/assistance information to the master node. The prediction result of handover related auxiliary/assistance information may be the aforementioned sixth message. The message may be transmitted through a DATA COLLECTION UPDATE message and/or an S-NODE MODIFICATION REQUEST ACKNOWLEDGE message and/or an S-NODE MODIFICATION REQUIRED message and/or an S-NODE CHANGE REQUIRED message and/or an S-NODE RELEASE REQUEST ACKNOWLEDGE message.

Step 406C: the master node transmits a prediction result of handover related auxiliary/assistance information to the fifth node. The prediction result of handover related auxiliary/assistance information may be the aforementioned sixth message. The message may be transmitted through a DATA COLLECTION UPDATE message and/or an S-NODE ADDITION REQUEST message and/or an S-NODE MODIFICATION REQUEST message and/or an S-NODE MODIFICATION CONFIRM message and/or an S-NODE CHANGE CONFIRM message and/or an S-NODE RELEASE REQUEST message.

Step 407C: UE accesses the fifth node.

Step 408C: the fifth node may make (subsequent) mobility-related decisions based on the prediction result of the handover related auxiliary/assistance information, or it may forward the prediction result of the handover related auxiliary/assistance information to other nodes for the other nodes to make (subsequent) handover decisions.

After the fifth node receives the prediction result of the handover related auxiliary/assistance information, in some implementations, for example, it may make subsequent mobility decisions based on the prediction result of the handover related auxiliary/assistance information. In another implementation, for example, the third node may select a target node for (conditional) handover and/or (conditional) secondary node addition and/or (conditional) secondary node change, and/or set a time for related handover and/or secondary node addition and/or secondary node change based on the handover related auxiliary/assistance information prediction result.

In some implementations, for example, step 401C and/or step 402C and/or step 403C and/or step 404C may be omitted.

In some implementations, for example, step 408C may occur before step 407C.

It should be understood that, depending on the application scenario, the various example aspects, methods, steps, processes, etc. shown in the drawings can be combined and implemented in any way, and there is no limitation here.

Next, FIG. 5 shows a flowchart of a method 500 performed by a second node in a wireless communication system according to embodiments of the present disclosure.

As shown in FIG. 5, a method 500 performed by a second node in a wireless communication system according to embodiments of the present disclosure may include: in step S501, receiving a first message from a first node, wherein the first message includes a first collection configuration and a first reporting configuration for multi-hop data collection of a user equipment (UE); and in step S502, transmitting a seventh message to a third node, wherein the seventh message includes a second collection configuration for the multi-hop data collection, wherein the second collection configuration is determined based on the first collection configuration and data collection information of the UE at the second node. In some implementations, the first message further includes at least one of: a node identifier of an initial configuration node of the multi-hop data collection, a UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the first collection configuration is a start configuration for the multi-hop data collection. In some implementations, the seventh message further includes at least one of: the node identifier of the initial configuration node, the UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the second collection configuration is a subsequent configuration for the multi-hop data collection.

FIG. 6 shows a flowchart of a method 600 performed by a first node in a wireless communication system according to embodiments of the present disclosure.

As shown in FIG. 6, a method 600 performed by a first node in a wireless communication system according to embodiments of the present disclosure may include: in step S601, transmitting a first message to a second node, wherein the first message includes a first collection configuration and a first reporting configuration for multi-hop data collection of a user equipment (UE); and in step S602, receiving a second message from the second node, wherein the second message includes a first response for the first message. In some implementations, a seventh message is transmitted by the second node to a third node, wherein the seventh message includes a second collection configuration for the multi-hop data collection. In some implementations, the second collection configuration is determined based on the first collection configuration and data collection information of the UE at the second node. In some implementations, the first message further includes at least one of: a node identifier of an initial configuration node of the multi-hop data collection, a UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the first collection configuration is a start configuration for the multi-hop data collection. In some implementations, the seventh message further includes at least one of: the node identifier of the initial configuration node, the UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the second collection configuration is a subsequent configuration for the multi-hop data collection.

FIG. 7 shows a flowchart of a method 700 performed by a third node in a wireless communication system according to embodiments of the present disclosure.

As shown in FIG. 7, a method 700 performed by a third node in a wireless communication system according to embodiments of the present disclosure may include: in step S701, receiving a seventh message from a second node, wherein the seventh message includes a second collection configuration for multi-hop data collection of a user equipment (UE), wherein the second collection configuration is determined based on a first collection configuration for the multi-hop data collection and data collection information of the UE at the second node, wherein the first collection configuration is received by the second node from a first node; and in step S702, transmitting a ninth message to the second node, wherein the ninth message includes information about whether the third node can be able to transmit a collection result of the multi-hop data collection to the initial configuration node of the multi-hop data collection directly. In some implementations, the seventh message further includes at least one of: a node identifier of an initial configuration node of the multi-hop data collection, a UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the second collection configuration is a subsequent configuration for the multi-hop data collection.

FIG. 8 shows a flowchart of a method 800 performed by a user equipment (UE) in a wireless communication system according to embodiments of the present disclosure.

As shown in FIG. 8, a method 800 performed by a user equipment (UE) in a wireless communication system according to embodiments of the present disclosure may include: in step S801, receiving a radio resource control (RRC) reconfiguration message from a first node; and in step S802, transmitting an RRC reconfiguration complete message to the first node. In some implementations, a first message is transmitted by the first node to a second node, wherein the first message includes a first collection configuration and a first reporting configuration for multi-hop data collection of the UE. In some implementations, a seventh message is transmitted by the second node to a third node, wherein the seventh message includes a second collection configuration for the multi-hop data collection. In some implementations, the second collection configuration is determined based on the first collection configuration and data collection information of the UE at the second node. In some implementations, the first message further includes at least one of: a node identifier of an initial configuration node of the multi-hop data collection, a UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the first collection configuration is a start configuration for the multi-hop data collection. In some implementations, the seventh message further includes at least one of: the node identifier of the initial configuration node, the UE identifier assigned for the UE by the initial configuration node, and an identification indicating that the second collection configuration is a subsequent configuration for the multi-hop data collection.

It should be understood that methods 500, 600, 700, 800, etc. according to embodiments of the present disclosure may further include any method or step described in connection with various examples, aspects, drawings, etc. of the present disclosure.

Next, FIG. 9 shows a schematic diagram of a node 900 according to embodiments of the present disclosure.

As shown in FIG. 9, a node 900 (or a node device, for example, the first node, the second node and/or the third node as described above) according to embodiments of the present disclosure may include a transceiver 910 and a processor 920. The transceiver 910 may be configured to transmit and receive signals. The processor 920 may be coupled to the transceiver 910 and may be configured to (e.g., control the transceiver 910 to) perform methods performed by a node (e.g., a first node, a second node and/or a third node) according to embodiments of the present disclosure.

FIG. 10 shows a schematic diagram of a user equipment 1000 according to embodiments of the present disclosure.

As shown in FIG. 10, a user equipment 1000 according to embodiments of the present disclosure may include a transceiver 1010 and a processor 1020. The transceiver 1010 may be configured to transmit and receive signals. The processor 1020 may be coupled to the transceiver 1010 and may be configured to (e.g., control the transceiver 1010 to) perform methods performed by a user equipment according to embodiments of the present disclosure. In the present disclosure, a processor may also be referred to as a controller. In the present disclosure, a node may also be referred to as a node device.

Embodiments of the present disclosure also provide a computer-readable medium having stored thereon computer-readable instructions which, when executed by a processor, implement any method according to embodiments of the present disclosure.

Various embodiments of the present disclosure may be implemented as computer-readable codes embodied on a computer-readable recording medium from a specific perspective. A computer-readable recording medium is any data storage device that can store data readable by a computer system. Examples of computer-readable recording media may include read-only memory (ROM), random access memory (RAM), compact disk read-only memory (CD-ROM), magnetic tape, floppy disk, optical data storage device, carrier wave (e.g., data transmission via the Internet), etc. Computer-readable recording media can be distributed by computer systems connected via a network, and thus computer-readable codes can be stored and executed in a distributed manner. Furthermore, functional programs, codes and code segments for implementing various embodiments of the present disclosure can be easily explained by those skilled in the art to which the embodiments of the present disclosure are applied.

It will be understood that the embodiments of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software. The software may be stored as program instructions or computer-readable codes executable on a processor on a non-transitory computer-readable medium. Examples of non-transitory computer-readable recording media include magnetic storage media (such as ROM, floppy disk, hard disk, etc.) and optical recording media (such as CD-ROM, digital video disk (DVD), etc.). Non-transitory computer-readable recording media may also be distributed on computer systems coupled to a network, so that computer-readable codes are stored and executed in a distributed manner. The medium can be read by a computer, stored in a memory, and executed by a processor. Various embodiments may be implemented by a computer or a portable terminal including a controller and a memory, and the memory may be an example of a non-transitory computer-readable recording medium suitable for storing program (s) with instructions for implementing embodiments of the present disclosure. The present disclosure may be realized by a program with code for concretely implementing the apparatus and method described in the claims, which is stored in a machine (or computer)-readable storage medium. The program may be electronically carried on any medium, such as a communication signal transmitted via a wired or wireless connection, and the present disclosure suitably includes its equivalents.

What has been described above is only the specific implementation of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Anyone who is familiar with this technical field may make various changes or substitutions within the technical scope disclosed in the present disclosure, and these changes or substitutions should be covered within the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

A method performed by a secondary node (SN) in a communication system, the method comprising:

performing an initiation procedure to report a data collection and to configure to collect requested information of the data collection;

receiving, from a master node (MN), an addition request message to request the data collection for a user equipment (UE), the addition request message including collection identifier (ID) information; and

as a response to the addition request message, transmitting, to the MN, an addition request acknowledge message to report a result of the data collection,

wherein the data collection is associated with a dual-connectivity.
The method of claim 1,

wherein the requested information configures information corresponding to at least one of a measurement ID, information associated with the MN, or information associated with SN.
The method of claim 1,

wherein the addition request acknowledge message includes the requested information.
The method of claim 1,

wherein a data corresponding to the dual-connectivity data collection includes at least one of information associated with user performance,

wherein the at least one information associated with the user performance includes at least one of a data rate, a throughput, a delay, a packet loss rate or at least one quality of environment (QoE) parameter,

wherein the addition request message includes at least one indication, and

wherein the at least one indication includes at least one of a request ID, a configuration ID, or information of a cell.
A method performed by a master node (MN) in a communication system, the method comprising:

performing an initiation procedure to report a data collection and to configure to collect requested information of the data collection;

transmitting, to a secondary node (SN), an addition request message to request the data collection for a user equipment (UE), the addition request message including collection identifier (ID) information; and

as a response to the addition request message, receiving, from the SN, an addition request acknowledge message to report a result of the data collection,

wherein the data collection is associated with a dual-connectivity.
The method of claim 5,

wherein the requested information configures information corresponding to at least one of a measurement ID, information associated with the MN, or information associated with SN.
The method of claim 5,

wherein the addition request acknowledge message includes the requested information.
The method of claim 5,

wherein a data corresponding to the dual-connectivity data collection includes at least one of information associated with user performance,

wherein the at least one information associated with the user performance includes at least one of a data rate, a throughput, a delay, a packet loss rate or at least one quality of environment (QoE) parameter,

wherein the addition request message includes at least one indication, and

wherein the at least one indication includes at least one of a request ID, a configuration ID, or information of a cell.
A secondary node (SN) in a communication system, the SN comprising:

a transceiver; and

a controller coupled with the transceiver, wherein the controller is configured to:

perform an initiation procedure to report a data collection and to configure to collect requested information of the data collection;

receive, from a master node (MN), an addition request message to request the data collection for a user equipment (UE), the addition request message including collection identifier (ID) information; and

as a response to the addition request message, transmit, to the MN, an addition request acknowledge message to report a result of the data collection,

wherein the data collection is associated with a dual-connectivity.
The SN of claim 9,

wherein the requested information configures information corresponding to at least one of a measurement ID, information associated with the MN, or information associated with SN.
The SN of claim 9,

wherein the addition request acknowledge message includes the requested information.
The SN of claim 9,

wherein a data corresponding to the dual-connectivity data collection includes at least one of information associated with user performance,

wherein the at least one information associated with the user performance includes at least one of a data rate, a throughput, a delay, a packet loss rate or at least one quality of environment (QoE) parameter,

wherein the addition request message includes at least one indication, and

wherein the at least one indication includes at least one of a request ID, a configuration ID, or information of a cell.
A master node (MN) in a communication system, the MN comprising:

a transceiver; and

a controller coupled with the transceiver, wherein the controller is configured to:

perform an initiation procedure to report a data collection and to configure to collect requested information of the data collection;

transmit, to a secondary node (SN), an addition request message to request the data collection for a user equipment (UE), the addition request message including collection identifier (ID) information; and

as a response to the addition request message, receive, from the SN, an addition request acknowledge message to report a result of the data collection,

wherein the data collection is associated with a dual-connectivity.
The MN of claim 13,

wherein the requested information configures information corresponding to at least one of a measurement ID, information associated with the MN, or information associated with SN, and

wherein the addition request acknowledge message includes the requested information.
The MN of claim 13,

wherein a data corresponding to the dual-connectivity data collection includes at least one of information associated with user performance,

wherein the at least one information associated with the user performance includes at least one of a data rate, a throughput, a delay, a packet loss rate or at least one quality of environment (QoE) parameter,

wherein the addition request message includes at least one indication, and

wherein the at least one indication includes at least one of a request ID, a configuration ID, or information of a cell.