Node in wireless communication system, user equipment and method performed by same

Abstract

The invention provides a node in a wireless communication system, user equipment and a method performed by the same. 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, the second information including continuous data collection related information associated with the second MDT configuration in a Radio Resource Control (RRC) inactive state or an RRC idle state, performing second MDT data collection based on the second MDT configuration; the first node is connected to a second node; sending 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, the third information including information indicating that the third MDT configuration is associated with the second MDT configuration and / or the first node.

Description

Technical Field

[0001] The present disclosure relates to the technical field of wireless communications, and more particularly, to a node, a user equipment, and a method executed by the same in a wireless communication system. Background Art

[0002] To meet the increased demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also referred to as "beyond 4G networks" or "post-LTE systems."

[0003] Wireless communication is one of the most successful innovations in modern history. The number of wireless communication service subscribers recently surpassed 5 billion and continues to grow rapidly. Demand for wireless data services is rapidly increasing due to the growing popularity of smartphones and other mobile data devices (e.g., tablets, laptops, netbooks, e-book readers, and machine-type devices) among consumers and businesses. Improving radio interface efficiency and coverage is crucial to meeting this rapid growth and supporting new applications and deployments. Summary of the Invention

[0004] An embodiment of the present disclosure provides a method performed by a user equipment (UE) in a wireless communication system, including: receiving a second minimization of drive tests (MDT) configuration and second information from a first node, the second information including 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; sending 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, the third information including information indicating that the third MDT configuration is associated with the second MDT configuration and / or the first node.

[0005] According to an embodiment of the present disclosure, the method further includes: sending, to the second node, fourth information regarding availability of a second MDT report associated with the second MDT configuration and reporting information related to the continuous data collection, and receiving, from the second node, a request for a second MDT report associated with the second MDT configuration and a second result associated with the continuous data collection, wherein the request is sent from the second node based on the reporting information.

[0006] According to an embodiment 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.

[0007] According to an embodiment of the present disclosure, the method further includes: sending a first MDT report associated with the first MDT configuration and a first result associated with the continuous data collection to the first node.

[0008] According to an embodiment of the present disclosure, the method further includes: sending a third MDT report associated with the third MDT configuration and a third result associated with the continuous data collection to the second node.

[0009] According to an embodiment of the present disclosure, each of the first result, the second result, and the third result includes a first identifier of the UE associated with the continuous data collection and / or a second identifier of an initial configuration node for the continuous data collection, wherein the first MDT report, the second MDT report, and the third MDT report are associated through the first identifier and / or the second identifier.

[0010] According to an embodiment 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, wherein the third MDT configuration is determined based on one or more of the accumulated time and the data collection configuration.

[0011] An embodiment of the present disclosure provides a method performed by a first node in a wireless communication system, comprising: sending a second minimization of drive tests (MDT) configuration and second information to a user equipment (UE), the second information including information related to continuous data collection associated with the second MDT configuration; sending a first MDT configuration and first information to the UE, the first information including 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.

[0012] According to an embodiment 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.

[0013] An embodiment of the present disclosure provides a method performed by a second node in a wireless communication system, comprising: receiving, from a user equipment (UE), a second MDT report associated with a second minimization of drive tests (MDT) configuration sent by a first node to the UE and a second result associated with continuous data collection; and sending a third MDT configuration and third information to the UE, the third information including information indicating that the third MDT configuration is associated with the second MDT configuration and / or the first node.

[0014] According to an embodiment of the present disclosure, the method further includes: receiving, from the UE, fourth information regarding availability of a second MDT report associated with the second MDT configuration and reporting information related to the continuous data collection, and sending, to the UE, a request for a second MDT report associated with the second MDT configuration and a second result associated with the continuous data collection, wherein the request is sent from the second node based on the reporting information.

[0015] According to an embodiment 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.

[0016] According to an embodiment 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.

[0017] According to an embodiment of the present disclosure, each of the second result and the third result includes a first identifier of the UE associated with the continuous data collection and / or a second identifier of an initial configuration node for the continuous data collection, wherein the second MDT report and the third MDT report are associated through the first identifier and / or the second identifier.

[0018] According to an embodiment 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, wherein the third MDT configuration is determined based on one or more of the accumulated time and the data collection configuration.

[0019] An embodiment of the present disclosure provides a first node device in a wireless communication system, including: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the first node in the wireless communication system according to an embodiment of the present disclosure.

[0020] An embodiment of the present disclosure provides a second node device in a wireless communication system, including: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the second node in the wireless communication system according to an embodiment of the present disclosure.

[0021] An embodiment of the present disclosure provides a user equipment UE in a wireless communication system, comprising: a transceiver configured to send and receive signals; and a processor coupled to the transceiver and configured to execute a method performed by the user equipment UE in the wireless communication system according to an embodiment of the present disclosure.

[0022] An embodiment of the present disclosure provides a computer-readable medium having computer-readable instructions stored thereon. When the instructions are executed by a processor, the instructions are used to implement a method performed by a first node and / or a second node and / or a user equipment in a wireless communication system according to an embodiment of the present disclosure.

[0023] The method provided by the present disclosure, which is performed by the first node and / or the second node and / or the user equipment in the wireless communication system, can effectively support the node 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. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0025] Figure 1 is an exemplary system architecture 100 of System Architecture Evolution (SAE);

[0026] Figure 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure;

[0027] Figure 3 A schematic diagram illustrating one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure;

[0028] Figures 4A-4H A schematic diagram illustrating one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure;

[0029] Figures 5A-5C A schematic diagram illustrating one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure;

[0030] Figure 6 A flowchart of a method performed by a user equipment UE in a wireless communication system according to an embodiment of the present disclosure is shown;

[0031] Figure 7 A flowchart of a method performed by a first node in a wireless communication system according to an embodiment of the present disclosure is shown;

[0032] Figure 8 A flowchart of a method performed by a second node in a wireless communication system according to an embodiment of the present disclosure is shown;

[0033] Figure 9 A schematic diagram of a node according to an embodiment of the present disclosure is shown; and

[0034] Figure 10 A schematic diagram of a user equipment according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0035] The following description, with reference to the accompanying drawings, is provided to facilitate a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. This description includes various specific details to facilitate understanding but should be considered as illustrative only. Therefore, one of ordinary skill in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. Furthermore, descriptions of well-known functions and structures may be omitted for the sake of clarity and conciseness.

[0036] The terms and expressions used in the following description and claims are not limited to their dictionary meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, 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 purposes only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0037] It will 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.

[0038] The terms "include" or "may include" refer to the presence of the corresponding disclosed functions, operations, or components that can be used in various embodiments of the present disclosure, rather than limiting the presence of one or more additional functions, operations, or features. In addition, the terms "include" or "have" can be interpreted as indicating certain characteristics, numbers, steps, operations, constituent elements, components, or combinations thereof, but should not be interpreted as excluding the possibility of the presence of one or more other characteristics, numbers, steps, operations, constituent elements, components, or combinations thereof.

[0039] The term "or" used in various embodiments of the present disclosure includes any of the listed terms and all combinations thereof. For example, "A or B" may include A, may include B, or may include both A and B.

[0040] Unless otherwise defined, all terms (including technical or scientific terms) used in this disclosure have the same meaning as understood by those skilled in the art described in this disclosure. Common terms as defined in dictionaries are interpreted as having a meaning consistent with the context in the relevant technical field and should not be interpreted in an idealized or overly formal manner unless explicitly defined in this disclosure.

[0041] The accompanying drawings discussed below and the various embodiments used to describe the principles of the present disclosure in this patent document are intended to be illustrative only and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0042] Figure 1 This is an exemplary system architecture 100 of System Architecture Evolution (SAE). User Equipment (UE) 101 is a terminal device used to receive data. Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 102 is a radio access network, which includes a macro base station (eNodeB / NodeB) that provides the UE with an access wireless network interface. The Mobility Management Entity (MME) 103 is responsible for managing the UE's mobility context, session context and security information. The Serving Gateway (SGW) 104 mainly provides user plane functions, and the MME 103 and SGW 104 may be in the same physical entity. The Packet Data Network Gateway (PGW) 105 is responsible for functions such as billing and lawful interception, and may also be in the same physical entity as the SGW 104. The Policy and Charging Rules Function (PCRF) 106 provides Quality of Service (QoS) policies and charging criteria. The General Packet Radio Service Support Node (SGSN) 108 is a network node device that provides routing for data transmission in the Universal Mobile Telecommunications System (UMTS). The Home Subscriber Server (HSS) 109 is the home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the serving node, user security information, and the packet data context of the user equipment.

[0043] Figure 2 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.

[0044] User equipment (UE) 201 is a terminal device used to receive data. The next-generation radio access network (NG-RAN) 202 is a radio access network that includes base stations (gNBs or eNBs connected to the 5G core network 5GC; eNBs connected to 5GC are also called ng-gNBs) that provide UEs with access to wireless network interfaces. The access control and mobility management function (AMF) 203 is responsible for managing the UE's mobility context and security information. The user plane function (UPF) 204 mainly provides user plane functions. The session management function (SMF) 205 is responsible for session management. The data network (DN) 206 includes services such as operator services, Internet access, and third-party services.

[0045] The nodes described 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 logical units, as well as the cells and / or beams managed by them.

[0046] In this disclosure, a node may refer to a node, or may refer to a cell and / or beam managed by the node.

[0047] In the present disclosure, a cell may refer to a cell, a node where a cell is located, or a beam corresponding to a cell, etc.

[0048] The information and / or fields described in the present disclosure may be average values, instantaneous values, maximum values, minimum values, etc. The present disclosure does not limit this.

[0049] The information and / or fields described in the present disclosure may be used to indicate one or more of the following situations: uplink, downlink, uplink and downlink, or uplink or downlink.

[0050] The information and / or fields described in the present disclosure may be measured values ​​and / or actual values, or may be predicted values.

[0051] The signal strength and / or signal quality and / or measurement report result and / or measurement result described in the present disclosure may be a received signal strength indicator (RSSI), a reference signal received power (RSRP), a reference signal received quality (RSRQ), a signal to interference plus noise ratio (SINR), etc.

[0052] In the present disclosure, a slice identifier may be identified by one or more single network slice selection assistance information (S-NSSAI).

[0053] In the present disclosure, a failure type and / or a problem type may also be a report type.

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

[0055] In the present disclosure, radio link failure includes two situations: radio link failure and handover failure.

[0056] In this disclosure, the TA value acquired in advance and the TA value in the LTM command may refer to each other.

