Method and apparatus for supporting data collection in wireless communication
The method enables continuous data collection in wireless communication systems by allowing UE and nodes to exchange configuration information and prioritize data collection, addressing the complexity of RRC state transitions and enhancing data collection efficiency.
Patent Information
- Application Number
- PCT/KR2026/005691
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-04-29
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems face challenges in efficiently and adaptively collecting data without distinguishing the Radio Resource Control (RRC) state of user equipment (UE), leading to complexity in data collection processes.
A method and apparatus that enable data collection by user equipment (UE) and nodes in a wireless communication system, allowing for configuration information exchange and selection based on priorities, enabling continuous data collection regardless of RRC state changes.
This approach simplifies and enhances the versatility of data collection processes by allowing seamless transitions and adaptations in RRC states, reducing complexity and improving data collection efficiency.
Smart Images

Figure KR2026005691_12112026_PF_FP_ABST
Abstract
Description
METHOD AND APPARATUS FOR SUPPORTING DATA COLLECTION IN WIRELESS COMMUNICATION
[0001] The present disclosure relates to a technical field of wireless communication, and more specifically, to a node and a user equipment in a wireless communication system and methods performed by the same.
[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.
[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.
[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.
[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.
[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.
[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.
[0008] In order to meet an increasing demand for wireless data communication services since a deployment of 4G communication system, efforts have been made to develop an improved 5G or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called "beyond 4G network" or "post LTE system".
[0009] Wireless communication is one of the most successful innovations in modern history. Recently, a number of subscribers of wireless communication services has exceeded 5 billion, and it continues growing rapidly. With the increasing popularity of smart phones and other mobile data devices (such as tablet computers, notebook computers, netbooks, e-book readers and machine-type devices) in consumers and enterprises, a demand for wireless data services is growing rapidly. In order to meet rapid growth of mobile data services and support new applications and deployments, it is very important to improve efficiency and coverage of wireless interfaces.
[0010] Embodiments of the present disclosure provide a method performed by a user equipment (UE) in a wireless communication system, including: receiving first information related to data collection from a first node, wherein the first information includes first configuration information for the data collection and a first priority of the first configuration information; performing the data collection based on the first configuration information; connecting to a second node; receiving second information related to the data collection from the second node, wherein the second information includes second configuration information for the data collection and a second priority of the second configuration information; and transmitting fourth information including a data collection result related to the data collection to the second node, wherein the data collection result includes at least one of a first data collection result generated by the UE based on the first configuration information before connecting to the second node and a second data collection result generated by the UE based on configuration information selected by the UE after connecting to the second node.
[0011] According to embodiments of the present disclosure, the configuration information selected by the UE is selected from the first configuration information and the second configuration information based on the first priority and the second priority.
[0012] According to embodiments of the present disclosure, the method further includes: transmitting third information related to reporting of the data collection to the second node, wherein the third information includes the configuration information selected by the UE and a reason for selecting the configuration information.
[0013] According to embodiments of the present disclosure, the first information further includes at least one of: a radio resource control (RRC) state corresponding to the first configuration information, information related to whether the data collection is data collection triggered by a radio access network (RAN) node, identification information of a configuration node of the first configuration information, identification information of a reporting node of a data collection result corresponding to the first configuration information.
[0014] According to embodiments of the present disclosure, the fourth information further includes at least one of: time information related to a change of an RRC state of the UE, indication information related to a change of an RRC state of the UE, a radio resource control (RRC) state corresponding to the data collection result, time information corresponding to the data collection result, and a reason why the data collection ends.
[0015] According to embodiments of the present disclosure, the third information further includes at least one of: information about ongoing data collection by the UE, information about whether the UE supports new data collection, information about whether the data collection result is a result of data collection triggered by a radio access network (RAN) node, identification information of a reporting node of the data collection result.
[0016] Embodiments of the present disclosure provide a method performed by a second node in a wireless communication system, including: transmitting second information related to data collection to a user equipment (UE), wherein the second information includes second configuration information for the data collection and a second priority of the second configuration information; and receiving fourth information including a data collection result related to the data collection from the UE, wherein the data collection result includes at least one of a first data collection result generated by the UE based on first configuration information for the data collection before connecting to the second node and a second data collection result generated by the UE based on configuration information selected by the UE after connecting to the second node, wherein the first configuration information and a first priority of the first configuration information are included in first information related to the data collection received by the UE from a first node.
[0017] According to embodiments of the present disclosure, the configuration information selected by the UE is selected from the first configuration information and the second configuration information based on the first priority and the second priority.
[0018] According to embodiments of the present disclosure, the method further includes: receiving third information related to reporting of the data collection from the UE, wherein the third information includes the configuration information selected by the UE and a reason for selecting the configuration information.
[0019] According to embodiments of the present disclosure, the first information further includes at least one of: a radio resource control (RRC) state corresponding to the first configuration information, information related to whether the data collection is data collection triggered by a radio access network (RAN) node, identification information of a configuration node of the first configuration information, identification information of a reporting node of a data collection result corresponding to the first configuration information.
[0020] According to embodiments of the present disclosure, the fourth information further includes at least one of: time information related to a change of an RRC state of the UE, indication information related to a change of an RRC state of the UE, a radio resource control (RRC) state corresponding to the data collection result, time information corresponding to the data collection result, and a reason why the data collection ends.
[0021] According to embodiments of the present disclosure, the third information further includes at least one of: information about ongoing data collection by the UE, information about whether the UE supports new data collection, information about whether the data collection result is a result of data collection triggered by a radio access network (RAN) node, identification information of a reporting node of the data collection result.
[0022] According to embodiments of the present disclosure, the information about whether the data collection result is a result of data collection triggered by a radio access network (RAN) node further includes identification information of the RAN node triggering the data collection, wherein the method further includes: in case the data collection result is a result of data collection triggered by a radio access network (RAN) node, transmitting the data collection result to the RAN node and / or the reporting node based on identification information of the RAN node and / or the identification information of the reporting node of the data collection result.
[0023] Embodiments of the present disclosure provide a method performed by a first node in a wireless communication system, including: transmitting first information related to data collection to a user equipment (UE), wherein the first information includes first configuration information for the data collection and a first priority of the first configuration information; and receiving a result of the data collection based on the first configuration from the UE, wherein second information related to the data collection is transmitted from a second node to the UE after the UE connects to the second node, wherein the second information includes second configuration information for the data collection and a second priority of the second configuration information; wherein fourth information including a data collection result related to the data collection is transmitted from the UE to the second node, wherein the data collection result includes at least one of a first data collection result generated by the UE based on the first configuration information before connecting to the second node and a second data collection result generated by the UE based on configuration information selected by the UE after connecting to the second node.
[0024] According to embodiments of the present disclosure, the configuration information selected by the UE is selected from the first configuration information and the second configuration information based on the first priority and the second priority.
[0025] According to embodiments of the present disclosure, the first information further includes at least one of: a radio resource control (RRC) state corresponding to the first configuration information, information related to whether the data collection is data collection triggered by a radio access network (RAN) node, identification information of a configuration node of the first configuration information, identification information of a reporting node of a data collection result corresponding to the first configuration information.
[0026] According to embodiments of the present disclosure, the fourth information further includes at least one of: time information related to a change of an RRC state of the UE, indication information related to a change of an RRC state of the UE, a radio resource control (RRC) state corresponding to the data collection result, time information corresponding to the data collection result, and a reason why the data collection ends.
[0027] Embodiments of the present disclosure provide a node device in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform methods performed by any node in a wireless communication system according to embodiments of the present disclosure.
[0028] Embodiments of the present disclosure provide a user equipment (UE) in a wireless communication system, including: a transceiver configured to transmit and receive signals; and a processor coupled to the transceiver and configured to perform methods performed by a user equipment (UE) in a wireless communication system according to embodiments of the present disclosure.
[0029] Embodiments of the present disclosure provide a computer-readable medium having stored thereon computer-readable instructions which, when executed by a processor, perform methods performed by any node and / or a user equipment in a wireless communication system according to embodiments of the present disclosure.
[0030] The present disclosure provides methods performed by a node and / or user equipment (UE) in a wireless communication system, which, by exchanging configuration information related to data collection and / or information related to ongoing data collection by the UE, etc. between nodes and / or user equipment (UE), enables (continuous) data collection without distinguishing an RRC state of the UE.
[0031] The objective of the present disclosure is to support data collection.
[0032] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the present disclosure and are not intended to be restrictive thereof.
[0033] The above and other aspects, features and advantages of certain embodiments of the present disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:
[0034] FIG. 1 is an exemplary system architecture of System Architecture Evolution (SAE);
[0035] FIG. 2 is an exemplary system architecture according to various embodiments of the present disclosure;
[0036] FIG. 3 shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0037] FIG. 4A shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0038] FIG. 4B each shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0039] FIG. 4C shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0040] FIG. 4D shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0041] FIG. 4E shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0042] FIG. 4F shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0043] FIG. 4G shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0044] FIG. 5A shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0045] FIG. 5B shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0046] FIG. 5C shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0047] FIG. 6A shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0048] FIG. 6B shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0049] FIG. 6C shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0050] FIG. 6D shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure;
[0051] FIG. 7 shows a flowchart of a method performed by a user equipment (UE) in a wireless communication system according to embodiments of the present disclosure;
[0052] FIG. 8A shows a flowchart of a method performed by a second node in a wireless communication system according to embodiments of the present disclosure;
[0053] FIG. 8B shows a flowchart of a method performed by a first node in a wireless communication system according to embodiments of the present disclosure;
[0054] FIG. 9 shows a schematic diagram of a node according to embodiments of the present disclosure; and
[0055] FIG. 10 shows a schematic diagram of a user equipment (UE) according to embodiments of the present disclosure.
[0056] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.
[0057] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustration purpose only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.
[0058] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.
[0059] The term "include" or "may include" refers to the existence of a corresponding disclosed function, operation or component which can be used in various embodiments of the present disclosure and does not limit one or more additional functions, operations, or components. The terms such as "include" and / or "have" may be construed to denote a certain characteristic, number, step, operation, constituent element, component or a combination thereof, but may not be construed to exclude the existence of or a possibility of addition of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.
[0060] The term "or" used in various embodiments of the present disclosure includes any or all of combinations of listed words. For example, the expression "A or B" may include A, may include B, or may include both A and B.
[0061] Unless defined differently, all terms used herein, which include technical terminologies or scientific terminologies, have the same meaning as that understood by a person skilled in the art to which the present disclosure belongs. Such terms as those defined in a generally used dictionary are to be interpreted to have the meanings equal to the contextual meanings in the relevant field of art, and are not to be interpreted to have ideal or excessively formal meanings unless clearly defined in the present disclosure.
[0062] FIGs. discussed below and various embodiments for describing the principles of the present disclosure in this patent document are only for illustration and should not be interpreted as limiting the scope of the present disclosure in any way. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.
[0063] FIG. 1 is an exemplary system architecture 100 of system architecture evolution (SAE). User equipment (UE) 101 is a terminal device for receiving data. An evolved universal terrestrial radio access network (E-UTRAN) 102 is a radio access network, which includes a macro base station (eNodeB / NodeB) that provides UE with interfaces to access the radio network. A mobility management entity (MME) 103 is responsible for managing mobility context, session context and security information of the UE. A serving gateway (SGW) 104 mainly provides functions of user plane, and the MME 103 and the SGW 104 may be in the same physical entity. A packet data network gateway (PGW) 105 is responsible for functions of charging, lawful interception, etc., and may be in the same physical entity as the SGW 104. A policy and charging rules function entity (PCRF) 106 provides Quality of Service (QoS) policies and charging criteria. A general packet radio service support node (SGSN) 108 is a network node device that provides routing for data transmission in a universal mobile telecommunications system (UMTS). A home subscriber server (HSS)109 is a home subsystem of the UE, and is responsible for protecting user information including a current location of the user equipment, an address of a serving node, user security information, and packet data context of the user equipment, etc.
[0064] FIG. 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of the present disclosure.
[0065] User equipment (UE) 201 is a terminal device for receiving data. A next generation radio access network (NG-RAN) 202 is a radio access network, which includes a base station (a gNB or an eNB connected to 5G core network 5GC, and the eNB connected to the 5GC is also called ng-gNB) that provides UE with interfaces to access the radio network. An access control and mobility management function entity (AMF) 203 is responsible for managing mobility context and security information of the UE. A user plane function entity (UPF) 204 mainly provides functions of user plane. A session management function entity SMF 205 is responsible for session management. A data network (DN) 206 includes, for example, services of operators, access of Internet and service of third parties.
[0066] Nodes and / or entities 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 nodes or network logic units, and cells and / or beams and / or slices managed by them, etc.
[0067] In the present disclosure, a node may refer to any node, and may also refer to a cell and / or beam managed by the node, etc.
[0068] In the present disclosure, a cell may refer to any cell, or a node where the cell is located, or a beam corresponding to the cell, etc.
[0069] Information and / or field described in the present disclosure may be an average value, an instantaneous value, the maximum value, the minimum value, etc., of the corresponding information and / or field and / or parameter and / or numerical value, etc., which is not limited herein.
[0070] Information and / or field described in the present disclosure may correspond to one or more of the following cases: uplink, downlink, uplink and downlink, uplink or downlink.
[0071] Information and / or field described in the present disclosure may be a measured value and / or an actual value and / or a predicted value of the corresponding information and / or field and / or parameter and / or numerical value, etc.
[0072] The signal strength and / or signal quality and / or measurement report result and / or measurement result described in the present disclosure may be Received Signal Strength Indicator (RSSI), Reference Signal Receiving Power (RSRP), Reference Signal Receiving Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), etc.
[0073] In the present disclosure, the slice identification may be represented by one or more Single Network Slice Selection Assistance Information (S-NSSAI).
[0074] In the present disclosure, failure type, and / or problem type, and / or report type may refer to each other.
[0075] In the present disclosure, self-optimization network (SON) related reports may include one or more of the following: a Connection Establishment Failure (CEF) report, a Random Access report, a Successful Handover report, a Radio Link Failure (RLF) report, a measurement report, or other radio connection related report.
[0076] In the present disclosure, radio link failure may refer to two cases: radio link failure and handover failure.
[0077] In the present disclosure, a TA value acquired in advance and a TA value in an LTM command may refer to each other.
[0078] Network self-optimization decisions may include network energy saving, load balancing, coverage and / or capacity optimization, mobility optimization and / or management, making and / or updating configurations, etc.
[0079] In the present disclosure, results and reports may be referred to each other.
[0080] In the present disclosure, time can be represented by one or more of the following: timestamp, time point, time window, timer, period of time, time length, time period, time interval, duration, etc. The time length may be the length of time from a certain time point, which may be the current time or any other time point. The time may be a relative time or an absolute time. In some implementations, the period of time may be represented by separate fields, for example, by a combination of a start time and an end time, or by a combination of a start time and a time period.
[0081] 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 playback delay, Playout Delay at Initial Startup, Device Information, Rendered viewports, Codec information, Buffer level, Representation switch events, Play List, MPD (Media presentation description) Information, Interactivity Summary, Interactivity Event List, etc.
[0082] In the present disclosure, Quality of Service (QoS) parameters may include at least one of the following: packet loss rate, latency, throughput, data rate, etc.
[0083] In the present disclosure, load condition and / or load information may include one or more of the following: Physical Resource Block (PRB) usage ratio, number of available PRBs, number of allocated PRBs, scheduled PDCCH CCE usage, Transport Network Layer (TNL) capacity indication, radio resource status, comprehensive available capacity group, comprehensive available resource group, number of active user terminals, number of Radio Resource Control (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 Receiving Quality (RSRQ) measurement report, Signal to Interference plus Noise Ratio (SINR) measurement report, Channel State Information (CSI) report, cell report indication, Channel Occupancy time ratio, Energy Detection threshold, signal strength and / or signal quality, channel busy ratio, data volume, and Jitter of each of the above parameters, etc.
[0084] In the present disclosure, load condition and / or load information may be referred to with resource status interchangeably.
[0085] In the present disclosure, capacity information may include one or more of the following: QoS requirement, QoS class, capacity status, average QoS requirement, average QoS class, average capacity status identifier, the proportion of one or more QoS requirements, the proportion of one or more QoS classes, the proportion of one and / or more capacity status identifiers, etc. Herein, the capacity status identifier is an identifier indicating a capacity configuration, where one identifier may represent one capacity configuration. The QoS class may be represented by an identifier, which may be, for example, a mapped 5G QoS Identifier (5QI) or a QoS Class Identifier (QCI).
[0086] In the present disclosure, capacity prediction information may be a predicted value of capacity information.
[0087] In the present disclosure, coverage information may include one or more of the following: coverage status, information related to coverage increase and / or decrease, proportion of coverage increase and / or decrease, information related to load located at cell edge, information related to load that changes from being located in coverage to being located out of coverage due to coverage changes, etc. Herein, the coverage status may be represented by an identifier, and one identifier represents one coverage status.
[0088] In the present disclosure, coverage may be referred to interchangeably with coverage range.
[0089] In the present disclosure, coverage prediction information may be a predicted value of coverage information.
[0090] In the present disclosure, coverage and / or capacity change, and, coverage and / or capacity optimization may refer to each other.
[0091] In the present disclosure, coverage and / or capacity policy (information) may include one or more of the following related to coverage and / or capacity: cell identifier, cell status, cell deployment status indication, replacing cell information, beam coverage change information, reason for coverage change, etc. The replacing cell information may include one or more of the following: identifier of a replacing cell, identifier of a replaced cell, the proportion of the replacing cells that can replace the replaced cells, etc. The beam coverage change information may include one or more of the following: beam identifier, beam coverage status, etc.
[0092] In the present disclosure, a beam may refer to a Synchronization Signal and Physical Broadcast Channel (PBCH) block (SSB) beam, or any other beam.
[0093] In the present disclosure, a location and / or location range may be represented by one or more of the following: coordinates, an area, a cell identifier, a beam identifier, an identifier used to represent a location and / or an area, etc. The cell identifier may include one or more of the following: a visited cell identifier, a connecting cell identifier, a serving cell identifier, etc. The beam identifier may include one or more of the following: a visited beam identifier, a connecting beam identifier, an accessing beam identifier, etc. The identifier used to represent a location and / or an area may be used to represent a certain location or locations and / or a certain area or areas. In some implementations, for example, an area whose distance is greater than and / or equal to and / or less than a certain threshold may be represented by an identifier. In some other implementations, for example, an area where the signal quality is greater than and / or equal to and / or less than a certain threshold may be represented by an identifier.
[0094] In the present disclosure, a target node may also be a candidate target node, a target master node, a target secondary node, a candidate target master node, a candidate target secondary node, etc.
[0095] In the present disclosure, a source node may also be a source master node, a source secondary node, etc.
[0096] In the present disclosure, data collection may be Minimization of Drive Tests (MDT) or any other data collection, which is not limited herein. The MDT may be logged MDT or immediate MDT. The MDT may be signalling-based MDT or management-based MDT. When a UE connects to another base station from a base station, (continuous) data collection is required. However, the existing technology has insufficient research on (continuous) data collection.
[0097] In the present disclosure, a base station may refer to any device in a radio access network that can connect with a user equipment, such as a gNB in a 5G network or a base station or node in any other network.
[0098] In the present disclosure, data collection may include continuous data collection or discontinuous data collection.
[0099] In the present disclosure, (continuous) data collection may refer to data collection by the UE without distinguishing the RRC state of the UE. That is, (continuous) data collection means that after the RRC state is changed, the UE can still perform data collection according to a previous configuration, and / or perform data collection continuously according to a new configuration.
[0100] In the present disclosure, collection may be referred to interchangeably with measurement. Data collection may be referred to interchangeably with data measurement.
[0101] In the present disclosure, the Radio Resource Control (RRC) state may include one or more of the following: RRC connected state, RRC idle state, RRC inactive state, and the like. The RRC state in the present disclosure may also be extended to a Connection Management (CM) state. For example, the methods applicable to the RRC state of the UE in the present disclosure can also be applicable to the CM state of the UE. In the present disclosure, the CM state may include one or more of the following: CM connected state, CM idle state, etc. The RRC state may refer to the RRC state of the UE. The CM state may refer to the CM state of the UE.
[0102] In the present disclosure, data corresponding to the data collection may include one or more of the following:
[0103] - MDT related data, which may include one or more of the following:
[0104] o User ID
[0105] o Measurement result
[0106] o Location information
[0107] o Power headroom
[0108] o PDCP SDU data volume
[0109] o (Average) UE throughput
[0110] o Packet delay
[0111] o Measurement result of a serving cell
[0112] o Measurement result of a neighbor cell
[0113] o Time stamp
[0114] - User trajectory related data, which may include one or more of the following:
[0115] o User ID
[0116] o Identifier of a visited cell
[0117] o Identifier of a visited primary cell
[0118] o Identifier of a visited secondary cell
[0119] o Identifier of a visited primary cell and identifier of a visited secondary cell, which indicate a visited primary cell and a visited secondary cell by the user in the case of dual-connectivity.
[0120] o Node where the visited cell is located, which may be a node identifier or a node name.
[0121] o Node where the visited primary cell is located, which may be a node identifier or a node name.
[0122] o Node where the visited secondary cell is located, which may be a node identifier or a node name.
[0123] o Visit time and / or stay time
[0124] o Coordinate
[0125] o Information of a visited beam, which may be a beam identifier.
[0126] - User performance related data, which may include one or more of the following:
[0127] o User ID
[0128] o Collection time for the user performance
[0129] o Node corresponding to collection of the user performance, which may be a node identifier or a node name.
[0130] o Cell ID corresponding to the user performance
[0131] o Beam ID corresponding to the user performance
[0132] o Slice ID corresponding to the user performance
[0133] o Packet Data Unit (PDU) session ID corresponding to the user performance
[0134] o Data Radio Bearer (DRB) ID corresponding to the user performance
[0135] o QoS Flow Identifier corresponding to the user performance
[0136] o User performance, which may include one or more of the following: uplink and / or downlink data rate, uplink and / or downlink throughput, uplink and / or downlink delay, uplink and / or downlink packet loss rate, uplink and / or downlink QoE parameters.
[0137] - Network performance related data, which may include one or more of the following:
[0138] o Collection time of the network performance
[0139] o Node corresponding to collection of the network performance, which may be a node identifier or a node name.
[0140] o Cell ID corresponding to the network performance
[0141] o Beam ID corresponding to the network performance
[0142] o Slice ID corresponding to the network performance
[0143] o Data Radio Bearer (DRB) ID corresponding to the network performance
[0144] o QoS Flow Identifier corresponding to the network performance
[0145] o Network performance, which may include one or more of the following: uplink and / or downlink data rate, uplink and / or downlink throughput, uplink and / or downlink delay, uplink and / or downlink packet loss rate, uplink and / or downlink QoE parameters.
[0146] - Information of a user measurement result, which may include one or more of the following:
[0147] o User ID
[0148] o Node ID and / or cell ID corresponding to the user measurement result
[0149] o Measurement result
[0150] o Measurement time
[0151] - Information of a perception related result, which may include one or more of the following:
[0152] o User ID
[0153] o Node ID and / or cell ID corresponding to a user perception related measurement result
[0154] o Perception related measurement result
[0155] o Perception related measurement time
[0156] In the present disclosure, user equipment (UE), user, terminal and the like may refer to each other.
[0157] In the present disclosure, "related to" or "associated with" and the like may also mean "including" and they may be used interchangeably. For example, a first message related to / associated with first information may also represent a first message including the first information, and so on.
[0158] The support of existing technologies for data collection (e.g., Minimization of Drive Tests) is complex, so a simple and highly adaptable solution is required.
[0159]
[0160] Example 1
[0161] An aspect of the present disclosure proposes a method for supporting (continuous) data collection, which may include one or more of the following steps.
[0162] A first node transmits a first message including configuration information related to (continuous) data collection (or referred to as information related to (continuous) data collection) to a second node to inform the second node of the configuration information related to (continuous) data collection. The second node performs (continuous) data collection according to the configuration information related to (continuous) data collection, and / or the second node decides whether to perform (continuous) data collection according to the configuration information related to (continuous) data collection, and / or, the second node selects and / or configures the UE to perform (continuous) data collection after receiving the configuration information related to (continuous) data collection, and / or the UE decides whether to perform (continuous) data collection based on the configuration information related to (continuous) data collection, etc. This solution can support data collection without distinguishing the RRC state of the UE, so as to reduce the complexity of data collection configuration and achieve highly versatile data collection.
[0163] In some implementations, the first message may be included in one or more of the following: a Handover Request message or a S-NODE ADDITION REQUEST message or a S-NODE MODIFICATION REQUEST message or a NG-RAN NODE CONFIGURATION UPDATE message or a NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message or a Xn SETUP REQUEST message or a XN SETUP RESPONSE message or a RETRIEVE UE CONTEXT RESPONSE message of Xn; or a UE CONTEXT RELEASE REQUEST message or a UE CONTEXT MODIFICATION REQUEST message or a UE CONTEXT MODIFICATION RESPONSE message or an INITIAL CONTEXT SETUP REQUEST message of NG; or an 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.
[0164] In some implementations, the first message may include one or more of the following information and / or fields:
[0165] - Transmitting node identifier (identification / ID): used to identify the node that transmits the message.
[0166] - Receiving node ID: used to identify the node that receives the message.
[0167] - Request identification: used to identify a request corresponding to the message.
[0168] - Measurement identification: used to identify a measurement corresponding to the message.
[0169] - Prediction identification: used to identify a prediction corresponding to the message.
[0170] - Reporting identification: used to identify a reporting corresponding to the message.
[0171] - Configuration identification: used to identify a configuration for (continuous) data collection corresponding to the message. This identification may uniquely identify a data collection configuration. For example, the configuration may be an MDT configuration or a continuous MDT configuration. For example, the configuration may be for one or more of an RRC idle state, an RRC inactive state, an RRC connected state. For example, the configuration may be independent of the RRC state of the UE. That is, the UE can perform data collection according to this configuration in any RRC state.
[0172] - (Continuous) data collection (request) identification: used to indicate that the information contains (continuous) data collection (request). In some implementations, for example, after the message receiving node receives the information, the information may trigger the message receiving node to perform (continuous) data collection. In other implementations, for example, the information may only inform the message receiving node of the configuration and / or information corresponding to (continuous) data collection, without triggering the message receiving node to perform (continuous) data collection. In yet other implementations, for example, the information may trigger the message receiving node to configure (continuous) data collection for a corresponding user, or may trigger the message receiving node to configure (continuous) data collection for a corresponding user according to the information in the message. In yet other implementations, for example, the information may indicate that anonymization is not required for the data collection and / or the reporting of data collection results.
[0173] - Collection time for (continuous) data collection: used to represent the collection time for (continuous) data collection.
[0174] - Start indication of (continuous) data collection: used to indicate the start of (continuous) data collection. In some implementations, for example, after receiving the indication, the message receiving node may start (continuous) data collection, or configure the UE to start (continuous) data collection. In yet other implementations, for example, after receiving the indication, the message receiving node may assign a first identifier, and / or configure the first identifier and / or an identifier of the node and / or cell corresponding to the start of (continuous) data collection and / or an identifier of the node and / or cell corresponding to an initial configuration for (continuous) data collection to the UE. In yet other implementations, for example, after receiving the indication, the UE starts timing the (continuous) data collection. For example, the UE may transmit an accumulated time of the (continuous) data collection to the node to which the UE is connected, for the node to which the UE is connected to configure subsequent data collection.
[0175] - Start time of (continuous) data collection: used to indicate the start time of (continuous) data collection. In some implementations, for example, the message receiving node may perform data collection at the start time of (continuous) data collection. In other implementations, for example, the message receiving node may configure (continuous) data collection for the UE at the start time of (continuous) data collection.
[0176] - End indication of (continuous) data collection: 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 it may configure the UE to stop (continuous) data collection.
[0177] - End time of (continuous) data collection: used to indicate the end time of (continuous) data collection. In some implementations, for example, after receiving the end time, the message receiving node may stop (continuous) data collection at the end time, or may configure the UE to stop (continuous) data collection at the end time.
[0178] - Time of (continuous) data collection: used to indicate the time information of (continuous) data collection. In some implementations, for example, after the message receiving node receives the time of the (continuous) data collection, it may only perform data collection within the time of the (continuous) data collection, or it may configure the UE to perform data collection within the time of the (continuous) data collection. In some implementations, the time of (continuous) data collection may also be the reporting time of the results of the (continuous) data collection.
[0179] - Remaining time of (continuous) data collection: used to indicate the time when (continuous) data collection is still required. In some implementations, for example, after receiving the information, the message receiving node performs data collection within the remaining time of (continuous) data collection, or it may configure the UE within the remaining time of (continuous) data collection to perform data collection, or it may configure the UE to perform data collection within the remaining time of (continuous) data collection. For example, if the remaining time of (continuous) data collection is equal to or less than a threshold, the message receiving node may not perform data collection, and / or not configure the UE to perform data collection. For example, the threshold may be 0 or any other value. For example, if the remaining time of (continuous) data collection is equal to or greater than a threshold, the message receiving node may perform data collection, and / or configure the UE to perform data collection.
[0180] - Accumulated time of (continuous) data collection: used to indicate the time for which (continuous) data collection has been performed. In some implementations, for example, the message receiving node may decide whether to continue to configure subsequent data collection based on the time of (continuous) data collection and / or the accumulated time of (continuous) data collection. For example, if the value of the time of (continuous) data collection minus the accumulated time of (continuous) data collection is equal to and / or greater than a threshold, the message receiving node may perform data collection, and / or configure the UE to perform data collection. For example, if the value of the time of (continuous) data collection minus the accumulated time of (continuous) data collection is equal to and / or less than a threshold, the message receiving node may not perform data collection, and / or not configure the UE to perform data collection. For example, the threshold may be 0 or any other value. In yet other implementations, the message receiving node may continue to configure subsequent data collection based on the time of (continuous) data collection and / or the accumulated time of (continuous) data collection, to achieve (continuous) data collection. For example, the message receiving node may configure to perform data collection within a first time. Herein, the first time may be the value of the time of (continuous) data collection minus the accumulated time of (continuous) data collection.
[0181] - Cell corresponding to (continuous) data collection: which may indicate cell information corresponding to (continuous) data collection. For example, the information may include one or more of the following: cell identifier and / or cell identifier list, and number of cells. In some implementations, for example, the (continuous) data collection is performed within the cells corresponding to the cell identifier and / or cell identifier list. In other implementations, for example, when the number of cells corresponding to the completed (continuous) data collection and / or data collection results reaches the number of cells, the (continuous) data collection should be stopped.
[0182] - Node corresponding to (continuous) data collection: which may indicate node information corresponding to (continuous) data collection. For example, the information may include one or more of the following: node identifier and / or node identifier list, number of nodes, etc. In some implementations, for example, the (continuous) data collection is performed within the nodes corresponding to the node identifier and / or node identifier list. In other implementations, for example, when the number of nodes corresponding to the completed (continuous) data collection and / or data collection results reaches the number of nodes, the (continuous) data collection should be stopped.
[0183] - PLMN information corresponding to (continuous) data collection: which may indicate the PLMN information corresponding to (continuous) data collection. For example, the information may include one or more of the following: PLMN and / or PLMN list, number of PLMNs, etc. In some implementations, for example, the (continuous) data collection is performed within the PLMNs corresponding to the PLMN and / or PLMN list. In other implementations, for example, when the number of PLMNs corresponding to the completed (continuous) data collection and / or data collection results reaches the number of PLMNs, the (continuous) data collection should be stopped.
[0184] - Slice information corresponding to (continuous) data collection: which may indicate slice information corresponding to (continuous) data collection. For example, the information may include one or more of the following: slice identifier and / or slice identifier list, and number of slices. In some implementations, for example, the (continuous) data collection is performed within the slices corresponding to the slice identifier and / or slice identifier list. In other implementations, for example, when the number of slices corresponding to the completed (continuous) data collection and / or data collection results reaches the number of slices, the (continuous) data collection should be stopped. The slice identifier may be represented by Single Network Slice Selection Assistance Information (S-NSSAI).
[0185] - Beam information corresponding to (continuous) data collection: which may indicate beam information corresponding to (continuous) data collection. For example, the information may include one or more of the following: beam identifier and / or beam identifier list, and number of beams. In some implementations, for example, the (continuous) data collection is performed within the beams corresponding to the beam identifier and / or the beam identifier list. In other implementations, for example, when the number of beams corresponding to the completed (continuous) data collection and / or data collection results reaches the number of beams, the (continuous) data collection should be stopped. For example, the beam may be an SSB beam or any other beam. In some implementations, for example, this information may be used for the message receiving node to determine whether to continue configuring (continuous) data collection, and / or, if it is determined to continue configuring (continuous) data collection, this information may be used to determine corresponding configuration information.
[0186] - First identifier: used to identify the collection corresponding to the message. For example, the identifier may be a random number. In some implementations, for example, during a (continuous) data collection process, the first identifier of a UE is the same. In other implementations, for example, the first identifier may be configured by the node and / or cell corresponding to the start of the (continuous) data collection and / or configured by the node and / or cell corresponding to the initial configuration for the (continuous) data collection.
[0187] - Identifier of node and / or cell corresponding to the start of (continuous) data collection and / or the initial configuration for (continuous) data collection: used to indicate the identifier of the node and / or cell corresponding to the start of the (continuous) data collection, or the identifier of the first node and / or cell that configures the (continuous) data collection for the UE. In some implementations, for example, this node and / or cell identifier and the first identifier may uniquely identify a UE and / or a UE corresponding to a data collection report in the network.
[0188] - (Continuous) data collection dedicated TR and / or TRSR: in some implementations, the dedicated TR and / or TRSR does not change during a (continuous) data collection process. For example, during a (continuous) data collection process, the dedicated TR and / or TRSR of the same UE does not change. In some implementations, for example, the node may associate multiple (continuous) data collection configurations and / or multiple data collection results of the same UE through the dedicated TR and / or TRSR.
[0189] - Association relationship of configurations for (continuous) data collection: used to indicate the association relationship of the configurations for the (continuous) data collection. In some implementations, for example, the association relationship may include that configuration A and configuration B both belong to one (continuous) data collection. A node may configure subsequent data collection according to this association relationship of configurations, to achieve an effect of (continuous) data collection. The association relationship of configurations may be a relationship or a list of relationships. The association relationship may be one or more of the following:
[0190] o Associated TR
[0191] o Associated TRSR
[0192] o Associated data collection configuration identification
[0193] o Associated data collection configuration
[0194] o Identifiers of nodes and / or cells corresponding to the configurations for (continuous) data collection
[0195] - 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 for the UE according to the information. It may include one or more of the following:
[0196] o Registration types for a data collection configuration: which may include one or more of the following: start, stop, pause, add, override, new configuration, release, cancel, etc. Herein, 'start' indicates starting data collection. 'Stop' indicates stopping data collection. In some implementations, for example, 'stop' may also indicate releasing a data collection configuration. 'Pause' indicates temporarily stopping data collection. In some implementations, for example, 'pause' may also indicate not releasing a data collection configuration. For example, the data collection configuration may be used for subsequent data collection. 'Add' indicates adding a new data collection configuration to the original data collection configuration. 'Override' indicates that the data collection configuration is a data collection configuration to be applied. In some implementations, for example, 'override' may also indicate that the original data collection configuration is no longer valid. 'New configuration' indicates that the data collection configuration is a new data collection configuration, for example, unrelated to the original data collection configuration. For example, 'new configuration' may also indicate that the data collection configuration and the original data collection configuration are two separate configurations. The message receiving node and / or the UE need to perform data collection according to the original data collection configuration and / or the new data collection configuration. 'Release' indicates that the data collection configuration needs to be released. The message receiving node and / or the UE no longer perform data collection according to the data collection configuration. 'Cancel' indicates cancelling the data collection configuration. The message receiving node and / or the UE no longer perform data collection according to the data collection configuration.
[0197] o Priority: used to indicate a priority of a data collection configuration and / or data collection. In some implementations, for example, the message receiving node and / or the UE may select an appropriate data collection configuration for data collection based on this information, for example, a data collection configuration with a high priority is selected for data collection. For example, when the message receiving node and / or the UE cannot perform data collection according to all received data collection configurations, the message receiving node and / or the UE may select an appropriate data collection configuration for data collection based on this information.
[0198] o RRC state corresponding to data collection: which may indicate RRC states corresponding to a data collection configuration and / or data collection. A data collection configuration and / or data collection may correspond to one or more RRC states, for example, one or more of an RRC connected state, an RRC idle state, an RRC inactive state, etc.
[0199] o Indication of whether it is data collection triggered by RAN: used to indicate whether data collection is RAN-triggered data collection. This information may be used for the reporting of a data collection result. For example, if the data collection is RAN-triggered data collection, the data collection result should be reported to a corresponding RAN node. Alternatively, if the data collection is RAN-triggered data collection, the receiving node of the data collection result needs to forward the data collection result to a corresponding RAN node that triggered the data collection.
[0200] o Indication of whether it is data collection triggered by OAM: used to indicate whether data collection is OAM-triggered data collection.
[0201] o Indication of whether it is data collection triggered by core network: used to indicate whether data collection is core network-triggered data collection. Herein, the core network may include any node in the core network.
[0202] o Identifier of configuration node and / or cell of data collection: used to identify the identifier of the configuration node and / or cell of the data collection (and / or data collection configuration). In some implementations, for example, after a node completes data collection, this information may be added to a message including the data collection result, and the receiving node of the data collection result may forward the data collection result to the corresponding configuration node and / or cell of the data collection. In other implementations, for example, after a node completes data collection, it may report the data collection result to the configuration node and / or cell of the data collection. In some implementations, for example, if a node has a relevant interface with the node and / or cell indicated by the identifier of the configuration node and / or cell of the data collection, the node may subsequently report the data collection result to the configuration node and / or cell of the data collection.
[0203] o Information of collection node and / or cell of data collection: used to represent the relevant information about the collection nodes and / or cells corresponding to the data collection (and / or the data collection results corresponding to the data collection configuration). For example, the information of the collection nodes and / or cells of the data collection may include one or more of the following: the identifiers of the collection nodes and / or cells corresponding to the data collection, the addresses of the collection nodes and / or cells corresponding to the data collection, the names of the collection nodes and / or cells corresponding to the data collection, etc. The identifier of the collection node and / or cell of the data collection may also be referred to as the identifier of the reporting node and / or cell of the data collection. In some implementations, for example, the address of the collection node and / or cell corresponding to the data collection may be the IP address of the collection node and / or cell. The information is used to indicate that the data collection result corresponding to the data collection configuration needs to be reported to the reporting node and / or cell corresponding to the identifier. In some implementations, for example, after a node completes data collection, this information may be added to a message including the data collection result, and the receiving node of the data collection result may forward the data collection result to the corresponding collection node and / or cell of the data collection. In other implementations, for example, after a node completes data collection, it may report the data collection result to the collection node and / or cell of the data collection. In some implementations, for example, if the node has a relevant interface with the node and / or cell indicated by the identifier of the collection node and / or cell of the data collection, the node may subsequently report the data collection result to the configuration node and / or cell of the data collection. In the present disclosure, a collection node / cell of data collection may also be referred to as a reporting node / cell of data collection.
[0204] o Measurement and / or collection item corresponding to data collection: the measurement and / or collection items of the data collection may include one or more of the data corresponding to the above data collection.
[0205] o Data collection configuration identification: used to identify a data collection configuration. The identification may uniquely identify a data collection configuration. For example, the identification may be an MDT configuration identification, which may uniquely determine an MDT configuration. The MDT configuration may include one or more of the data collection configurations described above.
[0206] o Trace Reference (TR): which may include one or more of the following: PLMN ID, Trace ID
[0207] o Trace Recording Session Reference (TRSR)
[0208] o Track Collection Entity ID
[0209] o Absolute time information: the absolute time of the cell. In some implementations, for example, it may be the absolute time of the current cell.
[0210] o Area configuration: which indicates area information for data collection. It may include one or more of the following: cell identifier and / or cell identifier list, PLMN ID, Tracking Area Code, uplink and / or downlink carrier frequencies, etc. The cell identifier may be a physical cell identifier (Physical Cell ID) or a cell global identifier (Cell Global ID).
[0211] o PLMN ID (list): which indicates the IDs of the PLMNs that the UE is configured to perform measurement recording, related status indication, and information acquisition.
[0212] o Bluetooth name (list): which indicates the names (list) of Bluetooth beacons that the UE is configured to measure.
[0213] o WLAN name (list): which indicates the names (list) of WLAN access points that the UE is configured to measure.
[0214] o Sensor name (list): which indicates the name (list) of the sensors that the UE is configured to measure.
[0215] o Recording time: which indicates the time when the UE is required to perform measurement recording.
[0216] o Reporting type: which may include periodic reporting, event triggered reporting, single reporting, etc.
[0217] o Recording interval: which indicates the time period and / or interval for recording the measurement results.
[0218] o Event trigger configuration: including trigger event, threshold, trigger time, hysteresis, etc. The trigger event may be one or more of the following: out-of-coverage, change of RRC state, etc.
[0219] o MDT configuration mode: used to indicate whether the configuration is signalling-based or management-based. The configuration mode also indicates the MDT type configured by the configuration. The MDT type may include one or more of the following: logged MDT, immediate MDT, signalling-based MDT, management-based MDT, and a combination thereof.
[0220] o Early measurement indication: used to indicate whether the UE is allowed to record relevant measurement results for early measurement frequencies.
[0221] o Events and / or conditions that trigger data collection: when the events and / or conditions that trigger data collection are met, data collection is performed. The events and / or conditions may include one or more of the following: end of current data collection, end of a logged MDT, etc. In some implementations, for example, it may be an event and / or condition that triggers an immediate MDT. For example, the event and / or condition that triggers the immediate MDT may be the end of a logged MDT. Therefore, immediate MDT can be started immediately after the logged MDT ends, thereby achieving an effect of (continuous) data collection.
[0222]
[0223] Example 2
[0224] An aspect of the present disclosure proposes a method for supporting (continuous) data collection, which may include one or more of the following steps.
[0225] A third node transmits a second message including all and / or part of (continuous) data collection results to a fourth node to report the all and / or part of (continuous) data collection results to the fourth node. This solution can support data collection without distinguishing the RRC state of the UE, so as to reduce the complexity of data collection configuration and achieve highly versatile data collection.
[0226] In some implementations, the second message may be included in one or more of the following: a RETRIEVE UE CONTEXT REQUEST message or a RETRIEVE UE CONTEXT RESPONSE message of Xn; a 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.
[0227] In some implementations, the second message may include one or more of the following information and / or fields:
[0228] - Transmitting node ID: used to identify the node that transmits the message.
[0229] - Receiving node ID: used to identify the node that receives the message.
[0230] - Measurement identification: used to identify a measurement corresponding to the message. In some implementations, for example, the measurement identification may be consistent with the measurement identification in the first message, so as to associate the reporting message with the configuration message.
[0231] - Request identification: used to identify a request corresponding to the message. In some implementations, for example, the request identification may be consistent with the request identification in the first message, so as to associate the reporting message with the configuration message.
[0232] - Prediction identification: used to identify a prediction corresponding to the message. In some implementations, for example, the prediction identification may be consistent with the prediction identification in the first message, so as to associate the reporting message with the configuration message.
[0233] - Reporting identification: used to identify a reporting corresponding to the message. In some implementations, for example, the reporting identification may be consistent with the reporting identification in the first message, so as to associate the reporting message with the configuration message.
[0234] - Configuration identification: used to identify a measurement and / or prediction and / or reporting configuration corresponding to the message. In some implementations, for example, the configuration identification may be consistent with the configuration identification in the first message, so as to associate the reporting message with the configuration message.
[0235] - Information on whether new data collection is supported: used to indicate whether new data collection is supported. For example, when the node (e.g., message transmitting node) and / or UE can support new data collection, the node (e.g., message receiving node) may configure a new data collection configuration to enable the node (e.g., message transmitting node) and / or UE to perform the new data collection. For example, the node (e.g., message transmitting node) and / or the UE perform data collection according to multiple data collection configurations (e.g., previous data collection configurations and / or new data collection configurations) simultaneously. In some implementations, for example, when node 1 (e.g., message transmitting node) and / or the UE are performing data collection according to a previous data collection configuration, this information may be carried to indicate whether node 1 and / or UE supports new data collection. For example, if node 1 and / or UE can support new data collection, node 2 (for example, message receiving node) may configure node 1 and / or UE with new data collection.
[0236] - (Continuous) data collection configuration: the (continuous) data collection configuration may be one or more of the information in the first message. The (continuous) data collection configuration informs the message receiving node of the configuration of the performed (continuous) data collection. In some implementations, for example, the message receiving node may continue to configure subsequent (continuous) data collection according to this configuration to achieve an effect of (continuous) data collection.
[0237] - Identification of (continuous) data collection configuration: the identification can uniquely identify a (continuous) data collection configuration. For example, the configuration may be an MDT configuration or a continuous MDT configuration. Informing the message receiving node of the configuration corresponding to (continuous) data collection by means of this identification can save signalling. In some implementations, for example, the message receiving node may know the (continuous) data collection configuration and / or MDT configuration through the identification, and may continue to configure subsequent data collection according to the configuration to achieve (continuous) data collection. In yet other implementations, for example, the identification may indicate that anonymization is not required for the data collection and / or the reporting of data collection results.
[0238] - Accumulated time of (continuous) data collection: used to indicate the time for which (continuous) data collection has been performed. In some implementations, for example, the message receiving node may decide whether to continue to configure subsequent data collection based on the time of (continuous) data collection and / or the accumulated time of (continuous) data collection. For example, if the value of the time of (continuous) data collection minus the accumulated time of (continuous) data collection is equal to and / or greater than a threshold, the message receiving node may perform data collection, and / or configure the UE to perform data collection. For example, if the value of the time of (continuous) data collection minus the accumulated time of (continuous) data collection is equal to and / or less than a threshold, the message receiving node may not perform data collection, and / or not configure the UE to perform data collection. For example, the threshold may be 0 or any other value. In yet other implementations, the message receiving node may continue to configure subsequent data collection based on the time of (continuous) data collection and / or the accumulated time of (continuous) data collection, to achieve (continuous) data collection. For example, the message receiving node may configure to perform data collection within a first time. Herein, the first time may be the value of the time of (continuous) data collection minus the accumulated time of (continuous) data collection.
[0239] - Start time of (continuous) data collection: used to indicate the start time of (continuous) data collection. In some implementations, for example, the message receiving node may decide whether to continue configuring subsequent data collection based on the start time of the (continuous) data collection. For example, the message receiving node may configure to perform data collection at a second time, where the second time may be derived from the time of the (continuous) data collection and the start time of the (continuous) data collection, e.g., the second time may be the remaining time of the (continuous) data collection derived from the time of the (continuous) data collection and the start time of the (continuous) data collection.
[0240] - 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.
[0241] - Remaining time of (continuous) data collection: used to indicate the time when (continuous) data collection is still required. In some implementations, for example, after receiving the information, the message receiving node performs data collection within the remaining time of (continuous) data collection, or it may configure the UE within the remaining time of (continuous) data collection to perform data collection, or it may configure the UE to perform data collection within the remaining time of (continuous) data collection. For example, if the remaining time of (continuous) data collection is equal to or less than a threshold, the message receiving node may not perform data collection, and / or not configure the UE to perform data collection. For example, the threshold may be 0 or any other value. For example, if the remaining time of (continuous) data collection is equal to or greater than a threshold, the message receiving node may perform data collection, and / or configure the UE to perform data collection.
[0242] - Information on completed and / or ongoing (continuous) data collection: used to indicate information of completed and / or ongoing (continuous) data collection. This information may include one or more of the following:
[0243] o TR and / or TRSR corresponding to the completed and / or ongoing (continuous) data collection: this information may be a TR and / or TRSR or a group of TRs and / or TRSRs. In some implementations, for example, this information may be used by a node to associate multiple data collection results, resulting in a (continuous) data collection result. For example, this information may be used by a node to associate multiple data collection results measured by the same UE, resulting in a (continuous) data collection result.
[0244] o Information of configuration node and / or cell corresponding to the completed and / or ongoing (continuous) data collection: this information indicates the node and / or cell from which the configuration information of the completed and / or ongoing data collection is obtained. This information may be a node and / or cell information or a list of node and / or cell information. This information may include one or more of the following:
[0245] § Node ID
[0246] § Node Name
[0247] § Cell ID
[0248] o Information corresponding to the completed and / or ongoing (continuous) data collection: which indicates the information corresponding to the completed and / or ongoing (continuous) data collection. In some implementations, for example, this information may be used for the message receiving node to determine whether to continue configuring (continuous) data collection, and / or, if it is determined to continue configuring (continuous) data collection, this information may be used to determine corresponding configuration information. It may include one or more of the following:
[0249] § Identifier and / or identifier list of corresponding cells
[0250] § Number of corresponding cells
[0251] § Identifier and / or identifier list of corresponding nodes
[0252] § Number of corresponding nodes
[0253] § Name and / or name list of corresponding nodes
[0254] § Corresponding PLMN and / or PLMN list
[0255] § Number of corresponding PLMNs
[0256] § Identifier and / or identifier list of corresponding slices
[0257] § Number of corresponding slices
[0258] § Identifier and / or identifier list of corresponding beams
[0259] § Number of corresponding beams
[0260] - Cell corresponding to (continuous) data collection: which may indicate cell information corresponding to (continuous) data collection. For example, the information may include one or more of the following: cell identifier and / or cell identifier list, and number of cells. In some implementations, for example, the (continuous) data collection is performed within the cells corresponding to the cell identifier and / or cell identifier list. In other implementations, for example, when the number of cells corresponding to the completed (continuous) data collection and / or data collection results reaches the number of cells, the (continuous) data collection should be stopped. In some implementations, for example, this information may be used for the message receiving node to determine whether to continue configuring (continuous) data collection, and / or, if it is determined to continue configuring (continuous) data collection, this information may be used to determine corresponding configuration information.
[0261] - Node corresponding to (continuous) data collection: which may indicate node information corresponding to (continuous) data collection. For example, the information may include one or more of the following: node identifier and / or node identifier list, number of nodes, etc. In some implementations, for example, the (continuous) data collection is performed within the nodes corresponding to the node identifier and / or node identifier list. In other implementations, for example, when the number of nodes corresponding to the completed (continuous) data collection and / or data collection results reaches the number of nodes, the (continuous) data collection should be stopped. In some implementations, for example, this information may be used for the message receiving node to determine whether to continue configuring (continuous) data collection, and / or, if it is determined to continue configuring (continuous) data collection, this information may be used to determine corresponding configuration information.
[0262] - PLMN information corresponding to (continuous) data collection: which may indicate the PLMN information corresponding to (continuous) data collection. For example, the information may include one or more of the following: PLMN and / or PLMN list, number of PLMNs, etc. In some implementations, for example, the (continuous) data collection is performed within the PLMNs corresponding to the PLMN and / or PLMN list. In other implementations, for example, when the number of PLMNs corresponding to the completed (continuous) data collection and / or data collection results reaches the number of PLMNs, the (continuous) data collection should be stopped. In some implementations, for example, this information may be used for the message receiving node to determine whether to continue configuring (continuous) data collection, and / or, if it is determined to continue configuring (continuous) data collection, this information may be used to determine corresponding configuration information.
[0263] - Slice information corresponding to (continuous) data collection: which may indicate slice information corresponding to (continuous) data collection. For example, the information may include one or more of the following: slice identifier and / or slice identifier list, and number of slices. In some implementations, for example, the (continuous) data collection is performed within the slices corresponding to the slice identifier and / or slice identifier list. In other implementations, for example, when the number of slices corresponding to the completed (continuous) data collection and / or data collection results reaches the number of slices, the (continuous) data collection should be stopped. The slice identifier may be represented by Single Network Slice Selection Assistance Information (S-NSSAI). In some implementations, for example, this information may be used for the message receiving node to determine whether to continue configuring (continuous) data collection, and / or, if it is determined to continue configuring (continuous) data collection, this information may be used to determine corresponding configuration information.
[0264] - Beam information corresponding to (continuous) data collection: which may indicate beam information corresponding to (continuous) data collection. For example, the information may include one or more of the following: beam identifier and / or beam identifier list, and number of beams. In some implementations, for example, the (continuous) data collection is performed within the beams corresponding to the beam identifier and / or the beam identifier list. In other implementations, for example, when the number of beams corresponding to the completed (continuous) data collection and / or data collection results reaches the number of beams, the (continuous) data collection should be stopped. For example, the beam may be an SSB beam or any other beam. In some implementations, for example, this information may be used for the message receiving node to determine whether to continue configuring (continuous) data collection, and / or, if it is determined to continue configuring (continuous) data collection, this information may be used to determine corresponding configuration information.
[0265] - Information related to a data collection result: which indicates the result of data collection. The result may be an MDT data collection result or other data collection results. The data collection result may include one or more of the following:
[0266] o Identifier and / or identifier list of cells corresponding to the data collection result
[0267] o Number of cells corresponding to the data collection result
[0268] o Identifier and / or identifier list of nodes corresponding to the data collection result
[0269] o Number of nodes corresponding to the data collection result
[0270] o Name and / or name list of nodes corresponding to the data collection result
[0271] o PLMN and / or PLMN list corresponding to the data collection result
[0272] o Number of PLMNs corresponding to the data collection result
[0273] o Identifier and / or identifier list of slices corresponding to the data collection result
[0274] o Number of slices corresponding to the data collection result
[0275] o Identifier and / or identifier list of beams corresponding to the data collection result
[0276] o Number of beams corresponding to the data collection result
[0277] o Data collection result: the data collection result may include one or more of the data corresponding to the data collection.
[0278] o Time information of change of RRC state: which may include one or more of the following: the time of the change of RRC state, the time from the change of RRC state to the reporting of the data collection result, the time from the configuration of data collection to the change of RRC state, etc. The change of RRC state may be a transition between an RRC connected state, an RRC idle state, and an RRC inactive state. For example, it may be a transition from an RRC connected state to an RRC idle state and / or an RRC inactive state. For example, it may be a transition from an RRC idle state and / or an RRC inactive state to an RRC active state.
[0279] o RRC state corresponding to the data collection result: which may represent the RRC state corresponding to one and / or more and / or some and / or all data collection results. The RRC state may include one or more of the following: an RRC connected state, an RRC idle state, an RRC inactive state, etc.
[0280] o Indication of RRC state transition: used to indicate the change of the RRC state. For example, it may indicate that part and / or all of the data collection results are corresponding data collection results after the RRC state is changed. The change of RRC state may include any transition between RRC states. The change of RRC state may be a transition between an RRC connected state, an RRC idle state, and an RRC inactive state. For example, it may be a transition from an RRC connected state to an RRC idle state and / or an RRC inactive state. For example, it may be a transition from an RRC idle state and / or an RRC inactive state to an RRC active state.
[0281] o Time information corresponding to the data collection result
[0282] o Configuration information corresponding to the data collection result: the configuration information may refer to the information in the first message.
[0283] - First identifier: used to identify the collection corresponding to the message. In some implementations, for example, during a (continuous) data collection process, the first identifier of a UE is the same. In some implementations, for example, this information may be used for a node to associate multiple data collection results of the same UE.
[0284] - Identifier of node and / or cell corresponding to the start of (continuous) data collection and / or the initial configuration for (continuous) data collection: used to indicate the identifier of the node and / or cell corresponding to the start of the (continuous) data collection, or the identifier of the first node and / or cell that configures the (continuous) data collection for the UE. In some implementations, for example, this node and / or cell identifier and the first identifier may uniquely identify a UE and / or a UE corresponding to a data collection report in the network. In some implementations, for example, this information may be used for a node to associate multiple data collection results of the same UE, or the combination of this information and the first identifier may be used for a node to associate multiple data collection results of the same UE.
[0285] - (Continuous) data collection dedicated TR and / or TRSR: in some implementations, the dedicated TR and / or TRSR does not change during a (continuous) data collection process. For example, during a (continuous) data collection process, the dedicated TR and / or TRSR of the same UE does not change. In some implementations, for example, the node may associate multiple (continuous) data collection configurations and / or multiple data collection results of the same UE through the dedicated TR and / or TRSR.
[0286] - Association relationship of configurations for (continuous) data collection: used to indicate the association relationship of the configurations for the (continuous) data collection. In some implementations, for example, the association relationship may include that configuration A and configuration B both belong to one (continuous) data collection. A node may configure subsequent data collection according to this association relationship of configurations, to achieve an effect of (continuous) data collection. The association relationship of configurations may be a relationship or a list of relationships. The association relationship may be one or more of the following:
[0287] o Associated TR
[0288] o Associated TRSR
[0289] o Identifiers of nodes and / or cells corresponding to the configurations for (continuous) data collection
[0290] o Associated data collection configuration identification
[0291] o Associated data collection configuration
[0292] - Reasons for the end of data collection: which may include one or more of the following: a data collection configuration with a higher priority is received, there is an ongoing data collection, the priority is high, the priority is low, the priority corresponding to a new data collection configuration is lower than that of an ongoing data collection, etc.
[0293]
[0294] In some implementations, for example, if an RRC state transition occurs during data collection, the data collection results before the RRC state transition may be reported first, and the data collection results after the RRC state transition may be reported next time. In other implementations, for example, if the collection items corresponding to different RRC states are different for the configured data collection, the corresponding RRC state may be determined based on the reported collection result.
[0295] In some implementations, for example, a node receives multiple data collection configurations, and if the multiple data collection configurations have the same portion, and / or the data collection results corresponding to the multiple data collection configurations have the same portion, the data collection results may be reported in the following methods:
[0296] Method 1: the node reports multiple data collection results, where one data collection result corresponds to one data collection configuration. The data collection result may refer to the data collection result in the above second message.
[0297] Method 2: the node reports one data collection result, and / or, multiple data collection configurations and / or configuration information related to data collection corresponding to the data collection result. The configuration information related to data collection may refer to the first message. The data collection result may refer to the data collection result in the above second message. The receiving node of the data collection result collates and / or processes the data collection result. For example, the data collection result may be collated and / or processed into data collection results corresponding to one or more of the multiple data collection configurations.
[0298]
[0299] Example 3
[0300] An aspect of the present disclosure proposes a method for supporting (continuous) data collection, which may include one or more of the following steps.
[0301] A fifth node transmits a third message including information related to the reporting of (continuous) data collection to a sixth node, to inform the sixth node of the information related to the reporting of (continuous) data collection. In some implementations, for example, the sixth node may transmit a data collection result request to the fifth node according to the information in the information related to the reporting of (continuous) data collection. This solution can support data collection without distinguishing the RRC state of the UE, so as to reduce the complexity of data collection configuration and achieve highly versatile data collection.
[0302] In some implementations, the third message may be included in one or more of the following: a UEInformationResponse message or an RRCSetupComplete message or an RRCResumeComplete message or an RRCReestablishmentComplete message or an RRCReconfigurationComplete 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.
[0303] In some implementations, the third message may include one or more of the following information and / or fields:
[0304] - Transmitting node ID: used to identify the node that transmits the message.
[0305] - Receiving node ID: used to identify the node that receives the message.
[0306] - Expected reporting time: which indicates the predicted and / or expected time when the reporting can be performed. In some implementations, for example, when the message transmitting node and / or UE is performing data collection and cannot perform reporting currently, the message transmitting node and / or UE may transmit the expected reporting time to the message receiving node. For example, the message receiving node may request the reporting of the data collection results according to the expected reporting time, or it may be that after the message transmitting node and / or UE inform the expected reporting time, the message transmitting node and / or UE transmit the data collection results to the message receiving node at the expected reporting time. The reporting time may be the reporting time of all information, or the reporting time of other information except the currently reportable information. The information may be one or more information of the above-mentioned second message or data collection results.
[0307] - Identification for ongoing data collection: which indicates that data collection is currently ongoing. In some implementations, for example, the message receiving node may subsequently request the message transmitting node and / or UE to report the data collection results based on this information. In other implementations, for example, the message transmitting node and / or UE will transmit the data collection results to the message receiving node after the ongoing data collection is completed.
[0308] - End time of ongoing data collection: which indicates the end time of the current ongoing data collection. In some implementations, for example, the receiving node of the message may request the reporting of the data collection results from the message transmitting node and / or UE after the end time based on this information. In other implementations, for example, the message transmitting node and / or UE will transmit the data collection results to the message receiving node at and / or after the end time.
[0309] - Identification of that only part of information can be reported: which indicates that only part of the information can be reported currently. In some implementations, for example, the message receiving node may request reporting of part of the information based on the information, and / or subsequently request reporting of the remaining part of the information. In other implementations, for example, the message receiving node may request reporting of all the information at a subsequent time. The information may be one or more information of the above-mentioned second message or data collection results.
[0310] - Data collection result available: which indicates that a data collection result is stored currently. In some implementations, for example, the message receiving node may request the message transmitting node to report the data collection result based on the information.
[0311] - Information on whether new data collection is supported: used to indicate whether new data collection is supported. For example, when the node (e.g., message transmitting node) and / or UE can support new data collection, the node (e.g., message receiving node) may configure a new data collection configuration to enable the node (e.g., message transmitting node) and / or UE to perform the new data collection. For example, the node (e.g., message transmitting node) and / or the UE perform data collection according to multiple data collection configurations (e.g., previous data collection configurations and / or new data collection configurations) simultaneously. In some implementations, for example, when node 1 (e.g., message transmitting node) and / or the UE are performing data collection according to a previous data collection configuration, this information may be carried to indicate whether node 1 and / or UE supports new data collection. For example, if node 1 and / or UE can support new data collection, node 2 (for example, message receiving node) may configure node 1 and / or UE with new data collection.
[0312] - Information related to data collection selected and / or decided to be performed: which indicates the information related to a data collection selected and / or decided to be performed. It may include one or more of the following: the data collection configuration corresponding to the data collection selected and / or decided to be performed, the reasons, etc. The data collection configuration corresponding to the data collection selected and / or decided to be performed may refer to the information in the first message. The reason may be the reason why the data collection is selected and / or decided to be performed, which may include one or more of the following: there is an ongoing data collection, the priority is high, the priority is low, the priority corresponding to a new data collection configuration is lower than that of an ongoing data collection, etc.
[0313] - Indication of whether a data collection result is the result of data collection triggered by RAN: used to indicate whether the data collection result is the result of RAN-triggered data collection. This information may be used for the reporting of the data collection result. For example, if the data collection result is the result of RAN-triggered data collection, the data collection result should be reported to the corresponding RAN node. Alternatively, if the data collection result is the result of RAN-triggered data collection, the receiving node of the data collection result needs to forward the data collection result to the corresponding RAN node that triggered the data collection.
[0314] - Indication of whether a data collection result is data collection triggered by OAM: used to indicate whether the data collection result is OAM-triggered data collection.
[0315] - Indication of whether a data collection result is data collection triggered by core network: used to indicate whether the data collection result is core network-triggered data collection. Herein, the core network may include any node in the core network.
[0316] - Identifier of configuration node and / or cell of data collection corresponding to a data collection result: used to identify the identifier of the configuration node and / or cell of the data collection (and / or data collection configuration) corresponding to the data collection result. In some implementations, for example, if a node has a relevant interface with the node and / or cell indicated by the identifier of the configuration node and / or cell of the data collection, the node may subsequently report the data collection result to the configuration node and / or cell of the data collection.
[0317] - Identifier of collection node and / or cell of a data collection result: used to identify the identifier of the collection node and / or cell corresponding to the data collection result. The identifier of the collection node and / or cell of the data collection result may also be called the identifier of the reporting node and / or cell of the data collection result, which is used to indicate that the data collection result needs to be reported to the reporting node and / or cell corresponding to the identifier. In some implementations, for example, if a node has a relevant interface with the node and / or cell indicated by the identifier of the collection node and / or cell of the data collection result, the node may subsequently report the data collection result to the configuration node and / or cell of the data collection.
[0318] - Measurement and / or collection items corresponding to data collection result: the measurement and / or collection items of the data collection result may include one or more of the data corresponding to the data collection in the first message.
[0319]
[0320] Example 4
[0321] An aspect of the present disclosure proposes a method for supporting (continuous) data collection, which may include one or more of the following steps.
[0322] A seventh node transmits a fourth message including a request for RAN-triggered (continuous) data collection to an eighth node to request to perform RAN-triggered (continuous) data collection. In some implementations, for example, it may be that the seventh node requests the eighth node to perform RAN-triggered (continuous) data collection. In other implementations, for example, it may be that the seventh node requests the eighth node to allow the seventh node to perform RAN-triggered (continuous) data collection. This solution can realize data collection triggered by the RAN side, so as to achieve highly applicable data collection.
[0323] In some implementations, the fourth message may be included in one or more of the following: a Handover Request message or a S-NODE ADDITION REQUEST message or a S-NODE MODIFICATION REQUEST message or a NG-RAN NODE CONFIGURATION UPDATE message or a NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message or a Xn SETUP REQUEST message or a XN SETUP RESPONSE message of Xn; or a UE CONTEXT RELEASE REQUEST message or a UE CONTEXT MODIFICATION REQUEST message or a UE CONTEXT MODIFICATION RESPONSE message or an INITIAL CONTEXT SETUP REQUEST message of NG; or an 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.
[0324] In some implementations, the fourth message may include one or more of the following information and / or fields:
[0325] - Transmitting node ID: used to identify the node that transmits the message.
[0326] - Receiving node ID: used to identify the node that receives the message.
[0327] - Request identification: used to identify a request corresponding to the message.
[0328] - Measurement identification: used to identify a measurement request corresponding to the message.
[0329] - Reporting identification: used to identify a reporting request corresponding to the message.
[0330] - Indication of a request for RAN-triggered (continuous) data collection: used to indicate that the request is for requesting RAN-triggered (continuous) data collection.
[0331] - Configuration information corresponding to the requested RAN-triggered (continuous) data collection: used to indicate the configuration information corresponding to the requested RAN-triggered (continuous) data collection. The configuration information may refer to one or more information of the first message.
[0332]
[0333] The eighth node transmits a fifth message including information related to RAN-triggered (continuous) data collection to the seventh node according to its own situation, to inform the seventh node of the information related to RAN-triggered (continuous) data collection. Alternatively, after receiving the fourth message including a request for RAN-triggered (continuous) data collection transmitted by the seventh node, in response to the fourth message, the eighth node transmits a fifth message including information related to the RAN-triggered (continuous) data collection to the seventh node. In some implementations, for example, it may be the eighth node that configures information related to the RAN-triggered (continuous) data collection and / or triggers the (continuous) data collection. In other implementations, for example, it may be the seventh node that configures information related to the RAN-triggered (continuous) data collection and / or triggers the (continuous) data collection.
[0334] The RAN-triggered (continuous) data collection may support RAN nodes to perform self-optimization and / or artificial intelligence and / or machine learning related operations. For example, the collected data may be used by RAN nodes for training and / or inference and / or performance evaluation of artificial intelligence and / or machine learning models, etc.
[0335] This solution can realize data collection triggered by the RAN side, so as to achieve highly applicable data collection.
[0336] In some implementations, the fifth message may be included in one or more of the following: a Handover Request message or a S-NODE ADDITION REQUEST message or a S-NODE MODIFICATION REQUEST message or a NG-RAN NODE CONFIGURATION UPDATE message or a NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message or a Xn SETUP REQUEST message or a XN SETUP RESPONSE message of Xn; or a UE CONTEXT RELEASE REQUEST message or a UE CONTEXT MODIFICATION REQUEST message or a UE CONTEXT MODIFICATION RESPONSE message or an INITIAL CONTEXT SETUP REQUEST message of NG; or an 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.
[0337] In some implementations, the fifth message may include one or more of the following information and / or fields:
[0338] - Transmitting node ID: used to identify the node that transmits the message.
[0339] - Receiving node ID: used to identify the node that receives the message.
[0340] - Request identification: used to identify a request corresponding to the message.
[0341] - Measurement identification: used to identify a measurement request corresponding to the message.
[0342] - Reporting identification: used to identify a reporting request corresponding to the message.
[0343] - Indication of that RAN-triggered (continuous) data collection is allowed: used to indicate that RAN-triggered (continuous) data collection is allowed. In some implementations, for example, the message receiving node is allowed to perform RAN-triggered (continuous) data collection.
[0344] - Configuration information corresponding to allowed RAN-triggered (continuous) data collection: used to indicate configuration information corresponding to allowed RAN-triggered (continuous) data collection. The configuration information may refer to one or more information of the first message.
[0345] - Configuration information corresponding to RAN-triggered (continuous) data collection: used to indicate configuration information corresponding to RAN-triggered (continuous) data collection. The configuration information may refer to one or more information of the first message.
[0346] Exemplary embodiments of the present disclosure are further described below with reference to the accompanying drawings.
[0347] The text and drawings are provided as examples only to help understand the present disclosure. They should not be construed as limiting the scope of the present disclosure in any way. Although certain embodiments and examples have been provided, based on the disclosure herein, it is obvious to those skilled in the art that changes can be made to the illustrated embodiments and examples without departing from the scope of the present disclosure.
[0348]
[0349] FIG. 3 shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 3 shows a process of exchanging information related to (continuous) data collection between two nodes, so that the second node may perform data collection, and / or configure subsequent data collection, and / or analyze the collected data collection results based on the information related to (continuous) data collection.
[0350] In some implementations, for example, the first node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB, and the second node may be a UE. In some implementations, for example, the first node may be a UE, and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the second node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the first node may be an AMF or SMF or MME, and the second node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the first node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the second node may be an AMF or SMF or MME. It may also be that, for example, the first node is a master node and the second node is a secondary node; for example, the first node is a secondary node and the second node is a master node; for example, the first node is a source node and the second node is a target node; for example, the first node is a target node and the second node is a source node; for example, the first node is a node (which may also be referred to as a new node) and the second node is a last serving node (which may also be referred to as an old node).
[0351] Step 300A: optionally, the second node transmits a request for information related to (continuous) data collection to the first node, for requesting the first node to transmit information related to (continuous) data collection. The request for information related to (continuous) data collection may include one or more of the following: indication of a request for information related to (continuous) data collection, a UE identifier and / or identifier list corresponding to the request for information related to (continuous) data collection, a cell identifier and / or identifier list corresponding to the request for information related to (continuous) data collection, a node identifier and / or identifier list corresponding to the request for information related to (continuous) data collection, a beam identifier and / or identifier list corresponding to the request for information related to (continuous) data collection, a slice identifier and / or identifier list corresponding to the request for information related to (continuous) data collection, indication of a request for information related to RAN-triggered (continuous) data collection, etc.
[0352] Step 301A: the first node transmits information related to (continuous) data collection to the second node. The information related to (continuous) data collection may be the aforementioned first message.
[0353] Step 302A: the second node may perform data collection, and / or configure subsequent data collection, and / or analyze the collected data collection results based on the information related to (continuous) data collection.
[0354] For example, the second node may perform subsequent data collection based on information in the information related to (continuous) data collection. In some implementations, for example, the second node may report part and / or all of the information related to (continuous) data collection together when reporting the (continuous) data collection results, so that the receiving node of the data collection results may continue configuring subsequent data collection, to achieve an effect of (continuous) data collection.
[0355] For example, the second node may configure subsequent data collection based on the information related to (continuous) data collection. In some implementations, for example, in a handover process, in step 301A, the source node transmits information related to (continuous) data collection to the target node; in step 302A, the target node may configure subsequent data collection for the UE based on the information related to (continuous) data collection, to achieve an effect of (continuous) data collection. In yet other implementations, in a secondary node addition process, in step 301A, the master node transmits information related to (continuous) data collection to the target secondary node; in step 302A, the secondary node configures subsequent data collection for the UE, to achieve an effect of (continuous) data collection. In yet other implementations, for example, in step 301A, the secondary node transmits information related to (continuous) data collection to the master node; in step 302A, the master node configures subsequent data collection for the UE, or the master node may transmit the information related to (continuous) data collection to another node for the other node to configure subsequent data collection for the UE. For example, the other node may be a target secondary node. In yet other implementations, for example, in step 301A, the last serving node (which may also be referred to as an old node) transmits information related to (continuous) data collection to the node (which may also be referred to as a new node). For example, the node (which may also be referred to as a new node) may use the information in step 301A to decide whether to request the UE to report the (continuous) data collection results, and / or the node (which may also be referred to as a new node) may use the information in step 301A to forward the (continuous) data collection results to the last serving node (which may also be referred to as an old node) after obtaining the (continuous) data collection results, and / or the node (which may also be referred to as a new node) may use the information in step 301A to decide to configure the same and / or different information related to (continuous) data collection for the UE.
[0356] For example, the second node may analyze the (continuous) data collection results based on the information related to (continuous) data collection. In some implementations, for example, the second node may associate multiple (continuous) data collection results of the same UE based on the information related to (continuous) data collection to obtain a (continuous) data collection result.
[0357]
[0358] FIG. 4A shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 4A shows a process of exchanging (continuous) data collection results between two nodes so that a fourth node can perform analysis based on the (continuous) data collection results.
[0359] In some implementations, for example, the third node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB, and the fourth node may be a UE. In some implementations, for example, the third node may be a UE, and the fourth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the third node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the fourth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the third node may be an AMF or SMF or MME, and the fourth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the third node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the fourth node may be an AMF or SMF or MME. It may also be that, for example, the third node is a master node and the fourth node is a secondary node; for example, the third node is a secondary node and the fourth node is a master node; for example, the third node is a source node and the fourth node is a target node; for example, the third node is a target node and the fourth node is a source node; for example, the third node is a node (which may also be referred to as a new node) and the fourth node is a last serving node (which may also be referred to as an old node).
[0360] Step 401A: the third node transmits (continuous) data collection results to the fourth node. The (continuous) data collection results may be the aforementioned second message.
[0361] Step 402A: the fourth node may perform data analysis based on the (continuous) data collection results, and / or combine the (continuous) data collection results to obtain (continuous) data, and / or configure subsequent data collection, to achieve (continuous) data collection.
[0362] For example, the fourth node may perform data analysis based on information in the (continuous) data collection results. In some implementations, for example, the fourth node may associate multiple collected data collection results based on the information in the (continuous) data collection results, resulting in a set of (continuous) collection results. For example, multiple (continuous) data collection 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 training and / or performance monitoring and / or inference of AI / ML.
[0363] For example, the fourth node may configure subsequent data collection based on the information in the (continuous) data collection results. In some implementations, for example, the fourth node may determine that (continuous) data collection needs to be configured and / or determine corresponding configuration information thereof based on the information in the (continuous) data collection results, and the fourth node configures subsequent data collection.
[0364] For example, based on the information in the (continuous) data collection results, the fourth node may obtain information about that data collection needs to be continued, and configure subsequent data collection. In some implementations, for example, in a handover process, in step 401A, the source node transmits (continuous) data collection results to the target node; in step 402A, the target node may configure subsequent data collection for the UE based on the (continuous) data collection results to achieve an effect of (continuous) data collection, and / or combine the subsequently collected data collection results with the already received (continuous) data collection results to obtain (continuous) data to achieve an effect of (continuous) data collection. In yet other implementations, in a secondary node addition process, in step 401A, the master node transmits information related to (continuous) data collection to the target secondary node; in step 402A, the secondary node configures subsequent data collection for the UE, to achieve an effect of (continuous) data collection, and / or combines the subsequently collected data collection results with the already received (continuous) data collection results to obtain (continuous) data to achieve an effect of (continuous) data collection. In yet other implementations, for example, in step 401A, the secondary node transmits information related to (continuous) data collection to the master node; in step 402A, the master node configures subsequent data collection for the UE, or the master node may transmit the information related to (continuous) data collection to another node for the other node to configure subsequent data collection for the UE. For example, the other node may be a target secondary node. And / or, the master node and / or the other node combine the subsequently collected data collection results with the already received (continuous) data collection results to obtain (continuous) data to achieve an effect of (continuous) data collection. In yet other implementations, for example, in step 401A, the last serving node (which may also be referred to as an old node) transmits information related to (continuous) data collection to the node (which may also be referred to as a new node); in step 402A, the node (which may also be referred to as a new node) configures subsequent data collection for the UE, or the node (which may also be referred to as a new node) transmits the information related to (continuous) data collection to another node for the other node to configure subsequent data collection for the UE. For example, the node (which may also be referred to as a new node) may use the information in step 401A to decide whether to request the UE to report the (continuous) data collection results, and / or the node (which may also be referred to as a new node) may use the information in step 401A to forward the (continuous) data collection results to the last serving node (which may also be referred to as an old node) after obtaining the (continuous) data collection results, and / or the node (which may also be referred to as a new node) may use the information in step 401A to decide to configure the same and / or different information related to (continuous) data collection for the UE.
[0365] FIG. 4B shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 4B shows a process of exchanging (continuous) data collection results between two nodes so that a fourth node can perform analysis based on the (continuous) data collection results.
[0366] In some implementations, for example, the third node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB, and the fourth node may be a UE. In some implementations, for example, the third node may be a UE, and the fourth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the third node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the fourth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the third node may be an AMF or SMF or MME, and the fourth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the third node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the fourth node may be an AMF or SMF or MME. It may also be that, for example, the third node is a master node and the fourth node is a secondary node; for example, the third node is a secondary node and the fourth node is a master node; for example, the third node is a source node and the fourth node is a target node; for example, the third node is a target node and the fourth node is a source node; for example, the third node is a node (which may also be referred to as a new node) and the fourth node is a last serving node (which may also be referred to as an old node).
[0367] Step 401B: the fourth node transmits information related to (continuous) data collection to the third node. The information related to (continuous) data collection may be the aforementioned first message.
[0368] Step 402B: the third node transmits (continuous) data collection results to the fourth node. The (continuous) data collection results may be the aforementioned second message. In some implementations, for example, the third node performs data collection according to the information related to (continuous) data collection received in step 401B, to obtain a (continuous) data collection result, and transmits it to the fourth node through step 402B.
[0369] Step 403B: the fourth node may perform data analysis based on the (continuous) data collection results, and / or combine the (continuous) data collection results to obtain (continuous) data, and / or configure subsequent data collection, to achieve (continuous) data collection.
[0370] For example, the fourth node may perform data analysis based on information in the (continuous) data collection results. In some implementations, for example, the fourth node may associate multiple collected data collection results based on the information in the (continuous) data collection results, resulting in a set of (continuous) collection results. For example, multiple (continuous) data collection 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 training and / or performance monitoring and / or inference of AI / ML.
[0371] For example, the fourth node may configure subsequent data collection based on the information in the (continuous) data collection results. In some implementations, for example, the fourth node may determine that (continuous) data collection needs to be configured and / or determine corresponding configuration information thereof based on the information in the (continuous) data collection results, and the fourth node configures subsequent data collection.
[0372] For example, based on the information in the (continuous) data collection results, the fourth node may obtain information about that data collection needs to be continued, and configure subsequent data collection. In some implementations, for example, in a handover process, in step 402B, the source node transmits (continuous) data collection results to the target node; in step 403B, the target node may configure subsequent data collection for the UE based on the (continuous) data collection results to achieve an effect of (continuous) data collection, and / or combine the subsequently collected data collection results with the already received (continuous) data collection results to obtain (continuous) data to achieve an effect of (continuous) data collection. In yet other implementations, in a secondary node addition process, in step 402B, the master node transmits information related to (continuous) data collection to the target secondary node; in step 403B, the secondary node configures subsequent data collection for the UE, to achieve an effect of (continuous) data collection, and / or combines the subsequently collected data collection results with the already received (continuous) data collection results to obtain (continuous) data to achieve an effect of (continuous) data collection. In yet other implementations, for example, in step 402B, the secondary node transmits information related to (continuous) data collection to the master node; in step 403B, the master node configures subsequent data collection for the UE, or the master node may transmit the information related to (continuous) data collection to another node for the other node to configure subsequent data collection for the UE. For example, the other node may be a target secondary node. And / or, the master node and / or the other node combine the subsequently collected data collection results with the already received (continuous) data collection results to obtain (continuous) data to achieve an effect of (continuous) data collection. In yet other implementations, for example, in step 401B, the last serving node (which may also be referred to as an old node) transmits information related to (continuous) data collection to the node (which may also be referred to as a new node); in step 402B, the node (which may also be referred to as a new node) configures subsequent data collection for the UE, or the node (which may also be referred to as a new node) transmits the information related to (continuous) data collection to another node for the other node to configure subsequent data collection for the UE. For example, the node (which may also be referred to as a new node) may use the information in step 401B to decide whether to request the UE to report the (continuous) data collection results, and / or the node (which may also be referred to as a new node) may use the information in step 401B to forward the (continuous) data collection results to the last serving node (which may also be referred to as an old node) after obtaining the (continuous) data collection results, and / or the node (which may also be referred to as a new node) may use the information in step 401B to decide to configure the same and / or different information related to (continuous) data collection for the UE.
[0373] FIG. 4C shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 4C shows a process in which two nodes configure the UE for (continuous) data collection to obtain (continuous) data.
[0374] Step 400C: Base station 1 and / or Base station 2 are configured with information related to (continuous) data collection. The information related to (continuous) data collection may be the information in the aforementioned first message, and / or an MDT configuration. In some implementations, for example, OAM and / or AMF configures Base station 1 and / or Base station 2 with the information related to (continuous) data collection.
[0375] Step 401C: Base station 1 transmits information related to (continuous) data collection to the corresponding UE. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration.
[0376] Step 402C: the UE performs data collection. Optionally, the UE transmits the corresponding (continuous) data collection results to Base station 1. The (continuous) data collection results may be the aforementioned second message. This step is optional. Step 402C may also be replaced by the process in FIG. 5B.
[0377] Step 403C: the UE enters an RRC inactive state or an RRC idle state, and the UE performs data collection according to the (continuous) data collection configuration received in step 401C.
[0378] Step 404C: the UE returns to an RRC connected state. For example, the UE is connected to Base station 2. The UE transmits information related to the reporting of the (continuous) data collection to the connected base station (in this example, the connected base station is Base station 2). The information related to the reporting of (continuous) data collection may be the aforementioned third message.
[0379] Step 405C: Base station 2 transmits a message including information related to (continuous) data collection to the UE. The information related to (continuous) data collection may be the aforementioned first message. For example, when Base station 2 decides to configure data collection for the UE, it transmits the information related to (continuous) data collection to the UE.
[0380] Step 406C: the UE performs data collection based on the information related to (continuous) data collection received in step 405C and / or step 401C.
[0381] Step 407C: the UE transmits a message including information related to that the (continuous) data collection results are available to the connected base station (in this example, the connected base station is Base station 2). The message may include information related to one or more of the following: a (continuous) data collection result is available, a data collection result is available, part of the data collection results are available, part of the (continuous) data collection results are available, etc. In some implementations, for example, after receiving the message, Base station 2 may request the UE to report the (continuous) data collection results subsequently.
[0382] Step 408C: Base station 2 transmits a message including a (continuous) data collection result request to the UE to request the UE to report (continuous) data collection results. The message may include one or more of the following: a request for (continuous) data collection results, a request for data collection results, a request for part of the data collection results, a request for part of the (continuous) data collection results, etc.
[0383] Step 409C: the UE transmits (continuous) data collection results to Base station 2. The (continuous) data collection results may be the aforementioned second message. The (continuous) data collection results may be all of the (continuous) data collection results, part of the (continuous) data collection results, or currently available (continuous) data collection results.
[0384] FIG. 4D shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 4D shows a process in which two nodes configure the UE for (continuous) data collection to obtain (continuous) data.
[0385] Step 400D: Base station 1 and / or Base station 2 are configured with information related to (continuous) data collection. The information related to (continuous) data collection may be the information in the aforementioned first message. In some implementations, for example, OAM and / or AMF configures Base station 1 and / or Base station 2 with the information related to (continuous) data collection.
[0386] Step 401D: Base station 1 transmits information related to (continuous) data collection to the corresponding UE. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration.
[0387] Step 402D: the UE performs data collection. Optionally, the UE transmits the corresponding (continuous) data collection results to Base station 1. The (continuous) data collection results may be the aforementioned second message. Step 402D may also be replaced by the process in FIG. 5B.
[0388] Step 403D: Base station 1 transmits information related to (continuous) data collection to Base station 2. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration. In some implementations, for example, in a handover process, the source node (e.g., Base station 1) transmits information related to (continuous) data collection to the target node (e.g., Base station 2); the target node (e.g., Base station 2) may configure subsequent data collection for the UE based on the information related to (continuous) data collection, to achieve an effect of (continuous) data collection. In yet other implementations, in a secondary node addition process, the master node (e.g., Base station 1) transmits information related to (continuous) data collection to the target secondary node (e.g., Base station 2); the secondary node (e.g., Base station 2) configures subsequent data collection for the UE, to achieve an effect of (continuous) data collection. In yet other implementations, for example, the secondary node (e.g., Base station 1) transmits information related to (continuous) data collection to the master node (e.g., Base station 2); the master node (e.g., Base station 2) configures subsequent data collection for the UE, or the master node (e.g., Base station 2) may transmit information related to (continuous) data collection to another node for the other node to configure subsequent data collection for the UE. For example, the other node may be a target secondary node. In yet other implementations, the last serving node (which may also be referred to as an old node) (e.g., Base station 1) transmits information related to (continuous) data collection to the node (which may also be referred to as a new node) to which the UE is newly connected (e.g., Base station 2).
[0389] Step 404D: Base station 2 transmits information related to (continuous) data collection to the UE. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration. In some implementations, for example, the Base station 2 continues to configure (continuous) data collection for the UE according to the information related to (continuous) data collection and transmits the information related to (continuous) data collection to the UE.
[0390] Step 405D: the UE performs data collection. Optionally, the UE transmits the corresponding (continuous) data collection results to Base station 2. The (continuous) data collection results may be the aforementioned second message. The step 405D may also be replaced by the process in FIG. 5B.
[0391] FIG. 4E shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 4E shows a process in which two secondary nodes configure the UE for (continuous) data collection to obtain (continuous) data.
[0392] Step 400E: Secondary node 1 and / or Secondary node 2 are configured with information related to (continuous) data collection. The information related to (continuous) data collection may be the information in the aforementioned first message. In some implementations, for example, OAM and / or AMF configures Secondary node 1 and / or Secondary node 2 with the information related to (continuous) data collection.
[0393] Step 401E: Secondary node 1 transmits information related to (continuous) data collection to the corresponding UE. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration.
[0394] Step 402E: the UE performs data collection. Optionally, the UE transmits the corresponding (continuous) data collection results to Secondary node 1. The (continuous) data collection results may be the aforementioned second message. Step 402E may also be replaced by the process in FIG. 5B.
[0395] Step 403E: Secondary node 1 transmits information related to (continuous) data collection to the master node. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration. In some implementations, for example, in a secondary node change process, the source secondary node (e.g., Secondary node 1) transmits information related to (continuous) data collection to the master node.
[0396] Step 404E: the master node transmits information related to (continuous) data collection to Secondary node 2. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration. In some implementations, for example, in a secondary node change process, the master node transmits information related to (continuous) data collection to the target secondary node (e.g., Secondary node 2).
[0397] Step 405E: Secondary node 2 transmits information related to (continuous) data collection to the UE. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration. In some implementations, for example, Secondary node 2 continues to configure (continuous) data collection for the UE and transmits information related to (continuous) data collection to the UE according to the information related to (continuous) data collection received in step 404E and / or the information related to (continuous) data collection in step 400E. In other implementations, for example, in a secondary node change process, when the UE accesses Secondary node 2, Secondary node 2 can directly transmit information related to (continuous) data collection to the UE, for example, through an RRCReconfiguration message. In yet other implementations, for example, in a secondary node change process, Secondary node 2 may transmit information related to (continuous) data collection to the UE via forwarding by the master node, e.g., through an RRCReconfiguration message.
[0398] Step 406E: the UE performs data collection. Optionally, the UE transmits the corresponding (continuous) data collection results to Secondary node 2. The (continuous) data collection results may be the aforementioned second message. Step 406E may also be replaced by the process in FIG. 5B.
[0399] FIG. 4F shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 4F shows a process in which three nodes exchanges information related to (continuous) data collection in order to configure the UE to perform (continuous) data collection to obtain (continuous) data.
[0400] In some implementations, for example, Node 1 may be a gNB CU, Node 2 may be a gNB DU, and Node 3 may be a gNB DU. In other implementations, for example, Node 1 may be a gNB CU CP, Node 2 may be a gNB CU UP, and Node 3 may be a gNB CU UP. In yet other implementations, for example, Node 1 may be an AMF and / or 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.
[0401] Step 400F: Node 2 and / or Node 3 are configured with information related to (continuous) data collection. The information related to (continuous) data collection may be the information in the aforementioned first message. In some implementations, for example, OAM and / or AMF configures Node 2 and / or Node 3 with the information related to (continuous) data collection.
[0402] Step 401F: Node 2 transmits information related to (continuous) data collection to the corresponding UE. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration.
[0403] Step 402F: the UE performs data collection. Optionally, the UE transmits the corresponding (continuous) data collection results to Node 2. The (continuous) data collection results may be the aforementioned second message. Step 402F may also be replaced by the process in FIG. 5B.
[0404] Step 403F: Node 2 transmits information related to (continuous) data collection to Node 1. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration. In some implementations, for example, in a user context release process and / or a bearer context release process, Node 2 transmits information related to (continuous) data collection to Node 1.
[0405] Step 404F: Node 1 transmits information related to (continuous) data collection to Node 3. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration. In some implementations, for example, in a user context setup process and / or a user context modification process and / or a bearer context setup process and / or a bearer context modification process, Node 1 transmits information related to (continuous) data collection to Node 3.
[0406] Step 405F: Node 3 transmits information related to (continuous) data collection to the UE. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration. In some implementations, for example, Node 3 continues to configure (continuous) data collection for the UE and transmits information related to (continuous) data collection to the UE according to the information related to (continuous) data collection received in step 404F and / or the information related to (continuous) data collection in step 400F.
[0407] Step 406F: the UE performs data collection. Optionally, the UE transmits the corresponding (continuous) data collection results to Node 3. The (continuous) data collection results may be the aforementioned second message. Step 406F may also be replaced by the process in FIG. 5B.
[0408] FIG. 4G shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 4G shows a process in which two nodes configure the UE for (continuous) data collection to obtain (continuous) data.
[0409] Step 400G: Base station 1 and / or Base station 2 are configured with information related to (continuous) data collection. The information related to (continuous) data collection may be the information in the aforementioned first message, and / or an MDT configuration. In some implementations, for example, OAM and / or AMF configures Base station 1 and / or Base station 2 with the information related to (continuous) data collection.
[0410] Step 401G: Base station 1 transmits information related to (continuous) data collection to the corresponding UE. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration.
[0411] Step 402G: the UE performs data collection. Optionally, the UE transmits the corresponding (continuous) data collection results to Base station 1. The (continuous) data collection results may be the aforementioned second message. This step is optional. Step 402G may also be replaced by the process in FIG. 5B.
[0412] Step 403G: the UE enters an RRC inactive state or an RRC idle state, and the UE performs data collection according to the (continuous) data collection configuration received in step 401G.
[0413] Step 404G: the UE returns to an RRC connected state. For example, the UE is connected to Base station 2. The UE performs an RRC setup and / or resume process with the connected base station (in this example, the connected base station is Base station 2).
[0414] Step 405G: Base station 2 transmits a message including information related to (continuous) data collection to the UE. The information related to (continuous) data collection may be the aforementioned first message. For example, when Base station 2 decides to configure data collection for the UE, it transmits the information related to (continuous) data collection to the UE.
[0415] Step 406G: the UE transmits information related to the reporting of the (continuous) data collection to the connected base station (in this example, the connected base station is Base station 2). The information related to the reporting of (continuous) data collection may be the aforementioned third message. In some implementations, the UE determines the data collection to be performed based on the information related to (continuous) data collection received in step 405G and / or step 401G. The UE may transmit information related to the decided and / or performed data collection to the connected base station (in this example, the connected base station is Base station 2) through information related to the reporting of (continuous) data collection.
[0416] Step 407G: the UE performs data collection according to the information related to (continuous) data collection received in step 405G and / or step 401G. In some implementations, the UE performs data collection based on the information related to the reporting of (continuous) data collection transmitted in step 406G.
[0417] Step 408G: the UE transmits a message including information related to that the (continuous) data collection results are available to the connected base station (in this example, the connected base station is Base station 2). The message may include information related to one or more of the following: a (continuous) data collection result is available, a data collection result is available, part of the data collection results are available, part of the (continuous) data collection results are available, etc. In some implementations, for example, after receiving the message, Base station 2 may request the UE to report the (continuous) data collection results subsequently.
[0418] Step 409G: Base station 2 transmits a message including a (continuous) data collection result request to the UE to request the UE to report (continuous) data collection results. The message may include one or more of the following: a request for (continuous) data collection results, a request for data collection results, a request for part of the data collection results, a request for part of the (continuous) data collection results, etc.
[0419] Step 410G: the UE transmits (continuous) data collection results to Base station 2. The (continuous) data collection results may be the aforementioned second message. The (continuous) data collection results may be all of the (continuous) data collection results, part of the (continuous) data collection results, or currently available (continuous) data collection results.
[0420]
[0421] FIG. 5A shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 5A shows a process of exchanging information related to the reporting of (continuous) data collection between two nodes, so that a sixth node can obtain (continuous) data collection results.
[0422] In some implementations, for example, the fifth node may be a UE, and the sixth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the fifth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the sixth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the fifth node may be an AMF or SMF or MME, and the sixth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the fifth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the sixth node may be an AMF or SMF or MME. It may also be that, for example, the fifth node is a master node and the sixth node is a secondary node; for example, the fifth node is a secondary node and the sixth node is a master node; for example, the fifth node is a source node and the sixth node is a target node; for example, the fifth node is a target node and the sixth node is a source node.
[0423] Step 501A: the fifth node transmits information related to the reporting of (continuous) data collection to the sixth node. The information related to the reporting of (continuous) data collection may be the aforementioned third message.
[0424] Step 502A: the sixth node may wait for and / or request (continuous) data collection results based on the information related to the reporting of (continuous) data collection. In some implementations, for example, the sixth node may transmit a data collection result request to the fifth node according to the information in the information related to the reporting of (continuous) data collection.
[0425] Step 503A: the sixth node transmits a message including a (continuous) data collection result request to the fifth node to request the fifth node to report the (continuous) data collection result. The (continuous) data collection result request may include one or more of the following: a request for (continuous) data collection results, a request for data collection results, a request for part of the data collection results, a request for part of the (continuous) data collection results, etc. The message may be transmitted via a UE information request message. In some implementations, for example, the message may be transmitted based on the information related to the reporting of the (continuous) data collection received in step 501A.
[0426] Step 504A: the fifth node transmits a message including the (continuous) data collection results to the sixth node. The (continuous) data collection results may be the aforementioned second message. In some implementations, for example, the message may be transmitted according to the information related to the reporting of (continuous) data collection in step 501A.
[0427] Step 503A is an optional step.
[0428] FIG. 5B shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 5B shows a process of exchanging information related to the reporting of (continuous) data collection between two nodes, so that a sixth node can obtain (continuous) data collection results.
[0429] In some implementations, for example, the fifth node may be a UE, and the sixth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the fifth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the sixth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the fifth node may be an AMF or SMF or MME, and the sixth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the fifth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the sixth node may be an AMF or SMF or MME. It may also be that, for example, the fifth node is a master node and the sixth node is a secondary node; for example, the fifth node is a secondary node and the sixth node is a master node; for example, the fifth node is a source node and the sixth node is a target node; for example, the fifth node is a target node and the sixth node is a source node.
[0430] Step 501B: the fifth node completes data collection, and / or stops data collection, and / or completes part of the data collection.
[0431] Step 502B: the fifth node transmits to the sixth node information related to the reporting of (continuous) data collection and / or information related to that the (continuous) data collection results are available. The information related to the reporting of (continuous) data collection may be the aforementioned third message.
[0432] Step 503B: the sixth node transmits a message including a (continuous) data collection result request to the fifth node to request the fifth node to report the (continuous) data collection result. The (continuous) data collection result request may include one or more of the following: a request for (continuous) data collection results, a request for data collection results, a request for part of the data collection results, a request for part of the (continuous) data collection results, etc. The message may be transmitted via a UE information request message. In some implementations, for example, the message may be transmitted based on the information related to the reporting of the (continuous) data collection received in step 502B.
[0433] Step 504B: the fifth node transmits a message including the (continuous) data collection results to the sixth node. The (continuous) data collection results may be the aforementioned second message. In some implementations, for example, the message may be transmitted according to the information related to the reporting of (continuous) data collection in step 502B.
[0434] Step 503B is an optional step.
[0435] FIG. 5C shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 5C shows a process of exchanging information related to the reporting of (continuous) data collection between two nodes, so that a sixth node can obtain (continuous) data collection results.
[0436] In some implementations, for example, the fifth node may be a UE, and the sixth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the fifth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the sixth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the fifth node may be an AMF or SMF or MME, and the sixth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the fifth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the sixth node may be an AMF or SMF or MME. It may also be that, for example, the fifth node is a master node and the sixth node is a secondary node; for example, the fifth node is a secondary node and the sixth node is a master node; for example, the fifth node is a source node and the sixth node is a target node; for example, the fifth node is a target node and the sixth node is a source node.
[0437] Step 501C: the fifth node is performing (continuous) data collection.
[0438] Step 502C: the fifth node transmits information related to the reporting of (continuous) data collection to the sixth node. The information related to the reporting of (continuous) data collection may be the aforementioned third message.
[0439] Step 503C: the sixth node transmits a message including a (continuous) data collection result request to the fifth node to request the fifth node to report the (continuous) data collection result. The (continuous) data collection result request may include one or more of the following: a request for (continuous) data collection results, a request for data collection results, a request for part of the data collection results, a request for part of the (continuous) data collection results, etc. The message may be transmitted via a UE information request message. In some implementations, for example, the message may be transmitted based on the information related to the reporting of the (continuous) data collection received in step 502C.
[0440] Step 504C: the fifth node transmits a message including the (continuous) data collection results to the sixth node. The (continuous) data collection results may be the aforementioned second message. In some implementations, for example, the message may be transmitted according to the information related to the reporting of (continuous) data collection in step 502C. In other implementations, for example, the fifth node may report currently available data. In yet other implementations, 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.
[0441] Step 505C: the fifth node completes data collection, and / or stops data collection, and / or completes part of the data collection.
[0442] Step 506C: the fifth node transmits to the sixth node information related to the reporting of (continuous) data collection and / or information related to that the (continuous) data collection results are available. The information related to the reporting of (continuous) data collection may be the aforementioned third message.
[0443] Step 507C: the sixth node transmits a message including a (continuous) data collection result request to the fifth node to request the fifth node to report the (continuous) data collection result. The (continuous) data collection result request may include one or more of the following: a request for (continuous) data collection results, a request for data collection results, a request for part of the data collection results, a request for part of the (continuous) data collection results, etc. The message may be transmitted via a UE information request message. In some implementations, for example, the message may be transmitted based on the information related to the reporting of the (continuous) data collection received in step 502C and / or step 506C.
[0444] Step 508C: the fifth node transmits a message including the (continuous) data collection results to the sixth node. The (continuous) data collection results may be the aforementioned second message. In some implementations, for example, the message may be transmitted according to the information related to the reporting of (continuous) data collection in step 502C and / or step 506C. In other implementations, for example, the fifth node may report currently available data. In yet other implementations, for example, after receiving the (continuous) data collection result request message in step 507C, the fifth node reports the currently collected and / or available data.
[0445] For example, the results obtained in steps 504C and 508C may be combined to form (continuous) data.
[0446] Step 503C is an optional step. Step 506C is an optional step.
[0447] Step 505C is an optional step.
[0448]
[0449] FIG. 6A shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 6A shows a process of exchanging information related to RAN-triggered (continuous) data collection between two nodes, so that a seventh node and / or an eighth node can configure and / or perform RAN-triggered (Continuous) data collection.
[0450] In some implementations, for example, the seventh node may be a UE, and the eighth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the seventh node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the eighth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the seventh node may be an AMF or SMF or MME, and the eighth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the seventh node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the eighth node may be an AMF or SMF or MME. It may also be that, for example, the seventh node is a master node and the eighth node is a secondary node; for example, the seventh node is a secondary node and the eighth node is a master node; for example, the seventh node is a source node and the eighth node is a target node; for example, the seventh node is a target node and the eighth node is a source node.
[0451] Step 601A: the seventh node transmits a request for RAN-triggered (continuous) data collection to the eighth node to request RAN-triggered (continuous) data collection. In some implementations, for example, it may be that the seventh node requests the eighth node to perform RAN-triggered (continuous) data collection. In other implementations, for example, it may be that the seventh node requests the eighth node to allow the seventh node to perform RAN-triggered (continuous) data collection. The request for RAN-triggered (continuous) data collection may be the aforementioned fourth message.
[0452] Step 602A: after receiving the request for RAN-triggered (continuous) data collection transmitted by the seventh node, the eighth node transmits the information related to the RAN-triggered (continuous) data collection to the seventh node in response to the request for RAN-triggered (continuous) data collection. The information related to RAN-triggered (continuous) data collection may be the aforementioned fifth message.
[0453] Step 603A: the seventh node and / or the eighth node may configure and / or perform RAN-triggered (continuous) data collection.
[0454] The RAN-triggered (continuous) data collection may support RAN nodes to perform self-optimization and / or artificial intelligence and / or machine learning related operations. For example, the collected data may be used by RAN nodes for training and / or inference and / or performance evaluation of artificial intelligence and / or machine learning models, etc.
[0455] FIG. 6B shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 6B shows a process of exchanging information related to RAN-triggered (continuous) data collection between two nodes, so that a seventh node and / or an eighth node can configure and / or perform RAN-triggered (Continuous) data collection.
[0456] In some implementations, for example, the seventh node may be a UE, and the eighth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In other implementations, for example, the seventh node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the eighth node may be a gNB or gNB-CU or gNB-DU or gNB CU-CP or gNB CU-UP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the seventh node may be an AMF or SMF or MME, and the eighth node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB. In yet other implementations, for example, the seventh node may be a gNB or gNB-CU or gNB CU-CP or en-gNB or eNB or ng-eNB, and the eighth node may be an AMF or SMF or MME. It may also be that, for example, the seventh node is a master node and the eighth node is a secondary node; for example, the seventh node is a secondary node and the eighth node is a master node; for example, the seventh node is a source node and the eighth node is a target node; for example, the seventh node is a target node and the eighth node is a source node.
[0457] Step 601B: the eighth node transmits the information related to the RAN-triggered (continuous) data collection to the seventh node. The information related to RAN-triggered (continuous) data collection may be the aforementioned fifth message.
[0458] Step 602B: the seventh node and / or the eighth node may configure and / or perform RAN-triggered (continuous) data collection.
[0459] The RAN-triggered (continuous) data collection may support RAN nodes to perform self-optimization and / or artificial intelligence and / or machine learning related operations. For example, the collected data may be used by RAN nodes for training and / or inference and / or performance evaluation of artificial intelligence and / or machine learning models, etc.
[0460] FIG. 6C shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 6C shows a process in which two nodes configure the UE for RAN-triggered (continuous) data collection to obtain (continuous) data.
[0461] Step 600C.a: optionally, the Base station 1 transmits information related to (continuous) data collection to a neighbor base station (e.g., Base station 2 in this illustration) to inform the neighbor base station of the information related to the (continuous) data collection. In some implementations, for example, the neighbor base station can obtain the data collection related configuration of Base station 1 through this information. For example, after obtaining data collection results, the neighbor base station may forward the data collection results based on this information.
[0462] Step 600C.b: optionally, the neighbor base station (e.g., Base station 2) transmits an acknowledgment for the information related to (continuous) data collection to Base station 1, to acknowledge the reception of the information related to (continuous) data collection.
[0463] Step 601C: Base station 1 transmits information related to (continuous) data collection to the corresponding UE. The information related to (continuous) data collection may be the aforementioned first message, and / or an MDT configuration.
[0464] Step 602C: the UE performs data collection. Optionally, the UE transmits the corresponding (continuous) data collection results to Base station 1. The (continuous) data collection results may be the aforementioned second message. This step is optional. Step 602C may also be replaced by the process in FIG. 5B.
[0465] Step 603C: the UE enters an RRC inactive state or an RRC idle state, and the UE performs data collection according to the (continuous) data collection configuration received in step 601C.
[0466] Step 604C: the UE returns to an RRC connected state. For example, the UE is connected to Base station 2. The UE transmits information related to the reporting of the (continuous) data collection to the connected base station (in this example, the connected base station is Base station 2). The information related to the reporting of (continuous) data collection may be the aforementioned third message. And / or, the UE transmits a message including information related to that the (continuous) data collection results are available to the connected base station (in this example, the connected base station is Base station 2). The message may include information related to one or more of the following: a (continuous) data collection result is available, a data collection result is available, part of the data collection results are available, part of the (continuous) data collection results are available, etc. In some implementations, for example, after receiving the message, Base station 2 may request the UE to report the (continuous) data collection results subsequently.
[0467] Step 605C: Base station 2 transmits a message including a (continuous) data collection result request to the UE to request the UE to report (continuous) data collection results. The message may include one or more of the following: a request for (continuous) data collection results, a request for data collection results, a request for part of the data collection results, a request for part of the (continuous) data collection results, etc.
[0468] Step 606C: the UE transmits (continuous) data collection results to Base station 2. The (continuous) data collection results may be the aforementioned second message. The (continuous) data collection results may be all of the (continuous) data collection results, part of the (continuous) data collection results, or currently available (continuous) data collection results.
[0469] Step 607C: Base station 2 transmits (continuous) data collection results to Base station 1. The (continuous) data collection results may be the aforementioned second message. Base station 2 may determine to transmit the received (continuous) data collection results to Base station 1 based on the information related to (continuous) data collection received in step 600C.a and / or the (continuous) data collection results received in step 606C and / or the information related to the reporting of the (continuous) data collection received in step 604C.
[0470] The RAN-triggered (continuous) data collection may support RAN nodes to perform self-optimization and / or artificial intelligence and / or machine learning related operations. For example, the collected data may be used by RAN nodes for training and / or inference and / or performance evaluation of artificial intelligence and / or machine learning models, etc.
[0471] FIG. 6D shows a schematic diagram of an aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure. Specifically, FIG. 6D shows a process in which two nodes configure the UE for RAN-triggered (continuous) data collection to obtain (continuous) data.
[0472] In some implementations, for example, the ninth node is Base station 1, the tenth node is Base station 2, and the eleventh node is AMF and / or OAM.
[0473] The exchanging of information related to RAN-triggered (continuous) data collection may be performed through Method A and / or Method B.
[0474] Method A:
[0475] Step 600D.a: the eleventh node transmits information related to RAN-triggered (continuous) data collection to the ninth node. The information related to RAN-triggered (continuous) data collection may be the aforementioned fifth message.
[0476] Method B:
[0477] Step 600D.b1: the ninth node transmits a request for RAN-triggered (continuous) data collection to the eleventh node. The request for RAN-triggered (continuous) data collection may be the aforementioned fourth message.
[0478] Step 600D.b2: the eleventh node transmits information related to RAN-triggered (continuous) data collection to the ninth node. The information related to RAN-triggered (continuous) data collection may be the aforementioned fifth message.
[0479] Step 600D.c and subsequent steps may refer to step 600C.a and subsequent steps in FIG. 6C.
[0480] The RAN-triggered (continuous) data collection may support RAN nodes to perform self-optimization and / or artificial intelligence and / or machine learning related operations. For example, the collected data may be used by RAN nodes for training and / or inference and / or performance evaluation of artificial intelligence and / or machine learning models, etc.
[0481] The above embodiments can be combined. Any one or more steps in the above embodiments can be omitted. The order of any one or more steps in the above embodiments is not limited and can be changed in any way.
[0482] In the above examples, if a node has a non-split architecture, a node CU and a node DU can be regarded as one node, and the interaction between the node CU and the node DU can be regarded as an internal interaction of the node. Alternatively, if the node has a non-split architecture, a node CU CP, a node CU UP, and a node DU can be regarded as one node, and the interaction between the node CU CP and the node CU UP, and / or the interaction between the node CU CP and the node DU can be regarded as internal interaction of the node.
[0483] In the above examples, if the node and / or cell to which the UE returns to an RRC connected state from an RRC inactive state and / or an RRC idle state is the same as the node and / or cell to which the UE was connected before entering the RRC inactive state and / or the RRC idle state, then Base station 1 and Base station 2 may be the same base station, and / or Secondary node 1 and Secondary node 2 may be the same node, and / or the ninth node and the tenth node may be the same node.
[0484] In the present disclosure, the embodiments are only given as examples, and the above embodiments may be combined with each other, etc.
[0485] In the above examples, for example, in a non-gNB CU and gNB DU split architecture, the first node (e.g., gNB CU) and the second node (e.g., gNB DU) may be combined into one node, for example, a gNB. In this case, the exchanging between gNB CU and gNB DU may be regarded as intra-node behaviors.
[0486] It should be understood that depending on the application scenario, the various examples, aspects, methods, steps, processes, etc. described herein may be implemented separately or in combination in any manner, which are not limited herein. In the present disclosure, to make the description more concise, generally, description performed in a specific step in an example or embodiment is not repeated again in the corresponding step in another example or embodiment. However, it should be understood that description performed in a specific step in an example or embodiment may apply to the corresponding step of any other example.
[0487]
[0488] Next, FIG. 7 shows a flowchart of a method 700 performed by a user equipment (UE) in a wireless communication system according to embodiments of the present disclosure.
[0489] As shown in FIG. 7, a method 700 performed by a user equipment (UE) in a wireless communication system according to embodiments of the present disclosure may include: in step S701, receiving first information related to data collection from a first node, wherein the first information includes first configuration information for the data collection and a first priority of the first configuration information; in step S702, performing the data collection based on the first configuration information; in step S703, connecting to a second node; in step S704, receiving second information related to the data collection from the second node, wherein the second information includes second configuration information for the data collection and a second priority of the second configuration information; and in step S705, transmitting fourth information including a data collection result related to the data collection to the second node, wherein the data collection result includes at least one of a first data collection result generated by the UE based on the first configuration information before connecting to the second node and a second data collection result generated by the UE based on configuration information selected by the UE after connecting to the second node.
[0490] According to embodiments of the present disclosure, the configuration information selected by the UE is selected from the first configuration information and the second configuration information based on the first priority and the second priority.
[0491] According to embodiments of the present disclosure, the method further includes: transmitting third information related to reporting of the data collection to the second node, wherein the third information includes the configuration information selected by the UE and a reason for selecting the configuration information.
[0492] According to embodiments of the present disclosure, the first information further includes at least one of: a radio resource control (RRC) state corresponding to the first configuration information, information related to whether the data collection is data collection triggered by a radio access network (RAN) node, identification information of a configuration node of the first configuration information, identification information of a reporting node of a data collection result corresponding to the first configuration information.
[0493] According to embodiments of the present disclosure, the fourth information further includes at least one of: time information related to a change of an RRC state of the UE, indication information related to a change of an RRC state of the UE, a radio resource control (RRC) state corresponding to the data collection result, time information corresponding to the data collection result, and a reason why the data collection ends.
[0494] According to embodiments of the present disclosure, the third information further includes at least one of: information about ongoing data collection by the UE, information about whether the UE supports new data collection, information about whether the data collection result is a result of data collection triggered by a radio access network (RAN) node, identification information of a reporting node of the data collection result.
[0495]
[0496] FIG. 8A shows a flowchart of a method 800 performed by a second node in a wireless communication system according to embodiments of the present disclosure.
[0497] As shown in FIG. 8A, a method 800 performed by a second node in a wireless communication system according to embodiments of the present disclosure may include: in step S801, transmitting second information related to data collection to a user equipment (UE), wherein the second information includes second configuration information for the data collection and a second priority of the second configuration information; and in step S802, receiving fourth information including a data collection result related to the data collection from the UE, wherein the data collection result includes at least one of a first data collection result generated by the UE based on first configuration information for the data collection before connecting to the second node and a second data collection result generated by the UE based on configuration information selected by the UE after connecting to the second node, wherein the first configuration information and a first priority of the first configuration information are included in first information related to the data collection received by the UE from a first node.
[0498] According to embodiments of the present disclosure, the configuration information selected by the UE is selected from the first configuration information and the second configuration information based on the first priority and the second priority.
[0499] According to embodiments of the present disclosure, the method further includes: receiving third information related to reporting of the data collection from the UE, wherein the third information includes the configuration information selected by the UE and a reason for selecting the configuration information.
[0500] According to embodiments of the present disclosure, the first information further includes at least one of: a radio resource control (RRC) state corresponding to the first configuration information, information related to whether the data collection is data collection triggered by a radio access network (RAN) node, identification information of a configuration node of the first configuration information, identification information of a reporting node of a data collection result corresponding to the first configuration information.
[0501] According to embodiments of the present disclosure, the fourth information further includes at least one of: time information related to a change of an RRC state of the UE, indication information related to a change of an RRC state of the UE, a radio resource control (RRC) state corresponding to the data collection result, time information corresponding to the data collection result, and a reason why the data collection ends.
[0502] According to embodiments of the present disclosure, the third information further includes at least one of: information about ongoing data collection by the UE, information about whether the UE supports new data collection, information about whether the data collection result is a result of data collection triggered by a radio access network (RAN) node, identification information of a reporting node of the data collection result.
[0503] According to embodiments of the present disclosure, the information about whether the data collection result is a result of data collection triggered by a radio access network (RAN) node further includes identification information of the RAN node triggering the data collection, wherein the method further includes: in case the data collection result is a result of data collection triggered by a radio access network (RAN) node, transmitting the data collection result to the RAN node and / or the reporting node based on identification information of the RAN node and / or the identification information of the reporting node of the data collection result.
[0504] FIG. 8B shows a flowchart of a method 810 performed by a first node in a wireless communication system according to embodiments of the present disclosure.
[0505] As shown in FIG. 8B, a method 810 performed by a first node in a wireless communication system according to embodiments of the present disclosure may include: in step S811, transmitting first information related to data collection to a user equipment (UE), wherein the first information includes first configuration information for the data collection and a first priority of the first configuration information; and in step S812, receiving a result of the data collection based on the first configuration from the UE. In some implementations, second information related to the data collection is transmitted from a second node to the UE after the UE connects to the second node, wherein the second information includes second configuration information for the data collection and a second priority of the second configuration information. In some implementations, fourth information including a data collection result related to the data collection is transmitted from the UE to the second node, wherein the data collection result includes at least one of a first data collection result generated by the UE based on the first configuration information before connecting to the second node and a second data collection result generated by the UE based on configuration information selected by the UE after connecting to the second node.
[0506] According to embodiments of the present disclosure, the configuration information selected by the UE is selected from the first configuration information and the second configuration information based on the first priority and the second priority.
[0507] According to embodiments of the present disclosure, the first information further includes at least one of: a radio resource control (RRC) state corresponding to the first configuration information, information related to whether the data collection is data collection triggered by a radio access network (RAN) node, identification information of a configuration node of the first configuration information, identification information of a reporting node of a data collection result corresponding to the first configuration information.
[0508] According to embodiments of the present disclosure, the fourth information further includes at least one of: time information related to a change of an RRC state of the UE, indication information related to a change of an RRC state of the UE, a radio resource control (RRC) state corresponding to the data collection result, time information corresponding to the data collection result, and a reason why the data collection ends.
[0509] It should be understood that the methods 700, 800, 810, etc. according to the embodiments of the present disclosure may also include any of the steps described in conjunction with various examples, aspects, drawings, etc. of the present disclosure, or delete one or more steps thereof.
[0510]
[0511] Next, FIG.9 shows a schematic diagram of a node 900 according to embodiments of the present disclosure.
[0512] As shown in FIG. 9, a node (or node device) 900 according to embodiments of the present disclosure may include a transceiver 910 and a processor 920. The transceiver 910 may be configured to transmit and receive signals. The processor 920 may be coupled to the transceiver 910 and may be configured to (e.g., control the transceiver 910 to) perform methods performed by any node according to embodiments of the present disclosure.
[0513]
[0514] FIG. 10 shows a schematic diagram of a user equipment (UE) 1000 according to embodiments of the present disclosure.
[0515] As shown in FIG. 10, a user equipment (UE) 1000 according to embodiments of the present disclosure may include a transceiver 1010 and a processor 1020. The transceiver 1010 can be configured to transmit and receive signals. The processor 1020 may be coupled to the transceiver 1010 and may be configured to (e.g., control the transceiver 1010 to) perform methods performed by a user equipment (UE) according to embodiments of the present disclosure. In the present disclosure, a processor may also be referred to as a controller.
[0516] Embodiments of the present disclosure also provide a computer-readable medium having stored thereon computer-readable instructions which, when executed by a processor, implement any method according to embodiments of the present disclosure.
[0517] Various embodiments of the present disclosure may be implemented as computer-readable codes embodied on a computer-readable recording medium from a specific perspective. A computer-readable recording medium is any data storage device that can store data readable by a computer system. Examples of computer-readable recording media may include read-only memory (ROM), random access memory (RAM), compact disk read-only memory (CD-ROM), magnetic tape, floppy disk, optical data storage device, carrier wave (e.g., data transmission via the Internet), etc. Computer-readable recording media can be distributed by computer systems connected via a network, and thus computer-readable codes can be stored and executed in a distributed manner. Furthermore, functional programs, codes and code segments for implementing various embodiments of the present disclosure can be easily explained by those skilled in the art to which the embodiments of the present disclosure are applied.
[0518] It will be understood that the embodiments of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software. The software may be stored as program instructions or computer-readable codes executable on a processor on a non-transitory computer-readable medium. Examples of non-transitory computer-readable recording media include magnetic storage media (such as ROM, floppy disk, hard disk, etc.) and optical recording media (such as CD-ROM, digital video disk (DVD), etc.). Non-transitory computer-readable recording media may also be distributed on computer systems coupled to a network, so that computer-readable codes are stored and executed in a distributed manner. The medium can be read by a computer, stored in a memory, and executed by a processor. Various embodiments may be implemented by a computer or a portable terminal including a controller and a memory, and the memory may be an example of a non-transitory computer-readable recording medium suitable for storing program (s) with instructions for implementing embodiments of the present disclosure. The present disclosure may be realized by a program with code for concretely implementing the apparatus and method described in the claims, which is stored in a machine (or computer)-readable storage medium. The program may be electronically carried on any medium, such as a communication signal transmitted via a wired or wireless connection, and the present disclosure suitably includes its equivalents.
[0519] What has been described above is only the specific implementation of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Anyone who is familiar with this technical field may make various changes or substitutions within the technical scope disclosed in the present disclosure, and these changes or substitutions should be covered within the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.
Claims
1.A method performed by a user equipment (UE) in a wireless communication system, comprising:receiving first information related to data collection from a first node, wherein the first information includes first configuration information for the data collection and a first priority of the first configuration information;performing the data collection based on the first configuration information;connecting to a second node;receiving second information related to the data collection from the second node, wherein the second information includes second configuration information for the data collection and a second priority of the second configuration information; andtransmitting fourth information including a data collection result related to the data collection to the second node, wherein the data collection result includes at least one of a first data collection result generated by the UE based on the first configuration information before connecting to the second node and a second data collection result generated by the UE based on configuration information selected by the UE after connecting to the second node.2.The method of claim 1, wherein the configuration information selected by the UE is selected from the first configuration information and the second configuration information based on the first priority and the second priority.3.The method of claim 1, further comprising:transmitting third information related to reporting of the data collection to the second node, wherein the third information includes the configuration information selected by the UE and a reason for selecting the configuration information, andwherein the third information further includes at least one of:information about ongoing data collection by the UE, information about whether the UE supports new data collection, information about whether the data collection result is a result of data collection triggered by a radio access network (RAN) node, identification information of a reporting node of the data collection result.4.The method of claim 1, wherein the first information further includes at least one of:a radio resource control (RRC) state corresponding to the first configuration information, information related to whether the data collection is data collection triggered by a radio access network (RAN) node, identification information of a configuration node of the first configuration information, identification information of a reporting node of a data collection result corresponding to the first configuration information, andwherein the fourth information further includes at least one of:time information related to a change of an RRC state of the UE, indication information related to a change of an RRC state of the UE, a radio resource control (RRC) state corresponding to the data collection result, time information corresponding to the data collection result, and a reason why the data collection ends.5.A method performed by a second node in a wireless communication system, comprising:transmitting second information related to data collection to a user equipment (UE), wherein the second information includes second configuration information for the data collection and a second priority of the second configuration information; andreceiving fourth information including a data collection result related to the data collection from the UE, wherein the data collection result includes at least one of a first data collection result generated by the UE based on first configuration information for the data collection before connecting to the second node and a second data collection result generated by the UE based on configuration information selected by the UE after connecting to the second node,wherein the first configuration information and a first priority of the first configuration information are included in first information related to the data collection received by the UE from a first node.6.The method of claim 5, wherein the configuration information selected by the UE is selected from the first configuration information and the second configuration information based on the first priority and the second priority.7.The method of claim 5, further comprising:receiving third information related to reporting of the data collection from the UE, wherein the third information includes the configuration information selected by the UE and a reason for selecting the configuration information, andwherein the third information further includes at least one of:information about ongoing data collection by the UE, information about whether the UE supports new data collection, information about whether the data collection result is a result of data collection triggered by a radio access network (RAN) node, identification information of a reporting node of the data collection result,wherein the information about whether the data collection result is a result of data collection triggered by a radio access network (RAN) node further includes identification information of the RAN node triggering the data collection,wherein the method further comprises:in case the data collection result is a result of data collection triggered by a radio access network (RAN) node, transmitting the data collection result to the RAN node and / or the reporting node based on identification information of the RAN node and / or the identification information of the reporting node of the data collection result.8.The method of claim 5, wherein the first information further includes at least one of:a radio resource control (RRC) state corresponding to the first configuration information, information related to whether the data collection is data collection triggered by a radio access network (RAN) node, identification information of a configuration node of the first configuration information, identification information of a reporting node of a data collection result corresponding to the first configuration information, and wherein the fourth information further includes at least one of:time information related to a change of an RRC state of the UE, indication information related to a change of an RRC state of the UE, a radio resource control (RRC) state corresponding to the data collection result, time information corresponding to the data collection result, and a reason why the data collection ends.9.A method performed by a first node in a wireless communication system, comprising:transmitting first information related to data collection to a user equipment (UE), wherein the first information includes first configuration information for the data collection and a first priority of the first configuration information; andreceiving a result of the data collection based on the first configuration from the UE,wherein second information related to the data collection is transmitted from a second node to the UE after the UE connects to the second node, wherein the second information includes second configuration information for the data collection and a second priority of the second configuration information;wherein fourth information including a data collection result related to the data collection is transmitted from the UE to the second node, wherein the data collection result includes at least one of a first data collection result generated by the UE based on the first configuration information before connecting to the second node and a second data collection result generated by the UE based on configuration information selected by the UE after connecting to the second node.10.The method of claim 9, wherein the configuration information selected by the UE is selected from the first configuration information and the second configuration information based on the first priority and the second priority.11.The method of claim 9, wherein the first information further includes at least one of:a radio resource control (RRC) state corresponding to the first configuration information, information related to whether the data collection is data collection triggered by a radio access network (RAN) node, identification information of a configuration node of the first configuration information, identification information of a reporting node of a data collection result corresponding to the first configuration information.12.The method of claim 9, wherein the fourth information further includes at least one of:time information related to a change of an RRC state of the UE, indication information related to a change of an RRC state of the UE, a radio resource control (RRC) state corresponding to the data collection result, time information corresponding to the data collection result, and a reason why the data collection ends.13.A user equipment (UE) in a wireless communication system, comprising:a transceiver configured to transmit and receive signals; anda controller coupled to the transceiver and configured to perform the method of any of claims 1-4.14.A node in a wireless communication system, comprising:a transceiver configured to transmit and receive signals; anda controller coupled to the transceiver and configured to perform the method of any of claims 5-8 or 9-12.15.A computer-readable medium having computer-readable instructions stored thereon, the instructions, when executed by a processor, being configured to implement the method of any of claims 1-4 or 5-8 or 9-12.
