WO2025198358A1

WO2025198358A1 - Method and apparatus for continuous minimization of drive tests in a wireless communication system

Info

Publication number: WO2025198358A1
Application number: PCT/KR2025/003637
Authority: WO
Inventors: Yanru Wang; Lixiang Xu; Hong Wang
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2024-03-22
Filing date: 2025-03-21
Publication date: 2025-09-25
Anticipated expiration: 2026-09-22
Also published as: CN120692573A

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a user equipment (UE) in a wireless communication system includes: receiving a second Minimization of Drive Tests (MDT) configuration and second information from a first node, wherein the second information includes information related to continuous data collection associated with the second MDT configuration; performing second MDT data collection based on the second MDT configuration in a radio resource control (RRC) inactive state or an RRC idle state; connecting to a second node; transmitting a second MDT report associated with the second MDT configuration and a second result associated with the continuous data collection to the second node; and receiving a third MDT configuration and third information from the second node, wherein the third information includes information indicating that the third MDT configuration is associated with the second MDT configuration and/or the first node.

Description

METHOD AND APPARATUS FOR CONTINUOUS MINIMIZATION OF DRIVE TESTS 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 (THz) 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.

Currently, there are needs to enhance continuous MDT in a wireless communication system.

Embodiments of the present disclosure provide a method performed by a user equipment (UE) (or, a terminal) in a wireless communication system, which includes: receiving a second Minimization of Drive Tests (MDT) configuration and second information from a first node, wherein the second information includes information related to continuous data collection associated with the second MDT configuration; performing second MDT data collection based on the second MDT configuration in a radio resource control (RRC) inactive state or an RRC idle state; connecting to a second node; transmitting a second MDT report associated with the second MDT configuration and a second result associated with the continuous data collection to the second node; and receiving a third MDT configuration and third information from the second node, wherein the third information includes information indicating that the third MDT configuration is associated with the second MDT configuration and/or the first node.

According to embodiments of the present disclosure, the method further includes: transmitting fourth information about that the second MDT report associated with the second MDT configuration is available and reporting information related to the continuous data collection to the second node, and receiving a request for the second MDT report associated with the second MDT configuration and the second result associated with the continuous data collection from the second node, wherein the request is transmitted from the second node based on the reporting information.

According to embodiments of the present disclosure, the method further includes: receiving a first MDT configuration and first information from the first node, wherein the first information includes information related to the continuous data collection, wherein the second information further includes information indicating that the second MDT configuration is associated with the first MDT configuration.

According to embodiments of the present disclosure, the method further includes: transmitting a first MDT report associated with the first MDT configuration and a first result associated with the continuous data collection to the first node.

According to embodiments of the present disclosure, the method further includes: transmitting a third MDT report associated with the third MDT configuration and a third result associated with the continuous data collection to the second node.

According to embodiments of the present disclosure, each of the first result, the second result and the third result includes a first identification of the UE associated with the continuous data collection and/or a second identification of an initial configuration node of the continuous data collection, and wherein the first MDT report, the second MDT report and the third MDT report are associated by the first identification and/or the second identification.

According to embodiments of the present disclosure, the second result includes one or more of an accumulated time and a data collection configuration associated with the continuous data collection, and wherein the third MDT configuration is determined based on one or more of the accumulated time and the data collection configuration.

Embodiments of the present disclosure provide a method performed by a first node in a wireless communication system, which includes: transmitting a second Minimization of Drive Tests (MDT) configuration and second information to a user equipment (UE), wherein the second information includes information related to continuous data collection associated with the second MDT configuration; transmitting a first MDT configuration and first information to the UE, wherein the first information includes information related to the continuous data collection; and receiving a first MDT report associated with the first MDT configuration and a first result associated with the continuous data collection from the UE.

According to embodiments of the present disclosure, the method further includes: receiving one or more of the second MDT configuration, the second information, the first MDT configuration and the first information from a core network node.

Embodiments of the present disclosure provide a method performed by a second node in a wireless communication system, which includes: receiving, from a user equipment (UE), a second MDT report associated with a second Minimization of Drive Tests (MDT) configuration transmitted to the UE by a first node and a second result associated with continuous data collection; and transmitting a third MDT configuration and third information to the UE, wherein the third information includes information indicating that the third MDT configuration is associated with the second MDT configuration and/or the first node.

According to embodiments of the present disclosure, the method further includes: receiving fourth information about that the second MDT report associated with the second MDT configuration is available and reporting information related to the continuous data collection from the UE, and transmitting a request for the second MDT report associated with the second MDT configuration and the second result associated with the continuous data collection to the UE, wherein the request is transmitted from the second node based on the reporting information.

According to embodiments of the present disclosure, the method further includes: receiving a third MDT report associated with the third MDT configuration and a third result associated with continuous data collection from the UE.

According to embodiments of the present disclosure, the method further includes: receiving one or more of the third MDT configuration and the third information from a core network node.

According to embodiments of the present disclosure, each of the second result and the third result includes a first identification of the UE associated with the continuous data collection and/or a second identification of an initial configuration node of the continuous data collection, and wherein the second MDT report and the third MDT report are associated by the first identification and/or the second identification.

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 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 user equipment in a wireless communication system according to embodiments of the present disclosure.

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

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. 3 shows a schematic diagram of an aspect of a method for supporting continuous data collection according to embodiments of the present disclosure;

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

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

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

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

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

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

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

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

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

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

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

FIG. 6 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. 7 shows a flowchart of a method performed by a first node in a wireless communication system according to embodiments of the present disclosure;

FIG. 8 shows a flowchart of a method performed by a second node 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 user equipment 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.

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.

In the present disclosure, a node may refer to a specific node, or may refer to a cell and/or beam managed by the node, etc.

In the present disclosure, a cell may refer to a specific cell, or may refer to a node where the cell is located, or may refer to a beam corresponding to the cell, 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 the following: 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: accessing cell identification, connecting cell identification, serving cell identification, etc. The beam identification may be one or more of the following: access beam identification, connecting beam identification, accessed 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 value, 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 value, 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, or any measurement, which is not limited in the present disclosure. The MDT may be a Logged MDT or an Immediate MDT; The MDT may be a Signalling-based MDT or a Management-based MDT. When a UE is connected from one base station to another, continuous data collection is necessary, but the research on continuous data collection in the prior art is insufficient.

In the present disclosure, a user equipment (UE) and a user, a terminal and the like may refer to each other.

In the present disclosure, data collection may include continuous data collection and discontinuous data collection.

In the present disclosure, "collect/collection" may also be "measure/measurement". Data collection may also be measurement.

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

● User trajectory related data: it may include one or more of the following:

o user identification

o visited cell identification

o visited primary cell identification

o visited secondary cell identification

o visited primary cell identification and visited secondary cell identification: it indicates the visited primary cell and visited secondary cell in a case of dual-connectivity.

o node where a visited cell is located: it may be a node identification or a node name.

o node where a visited primary cell is located: it may be a node identification or a node name.

o node where a visited secondary cell is located: it may be a node identification or a node name.

o visit time and/or residence time

o coordinate

o visited beam information: it may be a beam identification.

● User performance related data: it may include one or more of the following:

o user identification

o time of user performance collection

o node corresponding to user performance collection: it may be a node identification or a node name.

o cell identification corresponding to user performance

o beam identification corresponding to user performance

o slice identification corresponding to user performance

o Protocol Data Unit (PDU) session identification corresponding to user performance.

o Data Radio Bearer (DRB) identification corresponding to user performance.

o QoS flow identification corresponding to user performance

o user performance: it 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.

● Network performance related data: it may include one or more of the following:

o time of network performance collection

o node corresponding to network performance collection: it may be a node identification or a node name.

o cell identification corresponding to network performance

o beam identification corresponding to network performance

o slice identification corresponding to network performance

o Data Radio Bearer (DRB) identification corresponding to network performance

o QoS flow identification corresponding to network performance

o network performance: it 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: it may include one or more of the following:

o user identification

o node identification and/or cell identification corresponding to a user measurement result

o measurement result

o measurement time

● Perception related result information: it may include one or more of the following:

o user identification

o node identification and/or cell identification corresponding to a user perception related measurement result

o perception related measurement result

o perception related measurement time

Example 1

An aspect of the present disclosure provides a method for supporting continuous data collection, including:

a first node transmits a first message including information about continuous data collection to a second node to inform the second node of information corresponding to/associated with continuous data collection, and the second node needs to perform configuration according to the information in the first message when performing continuous data collection. In some implementations, for example, the first message may trigger the second node to perform continuous data collection. In another implementation, for example, the first message only informs the second node of information corresponding to continuous data collection, but does not trigger the second node to perform continuous data collection. In still other implementations, for example, the first message may trigger the second node to configure continuous data collection for corresponding users, or the first message may trigger the second node to configure continuous data collection for the corresponding users according to the information in the first message. In yet another implementation, for example, the first message may inform the second node to continuously collect corresponding information, and the second node can perform continuous data collection later.

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 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 of Xn; 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 of NG; an RRC reconfiguration message of RRC; 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 first message may include one or more of the following information and/or fields:

● Transmitting node identification (ID): used to identify the node transmitting the message.

● Receiving node ID: used to identify the node receiving the message.

● Request ID: used to identify the request.

● Measurement ID: used to identify the measurement request.

● Reporting ID: used to identify the reporting request.

● Configuration ID: used to identify the configuration of the continuous data collection. This identification can uniquely identify a continuous data collection configuration. For example, the configuration may be an MDT configuration or a continuous MDT configuration.

● Identification of continuous data collection (request): used to indicate that the information contains continuous data collection (request). After the message receiving node receives the information, in some implementations, for example, the message receiving node may be triggered to perform continuous data collection. In another implementation, for example, the information only informs the message receiving node of the information corresponding to the continuous data collection, but does not trigger the message receiving node to perform the continuous data collection. In still other implementations, for example, the information may trigger the message receiving node to configure continuous data collection for the corresponding users, or the information may trigger the message receiving node to configure continuous data collection for the corresponding users according to the information in the message. In still other implementations, for example, the information may indicate that the data collection and/or the reporting of the data collection results do not need to be anonymous.

● Collection time of continuous data collection: used to indicate the collection time of the continuous data collection.

● Start indication of continuous data collection: used to indicate the start of the continuous data collection. In some implementations, for example, after receiving the indication, the message receiving node starts continuous data collection or configure a UE to start continuous data collection. In still other implementations, for example, after the message receiving node receives the indication, the message receiving node may assign a first identification, and/or configure the first identification and/or an identification of a node and/or cell corresponding to the start of the continuous data collection and/or an initial configuration of the continuous data collection to the UE. In still other implementations, for example, after receiving the indication, the UE starts to time the continuous data collection. For example, an accumulated time of the continuous data collection may be transmitted to the node to which the UE is connected, so that the node to which the UE is connected can configure subsequent data collection.

● Start time of continuous data collection: used to indicate the start time of the continuous data collection. In some implementations, for example, the message receiving node may collect data from the start time of the continuous data collection. In another implementation, for example, the message receiving node may configure continuous data collection for the UE from the start time of the continuous data collection.

● End indication of continuous data collection: used to indicate the end of the continuous data collection. In some implementations, for example, after receiving the indication, the message receiving node stops continuous data collection or configures the UE to stop continuous data collection.

● End time of continuous data collection: used to indicate the end time of the continuous data collection. In some implementations, for example, after receiving the end time, the message receiving node stops the continuous data collection at the end time, or configures the UE to stop the continuous data collection at the end time.

● Time of continuous data collection: used to indicate time information of the continuous data collection. In some implementations, for example, after receiving this time, the message receiving node collects data only within the time of the continuous data collection, or configures the UE to collect data within the time of the continuous data collection. In some implementations, the time of the continuous data collection may also be a reporting time of results of the continuous data collection.

● Remaining time of continuous data collection: used to indicate the time for which the continuous data collection is still required to be performed. In some implementations, for example, after receiving this information, the message receiving node collects data within the remaining time of continuous data collection, or it may perform configuration within the remaining time of continuous data collection for the UE to collect data, or it may configure the UE to collect data within the remaining time of continuous data collection. For example, if the remaining time of the continuous data collection is equal to or less than a threshold value, the message receiving node may not collect data, and/or not configure the UE to collect data. For example, the threshold value may be 0. For example, if the remaining time of the continuous data collection is equal to or greater than a threshold value, the message receiving node may collect data and/or configure the UE to collect data.

● Accumulated time of continuous data collection: used to indicate the time for which the continuous data collection has been performed. In some implementations, for example, the message receiving node may decide whether to continue to configure subsequent data collection based on the time of continuous data collection and/or the accumulated time of continuous data collection. For example, if the time of continuous data collection minus the accumulated time of continuous data collection is equal to and/or greater than a threshold value, the message receiving node may collect data and/or configure the UE to collect data. For example, if the time of continuous data collection minus the accumulated time of continuous data collection is equal to and/or less than a threshold value, the message receiving node may not collect data, and/or not configure the UE to collect data. For example, the threshold value may be 0. In yet another implementation, the message receiving node may continue to configure subsequent data collection based on the time of continuous data collection and/or the accumulated time of continuous data collection, so as to achieve continuous data collection. For example, the message receiving node may configure to collect data at the first time. The first time may be the time of continuous data collection minus the accumulated time of continuous data collection.

● Cell corresponding to continuous data collection: it may represent information of the cell(s) corresponding to the continuous data collection. For example, it may include one or more of the following: cell identification and/or cell identification list, and number of cells. In some implementations, for example, the continuous data collection is performed within the cell(s) of a corresponding cell identification and/or cell identification list. In some other implementations, for example, when the number of cells corresponding to the completed continuous data collection and/or data collection results reaches this number of cells, the continuous data collection should be stopped.

● Node corresponding to continuous data collection: it may represent information of the node(s) corresponding to continuous data collection. For example, it may include one or more of the following: node identification and/or node identification list, and number of nodes. In some implementations, for example, continuous data collection is performed within the node(s) of a corresponding node identification and/or node identification list. In some other implementations, for example, when the number of nodes corresponding to the completed continuous data collection and/or data collection results reaches this number of nodes, the continuous data collection should be stopped.

● PLMN information corresponding to continuous data collection: it may represent PLMN information corresponding to the continuous data collection. For example, it may include one or more of the following: PLMN and/or PLMN list, and number of PLMNs. In some implementations, for example, continuous data collection is performed within PLMN(s) of a corresponding PLMN and/or PLMN list. In some other implementations, for example, when the number of PLMNs corresponding to the completed continuous data collection and/or data collection results reaches this number of PLMNs, continuous data collection should be stopped.

● Slice information corresponding to continuous data collection: it may represent the slice information corresponding to the continuous data collection. For example, it may include one or more of the following: slice identification and/or slice identification list, and number of slices. In some implementations, for example, continuous data collection is performed within the slice(s) of a corresponding slice identification and/or slice identification list. In some other implementations, for example, when the number of slices corresponding to the completed continuous data collection and/or data collection results reaches this number of slices, the continuous data collection should be stopped. The slice identification may be represented by Single Network Slice Selection Assistance Information (S-NSSAI).

● Beam information corresponding to continuous data collection: it may represent beam information corresponding to the continuous data collection. For example, it may include one or more of the following: beam identification and/or beam identification list, and number of beams. In some implementations, for example, continuous data collection is performed within beam(s) of a corresponding beam identification and/or beam identification list. In some other implementations, for example, when the number of beams corresponding to the completed continuous data collection and/or data collection results reaches this number of beams, the continuous data collection should be stopped. For example, the beam may be an SSB beam or any other beam. In some implementations, for example, this information may be used by the message receiving node to determine whether to continue to configure continuous data collection, and/or, if so, determine the corresponding configuration information.

● First identification: used to identify the collection. For example, the identification may be a random number. In some implementations, for example, in a continuous data collection process, the first identification of a UE is the same. In some other implementations, for example, the first identification may be configured by a node and/or cell corresponding to the start of the continuous data collection and/or configured by the node and/or cell corresponding to the initial configuration of the continuous data collection.

● Identification of node and/or cell corresponding to the start and/or initial configuration of continuous data collection: used to indicate the identification of the corresponding node and/or cell where the continuous data collection starts, or the identification of the first node and/or cell to configure continuous data collection for the UE. In some implementations, for example, this node and/or cell identification and the first identification can uniquely determine a UE and/or a UE corresponding to the data collection report in the network.