[0057] The network self-optimization decisions described in the present disclosure may include network energy saving, load balancing, coverage and / or capacity optimization, mobility optimization and / or management, formulation and / or update of configurations, etc.

[0058] Results and reports may refer to each other in this disclosure.

[0059] In this disclosure, time may be represented by one or more of the following: timestamp, time point, time interval, timer, time period, time length, time cycle, time interval, etc. A time length may be the length of time from a certain time point, which may be the current moment. The time may be relative or absolute. In some embodiments, a time period may be represented by a separate field, for example, a combination of a start time and an end time, or a combination of a start time and a time period.

[0060] 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 information (MPD (Media presentation description) Information), Interactivity Summary, Interactivity Event List, etc.

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

[0062] In the present disclosure, the load condition and / or load information may include one or more of the following: PRB usage ratio, number of available PRBs, number of allocated PRBs, scheduled PDCCH CCE usage, transport network layer (TNL) capacity indication, radio resource status, integrated available capacity group, integrated available resource group, number of active user terminals, number of radio resource control (RRC) connections, 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 received quality (RSRQ) measurement report, signal to interference plus noise ratio (SINR) measurement report, channel state information (CSI) report, cell report indication, channel occupancy (Channel Occupancy) time ratio, energy detection (Energy Detection) Detection) threshold, signal strength and / or signal quality, channel busy ratio, data volume, and jitter of various content parameters.

[0063] In this disclosure, load conditions and / or load information may be referred to interchangeably with resource status.

[0064] In the present disclosure, capacity information may be one or more of the following: QoS requirements, QoS levels, capacity status, average QoS requirements, average QoS levels, average capacity status identifiers, the proportion of one or more QoS requirements, the proportion of one or more QoS levels, the proportion of one and / or multiple capacity status identifiers, etc. Among them, the capacity status identifier is represented by an identifier, and one identifier represents one capacity configuration. The QoS level can be represented by an identifier, for example, it can be a mapped 5G service quality identifier (5G QoS Identifier, 5QI) or a service quality class identifier (QoS Class Identifier, QCI).

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

[0066] In the present disclosure, coverage information may include one or more of the following: coverage status, information about coverage increase and / or decrease, ratio of coverage increase and / or decrease, load information at the cell edge, load information resulting from a change from within coverage to outside coverage due to coverage changes, etc. The coverage status may be represented by an identifier, with one identifier representing one coverage configuration.

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

[0068] In this disclosure, coverage and / or capacity, coverage change, and coverage and / or capacity optimization may refer to each other.

[0069] In the present disclosure, coverage and / or capacity policy (information) may include one or more of the following: cell identity, cell status, cell deployment status indication, replacement cell information, beam coverage change information, reasons for coverage change, etc. The replacement cell information may include one or more of the following: replacement cell identity, replaced cell identity, ratio of replaced cells, etc. The beam coverage change information may include one or more of the following: beam identity, beam coverage status, etc.

[0070] In the present disclosure, a beam may refer to a synchronization signal / physical broadcast channel block (Synchronization Signal and Physical Broadcast Channel (PBCH) block, SSB) beam, or any other beam.

[0071] In the present disclosure, the location range may be referred to by one or more of the following: coordinates, areas, cell identifiers, beam identifiers, identifiers for indicating locations and / or areas, etc. Among them, the cell identifier may be one or more of the following: access cell identifier, connection cell identifier, service cell identifier, etc. The beam identifier may be one or more of the following: access beam identifier, connection beam identifier, access beam identifier, etc. Among them, the identifier for indicating a location and / or area is used to indicate one or more locations and / or one or more areas. In some embodiments, for example, it may be an area whose distance is greater than and / or equal to and / or less than a threshold value, represented by an identifier. In other embodiments, for example, it may be an area whose signal quality is greater than and / or equal to and / or less than a threshold value, represented by an identifier.

[0072] In the present disclosure, a target node may also be a candidate target node, a target primary node, a target secondary node, a candidate target primary node, a candidate target secondary node, etc.

[0073] In the present disclosure, the source node may also be a source master node, a source slave node, etc.

[0074] In the present disclosure, data collection may be Minimization of Drive Tests (MDT), any other data collection, or any measurement. This disclosure does not limit this. The MDT may be a delayed (logged) MDT or an immediate (immediate) MDT; the MDT may be a signaling-based (signaling-based) MDT or a management-based (management-based) MDT. When a UE is connected from one base station to another, continuous data collection is required, but the existing technology has deficiencies in the research on continuous data collection.

[0075] In this disclosure, user equipment (UE) may be referred to interchangeably with user, terminal, etc.

[0076] In the present disclosure, data collection may include continuous data collection or discontinuous data collection.

[0077] In the present disclosure, collection can also be measurement. Data collection can also be measurement.

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

[0079] User trajectory data: This may include one or more of the following:

[0080] ○User ID

[0081] ○The ID of the cell being visited

[0082] ○The primary cell ID of the visited area

[0083] ○ Accessed secondary cell ID

[0084] ○ The visited primary cell identifier and the visited secondary cell identifier: indicate the primary cell and the visited secondary cell visited by the user in the case of dual connectivity.

[0085] ○ The node where the visited cell is located: it can be a node ID or a node name.

[0086] ○ The node where the visited primary cell is located: it can be a node identifier or a node name.

[0087] ○ The node where the accessed secondary cell is located: it can be a node identifier or a node name.

[0088] ○ Visit time and / or length of stay

[0089] ○Coordinates

[0090] ○ Accessed beam information: can be beam identifier.

[0091] User performance related data: This may include one or more of the following:

[0092] ○User ID

[0093] ○ Time of user performance collection

[0094] ○ The node corresponding to the user performance collection: it can be a node ID or a node name.

[0095] ○Cell ID corresponding to user performance

[0096] ○Beam identification corresponding to user performance

[0097] ○Slice identification corresponding to user performance

[0098] ○ The protocol data unit (PDU) session identifier corresponding to the user performance

[0099] ○Data Radio Bearer (Packet Data Unit, DRB) identifier corresponding to user performance

[0100] ○QoS flow identification corresponding to user performance

[0101] ○ User performance: may include one or more of the following: uplink and / or downlink data rate, uplink and / or downlink throughput, uplink and / or downlink latency, uplink and / or downlink packet loss rate, uplink and / or downlink QoE parameters.

[0102] Network performance related data: This may include one or more of the following:

[0103] ○ Network performance collection time

[0104] ○ Node corresponding to network performance collection: can be node ID or node name.

[0105] ○Cell ID corresponding to network performance

[0106] ○Beam identification corresponding to network performance

[0107] ○Slice identification corresponding to network performance

[0108] ○Data Radio Bearer (Packet Data Unit, DRB) identifier corresponding to network performance

[0109] ○QoS flow identification corresponding to network performance

[0110] ○ Network performance: may include one or more of the following: uplink and / or downlink data rate, uplink and / or downlink throughput, uplink and / or downlink latency, uplink and / or downlink packet loss rate, uplink and / or downlink QoE parameters.

[0111] User measurement result information: may include one or more of the following:

[0112] ○User ID

[0113] ○Node ID and / or cell ID corresponding to the user measurement result

[0114] ○Measurement results

[0115] ○Measurement time

[0116] Perception-related result information: This may include one or more of the following:

[0117] ○User ID

[0118] ○Node identifier and / or cell identifier corresponding to the user perception related measurement results

[0119] ○Perception-related measurement results

[0120] ○Perception-related measurement time

[0121] Example 1

[0122] One aspect of the present disclosure provides a method for supporting continuous data collection, comprising:

[0123] The first node sends a first message including information about continuous data collection to the second node to inform the second node of information corresponding to / associated with continuous data collection, and the second node needs to be configured according to the information in the first message when performing continuous data collection. In some embodiments, for example, the first message can trigger the second node to perform continuous data collection. In another embodiment, for example, the first message only informs the second node of information corresponding to continuous data collection, and does not trigger the second node to perform continuous data collection. In some further embodiments, for example, the first message can trigger the second node to configure continuous data collection for the corresponding user, or the first message can trigger the second node to configure continuous data collection for the corresponding user according to the information in the first message. In yet another embodiment, for example, the first message can inform the second node of the corresponding information for continuous collection, and the second node can perform continuous data collection subsequently.

[0124] In some embodiments, the first message may be included in one or more of the following: a handover request (Handover Request) message or a secondary node add request (S-NODE ADDITION REQUEST) message or a secondary node modification request (S-NODE MODIFICATION REQUEST) message or an NG-RAN node configuration update (NG-RAN NODECONFIGURATION UPDATE) message or an NG-RAN node configuration update confirmation (NG-RAN NODE CONFIGURATIONUPDATE ACKNOWLEDGE) message or an Xn setup request (XN SETUP REQUEST) message or an Xn setup response (XNSETUP RESPONSE) message of NG; 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. SETUPREQUEST) message; RRC reconfiguration (RRCReconfiguration) message of RRC; or another 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.

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

[0126] ●Sending node ID: used to identify the node that sends the message.

[0127] ●Receiving node identifier: used to identify the node that receives the message.

[0128] ●Request ID: used to identify the request.

[0129] ●Measurement ID: used to identify the measurement request.

[0130] ●Report ID: used to identify the report request.

[0131] Configuration identifier: used to identify the configuration of continuous data collection. This identifier can uniquely identify a continuous data collection configuration. For example, the configuration can be an MDT configuration or a continuous MDT configuration.

[0132] ●Continuous data collection (request) identifier: used to indicate that the information contains continuous data collection (request). After the message receiving node receives the information, in some embodiments, for example, the message receiving node can be triggered to perform continuous data collection. In another embodiment, for example, the information only informs the message receiving node of the information corresponding to the continuous data collection, and does not trigger the message receiving node to perform continuous data collection. In some other embodiments, for example, the message receiving node can be triggered to configure continuous data collection for the corresponding user, or the message receiving node can be triggered to configure continuous data collection for the corresponding user according to the information in the message. In some other embodiments, for example, the reporting of the data collection and / or data collection results does not need to be anonymized.

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

[0134] ●Indication of the start of continuous data collection: used to indicate the start of continuous data collection. In some embodiments, for example, after the message receiving node receives the indication, it starts continuous data collection, or it can configure the UE to start continuous data collection. In some other embodiments, for example, after the message receiving node receives the indication, the message receiving node can assign a first identifier, and / or configure the first identifier and / or the node and / or cell identifier corresponding to the start and / or initial configuration of continuous data collection to the UE. In some other embodiments, for example, after the UE receives the indication, it starts timing the continuous data collection. For example, the accumulated time of continuous data collection can be sent to the node to which the UE is connected, so that the node to which the UE is connected can configure subsequent data collection.

[0135] Continuous Data Collection Start Time: used to indicate the start time of continuous data collection. In some embodiments, for example, the message receiving node may perform data collection at the start time of continuous data collection. In another embodiment, for example, the message receiving node may configure continuous data collection for the UE at the start time of continuous data collection.

[0136] ● Continuous data collection end indication: used to indicate the end of continuous data collection. In some implementations, for example, after receiving the indication, the message receiving node stops continuous data collection, or may configure the UE to stop continuous data collection.

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

[0138] Continuous Data Collection Time: This field indicates the time for continuous data collection. In some implementations, for example, after receiving this time, the message receiving node may only collect data during the continuous data collection time. Alternatively, the UE may be configured to collect data during the continuous data collection time. In some implementations, this continuous data collection time may also be the time for reporting the continuous data collection results.

[0139] ● Remaining time of continuous data collection: used to indicate the time during which continuous data collection is still required. In some embodiments, for example, after receiving the information, the message receiving node performs data collection within the remaining time of continuous data collection, or configures the UE to perform data collection within the remaining time of continuous data collection, or configures the UE to perform data collection 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 perform data collection, and / or may not configure the UE to perform data collection. 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 perform data collection, and / or configure the UE to perform data collection.

[0140] ●Cumulative time of continuous data collection: used to indicate the time when continuous data collection has been performed. In some embodiments, 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 cumulative time of continuous data collection. For example, if the time of continuous data collection minus the cumulative time of continuous data collection is equal to and / or greater than a threshold value, the message receiving node may perform data collection, and / or configure the UE to perform data collection. For example, if the time of continuous data collection minus the cumulative time of continuous data collection is equal to and / or less than a threshold value, the message receiving node may not perform data collection, and / or not configure the UE to perform data collection. For example, the threshold value may be 0. In another implementation, the message receiving node may continue to configure subsequent data collection based on the time of continuous data collection and / or the cumulative time of continuous data collection to achieve continuous data collection. For example, the message receiving node may be configured to perform data collection at the first time. The first time may be the time of continuous data collection minus the cumulative time of continuous data collection.

[0141] Cells corresponding to continuous data collection: This may indicate cell information corresponding to continuous data collection. For example, this may include one or more of the following: cell identifiers and / or cell identifier lists, and the number of cells. In some embodiments, for example, continuous data collection is performed within corresponding cell identifiers and / or cell identifier lists. In other embodiments, for example, when the number of cells corresponding to completed continuous data collection and / or data collection results reaches a specified number of cells, continuous data collection should be stopped.

[0142] Nodes corresponding to continuous data collection: This may indicate node information corresponding to continuous data collection. For example, this may include one or more of the following: node identifiers and / or node identifier lists, and the number of nodes. In some embodiments, for example, continuous data collection is performed within corresponding node identifiers and / or node identifier lists. In other embodiments, for example, when the number of nodes corresponding to completed continuous data collection and / or data collection results reaches the specified number of nodes, continuous data collection should be stopped.

[0143] PLMN information corresponding to continuous data collection: This may indicate the PLMN information corresponding to continuous data collection. For example, this may include one or more of the following: PLMN and / or PLMN list, number of PLMNs. In some embodiments, for example, continuous data collection is performed within the corresponding PLMN and / or PLMN list. In other embodiments, for example, when the number of PLMNs corresponding to completed continuous data collection and / or data collection results reaches the specified number of PLMNs, continuous data collection should be terminated.

[0144] ●Slice information corresponding to continuous data collection: can represent the slice information corresponding to continuous data collection. For example, it can include one or more of the following: slice identifier and / or slice identifier list, number of slices. In some embodiments, for example, continuous data collection is performed within the corresponding slice identifier and / or slice identifier list. In other embodiments, for example, when the number of slices corresponding to the completed continuous data collection and / or data collection results reaches the number of slices, continuous data collection should be stopped. The slice identifier can be represented by single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI).

[0145] ●Beam information corresponding to continuous data collection: can indicate beam information corresponding to continuous data collection. For example, it can include one or more of the following: beam identifier and / or beam identifier list, number of beams. In some embodiments, for example, continuous data collection is performed within the corresponding beam identifier and / or beam identifier list. In other embodiments, for example, when the number of beams corresponding to the completed continuous data collection and / or data collection results reaches the number of beams, continuous data collection should be stopped. For example, the beam can be an SSB beam or any other beam. In some embodiments, for example, this information can be used by the message receiving node to determine whether to continue configuring continuous data collection, and / or, if configuration continues, the corresponding configuration information.

[0146] First identifier: used to identify the collection. For example, the identifier can be a random number. In some embodiments, for example, during a continuous data collection process, the first identifier of a UE remains the same. In other embodiments, for example, the first identifier can be configured by the node and / or cell corresponding to the start of the continuous data collection and / or the node and / or cell corresponding to the initial configuration of the continuous data collection.

[0147] Node and / or cell identifier corresponding to the start and / or initial configuration of continuous data collection: This identifier indicates the node and / or cell identifier corresponding to the start of continuous data collection, and may also be the node and / or cell identifier corresponding to the first configuration of continuous data collection for a UE. In some embodiments, for example, this node and / or cell identifier and the first identifier may uniquely identify a UE and / or the UE corresponding to the data collection report in the network.

[0148] Continuous Data Collection Dedicated TR and / or TRSR: In one implementation, the dedicated TR and / or TRSR remains unchanged during a continuous data collection process. For example, the dedicated TR and / or TRSR for the same UE remains unchanged during a continuous data collection process. In some embodiments, for example, a node can use the dedicated TR and / or TRSR to correlate multiple data collection results for the same UE.

[0149] Configuration associations for continuous data collection: used to represent the associations configured in continuous data collection. In some embodiments, for example, configuration A and configuration B belong to the same continuous data collection. Nodes can configure subsequent data collections according to this configuration association to achieve continuous data collection. This configuration association can be a single relationship or a list of relationships. The associations can be one or more of the following:

[0150] ○Related TR

[0151] ○ Associated TRSR

[0152] ○ Associated data collection configuration identifier

[0153] ○ Associated data collection configuration

[0154] ○Configure the corresponding node and / or cell identifier

[0155] ● Data collection configuration: In some implementations, for example, the message receiving node may perform data collection according to the data collection configuration, or may perform relevant data collection configuration on the UE based on the information. This may include one or more of the following:

[0156] Data collection configuration identifier: used to identify a data collection configuration. This identifier can uniquely identify a data collection configuration. For example, this identifier can be an MDT configuration identifier, which can uniquely identify an MDT configuration. The MDT configuration can include one or more of the data collection configurations.

[0157] ○ Trace Reference (TR): can include one or more of the following: PLMN identifier, Trace ID

[0158] ○Trace Recording Session Reference (TRSR)

[0159] ○Trace Collection Entity ID

[0160] Absolute time information: the absolute time of the cell. In some implementations, for example, it may be the absolute time of the current cell.

[0161] ○ Regional Configuration: Indicates the regional information for data collection. This may include one or more of the following: cell ID and / or cell ID list, PLMN ID, Tracking Area Code, uplink and / or downlink carrier frequency, etc. The cell ID may be a Physical Cell ID or a Cell Global ID.

[0162] ○PLMN identity (list): indicates the PLMN identity corresponding to the UE's measurement records, related status indications, and information acquisition.

[0163] ○ Bluetooth name (list): indicates the name (list) of the Bluetooth beacon that the UE is configured to measure.

[0164] ○WLAN name (list): indicates the name (list) of the WLAN access points that the UE is configured to measure.

[0165] ○ Sensor name (list): indicates the name (list) of the sensors that the UE is configured to measure.

[0166] ○ Logging time: indicates the time when the UE is required to perform measurement logging.

[0167] ○ Report type: can include periodic reporting, event-triggered reporting, single reporting, etc.

[0168] ○Recording interval: Indicates the time period and / or interval for recording measurement results.

[0169] ○ Event trigger configuration: including trigger events, thresholds, trigger time, hysteresis, etc. The trigger events can be one or more of the following: out of coverage, RRC state change, etc.

[0170] MDT Configuration Mode: Indicates whether the configuration is signaling-based or management-based. This configuration mode also indicates the MDT type configured. The MDT type can include one or more of the following: delayed MDT, immediate MDT, signaling-based MDT, management-based MDT, and combinations thereof.

[0171] ○ Early measurement indication: used to indicate whether the UE is allowed to record the relevant measurement results of the early measurement frequency.

[0172] Data collection triggering events and / or conditions: Data collection begins when the events and / or conditions triggering data collection are met. These events and / or conditions may include one or more of the following: the end of current data collection, the end of delayed MDT, etc. In some implementations, for example, these events and / or conditions may trigger immediate MDT. For example, the event and / or condition triggering immediate MDT may be the end of delayed MDT. Therefore, immediate MDT can be initiated immediately after the end of delayed MDT, thereby achieving continuous data collection.

[0173] Example 2

[0174] One aspect of the present disclosure provides a method for supporting continuous data collection, comprising:

[0175] The third node sends a second message including all and / or part of the continuous data collection result to the fourth node, so as to report all and / or part of the continuous data collection result to the fourth node.

[0176] In some embodiments, the second message may be included in one or more of the following: a UE Information Response (UEInformationResponse) message of RRC; or another 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.

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

[0178] ●Sending node ID: used to identify the node that sends the message.

[0179] ●Receiving node identifier: used to identify the node that receives the message.

[0180] ● Measurement identifier: used to identify the measurement. In one implementation, for example, the measurement identifier may be consistent with the measurement identifier in the first message, and is used to associate the report message with the configuration message.

[0181] ● Request identifier: used to identify the request. In one implementation, for example, the request identifier may be consistent with the request identifier in the first message, and is used to associate the report message with the configuration message.

[0182] ● Prediction ID: used to identify the prediction request. In one implementation, for example, the prediction ID can be consistent with the prediction ID in the first message, and is used to associate the report message with the configuration message.

[0183] ● Reporting identifier: used to identify this reporting request. In one implementation, for example, the reporting identifier may be consistent with the reporting identifier in the first message, and is used to associate the reporting message with the configuration message.

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

[0185] Continuous data collection configuration: The continuous data collection configuration may be one or more items in the first message. The continuous data collection configuration informs the message receiving node of the continuous data collection configuration. In some embodiments, for example, the message receiving node may configure subsequent continuous data collection according to the configuration to achieve continuous data collection.