● Dedicated TR and/or TRSR for continuous data collection: in an implementation process, the dedicated TR and/or TRSR remain unchanged during a continuous data collection process. For example, in a continuous data collection process, the dedicated TR and/or TRSR for the same UE remain unchanged. In some implementations, for example, a node can associate multiple data collection results of the same UE through the dedicated TR and/or TRSR.

● Configuration association relationship of continuous data collection: used to represent an association relationship configured in continuous data collection. In some implementations, for example, Configuration A and Configuration B belong to a same continuous data collection, and a node can configure subsequent data collection according to this configuration association relationship to achieve an effect of continuous data collection. The configuration association relationship may be a relationship or a relationship list. The association relationship may be one or more of the following:

o associated TR

o associated TRSR

o associated data collection configuration ID

o associated data collection configuration

o identification of a node and/or cell corresponding to the configuration

● Data collection configuration: in some implementations, for example, the message receiving node may collect data according to the data collection configuration, or the message receiving node may configure related data collection configuration for the UE according to the information. It may include one or more of the following:

o Data collection configuration ID: used to identify the data collection configuration. This identification (ID) can uniquely identify a data collection configuration. For example, the identification may be an MDT configuration identification, which can uniquely identify an MDT configuration. The MDT configuration may include one or more of the data collection configurations.

o Trace Reference (TR): it may include one or more of the following: PLMN ID, and Trace ID

o Trace Recording Session Reference (TRSR)

o Trace Collection Entity ID

o Absolute time information: indicating the absolute time of a cell. In some implementations, for example, it may be the absolute time of the current cell.

o Area configuration: indicating area information for the data collection. It may include one or more of the following: cell identification and/or cell identification list, PLMN ID, Tracking Area Code, uplink and/or downlink carrier frequency, etc. The cell identification may be a Physical Cell ID or a Cell Global ID.

o PLMN ID (list): indicating the PLMN ID(s) corresponding to the measurement recording, related status indicating and information acquiring performed by the UE.

o Bluetooth name (list): indicating the name (list) of the Bluetooth beacon that the UE is configured to measure.

o WLAN name (list): indicating the WLAN access point name (list) that the UE is configured to measure.

o Sensor name (list): indicating the sensor name (list) that the UE is configured to measure.

o Recording time: indicating the time when the UE is required to perform measurement recording.

o Report type: it may include periodic reporting, event-triggered reporting and single-time reporting.

o Recording interval: indicating a time period and/or a time interval for recording measurement results.

o Configuration of event-triggering: including trigger event, threshold value, trigger time, delay, etc. The trigger event may be one or more of the following: out of coverage, RRC state change, etc.

o MDT configuration mode: used to indicate whether the configuration is Signalling-based or Management-based. This configuration mode also indicates an MDT type configured by this configuration. The MDT types may include one or more of the following: Logged MDT, Immediate MDT, Signalling-based MDT, Management-based MDT, and combinations thereof.

o Early measurement indication: used to indicate whether the UE is allowed to record related measurement results of an early measurement frequency.

o Events and/or conditions that trigger data collection: when an event and/or condition that triggers data collection is met, data collection is performed. The events and/or conditions may include one or more of the following: current data collection ends, Logged MDT ends, etc. In some implementations, for example, it may be an event and/or a condition that triggers an Immediate MDT. For example, the event and/or condition that triggers an Immediate MDT may be a Logged MDT ends. Therefore, an Immediate MDT can be started immediately after a Logged MDT ends, so as to achieve the effect of continuous data collection.

Example 2

A third node transmits a second message including all and/or part of continuous data collection results to a fourth node, so as to report all and/or part of continuous data collection results to the fourth node.

In some implementations, the second message may be included in one or more of the following: a UEInformationResponse message of RRC; 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 second message may include one or more of the following information and/or fields:

● Transmitting node ID: used to identify the node transmitting the message.

● Receiving node ID: used to identify the node receiving the message.

● Measurement ID: used to identify the measurement. In an implementation, for example, the measurement ID may be consistent with the measurement ID in the first message, which is used to associate the reporting message with the configuration message.

● Request ID: used to identify the request. In an implementation, for example, the request ID may be consistent with the request ID in the first message, which is used to associate the reporting message with the configuration message.

● Prediction ID: used to identify the prediction request. In an implementation, for example, the prediction ID may be consistent with the prediction ID in the first message, which is used to associate the reporting message with the configuration message.

● Reporting ID: used to identify the reporting request. In an implementation, for example, the reporting ID may be consistent with the reporting ID in the first message, which is used to associate the reporting message with the configuration message.

● Configuration ID: used to identify the configuration of the measurement and/or prediction and/or reporting. In some implementations, for example, the configuration ID may be consistent with the configuration ID in the first message, which is used to associate the reporting message with the configuration message.

● Configuration of continuous data collection: the configuration of continuous data collection may be one or more of the configurations in the first message. The configuration of the continuous data collection informs the message receiving node of a configured continuous data collection configuration. In some implementations, for example, the message receiving node may continue to configure subsequent continuous data collection according to the configuration, so as to achieve the effect of continuous data collection.

● Identification of continuous data collection configuration: this identification can uniquely identify a continuous data collection configuration. For example, the configuration may be an MDT configuration or a continuous MDT configuration. Using this identification to inform the message receiving node of the configuration corresponding to the continuous data collection can save signalling. In some implementations, for example, the message receiving node can know the continuous data collection configuration and/or MDT configuration through the identification, and can continue to configure subsequent data collection according to the configuration to achieve continuous data collection. In still other implementations, for example, the information may indicate that the data collection and/or the reporting of the data collection results do not need to be anonymous.

● Start time of continuous data collection: used to indicate the start time of the continuous data collection. In some implementations, for example, the message receiving node may decide whether to continue to configure subsequent data collection based on the start time of the continuous data collection. For example, the message receiving node may be configured to collect data at a second time, where the second time may be derived from the time of the continuous data collection and the start time of the continuous data collection. For example, the second time may be the remaining time of the continuous data collection derived from the time of the continuous data collection and the start time of the continuous data collection.

● Time of continuous data collection: used to indicate the time of the continuous data collection. In some implementations, for example, the message receiving node may decide whether to configure subsequent continuous data collection based on this information.

● Information of completed and/or ongoing (continuous) data collection: used to indicate the information of the (continuous) data collection that is completed and/or ongoing. This information may include one or more of the following:

o TR and/or TRSR corresponding to completed and/or ongoing (continuous) data collection: this information may be a TR and/or TRSR or a group of TRs and/or TRSRs. In some implementations, for example, this information may be used for a node to associate multiple data collection results to obtain the results of continuous data collection. For example, this information may be used for a node to associate multiple data collection results measured by the same UE to obtain the results of continuous data collection.

o Configuration node and/or cell information corresponding to completed and/or ongoing (continuous) data collection: this information indicates from which node and/or cell the configuration information of the completed and/or ongoing data collection was obtained. This information may be a node and/or cell information, or a node and/or cell information list. This information may include one or more of the following:

■ Node ID

■ Node name

■ Cell ID

o Information corresponding to completed and/or ongoing (continuous) data collection: information corresponding to (continuous) data collection that is completed and/or ongoing. In some implementations, for example, this information may be used by the message receiving node to determine whether to continue to configure continuous data collection, and/or, if so, determine the corresponding configuration information. It may include one or more of the following:

■ Corresponding cell identification and/or identification list

■ Number of corresponding cells

■ Corresponding node identification and/or identification list

■ Number of corresponding nodes

■ Corresponding node name and/or name list

■ Corresponding PLMN and/or PLMN list

■ Number of corresponding PLMNs

■ Corresponding slice identification and/or slice identification list

■ Number of corresponding slices

■ Corresponding beam identification and/or beam identification list

■ Corresponding number of beams

● Cell corresponding to continuous data collection: it may represent information of the cell(s) corresponding to the continuous data collection. For example, it may include one or more of the following: cell identification and/or cell identification list, and number of cells. In some implementations, for example, the continuous data collection is performed within the cell(s) of a corresponding cell identification and/or cell identification list. In some other implementations, for example, when the number of cells corresponding to the completed continuous data collection and/or data collection results reaches this number of cells, the continuous data collection should be stopped. In some implementations, for example, this information may be used by the message receiving node to determine whether to continue to configure continuous data collection, and/or, if so, determine the corresponding configuration information.