[0186] ●Identifier of continuous data collection configuration: This identifier can uniquely identify a continuous data collection configuration. For example, the configuration can be an MDT configuration or a continuous MDT configuration. Using this identifier to inform the message receiving node of the configuration corresponding to the continuous data collection can save signaling. In some embodiments, for example, the message receiving node can know the continuous data collection configuration and / or MDT configuration through this identifier, and can continue to configure subsequent data collection according to this configuration to achieve continuous data collection. In some other embodiments, for example, the reporting of the data collection and / or data collection results does not need to be anonymized.

[0187] ●Cumulative time of continuous data collection: used to indicate the time during which continuous data collection has been performed. In some embodiments, for example, the message receiving node may decide whether to continue configuring subsequent data collection based on the time of continuous data collection and / or the cumulative time of continuous data collection. For example, if the time of continuous data collection minus the cumulative time of continuous data collection is equal to and / or greater than a threshold value, the message receiving node may perform data collection, and / or configure the UE to perform data collection. For example, if the time of continuous data collection minus the cumulative time of continuous data collection is equal to and / or less than a threshold value, the message receiving node may not perform data collection, and / or not configure the UE to perform data collection. For example, the threshold value may be 0. In another implementation, the message receiving node may continue to configure subsequent data collection based on the time of continuous data collection and / or the cumulative time of continuous data collection to achieve continuous data collection. For example, the message receiving node may be configured to perform data collection at the first time. The first time may be the time of continuous data collection minus the cumulative time of continuous data collection.

[0188] Continuous data collection start time: used to indicate the start time of continuous data collection. In some embodiments, for example, the message receiving node may determine whether to continue configuring subsequent data collection based on the start time of continuous data collection. For example, the message receiving node may configure data collection at a second time, where the second time may be derived from the time of continuous data collection and the start time of continuous data collection. For example, the second time may be the remaining continuous data collection time derived from the time of continuous data collection and the start time of continuous data collection.

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

[0190] ● Remaining time of continuous data collection: used to indicate the time during which continuous data collection is still required. In some embodiments, for example, after receiving the information, the message receiving node performs data collection within the remaining time of continuous data collection, or configures the UE to perform data collection within the remaining time of continuous data collection, or configures the UE to perform data collection 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 perform data collection, and / or may not configure the UE to perform data collection. 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 perform data collection, and / or configure the UE to perform data collection.

[0191] ● Information about completed and / or ongoing (continuous) data collection: Information about completed and / or ongoing (continuous) data collection. This information may include one or more of the following:

[0192] TR and / or TRSR corresponding to completed and / or ongoing (continuous) data collection: This information can be a single TR and / or TRSR, or a group of TRs and / or TRSRs. In some embodiments, for example, this information can be used by a node to correlate multiple data collection results to obtain a continuous data collection result. For example, this information can be used by a node to correlate multiple data collection results measured by the same UE to obtain a continuous data collection result.

[0193] Configuration node and / or cell information corresponding to completed and / or ongoing (continuous) data collection: This information indicates the node and / or cell from which the configuration information for completed and / or ongoing data collection was obtained. This information can be a single node and / or cell information or a list of node and / or cell information. This information can include one or more of the following:

[0194] Node identification

[0195] Node name

[0196] ■City logo

[0197] ○ Information corresponding to completed and / or ongoing (continuous) data collection: Information corresponding to completed and / or ongoing (continuous) data collection. In some embodiments, for example, this information can be used by the message receiving node to determine whether to continue configuring continuous data collection, and / or, if so, the corresponding configuration information. This can include one or more of the following:

[0198] ■Corresponding cell ID and / or ID list

[0199] ■The number of corresponding cells

[0200] ■Corresponding node ID and / or ID list

[0201] ■The number of corresponding nodes

[0202] ■Corresponding node name and / or name list

[0203] ■Corresponding PLMN and / or PLMN list

[0204] ■Number of corresponding PLMNs

[0205] ■Corresponding slice ID and / or slice ID list

[0206] ■The corresponding number of slices

[0207] ■Corresponding beam identifier and / or beam identifier list

[0208] ■The number of corresponding beams

[0209] ● Cells corresponding to continuous data collection: may indicate cell information corresponding to continuous data collection. For example, it may include one or more of the following: cell identifier and / or cell identifier list, number of cells. In some embodiments, for example, continuous data collection is performed within the corresponding cell identifier and / or cell identifier list. In other embodiments, for example, when the number of cells corresponding to completed continuous data collection and / or data collection results reaches the number of cells, continuous data collection should be stopped. In some embodiments, for example, this information may be used by the message receiving node to determine whether to continue configuring continuous data collection, and / or, if configuration continues, the corresponding configuration information.

[0210] ● Nodes corresponding to continuous data collection: can represent node information corresponding to continuous data collection. For example, it can include one or more of the following: node identifier and / or node identifier list, number of nodes. In some embodiments, for example, continuous data collection is performed within the corresponding node identifier and / or node identifier list. In other embodiments, for example, when the number of nodes corresponding to the completed continuous data collection and / or data collection results reaches the number of nodes, continuous data collection should be stopped. In some embodiments, for example, this information can be used by the message receiving node to determine whether to continue configuring continuous data collection, and / or, if configuration continues, the corresponding configuration information.

[0211] ● PLMN information corresponding to continuous data collection: can indicate the PLMN information corresponding to continuous data collection. For example, it can include one or more of the following: PLMN and / or PLMN list, number of PLMNs. In some embodiments, for example, continuous data collection is performed within the corresponding PLMN and / or PLMN list. In other embodiments, for example, when the number of PLMNs corresponding to the completed continuous data collection and / or data collection results reaches the said number of PLMNs, continuous data collection should be stopped. In some embodiments, for example, this information can be used by the message receiving node to determine whether to continue configuring continuous data collection, and / or, if configuration continues, the corresponding configuration information.

[0212] ●Slice information corresponding to continuous data collection: can represent the slice information corresponding to continuous data collection. For example, it can include one or more of the following: slice identifier and / or slice identifier list, number of slices. In some embodiments, for example, continuous data collection is performed within the corresponding slice identifier and / or slice identifier list. In other embodiments, for example, when the number of slices corresponding to the completed continuous data collection and / or data collection results reaches the number of slices, continuous data collection should be stopped. The slice identifier can be represented by single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI). In some embodiments, for example, this information can be used by the message receiving node to determine whether to continue configuring continuous data collection, and / or, if continuing to configure, the corresponding configuration information.

[0213] ●Beam information corresponding to continuous data collection: can indicate beam information corresponding to continuous data collection. For example, it can include one or more of the following: beam identifier and / or beam identifier list, number of beams. In some embodiments, for example, continuous data collection is performed within the corresponding beam identifier and / or beam identifier list. In other embodiments, for example, when the number of beams corresponding to the completed continuous data collection and / or data collection results reaches the number of beams, continuous data collection should be stopped. For example, the beam can be an SSB beam or any other beam. In some embodiments, for example, this information can be used by the message receiving node to determine whether to continue configuring continuous data collection, and / or, if configuration continues, the corresponding configuration information.

[0214] ● Data Collection Results: Indicates the results of data collection. This result can be MDT data collection results or other data collection results. The data collection results may include one or more of the following:

[0215] ○Cell ID and / or ID list corresponding to the data collection results

[0216] ○The number of cells corresponding to the data collection results

[0217] ○Node IDs and / or ID lists corresponding to the data collection results

[0218] ○The number of nodes corresponding to the data collection results

[0219] ○Node name and / or name list corresponding to the data collection results

[0220] ○ PLMN and / or PLMN list corresponding to the data collection results

[0221] ○The number of PLMNs corresponding to the data collection results

[0222] ○ Slice ID and / or slice ID list corresponding to the data collection results

[0223] ○The number of slices corresponding to the data collection results

[0224] ○Beam ID and / or ID list corresponding to the data collection results

[0225] ○The number of beams corresponding to the data collection results

[0226] ● First Identifier: used to identify the collection. In some embodiments, for example, during a continuous data collection process, the first identifier of a UE remains the same. In some embodiments, for example, this information can be used by a node to associate multiple data collection results for the same UE.

[0227] ●Node and / or cell identifier corresponding to the start and / or initial configuration of continuous data collection: used to indicate the node and / or cell identifier corresponding to the start of continuous data collection, and may also be the node and / or cell identifier corresponding to the first configuration of continuous data collection for the UE. In some embodiments, for example, the node and / or cell identifier and the first identifier may uniquely identify a UE and / or the UE corresponding to the data collection report in the network. In some embodiments, for example, this information may be used by a node to associate multiple data collection results for the same UE, or the combination of this information and the first identifier may be used by a node to associate multiple data collection results for the same UE.

[0228] Continuous Data Collection Dedicated TR and / or TRSR: In one implementation, the dedicated TR and / or TRSR remains unchanged during a continuous data collection process. For example, the dedicated TR and / or TRSR for the same UE remains unchanged during a continuous data collection process. In some embodiments, for example, a node can use the dedicated TR and / or TRSR to correlate multiple data collection results for the same UE.

[0229] ●Configuration association relationship of continuous data collection: used to represent the association relationship of configurations in continuous data collection. In some embodiments, for example, configuration A and configuration B belong to the same continuous data collection. Nodes can configure subsequent data collection according to the configuration association relationship to achieve the effect of continuous data collection. The configuration association relationship can be a relationship or a

[0230] Relationship list. The association relationship can be one or more of the following:

[0231] ○Related TR

[0232] ○ Associated TRSR

[0233] ○Configure the corresponding node and / or cell identifier

[0234] ○ Associated data collection configuration identifier

[0235] ○ Associated data collection configuration

[0236] Example 3

[0237] One aspect of the present disclosure provides a method for supporting continuous data collection, comprising:

[0238] The fifth node sends a third message of continuous data collection and reporting information to the sixth node to inform the sixth node of the continuous data collection and reporting related information. In some embodiments, for example, the sixth node can send a data collection result request to the fifth node according to the information in the continuous data collection and reporting information.

[0239] In some embodiments, the third message may be included in one or more of the following: RRC's UE information response (UEInformationResponse) message or RRC setup complete (RRCSetupComplete) message or RRC recovery complete (RRCResumeComplete) message or RRC reconstruction complete (RRCReestablishmentComplete) message or RRC reconfiguration complete (RRCReconfigurationComplete) message; or another 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.

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

[0241] ●Sending node ID: used to identify the node that sends the message.

[0242] ●Receiving node identifier: used to identify the node that receives the message.

[0243] ● Expected reporting time: indicates the predicted and / or expected time that can be reported. In some embodiments, for example, the message sending node and / or UE is collecting data and cannot report at the moment, and the expected reporting time can be sent to the message receiving node. For example, the message receiving node can request reporting of the data collection results according to the expected reporting time, or the message sending node and / or UE can send the data collection results to the message receiving node at the expected reporting time after informing the expected reporting time. The reporting time can be the reporting time of all information, or it can be the reporting time of other information excluding the currently reportable information. The information can be referred to as the data collection result.

[0244] Data collection in progress indicator: Indicates that data collection is currently in progress. In some embodiments, for example, the message receiving node may subsequently request data result reporting from the message sending node and / or the UE based on this information. In other embodiments, for example, the message sending node and / or the UE will send the data collection results to the message receiving node after the ongoing data collection is completed.

[0245] End time of ongoing data collection: indicates the end time of the currently ongoing data collection. In some embodiments, for example, the message receiving node may, based on this information, request the message sending node and / or UE to report the data collection results after the end time. In other embodiments, for example, the message sending node and / or UE will send the data collection results to the message receiving node at and / or after the end time.

[0246] An indicator indicating that only partial information can be reported indicates that only partial information can be reported at this time. In some embodiments, for example, the message receiving node may request the reporting of partial information based on this information, and / or may subsequently request the reporting of the remaining information. In other embodiments, for example, the message receiving node may request the reporting of all information at a later time. This information may be referred to as a data collection result.

[0247] ● Data collection results are available: indicates that data collection results are already stored. In some implementations, for example, the message receiving node may request the message sending node to report the data collection results based on the information.

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

[0249] The text and drawings are provided as examples only to aid understanding of 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, it will be apparent to those skilled in the art based on what is disclosed herein that the embodiments and examples shown may be modified without departing from the scope of the present disclosure.

[0250] Figure 3 A schematic diagram showing one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure is shown. Specifically, Figure 3 The present invention shows a process of exchanging continuous data collection information (also referred to as information associated with continuous data collection in this article) between two nodes, so that the second node can collect data based on the continuous data collection information, and / or configure subsequent data collection, and / or analyze the collected data collection results.

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

[0252] Step 301A: The first node sends continuous data collection information to the second node. The continuous data collection information may be the aforementioned first message.

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

[0254] For example, the second node may perform subsequent data collection based on the information in the continuous data collection information. In some embodiments, for example, the second node may report part and / or all of the information in the data collection information together with the continuous data collection result, so that the receiving node of the data collection result can continue to configure subsequent data collection to achieve the effect of continuous data collection.

[0255] For example, the second node can configure subsequent data collection based on the continuous data collection information. In some embodiments, for example, during the switching process, the source node sends the continuous data collection information to the target node in step 301A; in step 302A, the target node can configure subsequent data collection for the UE based on the continuous data collection information to achieve the effect of continuous data collection. In some further embodiments, during the auxiliary node addition process, the main node sends the continuous data collection information to the target auxiliary node in step 301A; in step 302A, the auxiliary node configures subsequent data collection for the UE to achieve the effect of continuous data collection. In some further embodiments, for example, in step 301A, the auxiliary node sends the continuous data collection information to the main node; in step 302A, the main node configures subsequent data collection for the UE, or the main node sends it to other nodes, and the other nodes configure subsequent data collection for the UE. For example, the other node can be the target auxiliary node.

[0256] For example, the second node may analyze the continuous data collection result based on the continuous data collection information. In some embodiments, for example, the second node may correlate multiple (continuous) data collection results of the same UE based on the continuous data collection information to obtain the continuous data collection result.

[0257] Figure 4A A schematic diagram showing one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure is shown. Specifically, Figure 4A The process of exchanging continuous data collection results between two nodes is shown, so that a fourth node can perform analysis based on the continuous data collection results.

[0258] In one implementation, for example, the third node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB, and the fourth node may be a UE. In one implementation, for example, the third node may be a UE, and the fourth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In another implementation, for example, the third node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the fourth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In yet another implementation, for example, the third node may be an AMF, SMF, or MME, and the fourth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB. In another implementation, for example, the third node may be a gNB, a gNB-CU, a gNB CU-CP, an en-gNB, an eNB, or an ng-eNB, and the fourth node may be an AMF, an SMF, or an MME. Alternatively, for example, the third node may be a primary node and the fourth node may be a secondary node; the third node may be a secondary node and the fourth node may be a primary node; the third node may be a source node and the fourth node may be a target node; the third node may be a target node and the fourth node may be a source node.

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

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

[0261] For example, the fourth node may perform data analysis based on the information in the continuous data collection results. In some embodiments, for example, the fourth node may associate multiple collected data collection results based on the information in the continuous data collection results to obtain a set of continuous 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 artificial intelligence (AI) / machine learning (ML) training and / or performance monitoring and / or reasoning.

[0262] For example, the fourth node may configure subsequent data collection based on information in the continuous data collection result. In some embodiments, for example, the fourth node may obtain the need to configure continuous data collection and / or corresponding configuration information based on information in the continuous data collection result, and the fourth node configures subsequent data collection.

[0263] For example, the fourth node can obtain information that requires continued data collection based on the information in the continuous data collection result, and configure subsequent data collection. In some embodiments, for example, during the switching process, the source node sends the continuous data collection result to the target node in step 401A; in step 402A, the target node can configure subsequent data collection for the UE based on the continuous data collection result to achieve the effect of continuous data collection, and / or combine the subsequently collected data results with the received continuously collected data to obtain continuous data to achieve the effect of continuous collection. In some other embodiments, during the secondary node addition process, the main node sends the continuous data collection information to the target secondary node in step 401A; 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 subsequently collected data results with the received continuously collected data to obtain continuous data to achieve the effect of continuous collection. In yet other embodiments, for example, in step 401A, the secondary node sends the continuous data collection information to the primary node; in step 402A, the primary node configures subsequent data collection for the UE. Alternatively, the primary node sends the information to other nodes, which then configure subsequent data collection for the UE. For example, the other nodes may be target secondary nodes. Alternatively, the primary node and / or the other nodes combine the subsequently collected data results with the received continuously collected data to obtain continuous data, thereby achieving a continuous collection effect.

[0264] Figure 4B A schematic diagram showing one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure is shown. Specifically, Figure 4B The process of exchanging continuous data collection results between two nodes is shown, so that a fourth node can perform analysis based on the continuous data collection results.

[0265] In one implementation, for example, the third node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB, and the fourth node may be a UE. In one implementation, for example, the third node may be a UE, and the fourth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In another implementation, for example, the third node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the fourth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In yet another implementation, for example, the third node may be an AMF, SMF, or MME, and the fourth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB. In another implementation, for example, the third node may be a gNB, a gNB-CU, a gNB CU-CP, an en-gNB, an eNB, or an ng-eNB, and the fourth node may be an AMF, an SMF, or an MME. Alternatively, for example, the third node may be a primary node and the fourth node may be a secondary node; the third node may be a secondary node and the fourth node may be a primary node; the third node may be a source node and the fourth node may be a target node; the third node may be a target node and the fourth node may be a source node.

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

[0267] Step 402B: The third node sends the continuous data collection result to the fourth node. The continuous data collection result may be the aforementioned second message. In one embodiment, for example, the third node collects data according to the continuous data collection information received in step 401B, obtains the continuous data collection result, and sends it to the fourth node in step 402B.

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

[0269] For example, the fourth node may perform data analysis based on the information in the continuous data collection results. In some embodiments, for example, the fourth node may correlate multiple collected data collection results based on the information in the continuous data collection results to obtain a set of continuous collection results. For example, multiple (continuous) data results of the same UE may be correlated to obtain continuous data of the UE. For example, this continuous data may be used to support AI / ML training and / or performance monitoring and / or reasoning.

[0270] For example, the fourth node may configure subsequent data collection based on information in the continuous data collection result. In some embodiments, for example, the fourth node may obtain the need to configure continuous data collection and / or corresponding configuration information based on information in the continuous data collection result, and the fourth node configures subsequent data collection.

[0271] For example, the fourth node may obtain information requiring continued data collection based on the information in the continuous data collection result and configure subsequent data collection. In some embodiments, for example, during the handover process, in step 401A, the source node sends the continuous data collection result to the target node; in step 402A, the target node may configure subsequent data collection for the UE based on the continuous data collection result to achieve the effect of continuous data collection, and / or combine the subsequently collected data results with the received continuously collected data to obtain continuous data to achieve the effect of continuous collection. In other embodiments, during the addition of a secondary node, in step 401A, the primary node sends the continuous data collection information to the target secondary node; 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 subsequently collected data results with the received continuously collected data to obtain continuous data to achieve the effect of continuous collection. In other embodiments, for example, in step 401A, the secondary node sends the continuous data collection information to the primary node; in step 402A, the primary node configures subsequent data collection for the UE, or the primary node sends it to other nodes, and the other nodes configure subsequent data collection for the UE. For example, other nodes may be target auxiliary nodes. And / or, the master node and / or other nodes combine the subsequently collected data results with the received continuously collected data to obtain continuous data, thereby achieving a continuous collection effect.

[0272] Figure 4C A schematic diagram showing one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure is shown. Specifically, Figure 4C The diagram shows a process in which two nodes configure the UE to perform continuous data collection to obtain continuous data.

[0273] 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 embodiments, for example, OAM configures the continuous data collection information for gNB1 and / or gNB2.

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

[0275] Step 402C: The UE collects data and sends the corresponding continuous data collection results to gNB1. The continuous data collection results may be the aforementioned second message.

[0276] Step 403C: gNB1 sends 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 embodiments, for example, the continuous data collection information may be information for collecting data for the UE in the RRC inactive and / or RRC idle states.

[0277] Step 404C: The UE enters the RRC inactive or RRC idle state, and the UE collects data.

[0278] Step 405C: The UE returns to the RRC Connected state. The UE sends a message to the connected gNB (in this example, gNB2) containing information regarding the availability of continuous data collection results. The message may include one or more of the following: continuous data collection results available, data collection results available, partial data collection results available, partial continuous data collection results available, etc. In one embodiment, for example, after receiving this message, gNB2 may subsequently request the UE to report the continuous data collection results.

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

[0280] Step 407C: The UE sends 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 continuous data collection results, partial continuous data collection results, or currently available continuous data collection results.