● Node corresponding to continuous data collection: it may represent information of the node(s) corresponding to continuous data collection. For example, it may include one or more of the following: node identification and/or node identification list, and number of nodes. In some implementations, for example, continuous data collection is performed within the node(s) of a corresponding node identification and/or node identification list. In some other implementations, for example, when the number of nodes corresponding to the completed continuous data collection and/or data collection results reaches this number of nodes, the continuous data collection should be stopped. In some implementations, for example, this information may be used by the message receiving node to determine whether to continue to configure continuous data collection, and/or, if so, determine the corresponding configuration information.

● PLMN information corresponding to continuous data collection: it may represent PLMN information corresponding to the continuous data collection. For example, it may include one or more of the following: PLMN and/or PLMN list, and number of PLMNs. In some implementations, for example, continuous data collection is performed within PLMN(s) of a corresponding PLMN and/or PLMN list. In some other implementations, for example, when the number of PLMNs corresponding to the completed continuous data collection and/or data collection results reaches this number of PLMNs, continuous data collection should be stopped. In some implementations, for example, this information may be used by the message receiving node to determine whether to continue to configure continuous data collection, and/or, if so, determine the corresponding configuration information.

● Slice information corresponding to continuous data collection: it may represent the slice information corresponding to the continuous data collection. For example, it may include one or more of the following: slice identification and/or slice identification list, and number of slices. In some implementations, for example, continuous data collection is performed within the slice(s) of a corresponding slice identification and/or slice identification list. In some other implementations, for example, when the number of slices corresponding to the completed continuous data collection and/or data collection results reaches this number of slices, the continuous data collection should be stopped. The slice identification may be represented by Single Network Slice Selection Assistance Information (S-NSSAI). In some implementations, for example, this information may be used by the message receiving node to determine whether to continue to configure continuous data collection, and/or, if so, determine the corresponding configuration information.

● Data collection result: indicating the result of data collection. The result may be a result of MDT data collection or a result of other data collection. The data collection result may include one or more of the following:

o Cell identification and/or identification list corresponding to the data collection result

o Number of cells corresponding to the data collection result

o Node identification and/or identification list corresponding to the data collection result

o Number of nodes corresponding to the data collection result

o Node name and/or name list corresponding to the data collection result

o PLMN and/or PLMN list corresponding to the data collection result

o Number of PLMNs corresponding to the data collection result

o Slice identification and/or slice identification list corresponding to the data collection result

o Number of slices corresponding to the data collection result

o Beam identification and/or identification list corresponding to the data collection result

o Number of beams corresponding to the data collection result

● First identification: used to identify the collection. In some implementations, for example, in a continuous data collection process, the first identification of a UE is the same. In some implementations, for example, this information may be used for a node to associate multiple data collection results of the same UE.

● Identification of node and/or cell corresponding to the start and/or initial configuration of continuous data collection: used to indicate the identification of the corresponding node and/or cell where the continuous data collection starts, or the identification of the first node and/or cell to configure continuous data collection for the UE. In some implementations, for example, this node and/or cell identification and the first identification can uniquely determine a UE and/or a UE corresponding to the data collection report in the network. In some implementations, for example, the information may be used for a node to associate multiple data collection results of the same UE, or the combination of the information and the first identification may be used for a node to associate multiple data collection results of the same UE.

o associated TR

o associated TRSR

o identification of a node and/or cell corresponding to the configuration

o associated data collection configuration ID

o associated data collection configuration

Example 3

A fifth node transmits a third message of reporting information of continuous data collection to a sixth node to inform the sixth node of reporting related information of the continuous data collection. In some implementations, for example, the sixth node may transmit a data collection result request to the fifth node according to the information in the reporting information of continuous data collection.

In some implementations, the third message may be included in one or more of the following: a UEInformationResponse message or an RRCSetupComplete message or an RRCReestablishmentComplete message or an RRCReestablishmentComplete message or an RRCReconfigurationComplete message of RRC; 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 third message may include one or more of the following information and/or fields:

● Transmitting node ID: used to identify the node transmitting the message.

● Receiving node ID: used to identify the node receiving the message.

● Expected reporting time: indicating a predicted and/or expected time when reporting can be performed. In some implementations, for example, the message transmitting node and/or UE are performing data collection and cannot performing reporting at present, and an expected reporting time may be transmitted to the message receiving node. For example, the message receiving node may request the reporting of a data collection result according to the expected reporting time, or the message transmitting node and/or UE may transmit the data collection result to the message receiving node at the expected reporting time after the message transmitting node and/or UE inform the expected reporting time. The reporting time may be a reporting time of all information, or a reporting time of other information except the information that can be reported at present. The "information" here may be referred to by "data collection result".

● Identification of ongoing data collection: indicating that data collection is currently ongoing. In some implementations, for example, the message receiving node may request the reporting of data results from the message transmitting node and/or UE according to the information later. In some other implementations, for example, the message transmitting node and/or UE will transmit the data collection result to the message receiving node after the ongoing data collection is completed.

● End time of ongoing data collection: indicating the end time of current ongoing data collection. In some implementations, for example, the message receiving node may request the reporting of data collection results from the message transmitting node and/or UE after the end time according to this information. In some other implementations, for example, the message transmitting node and/or the UE will transmit data collection results to the message receiving node at and/or after the end time.

● Identification about that only partial information may be reported: indicating that only partial information may be reported at present. In some implementations, for example, the message receiving node may request the reporting of part of the information according to the information, and/or request the reporting of the other part of the information later. In some other implementations, for example, the message receiving node may request reporting of all the information at a later time. The "information" here may be referred to by "data collection result".

● Data collection result available: indicating that there is a data collection result stored. In some implementations, for example, the message receiving node may request the message transmitting node to report the data collection result according to the information.

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 apparent 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. 3 shows a schematic diagram of an aspect of a method for supporting continuous data collection according to embodiments of the present disclosure. Specifically, FIG. 3 shows a process of exchanging continuous data collection information (herein, it may also be called information associated with continuous data collection) between two nodes, so that the second node may collect data, and/or configure subsequent data collection, and/or analyze collected data collection results based on the continuous data collection information.

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 301A: the first node transmits continuous data collection information to the second node. The continuous data collection information may be the aforementioned first message.

Step 302A: the second node may collect data, and/or configure subsequent data collection, and/or analyze collected data collection results based on the continuous data collection information.

For example, the second node may perform subsequent data collection based on the information in the continuous data collection information. In some implementations, for example, the second node may report part and/or all of the data collection information when reporting the continuous data collection results, so that the receiving node of the data collection results can continue to configure subsequent data collection to achieve the effect of continuous data collection.

For example, the second node may configure subsequent data collection based on the continuous data collection information. In some implementations, for example, in a handover process, in step 301A, a source node transmits continuous data collection information to a target node; and in step 302A, the target node may configure subsequent data collection for the UE based on the continuous data collection information, so as to achieve the effect of continuous data collection. In still other implementations, in a secondary node addition process, in step 301A, a master node transmits continuous data collection information to a target secondary node; and in step 302A, the secondary node configures subsequent data collection for the UE to achieve the effect of continuous data collection. In still other implementations, for example, in step 301A, a secondary node transmits continuous data collection information to a master node; and in step 302A, the master node configures subsequent data collection for the UE, or the master node transmits the continuous data collection information to another node, and the other node configures subsequent data collection for the UE. For example, the other node may be a target secondary node.

For example, the second node may analyze the continuous data collection results based on the continuous data collection information. In some implementations, for example, the second node may associate multiple (continuous) data collection results of the same UE based on the continuous data collection information to obtain continuous data collection results.

FIG. 4A shows a schematic diagram of an aspect of a method for supporting continuous data collection according to embodiments of the present disclosure. Specifically, FIG. 4A shows a process of exchanging continuous data collection results between two nodes, so that the fourth node may perform analysis based on the continuous data collection results.

In an implementation, for example, the third 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 fourth node may be a UE. In an implementation, for example, the third node may be a UE, and the fourth 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 third 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 fourth 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 third node may be an AMF or an SMF or an MME, and the fourth 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 third 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 fourth node may be an AMF or an SMF or an MME. Alternatively, for example, the third node is a master node and the fourth node is a secondary node; for example, the third node is a secondary node and the fourth node is a master node; for example, the third node is a source node and the fourth node is a target node; for example, the third node is a target node and the fourth node is a source node.

Step 401A: the third node transmits a continuous data collection result to the fourth node. The continuous data collection result may be the aforementioned second message.

Step 402A: the fourth node may perform data analysis, and/or combine the continuous data collection results to obtain continuous data, and/or configure subsequent data collection based on the continuous data collection results, to achieve continuous data collection.

For example, the fourth node may perform data analysis based on the information in the continuous data collection results. In some implementations, for example, the fourth node may associate a plurality of collected data collection results to obtain a set of continuous collection results based on the information in the continuous data collection results. For example, multiple (continuous) data results of the same UE may be associated to obtain continuous data of the UE. For example, the continuous data may be used to support the training and/or performance monitoring and/or inference of artificial intelligence (AI)/ machine learning (ML).

For example, the fourth node may configure subsequent data collection based on the information in the continuous data collection results. In some implementations, for example, the fourth node may obtain information about that continuous data collection needs to be configured and/or corresponding configuration information of the continuous data collection based on the information in the continuous data collection results, and the fourth node configures subsequent data collection.

For example, the fourth node may obtain information about that data collection needs to be continued based on the information in the continuous data collection results, and configure subsequent data collection. In some implementations, for example, in a handover process, the source node transmits the continuous data collection results to the target node in step 401A; and in step 402A, the target node may configure subsequent data collection for the UE based on the continuous data collection results to achieve the effect of continuous data collection, and/or combine the subsequent data collection results with the received continuous collected data to obtain continuous data, so as to achieve the effect of continuous data collection. In still other implementations, in a secondary node addition process, in step 401A, the master node transmits continuous data collection information to the target secondary node; and in step 402A, the secondary node configures subsequent data collection for the UE to achieve the effect of continuous data collection, and/or combines the data results collected subsequently with the received continuous collected data to obtain continuous data, so as to achieve the effect of continuous data collection. In still other implementations, for example, in step 401A, the secondary node transmits continuous data collection information to the master node; and in step 402A, the master node configures subsequent data collection for the UE, or the master node transmits the continuous data collection information to another node, and the other node configures subsequent data collection for the UE. For example, the other node may be a target secondary node. And/or, the master node and/or other nodes combine the data results collected subsequently with the received continuous collected data to obtain continuous data, so as to achieve the effect of continuous collection.

FIG. 4B shows a schematic diagram of an aspect of a method for supporting continuous data collection according to embodiments of the present disclosure. Specifically, FIG. 4B shows a process of exchanging continuous data collection results between two nodes, so that the fourth node may perform analysis based on the continuous data collection results.

Step 401B: the fourth node transmits continuous data collection information to the third node. The continuous data collection information may be the aforementioned first message.

Step 402B: the third node transmits a continuous data collection result to the fourth node. The continuous data collection result may be the aforementioned second message. In an implementation, for example, the third node collects data according to the continuous data collection information received in step 401B to obtain a continuous data collection result, and transmits it to the fourth node through step 402B.

Step 403B: the fourth node may perform data analysis, and/or combine the continuous data collection results to obtain continuous data, and/or configure subsequent data collection based on the continuous data collection results, to achieve continuous data collection.

For example, the fourth node may perform data analysis based on the information in the continuous data collection results. In some implementations, for example, the fourth node may associate a plurality of collected data collection results to obtain a set of continuous collection results based on the information in the continuous data collection results. For example, multiple (continuous) data results of the same UE may be associated to obtain continuous data of the UE. For example, the continuous data may be used to support the training and/or performance monitoring and/or inference of AI/ML.

FIG. 4C shows a schematic diagram of an aspect of a method for supporting continuous data collection according to embodiments of the present disclosure. Specifically, FIG. 4C shows a process in which two nodes configure the UE to perform continuous data collection to obtain continuous data.

Step 400C: gNB1 and/or gNB2 are configured with continuous data collection information and/or MDT configuration. The continuous data collection information may be the information in the aforementioned first message. In some implementations, for example, OAM configures continuous data collection information for gNB1 and/or gNB2.

Step 401C: gNB1 transmits the continuous data collection information and/or MDT configuration to the corresponding UE. The continuous data collection information may be the aforementioned first message.

Step 402C: the UE collects data and transmits the corresponding continuous data collection results to gNB1. The continuous data collection result may be the aforementioned second message.

Step 403C: gNB1 transmits the continuous data collection information and/or MDT configuration to the corresponding UE. The continuous data collection information may be the aforementioned first message. In some implementations, for example, the continuous data collection information may be information for data collection for the UE in an RRC inactive state and/or an RRC idle state.

Step 404C: the UE enters an RRC inactive state or an RRC idle state, and the UE performs data collection.

Step 405C: the UE returns to an RRC connected state. The UE transmits a message containing information about that the continuous data collection results are available to the connected gNB (in this example, the connected gNB is gNB2). The message may include one or more of the following: continuous data collection results are available, data collection results are available, partial data collection results are available, partial continuous data collection results are available, etc. In an implementation, for example, gNB2 may request the UE to report the continuous data collection results after receiving the message.

Step 406C: gNB2 transmits a message containing a continuous data collection result request to the UE to request the UE to report the continuous data collection result. The message may include one or more of the following: a request for continuous data collection results, a request for data collection results, a request for partial data collection results, a request for partial continuous data collection results, a request for currently available (continuous) data collection results, etc.

Step 407C: UE transmits a continuous data collection result to gNB2. The continuous data collection result may be the aforementioned second message. The continuous data collection result may be all the continuous data collection results, part of the continuous data collection results, or the currently available continuous data collection results.

Step 408C: gNB2 transmits continuous data collection information and/or MDT configuration to the UE. The continuous data collection information may be the aforementioned first message. In some implementations, for example, gNB2 continues to configure continuous data collection to the UE according to the information in the continuous data collection results, and transmits continuous data collection information to the UE.

Step 409C: the UE collects data and transmits the corresponding continuous data collection results to gNB2. The continuous data collection result may be the aforementioned second message.

Herein, step 403C may be merged with step 401C.

FIG. 4D shows a schematic diagram of an aspect of a method for supporting continuous data collection according to embodiments of the present disclosure. Specifically, FIG. 4D shows a process in which two nodes configure the UE to perform continuous data collection to obtain continuous data.

Step 400D: gNB1 and/or gNB2 are configured with continuous data collection information. The continuous data collection information may be the information in the aforementioned first message. In some implementations, for example, OAM configures continuous data collection information for gNB1 and/or gNB2.

Step 401D: gNB1 transmits the continuous data collection information and/or MDT configuration to the corresponding UE. The continuous data collection information may be the aforementioned first message.

Step 402D: the UE collects data and transmits the corresponding continuous data collection results to gNB1. The continuous data collection result may be the aforementioned second message.

Step 403D: gNB1 transmits continuous data collection information and/or MDT configuration to gNB2. The continuous data collection information may be the aforementioned first message. In some implementations, for example, in a handover process, a source node (gNB1 in this example) transmits continuous data collection information to a target node (gNB2 in this example); the target node (gNB2 in this example) may configure subsequent data collection for the UE based on the continuous data collection information, so as to achieve the effect of continuous data collection In still other implementations, in a secondary node addition process, a master node (gNB1 in this example) transmits continuous data collection information to a target secondary node (gNB2 in this example); the secondary node (gNB2 in this example) configures subsequent data collection for the UE to achieve the effect of continuous data collection. In still other implementations, for example, the secondary node (gNB1 in this example) transmits continuous data collection information to the master node (gNB2 in this example); the master node (gNB2 in this example) configures subsequent data collection for the UE, or the master node (gNB2 in this example) transmits the continuous data collection information to another node, and the other node configures subsequent data collection for the UE. For example, the other node may be a target secondary node.

Step 404D: gNB2 transmits continuous data collection information and/or MDT configuration to the UE. The continuous data collection information may be the aforementioned first message. In some implementations, for example, gNB2 continues to configure continuous data collection to the UE according to the continuous data collection information, and transmits the continuous data collection information to the UE.

Step 405D: the UE collects data and transmits the corresponding continuous data collection results to gNB2. The continuous data collection result may be the aforementioned second message.

FIG. 4E shows a schematic diagram of an aspect of a method for supporting continuous data collection according to embodiments of the present disclosure. Specifically, FIG. 4E shows a process in which two secondary nodes configure UE for continuous data collection to obtain continuous data.