[0281] Step 408C: gNB2 sends continuous data collection information and / or MDT configuration to the UE. The continuous data collection information may be the aforementioned first message. In some embodiments, for example, gNB2 continues to configure continuous data collection for the UE based on the information in the continuous data collection result and sends the continuous data collection information to the UE.

[0282] Step 409C: The UE collects data and sends the corresponding continuous data collection results to gNB2. The continuous data collection results may be the aforementioned second message.

[0283] Step 403C may be combined with step 401C.

[0284] Figure 4D A schematic diagram showing one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure is shown. Specifically, Figure 4D The diagram shows a process in which two nodes configure the UE to perform continuous data collection to obtain continuous data.

[0285] 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 embodiments, for example, the OAM configures the continuous data collection information for gNB1 and / or gNB2.

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

[0287] Step 402D: The UE collects data and sends the corresponding continuous data collection results to gNB1. The continuous data collection results may be the aforementioned second message.

[0288] Step 403D: gNB1 sends continuous data collection information and / or MDT configuration to gNB2. The continuous data collection information may be the aforementioned first message. In some embodiments, for example, during a handover, the source node (gNB1 in this example) sends the continuous data collection information to the 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, thereby achieving continuous data collection. In yet other embodiments, during the addition of a secondary node, the primary node (gNB1 in this example) sends the continuous data collection information to the target secondary node (gNB2 in this example). The secondary node (gNB2 in this example) configures subsequent data collection for the UE, thereby achieving continuous data collection. In yet other embodiments, for example, the secondary node (gNB1 in this example) sends the continuous data collection information to the primary node (gNB2 in this example). The primary node (gNB2 in this example) configures subsequent data collection for the UE. Alternatively, the primary node (gNB2 in this example) may send the continuous data collection information to other nodes, which then configure subsequent data collection for the UE. For example, the other node may be the target secondary node.

[0289] Step 404D: gNB2 sends continuous data collection information and / or MDT configuration to the UE. The continuous data collection information may be the aforementioned first message. In some embodiments, for example, gNB2 continues to configure continuous data collection for the UE based on the continuous data collection information and sends the continuous data collection information to the UE.

[0290] Step 405D: The UE performs data collection and sends the corresponding continuous data collection results to gNB2. The continuous data collection results may be the aforementioned second message.

[0291] Figure 4E A schematic diagram showing one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure is shown. Specifically, Figure 4E The diagram shows a process in which two auxiliary nodes configure the UE to perform continuous data collection to obtain continuous data.

[0292] Step 400E: Secondary node 1 and / or 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 the continuous data collection information for secondary node 1 and / or secondary node 2.

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

[0294] Step 402E: The UE performs data collection and sends the corresponding continuous data collection result to the secondary node 1. The continuous data collection result may be the aforementioned second message.

[0295] Step 403E: Secondary node 1 sends continuous data collection information and / or MDT configuration to the primary node. The continuous data collection information may be the aforementioned first message. In some embodiments, for example, during a secondary node change, the source secondary node (in this example, secondary node 1) sends the continuous data collection information to the primary node.

[0296] Step 404E: The primary node sends continuous data collection information and / or MDT configuration to secondary node 2. The continuous data collection information may be the aforementioned first message. In some embodiments, for example, during a secondary node change, the primary node sends the continuous data collection information to the target secondary node (in this example, secondary node 2).

[0297] Step 405E: The secondary node 2 sends continuous data collection information and / or MDT configuration to the UE. The continuous data collection information may be the aforementioned first message. In some embodiments, for example, the secondary node 2 continues to configure continuous data collection to the UE based on the continuous data collection information received in step 404E and / or step 400E, and sends the continuous data collection information to the UE. In other embodiments, for example, during the secondary node change process, when the UE accesses the secondary node 2, the secondary node 2 may directly send the continuous data collection information to the UE, for example, by sending it through an RRC reconfiguration (RRCReconfiguration) message. In yet another embodiment, for example, during the secondary node change process, the secondary node 2 may send the continuous data collection information to the UE by forwarding the primary node, for example, by sending it through an RRCReconfiguration message.

[0298] Step 406E: The UE performs data collection and sends the corresponding continuous data collection result to the secondary node 2. The continuous data collection result may be the aforementioned second message.

[0299] Figure 4F A schematic diagram showing one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure is shown. Specifically, Figure 4F It shows a process in which two nodes configure a UE to perform continuous MDT data collection during the MDT process to obtain continuous MDT data.

[0300] 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 embodiments, for example, OAM configures continuous data collection information for gNB1 and / or gNB2. For example, gNB1 receives an immediate MDT configuration (e.g., TR=X) and / or continuous data collection information. For example, gNB1 receives a delayed MDT configuration (e.g., TR=Y) and / or continuous data collection information (e.g., associated with TR=X). For example, gNB2 receives an immediate MDT configuration (e.g., TR=V) and / or continuous data collection information (e.g., associated with gNB1, TR=Y). For example, gNB2 receives a delayed MDT configuration (e.g., TR=W) and / or continuous data collection information.

[0301] Step 401F: gNB1 sends the immediate MDT configuration and / or continuous data collection information to the UE. The continuous data collection information may be the aforementioned first message. This message may be sent via an RRC Reconfiguration message.

[0302] Step 402F: The UE performs data collection and sends the corresponding immediate MDT report and / or continuous data collection results to gNB1. The continuous data collection results may be the aforementioned second message. This message may be sent via a Measurement Report message.

[0303] Step 403F: When processing the immediate MDT report and / or continuous data collection result, gNB1 performs corresponding processing, for example, the TR of the report and / or result is X and the TRSR is A.

[0304] Step 404F: gNB1 sends the delayed MDT configuration and / or continuous data collection information to the UE. The continuous data collection information may be the aforementioned first message. This message may be sent via an RRC Reconfiguration message. For example, the delayed MDT corresponding TRSR in this message may be set to the same as the immediate MDT report TRSR (e.g., TRSR = A). This ensures that the TRSR for the same UE is the same. The analyzing node may correlate multiple reports and / or results for the same UE based on the TRSR.

[0305] Step 405F: The UE enters the RRC inactive or RRC idle state, and the UE collects data.

[0306] Step 406F: The UE sends an RRC Setup Request (RRCSetupRequest) and / or an RRC Resume Request (RRCResumeRequest) and / or an RRC Resume Request 1 (RRCResumeRequest1) and / or an RRC Reestablishment Request (RRCReestablishmentRequest) message to gNB2.

[0307] Step 407F: gNB2 sends RRC Setup and / or RRC Resume and / or RRC Reestablishment and / or RRC Reconfiguration messages to the UE.

[0308] Step 408F: The UE sends a message to gNB2 containing information indicating that a delayed (logged) measurement report is available (logMeasAvailable) and / or continuous data collection and reporting. The continuous data collection and reporting information may be the aforementioned third message. The message may be sent via an RRC Setup Complete message, an RRC Resume Complete message, an RRC Reestablishment Complete message, and / or an RRC Reconfiguration Complete message.

[0309] Step 409F: gNB2 sends a message containing a continuous data collection result request and / or a delayed (logged) measurement report request (logMeasReportReq) to the UE, requesting the UE to report the continuous data collection result. The continuous data collection result request may include one or more of the following: a continuous data collection result request, a data collection result request, a partial data collection result request, a partial continuous data collection result request, a currently available (continuous) data collection result request, etc. The message may be sent via a UE Information Request message. In some embodiments, for example, the message may be sent based on the continuous data collection report information received in step 408F.

[0310] Step 410F: The UE sends a message containing a Delay (Logged) Measurement Report and / or Continuous Data Collection Results to gNB2. The Continuous Data Collection Results may be the aforementioned second message. In some embodiments, the TRSR in the Delay (Logged) Measurement Report and / or Continuous Data Collection Results needs to be set according to the TRSR received in step 404F, for example, TRSR = A. This message may be sent via a UE Information Response message.

[0311] Step 411F: gNB2 sends a message to the UE containing the immediate MDT configuration and / or continuous data collection information. The continuous data collection information may be the first message described above. The message may be sent via an RRC configuration message. In some embodiments, for example, gNB2 continues to configure continuous data collection for the UE based on the information received in step 410F and / or the information in step 400F, and sends the continuous data collection information to the UE. For example, the report and / or result received by gNB2 in step 410F indicates TR=Y, TRSR=A, and / or indicates that the configuration node is gNB1 (or the configuration cell is a cell managed by gNB1). The information obtained by gNB2 in step 400F indicates that the immediate MDT configuration with TR=V is associated with gNB1's TR=Y. Therefore, gNB2 needs to continue to configure the UE with immediate MDT with TR=V.

[0312] Step 412F: The UE performs data collection and sends the corresponding immediate MDT report and / or continuous data collection results to gNB2. The continuous data collection results may be the aforementioned second message. This message may be sent via a Measurement Report message.

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

[0314] Step 401F and step 404F may be combined. Step 404F may also occur before step 401F and / or step 402F and / or step 403F. Step 406F may be omitted.

[0315] The node performing the analysis can associate one or more of the following reports via TRSR=A to obtain a continuous data set:

[0316] ●The report and / or results obtained in step 402F and step 403F

[0317] • The report and / or results obtained in step 410F

[0318] ●The report and / or results obtained in step 412F and step 413F

[0319] Figure 4G A schematic diagram showing one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure is shown. Specifically, Figure 4G It shows a process in which two nodes configure a UE to perform continuous MDT data collection during the MDT process to obtain continuous MDT data.

[0320] 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 embodiments, for example, OAM configures continuous data collection information for gNB1 and / or gNB2. For example, gNB1 receives an immediate MDT configuration (e.g., TR=X) and / or continuous data collection information. For example, gNB1 receives a delayed MDT configuration (e.g., TR=Y) and / or continuous data collection information (e.g., associated with TR=X). For example, gNB2 receives an immediate MDT configuration (e.g., TR=V) and / or continuous data collection information (e.g., associated with gNB1, TR=Y). For example, gNB2 receives a delayed MDT configuration (e.g., TR=W) and / or continuous data collection information.

[0321] Step 401G: gNB1 sends the immediate MDT configuration and / or continuous data collection information to the UE. The continuous data collection information may be the aforementioned first message. This message may be sent via an RRC Reconfiguration message.

[0322] Step 402G: The UE performs data collection and sends the corresponding immediate MDT report and / or continuous data collection results to gNB1. The continuous data collection results may be the aforementioned second message. This message may be sent via a Measurement Report message.