Step 400E: the secondary node 1 and/or the secondary node 2 are configured with continuous data collection information. The continuous data collection information may be the information in the aforementioned first message. In some implementations, for example, OAM configures continuous data collection information for secondary node 1 and/or secondary node 2.

Step 401E: the secondary node 1 transmits the continuous data collection information and/or MDT configuration to the corresponding UE. The continuous data collection information may be the aforementioned first message.

Step 402E: the UE collects data and transmits the corresponding continuous data collection results to the secondary node 1. The continuous data collection result may be the aforementioned second message.

Step 403E: the secondary node 1 transmits continuous data collection information and/or MDT configuration to the master node. The continuous data collection information may be the aforementioned first message. In some implementations, for example, in a secondary node modification process, the source secondary node (in this example, secondary node 1) transmits continuous data collection information to the master node.

Step 404E: the master node transmits continuous data collection information and/or MDT configuration to the secondary node 2. The continuous data collection information may be the aforementioned first message. In some implementations, for example, in a secondary node modification process, the master node transmits continuous data collection information to a target secondary node (secondary node 2 in this example).

Step 405E: the secondary node 2 transmits continuous data collection information and/or MDT configuration to the UE. The continuous data collection information may be the aforementioned first message. In some implementations, for example, the secondary node 2 continues to configure the continuous data collection to the UE according to the continuous data collection information received in step 404E and/or step 400E, and transmits the continuous data collection information to the UE. In some other implementations, for example, in a secondary node modification process, after the UE accesses the secondary node 2, the secondary node 2 can directly transmit the continuous data collection information to the UE, for example, through an RRCReconfiguration message. In yet another implementation, for example, in a secondary node modification process, the secondary node 2 may transmit the continuous data collection information to the UE through the forwarding by the master node, for example, through an RRCReconfiguration message.

Step 406E: the UE collects data and transmits the corresponding continuous data collection results to the secondary node 2. The continuous data collection result may be the aforementioned second message.

FIG. 4F shows a schematic diagram of an aspect of a method for supporting continuous data collection according to embodiments of the present disclosure. Specifically, FIG. 4F shows a process in which two nodes configure UE for continuous MDT data collection in an MDT process in order to obtain continuous MDT data.

Step 400F: gNB1 and/or gNB2 are configured with continuous data collection information and/or MDT configuration. The continuous data collection information may be the information in the aforementioned first message. In some implementations, for example, OAM configures continuous data collection information for gNB1 and/or gNB2. For example, gNB1 receives Immediate MDT configuration (for example, TR=X) and/or continuous data collection information. For example, gNB1 receives a Logged MDT configuration (for example, TR=Y) and/or continuous data collection information (for example, associated with TR=X). For example, gNB2 receives Immediate MDT configuration (for example, TR=V) and/or continuous data collection information (for example, associated with gNB1, TR=Y). For example, gNB2 receives Logged MDT configuration (for example, TR=W) and/or continuous data collection information.

Step 401F: gNB1 transmits the Immediate MDT configuration and/or continuous data collection information to the UE. The continuous data collection information may be the aforementioned first message. The message may be transmitted through an RRCReconfiguration message.

Step 402F: the UE collects data and transmits a corresponding Immediate MDT report and/or continuous data collection results to gNB1. The continuous data collection result may be the aforementioned second message. The message may be transmitted by a Measurement report message.

Step 403F: gNB1 performs corresponding processing when processing the Immediate MDT report and/or the continuous data collection results, for example, the TR of the report and/or the results is X and the TRSR is A.

Step 404F: gNB1 transmits the Logged MDT configuration and/or continuous data collection information to the UE. The continuous data collection information may be the aforementioned first message. The message may be transmitted through an RRCReconfiguration message. For example, TRSR corresponding to the Logged MDT in this message may be set to be the same as the TRSR of the aforementioned Immediate MDT report (for example, TRSR=A). This can make the TRSRs of the same UE the same. The node performing analysis may associate multiple reports and/or results of the same UE according to the TRSRs.

Step 405F: the UE enters an RRC inactive state or an RRC idle state, and the UE performs data collection.

Step 406F: UE transmits an RRCSetupRequest message and/or an RRCResumeRequest message and/or an RRCResumeRequest1 message and/or an RRCReestablishmentRequest message to gNB2.

Step 407F: gNB2 transmits an RRCSetup message and/or an RRCResume message and/or an RRCReestablishment message and/or an RRCReconfiguration message to the UE.

Step 408F: the UE transmits a message containing information about that a logged measurement report is available (logMeasAvailable) and/or reporting information of continuous data collection to gNB2. The reporting information of continuous data collection may be the aforementioned third message. The message may be transmitted through an RRCSetupComplete message and/or an RRCResumeComplete message and/or an RRCReestablishmentComplete message and/or an RRCReconfigurationComplete message.

Step 409F: gNB2 transmits a message including a continuous data collection result request and/or a logged measurement report request (logMeasReportReq) to the UE to request the UE to report the continuous data collection result. The continuous data collection result request may include one or more of the following: a request for continuous data collection results, a request for data collection results, a request for partial data collection results, a request for partial continuous data collection results, a request for currently available (continuous) data collection results, etc. The message may be transmitted by a UEInformationRequest message. In some implementations, for example, the message may be transmitted according to the reporting information of continuous data collection received in step 408F.

Step 410F: the UE transmits a message containing a logged measurement report and/or a continuous data collection result to gNB2. The continuous data collection result may be the aforementioned second message. In some implementations, the TRSR in the logged measurement report and/or the continuous data collection result needs to be set according to the TRSR received in step 404F, for example, TRSR = A. The message may be transmitted by a UEInformationResponse message.

Step 411F: gNB2 transmits a message containing Immediate MDT configuration and/or continuous data collection information to the UE. The continuous data collection information may be the aforementioned first message. The message may be transmitted through an RRC configuration message. In some implementations, for example, gNB2 continues to configure continuous data collection to the UE according to the information received in step 410F and/or the information in step 400F, and transmits continuous data collection information to the UE. For example, the reports and/or results received by gNB2 through step 410F indicate TR=Y and TRSR=A, and/or indicate that the configuration node is gNB1 (or the configuration cell may be a cell managed by gNB1), and gNB2 associates the Immediate MDT configuration with gNB1 (TR=V) according to the information obtained through step 400F. Therefore, gNB2 needs to continue to configure an Immediate MDT with TR=V for the UE.

Step 412F: the UE collects data and transmits the corresponding Immediate MDT report and/or continuous data collection results to gNB2. The continuous data collection result may be the aforementioned second message. The message may be transmitted by a Measurement report message.

Step 403F: gNB2 performs corresponding processing when processing the Immediate MDT report and/or the continuous data collection results. For example, the report belongs to the same continuous data collection as the reports and/or results received in step 404F. For example, the relevant parameters of the reports and/or results may be set as the parameters related to step 404F, for example, TR is V and TRSR is A.

Step 401F and step 404F may be merged. Step 404F may also occur before step 401F and/or step 402F and/or step 403F. Step 406F may be omitted.

The node performing analysis may associate one or more of the following reports through TRSR=A to obtain a continuous data:

● Reports and/or results obtained in step 402F and step 403F

● Reports and/or results obtained in step 410F

● Reports and/or results obtained in step 412F and step 413F

FIG. 4G shows a schematic diagram of an aspect of a method for supporting continuous data collection according to embodiments of the present disclosure. Specifically, FIG. 4G shows a process in which two nodes configure UE for continuous MDT data collection in an MDT process in order to obtain continuous MDT data.

Step 400G: gNB1 and/or gNB2 are configured with continuous data collection information and/or MDT configuration. The continuous data collection information may be the information in the aforementioned first message. In some implementations, for example, OAM configures continuous data collection information for gNB1 and/or gNB2. For example, gNB1 receives Immediate MDT configuration (for example, TR=X) and/or continuous data collection information. For example, gNB1 receives a Logged MDT configuration (for example, TR=Y) and/or continuous data collection information (for example, associated with TR=X). For example, gNB2 receives Immediate MDT configuration (for example, TR=V) and/or continuous data collection information (for example, associated with gNB1, TR=Y). For example, gNB2 receives Logged MDT configuration (for example, TR=W) and/or continuous data collection information.

Step 401G: gNB1 transmits the Immediate MDT configuration and/or continuous data collection information to the UE. The continuous data collection information may be the aforementioned first message. The message may be transmitted through an RRCReconfiguration message.