[0323] Step 403G: gNB1 processes the immediate MDT report and / or continuous data collection results.

[0324] Step 404G: gNB1 sends the delayed MDT configuration and / or continuous data collection information to the UE. The continuous data collection information may be the aforementioned first message. This message may be sent via an RRC Reconfiguration message.

[0325] Step 405G: The UE enters the RRC inactive or RRC idle state, and the UE collects data.

[0326] Step 406G: The UE sends an RRC Setup Request (RRCSetupRequest) and / or an RRC Resume Request (RRCResumeRequest) and / or an RRC Resume Request 1 (RRCResumeRequest1) and / or an RRC Reestablishment Request (RRCReestablishmentRequest) message to gNB2.

[0327] Step 407G: gNB2 sends RRC Setup and / or RRC Resume and / or RRC Reestablishment and / or RRC Reconfiguration messages to the UE.

[0328] Step 408G: The UE sends a message including the delayed (logged) measurement report available (logMeasAvailable) and / or continuous data collection reporting information to gNB2. The continuous data collection reporting information may be the aforementioned third message. The message may be sent via an RRC Setup Complete message, an RRC Recovery Complete message, an RRC Reestablishment Complete message, and / or an RRC Reconfiguration Complete message.

[0329] Step 409G: gNB2 sends a message containing a continuous data collection result request and / or a delayed (logged) measurement report request (logMeasReportReq) to the UE, requesting the UE to report the continuous data collection result. The continuous data collection result request may include one or more of the following: a continuous data collection result request, a data collection result request, a partial data collection result request, a partial continuous data collection result request, a currently available (continuous) data collection result request, etc. The message may be sent via a UE Information Request message. In some embodiments, for example, the message may be sent based on the continuous data collection report information received in step 408G.

[0330] Step 410G: The UE sends a message containing a logged measurement report and / or a continuous data collection result to gNB2. The continuous data collection result may be the second message described above. The message may be sent via a UEInformationResponse message.

[0331] Step 411G: gNB2 sends a message to the UE containing immediate MDT configuration and / or continuous data collection information. The continuous data collection information may be the first message described above. The message may be sent via an RRC configuration message. In some embodiments, for example, gNB2 continues to configure continuous data collection for the UE based on the information received in step 410G and / or the information received in step 400G, and sends the continuous data collection information to the UE.

[0332] Step 412G: The UE performs data collection and sends the corresponding immediate MDT report and / or continuous data collection results to gNB2. The continuous data collection results may be the aforementioned second message. This message may be sent via a Measurement Report message.

[0333] Step 413G: gNB2 processes the immediate MDT report and / or continuous data collection results.

[0334] Step 401G and step 404G may be combined. Step 404G may also occur before step 401G and / or step 402G and / or step 403G. Step 406G may be omitted.

[0335] The node performing the analysis can associate one or more of the following reports with the continuous data collection results to obtain a continuous data:

[0336] ●The report and / or results obtained in step 402G and step 403G

[0337] The report and / or results obtained in step 410G

[0338] ●The report and / or results obtained in step 412G and step 413G

[0339] Figure 4H A schematic diagram showing one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure is shown. Specifically, Figure 4H It shows the process of three nodes exchanging continuous data collection information, which is to configure the UE to perform continuous data collection to obtain continuous data.

[0340] In some embodiments, 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 other embodiments, 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 still other embodiments, for example, node 1 may be an AMF and / or SMF, node 2 may be a gNB and / or gNB CU and / or gNB CU CP, and node 3 may be a gNB and / or gNB CU and / or gNB CU CP.

[0341] 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 the continuous data collection information for Node 2 and / or Node 3.

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

[0343] Step 402H: The UE performs data collection and sends the corresponding continuous data collection result to node 2. The continuous data collection result may be the aforementioned second message.

[0344] Step 403H: Node 2 sends continuous data collection information and / or MDT configuration to node 1. The continuous data collection information may be the aforementioned first message. In some embodiments, for example, during a user context release process and / or a bearer context release process, node 2 sends the continuous data collection information to node 1.

[0345] Step 404H: Node 1 sends continuous data collection information and / or MDT configuration to node 3. The continuous data collection information may be the aforementioned first message. In some embodiments, for example, during a user context establishment process, a user context modification process, a bearer context establishment process, and / or a bearer context modification process, node 1 sends the continuous data collection information to node 3.

[0346] Step 405H: Node 3 sends continuous data collection information and / or MDT configuration to the UE. The continuous data collection information may be the aforementioned first message. In some embodiments, for example, based on the continuous data collection information received in step 404H and / or in step 400H, node 3 continues to configure continuous data collection for the UE and sends the continuous data collection information to the UE.

[0347] Step 406H: The UE performs data collection and sends the corresponding continuous data collection result to the node 3. The continuous data collection result may be the aforementioned second message.

[0348] Figure 5A A schematic diagram showing one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure is shown. Specifically, Figure 5A The process of interactive continuous data collection and reporting information between two nodes is shown, so that the sixth node can obtain the continuous data collection results.

[0349] In one implementation, for example, the fifth node may be a UE, and the sixth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In another implementation, for example, the fifth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the sixth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In yet another implementation, for example, the fifth node may be an AMF, SMF, or MME, and the sixth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB. In yet another implementation, for example, the fifth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the sixth node may be an AMF, SMF, or MME. It can also be, for example, that the fifth node is the primary node and the sixth node is the secondary node; for example, the fifth node is the secondary node and the sixth node is the primary node; for example, the fifth node is the source node and the sixth node is the target node; for example, the fifth node is the target node and the sixth node is the source node.

[0350] Step 501A: The fifth node sends continuous data collection and reporting information to the sixth node. The continuous data collection and reporting information may be the aforementioned third message.

[0351] Step 502A: The sixth node may wait for and / or request a continuous data collection result based on the continuous data collection reporting information. In some embodiments, for example, the sixth node may send a data collection result request to the fifth node according to information in the continuous data collection reporting information.

[0352] Step 503A: The sixth node sends a message containing a continuous data collection result request to the fifth node, requesting the UE to report the continuous data collection result. The continuous data collection result request may include one or more of the following: a continuous data collection result request, a data collection result request, a partial data collection result request, a partial continuous data collection result request, a currently available (continuous) data collection result request, etc. The message may be sent via a UE Information Request message. In some embodiments, for example, the message may be sent based on the continuous data collection reporting information received in step 501A.

[0353] Step 504A: The fifth node sends 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 embodiments, for example, the message may be sent according to the continuous data collection reporting information in step 501A.

[0354] Step 503A is an optional step.

[0355] Figure 5B A schematic diagram showing one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure is shown. Specifically, Figure 5B The process of interactive continuous data collection and reporting information between two nodes is shown, so that the sixth node can obtain the continuous data collection results.

[0356] In one implementation, for example, the fifth node may be a UE, and the sixth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In another implementation, for example, the fifth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the sixth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In yet another implementation, for example, the fifth node may be an AMF, SMF, or MME, and the sixth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB. In yet another implementation, for example, the fifth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the sixth node may be an AMF, SMF, or MME. It can also be, for example, that the fifth node is the primary node and the sixth node is the secondary node; for example, the fifth node is the secondary node and the sixth node is the primary node; for example, the fifth node is the source node and the sixth node is the target node; for example, the fifth node is the target node and the sixth node is the source node.

[0357] Step 501B: The fifth node completes data collection.

[0358] Step 502B: The fifth node sends continuous data collection and reporting information to the sixth node. The continuous data collection and reporting information may be the aforementioned third message.

[0359] Step 503B: The sixth node sends a message containing a continuous data collection result request to the fifth node, requesting the UE to report the continuous data collection result. The continuous data collection result request may include one or more of the following: a continuous data collection result request, a data collection result request, a partial data collection result request, a partial continuous data collection result request, a currently available (continuous) data collection result request, etc. The message may be sent via a UE Information Request message. In some embodiments, for example, the message may be sent based on the continuous data collection reporting information received in step 502B.

[0360] Step 504B: The fifth node sends 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 embodiments, for example, the message may be sent according to the continuous data collection reporting information in step 502B.

[0361] Step 503B is an optional step.

[0362] Figure 5C A schematic diagram showing one aspect of a method for supporting continuous data collection according to an embodiment of the present disclosure is shown. Specifically, Figure 5C The process of interactive continuous data collection and reporting information between two nodes is shown, so that the sixth node can obtain the continuous data collection results.

[0363] In one implementation, for example, the fifth node may be a UE, and the sixth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In another implementation, for example, the fifth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the sixth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In yet another implementation, for example, the fifth node may be an AMF, SMF, or MME, and the sixth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB. In yet another implementation, for example, the fifth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the sixth node may be an AMF, SMF, or MME. It can also be, for example, that the fifth node is the primary node and the sixth node is the secondary node; for example, the fifth node is the secondary node and the sixth node is the primary node; for example, the fifth node is the source node and the sixth node is the target node; for example, the fifth node is the target node and the sixth node is the source node.

[0364] Step 501C: The fifth node is performing continuous data collection.

[0365] Step 502C: The fifth node sends continuous data collection and reporting information to the sixth node. The continuous data collection and reporting information may be the aforementioned third message.

[0366] Step 503C: The sixth node sends a message containing a continuous data collection result request to the fifth node, requesting the UE to report the continuous data collection result. The continuous data collection result request may include one or more of the following: a continuous data collection result request, a data collection result request, a partial data collection result request, a partial continuous data collection result request, a currently available (continuous) data collection result request, etc. The message may be sent via a UE Information Request message. In some embodiments, for example, the message may be sent based on the continuous data collection reporting information received in step 502C.

[0367] Step 504C: The fifth node sends 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 embodiments, for example, the message may be sent in accordance with the continuous data collection reporting information in step 502C. In other embodiments, for example, the fifth node may report the currently available data. In yet other embodiments, for example, after receiving the continuous data collection result request message in step 503C, the fifth node reports the currently collected and / or available data.

[0368] Step 505C: The fifth node completes data collection.

[0369] Step 505C: The fifth node sends continuous data collection and reporting information to the sixth node. The continuous data collection and reporting information may be the aforementioned third message.

[0370] Step 506C: The sixth node sends 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 continuous data collection result request, a data collection result request, a partial data collection result request, a partial continuous data collection result request, a currently available (continuous) data collection result request, etc. The message may be sent via a UE Information Request message. In some embodiments, for example, the message may be sent based on the continuous data collection reporting information received in step 502C and / or step 505C.