Step 402G: the UE collects data and transmits a corresponding Immediate MDT report and/or continuous data collection results to gNB1. The continuous data collection result may be the aforementioned second message. The message may be transmitted by a Measurement report message.

Step 403G: gNB1 processes the Immediate MDT report and/or the continuous data collection results.

Step 404G: gNB1 transmits the Logged MDT configuration and/or continuous data collection information to the UE. The continuous data collection information may be the aforementioned first message. The message may be transmitted through an RRCReconfiguration message.

Step 405G: the UE enters an RRC inactive state or an RRC idle state, and the UE performs data collection.

Step 406G: UE transmits an RRCSetupRequest message and/or an RRCResumeRequest message and/or an RRCResumeRequest1 message and/or an RRCReestablishmentRequest message to gNB2.

Step 407G: gNB2 transmits an RRCSetup message and/or an RRCResume message and/or an RRCReestablishment message and/or an RRCReconfiguration message to the UE.

Step 408G: the UE transmits a message containing information about that a logged measurement report is available (logMeasAvailable) and/or reporting information of continuous data collection to gNB2. The message may be transmitted through an RRCSetupComplete message and/or an RRCResumeComplete message and/or an RRCReestablishmentComplete message and/or an RRCReconfigurationComplete message.

Step 409G: gNB2 transmits a message including a continuous data collection result request and/or a logged measurement report request (logMeasReportReq) to the UE to request the UE to report the continuous data collection result. The continuous data collection result request may include one or more of the following: a request for continuous data collection results, a request for data collection results, a request for partial data collection results, a request for partial continuous data collection results, a request for currently available (continuous) data collection results, etc. The message may be transmitted by a UEInformationRequest message. In some implementations, for example, the message may be transmitted according to the reporting information of continuous data collection received in step 408G.

Step 410G: the UE transmits a message containing a logged measurement report and/or a continuous data collection result to gNB2. The continuous data collection result may be the aforementioned second message. The message may be transmitted by a UEInformationResponse message.

Step 411G: gNB2 transmits a message containing Immediate MDT configuration and/or continuous data collection information to the UE. The continuous data collection information may be the aforementioned first message. The message may be transmitted through an RRC configuration message. In some implementations, for example, gNB2 continues to configure continuous data collection to the UE according to the information received in step 410G and/or the information in step 400G, and transmits continuous data collection information to the UE.

Step 412G: the UE collects data and transmits the corresponding Immediate MDT report and/or continuous data collection results to gNB2. The continuous data collection result may be the aforementioned second message. The message may be transmitted by a Measurement report message.

Step 413G: gNB2 processes the Immediate MDT report and/or the continuous data collection results.

Step 401G and step 404G may be merged. Step 404G may also occur before step 401G and/or step 402G and/or step 403G. Step 406G may be omitted.

The node performing analysis may associate one or more of the following reports through the continuous data collection results to obtain a continuous data:

● Reports and/or results obtained in step 402G and step 403G

● Reports and/or results obtained in step 410G

● Reports and/or results obtained in step 412G and step 413G

FIG. 4H shows a schematic diagram of an aspect of a method for supporting continuous data collection according to embodiments of the present disclosure. Specifically, FIG. 4H shows a process in which three nodes exchanging continuous data collection information, so as to configure the UE to perform continuous data collection, to obtain continuous data.

In some implementations, for example, Node 1 may be a gNB CU, Node 2 may be a gNB DU, and Node 3 may be a gNB DU. In some other implementations, for example, Node 1 may be a gNB CU CP, Node 2 may be a gNB CU UP, and Node 3 may be a gNB CU UP. In yet other implementations, for example, Node 1 may be an AMF and/or an SMF, Node 2 may be a gNB and/or a gNB CU and/or a gNB CU CP, and Node 3 may be a gNB and/or a gNB CU and/or a gNB CU CP.

Step 400H: Node 2 and/or Node 3 are configured with continuous data collection information. The continuous data collection information may be the information in the aforementioned first message. In some implementations, for example, OAM configures continuous data collection information for Node 2 and/or Node 3.

Step 401H: Node 2 transmits continuous data collection information and/or MDT configuration to the corresponding UE. The continuous data collection information may be the aforementioned first message.

Step 402H: the UE collects data and transmits the corresponding continuous data collection results to the Node 2. The continuous data collection result may be the aforementioned second message.

Step 403H: Node 2 transmits continuous data collection information and/or MDT configuration to Node 1. The continuous data collection information may be the aforementioned first message. In some implementations, for example, in a user context release process and/or a bearer context release process, Node 2 transmits continuous data collection information to Node 1.

Step 404H: Node 1 transmits continuous data collection information and/or MDT configuration to Node 3. The continuous data collection information may be the aforementioned first message. In some implementations, for example, in a user context setup process and/or a user context modification process and/or a bearer context setup process and/or a bearer context modification process, Node 1 transmits continuous data collection information to Node 3.

Step 405H: Node 3 transmits continuous data collection information and/or MDT configuration to the UE. The continuous data collection information may be the aforementioned first message. In some implementations, for example, Node 3 continues to configure continuous data collection to the UE according to the continuous data collection information received in step 404H and/or in step 400H, and transmits the continuous data collection information to the UE.

Step 406H: the UE collects data and transmits the corresponding continuous data collection result to Node 3. The continuous data collection result may be the aforementioned second message.

FIG. 5A shows a schematic diagram of an aspect of a method for supporting continuous data collection according to embodiments of the present disclosure. Specifically, FIG. 5A shows a process of exchanging reporting information of continuous data collection between two nodes, so that the sixth node may obtain the continuous data collection results.

In an implementation, for example, the fifth node may be a UE, and the sixth 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 fifth 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 sixth 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 fifth node may be an AMF or an SMF or an MME, and the sixth 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 fifth 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 sixth node may be an AMF or an SMF or an MME. Alternatively, for example, the fifth node is a master node and the sixth node is a secondary node; for example, the fifth node is a secondary node and the sixth node is a master node; for example, the fifth node is a source node and the sixth node is a target node; for example, the fifth node is a target node and the sixth node is a source node.

Step 501A: the fifth node transmits reporting information of continuous data collection to the sixth node. The reporting information of continuous data collection may be the aforementioned third message.

Step 502A: the sixth node may wait and/or request the continuous data collection results based on the reporting information of continuous data collection. In some implementations, for example, the sixth node may transmit a data collection result request to the fifth node according to the information in the reporting information of continuous data collection.

Step 503A: the sixth node transmits a message containing a continuous data collection result request to the fifth node to request the UE to report the continuous data collection results. The continuous data collection result request may include one or more of the following: a request for continuous data collection results, a request for data collection results, a request for partial data collection results, a request for partial continuous data collection results, a request for currently available (continuous) data collection results, etc. The message may be transmitted by a UEInformationRequest message. In some implementations, for example, the message may be transmitted according to the reporting information of continuous data collection received in step 501A.

Step 504A: the fifth node transmits a message containing the continuous data collection result to the sixth node. The continuous data collection result may be the aforementioned second message. In some implementations, for example, the message may be transmitted according to the reporting information of continuous data collection in step 501A.

Herein, step 503A is an optional step.

FIG. 5B shows a schematic diagram of an aspect of a method for supporting continuous data collection according to embodiments of the present disclosure. Specifically, FIG. 5B shows a process of exchanging reporting information of continuous data collection between two nodes, so that the sixth node may obtain the continuous data collection results.

Step 501B: the fifth node completes data collection.

Step 502B: the fifth node transmits reporting information of continuous data collection to the sixth node. The reporting information of continuous data collection may be the aforementioned third message.

Step 503B: the sixth node transmits a message containing a continuous data collection result request to the fifth node to request the UE to report the continuous data collection result. The continuous data collection result request may include one or more of the following: a request for continuous data collection results, a request for data collection results, a request for partial data collection results, a request for partial continuous data collection results, a request for currently available (continuous) data collection results, etc. The message may be transmitted by a UEInformationRequest message. In some implementations, for example, the message may be transmitted according to the reporting information of continuous data collection received in step 502B.

Step 504B: the fifth node transmits a message containing the continuous data collection results to the sixth node. The continuous data collection result may be the aforementioned second message. In some implementations, for example, the message may be transmitted according to the reporting information of continuous data collection in step 502B.

Herein, step 503B is an optional step.

FIG. 5C shows a schematic diagram of an aspect of a method for supporting continuous data collection according to embodiments of the present disclosure. Specifically, FIG. 5C shows a process of exchanging reporting information of continuous data collection between two nodes, so that the sixth node may obtain the continuous data collection results.

Step 501C: the fifth node is performing continuous data collection.

Step 502C: the fifth node transmits reporting information of continuous data collection to the sixth node. The reporting information of continuous data collection may be the aforementioned third message.

Step 503C: the sixth node transmits a message containing a continuous data collection result request to the fifth node to request the UE to report the continuous data collection result. The continuous data collection result request may include one or more of the following: a request for continuous data collection results, a request for data collection results, a request for partial data collection results, a request for partial continuous data collection results, a request for currently available (continuous) data collection results, etc. The message may be transmitted by a UEInformationRequest message. In some implementations, for example, the message may be transmitted according to the reporting information of continuous data collection received in step 502C.

Step 504C: the fifth node transmits a message containing the continuous data collection result to the sixth node. The continuous data collection result may be the aforementioned second message. In some implementations, for example, the message may be transmitted according to the reporting information of continuous data collection in step 502C. In some other implementations, for example, the fifth node may report the currently available data. In still other implementations, for example, the fifth node reports the currently collected and/or available data after receiving the continuous data collection result request message in step 503C.

Step 505C: the fifth node completes data collection.

Step 505C: the fifth node transmits reporting information of continuous data collection to the sixth node. The reporting information of continuous data collection may be the aforementioned third message.

Step 506C: the sixth node transmits a message containing a continuous data collection result request to the fifth node to request the UE to report the continuous data collection result. The continuous data collection result request may include one or more of the following: a request for continuous data collection results, a request for data collection results, a request for partial data collection results, a request for partial continuous data collection results, a request for currently available (continuous) data collection results, etc. The message may be transmitted by a UEInformationRequest message. In some implementations, for example, the message may be transmitted according to the reporting information of continuous data collection received in step 502C and/or step 505C.

Step 507C: the fifth node transmits a message containing the continuous data collection result to the sixth node. The continuous data collection result may be the aforementioned second message. In some implementations, for example, the message may be transmitted according to the reporting information of continuous data collection in step 502C and/or step 505C. In some other implementations, for example, the fifth node may report the currently available data. In still other implementations, for example, the fifth node reports the currently collected and/or available data after receiving the continuous data collection result request message in step 506C.

For example, the results obtained in step 504C and step 507C can be combined to form continuous data.

Herein, step 503C is an optional step. Herein, step 506C is an optional step.

Herein, step 505C is an optional step.

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. 6 shows a flowchart of a method 600 performed by a user equipment (UE) in a wireless communication system according to embodiments of the present disclosure.

A method 600 performed by a user equipment (UE) in a wireless communication system according to embodiments of the present disclosure may include: in step S601, receiving a second Minimization of Drive Tests (MDT) configuration and second information from a first node, wherein the second information includes information related to continuous data collection associated with the second MDT configuration; performing second MDT data collection based on the second MDT configuration in a radio resource control (RRC) inactive state or an RRC idle state; and in step S602, connecting to a second node; in step S603, transmitting a second MDT report associated with the second MDT configuration and a second result associated with the continuous data collection to the second node; and in step S604, receiving a third MDT configuration and third information from the second node, wherein the third information includes information indicating that the third MDT configuration is associated with the second MDT configuration and/or the first node.

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

A method 700 performed by a first node in a wireless communication system according to embodiments of the present disclosure may include: in step S701, transmitting a second Minimization of Drive Tests (MDT) configuration and second information to a user equipment (UE), wherein the second information includes information related to continuous data collection associated with the second MDT configuration; and in step S702, transmitting a first MDT configuration and first information to the UE, wherein the first information includes information related to the continuous data collection; and in step S703, receiving a first MDT report associated with the first MDT configuration and a first result associated with the continuous data collection from the UE.

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

A method 800 performed by a second node in a wireless communication system according to embodiments of the present disclosure may include: in step S801, receiving, from a user equipment (UE), a second MDT report associated with a second Minimization of Drive Tests (MDT) configuration transmitted to the UE by a first node and a second result associated with continuous data collection; and in step S802, transmitting a third MDT configuration and third information to the UE, wherein the third information includes information indicating that the third MDT configuration is associated with the second MDT configuration and/or the first node.

It should be understood that methods 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 (or a node device, for example, a first node or a second node as described above) 900 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 a method performed by a node (e.g., a first node and/or a second 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 a method 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.

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 terminal in a wireless communication system, comprising:

receiving a second Minimization of Drive Tests (MDT) configuration and second information from a first node, wherein the second information includes information related to continuous data collection associated with the second MDT configuration; performing second MDT data collection based on the second MDT configuration in a radio resource control (RRC) inactive state or an RRC idle state;

connecting to a second node;

transmitting a second MDT report associated with the second MDT configuration and a second result associated with the continuous data collection to the second node; and

receiving a third MDT configuration and third information from the second node, wherein the third information includes information indicating that the third MDT configuration is associated with the second MDT configuration and/or the first node.
The method according to claim 1, further comprising:

transmitting fourth information about that the second MDT report associated with the second MDT configuration is available and reporting information related to the continuous data collection to the second node, and

receiving a request for the second MDT report associated with the second MDT configuration and the second result associated with the continuous data collection from the second node,

wherein the request is transmitted from the second node based on the reporting information.
The method according to claim 1, further comprising:

receiving a first MDT configuration and first information from the first node, wherein the first information includes information related to the continuous data collection,

wherein the second information further includes information indicating that the second MDT configuration is associated with the first MDT configuration.
The method according to claim 3, further comprising:

transmitting a first MDT report associated with the first MDT configuration and a first result associated with the continuous data collection to the first node.
The method according to claim 4, further comprising:

transmitting a third MDT report associated with the third MDT configuration and a third result associated with the continuous data collection to the second node.
The method according to claim 5, wherein each of the first result, the second result and the third result includes a first identification of the terminal associated with the continuous data collection and/or a second identification of an initial configuration node of the continuous data collection, and

wherein the first MDT report, the second MDT report and the third MDT report are associated by the first identification and/or the second identification.
The method according to claim 1, wherein the second result includes one or more of an accumulated time and a data collection configuration associated with the continuous data collection, and

wherein the third MDT configuration is determined based on one or more of the accumulated time and the data collection configuration.
A method performed by a first node in a wireless communication system, comprising:

transmitting a second Minimization of Drive Tests (MDT) configuration and second information to a terminal, wherein the second information includes information related to continuous data collection associated with the second MDT configuration;

transmitting a first MDT configuration and first information to the terminal, wherein the first information includes information related to the continuous data collection; and

receiving a first MDT report associated with the first MDT configuration and a first result associated with the continuous data collection from the terminal.
The method according to claim 8, further comprising:

receiving one or more of the second MDT configuration, the second information, the first MDT configuration and the first information from a core network node.
A method performed by a second node in a wireless communication system, comprising:

receiving, from a terminal, a second MDT report associated with a second Minimization of Drive Tests (MDT) configuration transmitted to the terminal by a first node and a second result associated with continuous data collection; and

transmitting a third MDT configuration and third information to the terminal, wherein the third information includes information indicating that the third MDT configuration is associated with the second MDT configuration and/or the first node.
The method according to claim 10, further comprising:

receiving fourth information about that the second MDT report associated with the second MDT configuration is available and reporting information related to the continuous data collection from the terminal, and

transmitting a request for the second MDT report associated with the second MDT configuration and the second result associated with the continuous data collection to the terminal,

wherein the request is transmitted from the second node based on the reporting information.
The method according to claim 10, further comprising:

receiving a third MDT report associated with the third MDT configuration and a third result associated with continuous data collection from the terminal.
The method according to claim 10, further comprising:

receiving one or more of the third MDT configuration and the third information from a core network node.
The method according to claim 12, wherein each of the second result and the third result includes a first identification of the terminal associated with the continuous data collection and/or a second identification of an initial configuration node of the continuous data collection, and

wherein the second MDT report and the third MDT report are associated by the first identification and/or the second identification.
The method according to claim 10, wherein the second result includes one or more of an accumulated time and a data collection configuration associated with the continuous data collection, and

wherein the third MDT configuration is determined based on one or more of the accumulated time and the data collection configuration.