[0371] Step 507C: The fifth node sends 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 embodiments, for example, the message may be sent in accordance with the continuous data collection reporting information in step 502C and / or step 505C. In other embodiments, for example, the fifth node may report the currently available data. In yet other embodiments, for example, after receiving the continuous data collection result request message in step 506C, the fifth node reports the currently collected and / or available data.

[0372] For example, the results obtained in step 504C and step 507C may be combined to form continuous data.

[0373] Step 503C is an optional step. Step 506C is an optional step.

[0374] Step 505C is an optional step.

[0375] It should be understood that, depending on the application scenario, the various exemplary aspects, methods, steps, processes, etc. shown in the above-mentioned drawings can be combined and implemented in any manner, and this document does not limit them.

[0376] Next, Figure 6 A flowchart of a method 600 executed by a user equipment UE in a wireless communication system according to an embodiment of the present disclosure is shown.

[0377] According to an embodiment of the present disclosure, a method 600 performed by a user equipment UE in a wireless communication system may include: in step S601, receiving a second minimization of drive tests (MDT) configuration and second information from a first node, the second information including 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; in step S602, connecting to a second node; in step S603, sending 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, the third information including information indicating that the third MDT configuration is associated with the second MDT configuration and / or the first node.

[0378] According to an embodiment of the present disclosure, the method further includes: sending, to the second node, fourth information regarding availability of a second MDT report associated with the second MDT configuration and reporting information related to the continuous data collection, and receiving, from the second node, a request for a second MDT report associated with the second MDT configuration and a second result associated with the continuous data collection, wherein the request is sent from the second node based on the reporting information.

[0379] According to an embodiment 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.

[0380] According to an embodiment of the present disclosure, the method further includes: sending a first MDT report associated with the first MDT configuration and a first result associated with the continuous data collection to the first node.

[0381] According to an embodiment of the present disclosure, the method further includes: sending a third MDT report associated with the third MDT configuration and a third result associated with the continuous data collection to the second node.

[0382] According to an embodiment of the present disclosure, each of the first result, the second result, and the third result includes a first identifier of the UE associated with the continuous data collection and / or a second identifier of an initial configuration node for the continuous data collection, wherein the first MDT report, the second MDT report, and the third MDT report are associated through the first identifier and / or the second identifier.

[0383] According to an embodiment 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, wherein the third MDT configuration is determined based on one or more of the accumulated time and the data collection configuration.

[0384] Figure 7 A flowchart of a method 700 performed by a first node in a wireless communication system according to an embodiment of the present disclosure is shown.

[0385] According to an embodiment of the present disclosure, a method 700 performed by a first node in a wireless communication system may include: in step S701, sending a second minimization of drive tests (MDT) configuration and second information to a user equipment (UE), where the second information includes information related to continuous data collection associated with the second MDT configuration; in step S702, sending a first MDT configuration and first information to the UE, where 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.

[0386] According to an embodiment 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.

[0387] Figure 8 A flowchart of a method 800 performed by a second node in a wireless communication system according to an embodiment of the present disclosure is shown.

[0388] According to an embodiment of the present disclosure, a method 800 performed by a second node in a wireless communication system 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 sent by a first node to the UE and a second result associated with continuous data collection; and in step S802, sending a third MDT configuration and third information to the UE, the third information including information indicating that the third MDT configuration is associated with the second MDT configuration and / or the first node.

[0389] According to an embodiment of the present disclosure, the method further includes: receiving, from the UE, fourth information regarding availability of a second MDT report associated with the second MDT configuration and reporting information related to the continuous data collection, and sending, to the UE, a request for a second MDT report associated with the second MDT configuration and a second result associated with the continuous data collection, wherein the request is sent from the second node based on the reporting information.

[0390] According to an embodiment 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.

[0391] According to an embodiment 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.

[0392] According to an embodiment of the present disclosure, each of the second result and the third result includes a first identifier of the UE associated with the continuous data collection and / or a second identifier of an initial configuration node for the continuous data collection, wherein the second MDT report and the third MDT report are associated through the first identifier and / or the second identifier.

[0393] According to an embodiment 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, wherein the third MDT configuration is determined based on one or more of the accumulated time and the data collection configuration.

[0394] It should be understood that methods 600, 700, 800, etc. according to the embodiments of the present disclosure may also include any method or step described in conjunction with various examples, aspects, figures, etc. of the present disclosure.

[0395] Next, Figure 9 A schematic diagram of a node 900 according to an embodiment of the present disclosure is shown.

[0396] like Figure 9 As shown, a node (or node device, such as the first node or the second node described above) 900 according to an embodiment of the present disclosure may include a transceiver 910 and a processor 920. The transceiver 910 may be configured to send and receive signals. The processor 920 may be coupled to the transceiver 910 and may be configured (e.g., control the transceiver 910) to execute a method performed by a node (e.g., the first node and / or the second node) according to an embodiment of the present disclosure.

[0397] Figure 10 A schematic diagram of a user equipment 1000 according to an embodiment of the present disclosure is shown.

[0398] like Figure 10 As shown, a user equipment 1000 according to an embodiment of the present disclosure may include a transceiver 1010 and a processor 1020. The transceiver 1010 may be configured to send and receive signals. The processor 1020 may be coupled to the transceiver 1010 and may be configured to (e.g., control the transceiver 1010) execute the method performed by the user equipment according to an embodiment of the present disclosure. In the present disclosure, a processor may also be referred to as a controller.

[0399] An embodiment of the present disclosure further provides a computer-readable medium having computer-readable instructions stored thereon. When the instructions are executed by a processor, they can be used to implement any method according to the embodiment of the present disclosure.

[0400] Various embodiments of the present disclosure can 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 disc read-only memory (CD-ROM), magnetic tape, floppy disk, optical data storage device, carrier wave (e.g., data transmission via the Internet), and the like. Computer-readable recording media can be distributed by computer systems connected via a network, and therefore computer-readable codes can be stored and executed in a distributed manner. Moreover, the functional programs, codes, and code segments for implementing the various embodiments of the present disclosure can be easily interpreted by those skilled in the art in the field of applying the embodiments of the present disclosure.

[0401] It will be understood that the embodiments of the present disclosure can be implemented in the form of hardware, software, or a combination of hardware and software. Software can be stored as program instructions or computer-readable code executable on a processor on a non-transient computer-readable medium. Examples of non-transient computer-readable recording media include magnetic storage media (e.g., ROM, floppy disk, hard disk, etc.) and optical recording media (e.g., CD-ROM, digital video disk (DVD), etc.). Non-transient computer-readable recording media can also be distributed on network-coupled computer systems so that computer-readable code is 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 can be implemented by a computer or a portable terminal including a controller and a memory, and the memory can be an example of a non-transient computer-readable recording medium suitable for storing (multiple) programs with instructions for implementing the embodiments of the present disclosure. The present disclosure can be implemented by a program having a code for specifically implementing the apparatus and method described in the claims, the program being stored in a machine (or computer) readable storage medium. The program can 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.

[0402] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any person skilled in the art may make various changes or substitutions within the technical scope disclosed in the present disclosure, and such changes or substitutions shall be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure shall be subject to the scope of protection of the claims.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, comprising: receiving a second minimization of drive tests (MDT) configuration and second information from the first node, the second information including information related to continuous data collection associated with the second MDT configuration, and performing second MDT data collection based on the second MDT configuration in a radio resource control (RRC) inactive state or an RRC idle state; Connect to the second node; sending a second MDT report associated with the second MDT configuration and a second result associated with the continuous data collection to the second node; as well as A third MDT configuration and third information are received from the second node, the third information including information indicating that the third MDT configuration is associated with the second MDT configuration and / or the first node.

2. The method according to claim 1, further comprising: sending fourth information about availability of a second MDT report associated with the second MDT configuration and reporting information related to the continuous data collection to the second node, and receiving, from the second node, a request for a second MDT report associated with the second MDT configuration and a second result associated with the continuous data collection, The request is sent from the second node based on the reported information.

3. 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, The second information further includes information indicating that the second MDT configuration is associated with the first MDT configuration.

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

5. The method according to claim 4, further comprising: A third MDT report associated with the third MDT configuration and a third result associated with the continuous data collection are sent to the second node.

6. The method according to claim 5, wherein: Each of the first result, the second result, and the third result includes a first identifier of the UE associated with the continuous data collection and / or a second identifier of an initial configuration node for the continuous data collection, The first MDT report, the second MDT report, and the third MDT report are associated through the first identifier and / or the second identifier.

7. The method according to claim 1, wherein The second result includes one or more of a cumulative time associated with the continuous data collection and a data collection configuration, The third MDT configuration is determined based on one or more of the accumulated time and the data collection configuration.

8. A method performed by a first node in a wireless communication system, comprising: Sending a second minimization of drive tests (MDT) configuration and second information to a user equipment (UE), where the second information includes information related to continuous data collection associated with the second MDT configuration; sending a first MDT configuration and first information to the UE, where the first information includes information related to the continuous data collection; as well as A first MDT report associated with the first MDT configuration and a first result associated with the continuous data collection are received from the UE.

9. The method according to claim 8, further comprising: One or more of the second MDT configuration, the second information, the first MDT configuration, and the first information are received from a core network node.

10. A method performed by a second node in a wireless communication system, comprising: receiving, from a user equipment (UE), a second MDT report associated with a second minimization of drive tests (MDT) configuration sent by the first node to the UE and a second result associated with continuous data collection; as well as A third MDT configuration and third information are sent to the UE, where the third information includes information indicating that the third MDT configuration is associated with the second MDT configuration and / or the first node.

11. The method according to claim 10, further comprising: receiving, from the UE, fourth information regarding availability of a second MDT report associated with the second MDT configuration and reporting information related to the continuous data collection; and sending a request for a second MDT report associated with the second MDT configuration and a second result associated with the continuous data collection to the UE, The request is sent from the second node based on the reported information.

12. The method according to claim 10, further comprising: A third MDT report associated with the third MDT configuration and a third result associated with continuous data collection are received from the UE.

13. The method according to claim 10, further comprising: One or more of the third MDT configuration and the third information is received from a core network node.

14. The method according to claim 12, wherein: Each of the second result and the third result includes a first identifier of the UE associated with the continuous data collection and / or a second identifier of an initial configuration node for the continuous data collection, The second MDT report and the third MDT report are associated through the first identifier and / or the second identifier.

15. The method according to claim 10, wherein The second result includes one or more of a cumulative time associated with the continuous data collection and a data collection configuration, The third MDT configuration is determined based on one or more of the accumulated time and the data collection configuration.

Images