Nodes, user equipment, and their execution methods in a wireless communication system
By exchanging configuration information and priorities in the wireless communication system, the complexity of continuous data collection in 5G systems is solved, enabling efficient and universal data collection under different RRC states.
Patent Information
- Application Number
- CN202510592314.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-08
- Publication Date
- 2026-11-10
AI Technical Summary
In existing wireless communication systems, especially in 5G or near-5G communication systems, the data collection process is complex. In particular, the support for continuous data collection under different Radio Resource Control (RRC) states is insufficient, resulting in high data collection configuration complexity and difficulty in achieving high applicability.
By exchanging configuration and information related to data collection between nodes and user equipment (UE) in a wireless communication system, priority can be selected for data collection, supporting continuous data collection regardless of the UE's RRC state, and simplifying data collection configuration.
It simplifies data collection configuration under different RRC states, improves the universality and efficiency of data collection, and reduces the complexity of data collection.
Smart Images

Figure CN123075460A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of wireless communication technology, and more specifically, to nodes, user equipment, and methods for performing such operations in wireless communication systems. Background Technology
[0002] To meet the increased demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or near-5G communication systems. Therefore, 5G or near-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems".
[0003] Wireless communication is one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services surpassed 5 billion and continues to grow rapidly. The demand for wireless data services is growing rapidly due to the increasing prevalence of smartphones and other mobile data devices (such as tablets, laptops, netbooks, e-book readers, and machine-type devices) among consumers and businesses. To meet the rapid growth of mobile data services and support new applications and deployments, improving the efficiency and coverage of wireless interfaces is crucial. Summary of the Invention
[0004] Embodiments of this disclosure provide 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; and sending fourth information to the second node including data collection results related to the data collection, wherein the data collection results include 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.
[0005] According to embodiments of this disclosure, the configuration information selected by the UE is chosen from the first configuration information and the second configuration information based on the first priority and the second priority.
[0006] According to an embodiment of this disclosure, the method further includes: sending third information related to the reporting of the data collection to the second node, wherein the third information includes the configuration information selected by the UE and the reason for selecting the configuration information.
[0007] According to embodiments of this disclosure, the first information further includes at least one of the following: the Radio Resource Control (RRC) status corresponding to the first configuration information, information related to whether the data collection is triggered by a Radio Access Network (RAN) node, the identification information of the configuration node of the first configuration information, and the identification information of the reporting node of the data collection results corresponding to the first configuration information.
[0008] According to embodiments of this disclosure, the fourth information further includes at least one of the following: time information related to a change in the RRC state of the UE, indication information related to a change in the 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 for the end of the data collection.
[0009] According to embodiments of this disclosure, the third information further includes at least one of the following: information about the data collection that the UE is currently conducting, information about whether the UE supports new data collection, information about whether the data collection result is the result of data collection triggered by a radio access network (RAN) node, and identification information of the node that reported the data collection result.
[0010] Embodiments of this disclosure provide a method performed by a second node in a wireless communication system, comprising: sending 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 from the UE fourth information including data collection results related to the data collection, wherein the data collection results include 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 the first priority of the first configuration information are included in the first information related to the data collection received by the UE from the first node.
[0011] According to embodiments of this disclosure, the configuration information selected by the UE is chosen from the first configuration information and the second configuration information based on the first priority and the second priority.
[0012] According to embodiments of this disclosure, the method further includes: receiving third information from the UE related to the reporting of the data collection, wherein the third information includes the configuration information selected by the UE and the reason for selecting the configuration information.
[0013] According to embodiments of this disclosure, the first information further includes at least one of the following: the Radio Resource Control (RRC) status corresponding to the first configuration information, information related to whether the data collection is triggered by a Radio Access Network (RAN) node, the identification information of the configuration node of the first configuration information, and the identification information of the reporting node of the data collection results corresponding to the first configuration information.
[0014] According to embodiments of this disclosure, the fourth information further includes at least one of the following: time information related to a change in the RRC state of the UE, indication information related to a change in the 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 for the end of the data collection.
[0015] According to embodiments of this disclosure, the third information further includes at least one of the following: information about the data collection that the UE is currently conducting, information about whether the UE supports new data collection, information about whether the data collection result is the result of data collection triggered by a radio access network (RAN) node, and identification information of the node that reported the data collection result.
[0016] According to embodiments of this disclosure, the information regarding whether the data collection result is a result of data collection triggered by a Radio Access Network (RAN) node further includes the identification information of the RAN node that triggered the data collection. The method further includes: if the data collection result is a result of data collection triggered by a RAN node, sending the data collection result to the RAN node and / or the reporting node based on the identification information of the RAN node and / or the identification information of the reporting node of the data collection result.
[0017] Embodiments of this disclosure provide a method performed by a first node in a wireless communication system, comprising: sending 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 from the UE the result of the data collection based on the first configuration, wherein, after the UE connects to a second node, second information related to the data collection is sent from the second node to the UE, 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 the data collection result related to the data collection is sent 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.
[0018] According to embodiments of this disclosure, the configuration information selected by the UE is chosen from the first configuration information and the second configuration information based on the first priority and the second priority.
[0019] According to embodiments of this disclosure, the first information further includes at least one of the following: the Radio Resource Control (RRC) status corresponding to the first configuration information, information related to whether the data collection is triggered by a Radio Access Network (RAN) node, the identification information of the configuration node of the first configuration information, and the identification information of the reporting node of the data collection results corresponding to the first configuration information.
[0020] According to embodiments of this disclosure, the fourth information further includes at least one of the following: time information related to a change in the RRC state of the UE, indication information related to a change in the 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 for the end of the data collection.
[0021] Embodiments of this 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 a method performed by any node in the wireless communication system according to embodiments of this disclosure.
[0022] Embodiments of this 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 a method executed by the UE in the wireless communication system according to embodiments of this disclosure.
[0023] Embodiments of this disclosure provide a computer-readable medium having computer-readable instructions stored thereon, which, when executed by a processor, are used to implement a method performed by any node and / or user equipment in a wireless communication system according to embodiments of this disclosure.
[0024] The method provided in this disclosure, performed by a node and / or user equipment (UE) in a wireless communication system, enables (continuous) data collection without distinguishing the RRC state of the UE by exchanging configuration information related to data collection and / or information related to the data collection being performed by the UE between the node and / or UE. Attached Figure Description
[0025] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, wherein:
[0026] Figure 1 This is an exemplary system architecture for System Architecture Evolution (SAE);
[0027] Figure 2 These are exemplary system architectures based on various embodiments of this disclosure;
[0028] Figure 3 A schematic diagram of one aspect of a method for supporting (continuous) data collection according to an embodiment of the present disclosure is shown;
[0029] Figures 4A-4G Schematic diagrams of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure are shown respectively;
[0030] Figures 5A-5C Schematic diagrams of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure are shown respectively;
[0031] Figures 6A-6D Schematic diagrams of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure are shown respectively;
[0032] Figure 7 A flowchart illustrating a method performed by a user equipment (UE) in a wireless communication system according to an embodiment of the present disclosure is shown;
[0033] Figure 8AA flowchart is shown illustrating a method performed by a second node in a wireless communication system according to an embodiment of this disclosure;
[0034] Figure 8B A flowchart is shown showing a method performed by a first node in a wireless communication system according to an embodiment of the present disclosure;
[0035] Figure 9 A schematic diagram of a node according to an embodiment of this disclosure is shown; and
[0036] Figure 10 A schematic diagram of a user equipment (UE) according to an embodiment of the present disclosure is shown. Detailed Implementation
[0037] The following description, with reference to the accompanying drawings, is provided to aid in a thorough understanding of the various embodiments of this disclosure as defined by the claims and their equivalents. This description includes various specific details to aid understanding but should be considered exemplary only. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of this disclosure. Furthermore, for clarity and brevity, descriptions of well-known functions and structures may be omitted.
[0038] The terms and wording used in the following description and claims are not limited to their dictionary meanings, but are merely used by the inventors to enable a clear and consistent understanding of this disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of this disclosure is for illustrative purposes only and not for limiting the purpose of this disclosure as defined in the appended claims and their equivalents.
[0039] It should be understood that the singular forms of “one,” “an,” and “the” include plural references unless the context clearly indicates otherwise. Thus, for example, the reference to “component surface” includes one or more such surfaces.
[0040] The terms “comprising” or “may include” refer to the presence of a corresponding disclosed function, operation, or component that may be used in the various embodiments of this disclosure, rather than limiting the presence of one or more additional functions, operations, or features. Furthermore, the terms “comprising” or “having” may be interpreted as indicating certain characteristics, numbers, steps, operations, constituent elements, components, or combinations thereof, but should not be construed as excluding the possibility of the presence of one or more other characteristics, numbers, steps, operations, constituent elements, components, or combinations thereof.
[0041] The term "or" as used in the various embodiments of this disclosure includes any of the listed terms and all combinations thereof. For example, "A or B" may include A, may include B, or may include both A and B.
[0042] Unless otherwise defined, all terms used in this disclosure (including technical or scientific terms) have the same meaning as understood by one of those skilled in the art as described herein. Common terms as defined in dictionaries are to be interpreted as having a meaning consistent with the context in the relevant technical field and should not be interpreted ideally or overly formally unless expressly defined in this disclosure.
[0043] The accompanying drawings and various embodiments used to illustrate the principles of this disclosure in this patent document are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or apparatus.
[0044] Figure 1 This is an exemplary system architecture 100 of System Architecture Evolution (SAE). User Equipment (UE) 101 is a terminal device used to receive data. Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 102 is a radio access network, including macro base stations (eNodeB / NodeB) that provide the UE with an interface to access the radio network. Mobility Management Entity (MME) 103 is responsible for managing the UE's mobility context, session context, and security information. Serving Gateway (SGW) 104 primarily provides user plane functions; MME 103 and SGW 104 may reside in the same physical entity. Packet Data Network Gateway (PGW) 105 is responsible for functions such as charging and lawful interception, and may also reside in the same physical entity as SGW 104. Policy and Charging Rules Function Entity (PCRF) 106 provides Quality of Service (QoS) policies and charging criteria. Universal Packet Radio Service Support Node (SGSN) 108 is a network node device in the Universal Mobile Telecommunications System (UMTS) that provides routing for data transmission. The Home Subscriber Server (HSS) 109 is the UE's home subsystem, responsible for protecting user information including the UE's current location, the address of the serving node, user security information, and the UE's packet data context.
[0045] Figure 2 This 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.
[0046] User Equipment (UE) 201 is the terminal equipment used to receive data. Next-Generation Radio Access Network (NG-RAN) 202 is the radio access network, which includes base stations (gNBs or eNBs connected to the 5G core network 5GC; eNBs connected to the 5GC are also called ng-gNBs) that provide the UE with access to the radio network interface. Access Control and Mobility Management Function Entity (AMF) 203 is responsible for managing the UE's mobility context and security information. User Plane Function Entity (UPF) 204 primarily provides user plane functions. Session Management Function Entity (SMF) 205 is responsible for session management. Data Network (DN) 206 includes services such as operator services, internet access, and third-party services.
[0047] The nodes and / or entities described in this 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 logical units, as well as the cells and / or beams and / or slices they manage.
[0048] In this disclosure, a node may refer to any node, or to the cell and / or beam managed by the node.
[0049] In this disclosure, "cell" can refer to any cell, the node where the cell is located, or the beam corresponding to the cell, etc.
[0050] The information and / or fields mentioned in this disclosure may be the average value, instantaneous value, maximum value, minimum value, etc. of the corresponding information and / or fields and / or parameters and / or values, and this disclosure does not limit them.
[0051] The information and / or fields described in this disclosure may correspond to one or more of the following: up, down, up and down, up or down.
[0052] The information and / or fields described in this disclosure may be measured and / or actual values of the corresponding information and / or fields and / or parameters and / or numerical values, or their predicted values.
[0053] The signal strength and / or signal quality and / or measurement report results and / or measurement results mentioned in this 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.
[0054] In this disclosure, a slice identifier can be identified using one or more Single Network Slice Selection Assistance Information (S-NSSAI).
[0055] In this disclosure, failure type and / or problem type and / or report type may refer to each other.
[0056] In this disclosure, reports related to the Self-Optimization Network (SON) may include one or more of the following: Connection Establishment Failure (CEF) reports, Random Access reports, Successful Handover reports, Radio Link Failure (RLF) reports, measurement reports, or other reports related to wireless connectivity.
[0057] In this disclosure, wireless link failure can refer to both wireless link failure and handover failure.
[0058] In this disclosure, the TA value obtained in advance and the TA value in the LTM command can refer to each other.
[0059] In this disclosure, network self-optimization decisions may include network energy saving, load balancing, coverage and / or capacity optimization, mobility optimization and / or management, configuration formulation and / or configuration updates, etc.
[0060] In this disclosure, results and reports may refer to each other.
[0061] In this disclosure, time can be represented by one or more of the following: timestamp, point in time, time interval, timer, time period, time length, time cycle, time interval, duration, etc. The time length can be the time elapsed since a certain point in time, which can be the current moment or any other moment. The time can be relative or absolute. In some implementations, a time period can be represented by a separate field; for example, it can be a combination of start and end times, or a combination of start and time period.
[0062] In this disclosure, Quality of Experience (QoE) parameters and / or user experience parameters may include one or more of the following: Round-trip time, Jitter duration, Corruption duration, Average throughput, Initial playout delay, Playout Delay at InitialStartup, Device information, Rendered viewports, Codec information, Buffer level, Representation switch events, Play List, Media presentation description (MPD) information, Interactivity Summary, Interactivity Event List, etc.
[0063] In this disclosure, the Quality of Service (QoS) parameters may include at least one of the following: packet loss rate, latency, throughput, data rate, etc.
[0064] In this disclosure, load status 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, scheduling PDCCHCCE usage, Transport Network Layer (TNL) capacity indication, radio resource status, integrated available capacity group, integrated available resource group, number of active user terminals, number of Radio Resource Control (RRC) connections, slice available capacity, hardware capacity indication, S1 TNL load indication, hardware load indication, almost blank subframe (ABS) status, Reference Signal Received Power (RSRP) measurement report list, Reference Signal Received Quality (RSRQ) measurement report, Signal to Interference plus Noise Ratio (SINR) measurement report, Channel State Information (CSI) report, Cell Report Indicator, Channel Occupancy (CSI) The parameters include the occupancy time ratio, energy detection threshold, signal strength and / or signal quality, channel busy ratio, data volume, and jitter of the aforementioned parameters.
[0065] In this disclosure, load status and / or load information may refer to resource status.
[0066] In this disclosure, capacity information may include one or more of the following: QoS requirements, QoS levels, capacity status, average QoS requirements, average QoS levels, average capacity status identifier, the proportion of one or more QoS requirements, the proportion of one or more QoS levels, and the proportion of one and / or more capacity status identifiers. The capacity status identifier is an identifier representing a capacity configuration; one identifier can represent one capacity configuration. QoS levels can be represented by identifiers, for example, a mapped 5G QoS Identifier (5QI) or QoS Class Identifier (QCI).
[0067] In this disclosure, capacity prediction information can be a predicted value of capacity information.
[0068] In this disclosure, coverage information may include one or more of the following: coverage status, information related to an increase or / or decrease in coverage area, the percentage by which coverage area increases or / or decreases, information related to loads located at the cell edge, and information related to loads that have changed from being within the coverage area to being outside the coverage area due to a change in coverage area. The coverage status can be represented by an identifier, with one identifier representing one coverage status.
[0069] In this disclosure, "coverage" and "coverage range" can refer to each other.
[0070] In this disclosure, the coverage prediction information can be the predicted value of the coverage information.
[0071] In this disclosure, coverage and / or capacity change and coverage and / or capacity optimization may refer to each other.
[0072] In this disclosure, coverage and / or capacity policies (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: the identifier of the replacing cell, the identifier of the replaced cell, the proportion of the replacing cell that can replace the replaced cell, etc. The beam coverage change information may include one or more of the following: beam identifier, beam coverage status, etc.
[0073] In this disclosure, "beam" can refer to the Synchronization Signal and Physical Broadcast Channel (PBCH) block (SSB) beam, or any other beam.
[0074] In this disclosure, location and / or location range can be referred to by one or more of the following: coordinates, area, cell identifier, beam identifier, identifier for representing location and / or area, etc. The cell identifier can include one or more of the following: access cell identifier, connected cell identifier, serving cell identifier, etc. The beam identifier can include one or more of the following: access beam identifier, connected beam identifier, access beam identifier, etc. The identifier for representing location and / or area can be used to represent one or more locations and / or one or more areas. In some embodiments, for example, an identifier can be used to represent an area where the distance is greater than and / or equal to and / or less than a threshold. In other embodiments, for example, an identifier can be used to represent an area where the signal quality is greater than and / or equal to and / or less than a threshold.
[0075] In this disclosure, the target node can also be a candidate target node, a target master node, a target auxiliary node, a candidate target master node, a candidate target auxiliary node, etc.
[0076] In this disclosure, the source node can also be a source master node, a source slave node, etc.
[0077] In this disclosure, data collection can be Minimization of Drive Tests (MDT) or any other data collection method, without limitation. MDT can be a logged MDT or an immediate MDT. MDT can be a signaling-based MDT or a management-based MDT. When a UE connects from one base station to another, (continuous) data collection is required, but existing technologies have insufficient research on (continuous) data collection.
[0078] In this disclosure, "base station" can refer to any device in a wireless access network that can be connected to a user equipment, such as a gNB in a 5G network or a base station or node in any other network.
[0079] In this disclosure, data collection may include continuous data collection or non-continuous data collection.
[0080] In this disclosure, (continuous) data collection can refer to data collection performed by the UE without distinguishing between the UE's RRC state. That is, (continuous) data collection means that after the UE changes its RRC state, it can continue to collect data according to the previous configuration and / or continuously collect data according to the new configuration.
[0081] In this disclosure, collection and measurement are interchangeable. Data collection and data measurement are interchangeable.
[0082] In this disclosure, the Radio Resource Control (RRC) state may include one or more of the following: RRC connected state, RRC idle state, RRC inactive state, etc. The RRC state in this disclosure can also be extended to the Connection Management (CM) state; for example, the method applicable to the RRC state of the UE in this disclosure can also be applied to the CM state of the UE. In this disclosure, the CM state may include one or more of the following: CM connected state, CM idle state, etc. RRC state can refer to the UE's RRC state. CM state can refer to the UE's CM state.
[0083] In this disclosure, the data collected may include one or more of the following:
[0084] ●MDT-related data: may include one or more of the following:
[0085] ○ User ID
[0086] ○ Measurement Results
[0087] ○Location Information
[0088] ○ Power Headroom
[0089] ○PDCP SDU data volume
[0090] ○ (Average) UE throughput
[0091] ○ Data packet delay
[0092] ○ Measurement results of the service area
[0093] ○ Neighboring area measurement results
[0094] ○Timestamp
[0095] ●User trajectory-related data: may include one or more of the following:
[0096] ○ User ID
[0097] ○ Visited community identifier
[0098] ○ Accessing the main cell identifier
[0099] ○ Accessible secondary community identifier
[0100] ○ Primary cell identifier and secondary cell identifier accessed: These indicate the primary cell and secondary cell accessed by the user in the case of dual connectivity.
[0101] ○ The node where the accessed cell is located: This can be either the node identifier or the node name.
[0102] ○The node where the main cell is located: This can be either the node identifier or the node name.
[0103] ○ The node where the secondary cell is located: This can be either the node identifier or the node name.
[0104] ○ Visiting time and / or stay time
[0105] ○ Coordinates
[0106] ○ Accessed beam information: This can be a beam identifier.
[0107] ●User performance-related data: may include one or more of the following:
[0108] ○ User ID
[0109] ○ User performance collection time
[0110] ○ The node corresponding to user performance collection: can be either a node identifier or a node name.
[0111] ○ Cell identifier corresponding to user performance
[0112] ○ Beam identifier corresponding to user performance
[0113] ○ Slice identifier corresponding to user performance
[0114] ○ User performance-related Protocol Data Unit (PDU) session identifier
[0115] ○Packet Data Unit (DRB) identifier corresponding to user performance
[0116] ○ QoS flow identifier corresponding to user performance
[0117] ○ User performance: may include one or more of the following: uplink and / or downlink data rate, uplink and / or downlink throughput, uplink and / or downlink latency, uplink and / or downlink packet loss rate, uplink and / or downlink QoE parameters.
[0118] ●Network performance related data: may include one or more of the following:
[0119] ○ Network performance collection time
[0120] ○ The node corresponding to network performance collection: can be a node identifier or a node name.
[0121] ○ Cell identifier corresponding to network performance
[0122] ○ Beam identifier corresponding to network performance
[0123] ○Slice identifier corresponding to network performance
[0124] ○ Data Radio Bearer (DRB) identifier corresponding to network performance
[0125] ○ QoS flow identifier corresponding to network performance
[0126] ○ Network performance: may include one or more of the following: uplink and / or downlink data rate, uplink and / or downlink throughput, uplink and / or downlink latency, uplink and / or downlink packet loss rate, uplink and / or downlink QoE parameters.
[0127] ●User measurement result information: may include one or more of the following:
[0128] ○ User ID
[0129] ○ Node identifier and / or cell identifier corresponding to user measurement results
[0130] ○ Measurement Results
[0131] ○ Measurement time
[0132] ●Relevant perception result information: may include one or more of the following:
[0133] ○ User ID
[0134] ○ Node identifiers and / or cell identifiers corresponding to user perception-related measurement results
[0135] ○Sensory related measurement results
[0136] ○Sensing related measurement time
[0137] In this disclosure, user equipment (UE) can refer to user, terminal, etc.
[0138] In this disclosure, "related to" or "associated with" can also mean "including," and they can be used interchangeably. For example, "the first message related to / associated with the first information" can also mean "the first message including the first information," and so on.
[0139] Existing technologies are complex to support data collection (e.g., minimizing road tests), so a simple and widely applicable solution is needed.
[0140] Example 1
[0141] One aspect of this disclosure provides a method for supporting (continuous) data collection, which may include one or more of the following steps.
[0142] The first node sends a first message to the second node, including configuration information related to (continuous) data collection (or information related to (continuous) data collection), to inform the second node of this configuration information. The second node performs (continuous) data collection according to the configuration information, and / or decides whether to perform (continuous) data collection based on the configuration information, and / or selects and / or configures the UE to perform (continuous) data collection after receiving the configuration information, and / or the UE decides whether to perform (continuous) data collection based on the configuration information, etc. This scheme can support data collection without distinguishing the UE's RRC state, reducing the complexity of data collection configuration and achieving highly versatile data collection.
[0143] In some implementations, the first message may include one or more of the following: a Handover Request message for Xn, or a S-NODE ADDITION REQUEST message, or a S-NODE MODIFICATION REQUEST message, or an NG-RAN NODE CONFIGURATION UPDATE message, or an NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, or an Xn SETUP REQUEST message, or an Xn SETUP RESPONSE message, or a RETRIEVE UE CONTEXT RESPONSE message; a UE CONTEXT RELEASE REQUEST message for NG, or a UE CONTEXT MODIFICATION REQUEST message, or a UE CONTEXT MODIFICATION RESPONSE message, or an INITIAL CONTEXT SETUP message. REQUEST message; RRC reconfiguration message; or another and / or newly defined RRC message and / or Xn message and / or X2 message and / or F1 message and / or E1 message and / or NG message and / or RRC container and / or MAC CE, etc.
[0144] In some implementations, the first message may include one or more of the following information and / or fields:
[0145] ●Sending node identifier: Used to identify the node that sent the message.
[0146] ● Receiver node identifier: Used to identify the node that received the message.
[0147] ● Request Identifier: Used to identify the request corresponding to this message.
[0148] ●Measurement identifier: Used to identify the measurement corresponding to this message.
[0149] ●Prediction identifier: Used to indicate the prediction corresponding to this message.
[0150] ● Reporting identifier: Used to identify the report corresponding to this message.
[0151] ● Configuration Identifier: Used to identify the (continuous) data collection configuration corresponding to this message. This identifier can uniquely identify a data collection configuration. For example, the configuration can be an MDT configuration or a continuous MDT configuration. For example, the configuration can be for one or more of the following: RRC idle state, RRC inactive state, and RRC connected state. For example, the configuration can be indiscriminate of the UE's RRC state. That is, the UE can perform data collection according to this configuration in any RRC state.
[0152] ● (Continuous) Data Collection (Request) Identifier: Used to indicate that the information contains a (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 the (continuous) data collection, without triggering the message receiving node to perform (continuous) data collection. In still other implementations, for example, the information may trigger the message receiving node to configure (continuous) data collection for the corresponding user, or it may trigger the message receiving node to configure (continuous) data collection for the corresponding user according to the information in the message. In yet another implementation, for example, the information may indicate that the data collection and / or the reporting of the data collection results does not require anonymization.
[0153] ● Collection time for (continuous) data collection: Used to indicate the collection time for (continuous) data collection.
[0154] ● Start Indication for (Continuous) Data Collection: Used to indicate the start of (continuous) data collection. In some implementations, for example, upon receiving this indication, the message receiving node may begin (continuous) data collection, or configure the UE to begin (continuous) data collection. In still other implementations, for example, upon receiving this indication, the message receiving node may assign a first identifier, and / or configure the node and / or cell identifier corresponding to the first identifier and / or the start of (continuous) data collection and / or the initial configuration of (continuous) data collection to the UE. In yet another implementation, for example, upon receiving this indication, the UE begins timing (continuous) data collection. For example, the UE may send the cumulative time of (continuous) data collection to the node to which the UE is connected, so that the node to which the UE is connected can configure subsequent data collection.
[0155] ● 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.
[0156] ● (Continuous) Data Collection End Indication: Used to indicate the end of (continuous) data collection. In some implementations, for example, the message receiving node stops (continuous) data collection upon receiving this indication; alternatively, the UE may be configured to stop (continuous) data collection.
[0157] ● (Continuous) Data Collection End Time: Used to indicate the end time of (continuous) data collection. In some implementations, for example, the message receiving node can stop (continuous) data collection at the end time after receiving the end time, or the UE can be configured to stop (continuous) data collection at the end time.
[0158] ● (Continuous) Data Collection Time: Information indicating the time of (continuous) data collection. In some implementations, for example, after receiving the (continuous) data collection time, the message receiving node may only collect data within the (continuous) data collection time, or the UE may be configured to collect data within the (continuous) data collection time. In some implementations, the (continuous) data collection time may also be the reporting time of the (continuous) data collection results.
[0159] ● Remaining Time for (Continuous) Data Collection: This indicates the remaining time for (continuous) data collection. In some implementations, for example, the message receiving node performs data collection within the remaining time after receiving this information; alternatively, the UE is configured to perform data collection within the remaining time; or the UE is configured to perform data collection within the remaining time. For example, if the remaining time for (continuous) data collection is equal to or less than a threshold, the message receiving node may not perform data collection, and / or may 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 for (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.
[0160] ● Cumulative time of (continuous) data collection: This indicates the time during which (continuous) data collection has been performed. In some implementations, for example, the message receiving node may decide whether to continue configuring subsequent data collection based on the (continuous) data collection time and / or the cumulative time of (continuous) data collection. For example, if the value after subtracting the cumulative time of (continuous) data collection from the (continuous) data collection time 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 after subtracting the cumulative time of (continuous) data collection from the (continuous) data collection time 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 configuring subsequent data collection based on the (continuous) data collection time and / or the cumulative time of (continuous) data collection to achieve (continuous) data collection. For example, the message receiving node may be configured to perform data collection within a first time period. The first time period may be the value after subtracting the cumulative time of (continuous) data collection from the (continuous) data collection time.
[0161] ● Cells corresponding to (continuous) data collection: This can represent cell information corresponding to (continuous) data collection. For example, this information may include one or more of the following: cell identifier and / or a list of cell identifiers, and the number of cells. In some implementations, for example, (continuous) data collection is performed within the cells corresponding to the cell identifier and / or the list of cell identifiers. In other implementations, for example, (continuous) data collection should be stopped when the number of cells corresponding to the completed (continuous) data collection and / or the data collection results reaches the stated number of cells.
[0162] ● Nodes corresponding to (continuous) data collection: This can represent node information corresponding to (continuous) data collection. For example, this information may include one or more of the following: node identifiers and / or a list of node identifiers, the number of nodes, etc. In some implementations, for example, (continuous) data collection is performed within the nodes corresponding to the node identifiers and / or the list of node identifiers. In other implementations, for example, (continuous) data collection should be stopped when the number of nodes corresponding to the completed (continuous) data collection and / or the data collection results reaches the stated number of nodes.
[0163] ● PLMN Information Corresponding to (Continuous) Data Collection: This can represent the PLMN information corresponding to (continuous) data collection. For example, this information may include one or more of the following: PLMNs and / or a list of PLMNs, the number of PLMNs, etc. In some implementations, for example, (continuous) data collection is performed within the PLMNs corresponding to the PLMNs and / or the list of PLMNs. In other implementations, for example, (continuous) data collection should be stopped when the number of PLMNs corresponding to the completed (continuous) data collection and / or the data collection results reaches the stated number of PLMNs.
[0164] ● Slice information corresponding to (continuous) data collection: This can represent the slice information corresponding to (continuous) data collection. For example, this information may include one or more of the following: slice identifier and / or a list of slice identifiers, and the number of slices. In some implementations, for example, (continuous) data collection is performed within the slices corresponding to the slice identifier and / or the list of slice identifiers. In other implementations, for example, (continuous) data collection should be stopped when the number of slices corresponding to the completed (continuous) data collection and / or the data collection results reaches the number of slices. The slice identifier may be represented by Single Network Slice Selection Assistance Information (S-NSSAI).
[0165] ● Beam information corresponding to (continuous) data collection: This can represent the beam information corresponding to (continuous) data collection. For example, this information may include one or more of the following: beam identifier and / or beam identifier list, number of beams. In some implementations, for example, (continuous) data collection is performed within the beams corresponding to the beam identifier and / or beam identifier list. In other implementations, for example, (continuous) data collection should be stopped when the number of beams corresponding to the completed (continuous) data collection and / or the data collection results reaches the stated number of beams. For example, the beam may be an SSB beam or any other arbitrary beam. In some implementations, for example, this information may be used by 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 the corresponding configuration information.
[0166] ● First Identifier: Used to identify the collection corresponding to this message. For example, the identifier can be a random number. In some implementations, for example, the first identifier of a UE is the same throughout a (continuous) data collection process. In other implementations, for example, the first identifier can be configured by the node and / or cell corresponding to the start of (continuous) data collection and / or the node and / or cell corresponding to the initial configuration of (continuous) data collection.
[0167] ● Node and / or cell identifier corresponding to the start of (continuous) data collection and / or the initial configuration of (continuous) data collection: An identifier for the node and / or cell corresponding to the start of (continuous) data collection, or the identifier of the first node and / or cell to configure (continuous) data collection for the UE. In some implementations, for example, this node and / or cell identifier and the first identifier can uniquely identify a UE and / or the UE corresponding to the data collection report in the network.
[0168] ● (Continuous) Data Collection Dedicated TR and / or TRSR: In some implementations, the dedicated TR and / or TRSR remain unchanged during a (continuous) data collection process. For example, the dedicated TR and / or TRSR for the same UE remains unchanged during a (continuous) data collection process. In some implementations, for example, a node can associate multiple (continuous) data collection configurations and / or multiple data collection results for the same UE using the dedicated TR and / or TRSR.
[0169] ● Configuration Associations for (Continuous) Data Collection: This represents the configuration relationships within (continuous) data collection. In some implementations, for example, this association may include configuration A and configuration B belonging to the same (continuous) data collection. Nodes can configure subsequent data collections according to this configuration association to achieve the effect of (continuous) data collection. This configuration association can be a single relation or a list of relations. The association can be one or more of the following:
[0170] ○Related TR
[0171] ○Related TRSR
[0172] ○ Associated data collection configuration identifier
[0173] ○ Associated data collection configuration
[0174] ○ The node and / or cell identifier corresponding to the configuration of (continuous) data collection.
[0175] ●Data collection configuration: In some implementations, for example, the message receiving node can collect data according to this data collection configuration, or the UE can be configured to perform relevant data collection based on this information. This may include one or more of the following:
[0176] ○ Data collection configuration registration types: These can include one or more of the following: Start, Stop, Pause, Add, Overwrite, New Configuration, Release, Cancel, etc. Start indicates the commencement of data collection. Stop indicates the cessation of data collection. In some implementations, Stop may also indicate the release of the data collection configuration. Pause indicates the temporary cessation of data collection. In some implementations, Pause may also indicate that the data collection configuration is not released. For example, the data collection configuration can be used for subsequent data collection. Add indicates the addition of a new data collection configuration to the existing one. Overwrite indicates that this data collection configuration is the one to be applied. In some implementations, Overwrite may also indicate that the original data collection configuration is no longer valid. New Configuration indicates that this data collection configuration is a new one, for example, unrelated to the original data collection configuration. For example, New Configuration may also indicate that this data collection configuration and the original data collection configuration are two separate configurations. The message receiving node and / or UE need to collect data 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 UE no longer collect data according to this data collection configuration. Cancel indicates the cancellation of the data collection configuration. The message receiving node and / or UE no longer collect data according to this data collection configuration.
[0177] ○ Priority: Used to indicate the priority of data collection configuration and / or data collection. In some implementations, for example, the message receiving node and / or UE can select an appropriate data collection configuration for data collection based on this information, such as selecting a high-priority data collection configuration. For example, when the message receiving node and / or UE cannot collect data according to all received data collection configurations, the message receiving node and / or UE can select an appropriate data collection configuration for data collection based on this information.
[0178] ○ RRC Status Corresponding to Data Collection: This indicates the RRC status corresponding to the data collection configuration and / or data collection. The data collection configuration and / or data collection may correspond to one or more RRC statuses, such as one or more of the following: RRC connected status, RRC idle status, RRC inactive status, etc.
[0179] ○ Indicator of whether data collection is RAN-triggered: This indicates whether the data collection is RAN-triggered. This information can be used for reporting data collection results. For example, if the data collection is RAN-triggered, the data collection results should be reported to the corresponding RAN node. Alternatively, if the data collection is RAN-triggered, the node receiving the data collection results needs to forward the results to the corresponding RAN node that triggered the data collection.
[0180] ○ Indicator of whether data collection is OAM-triggered: Used to indicate whether data collection is OAM-triggered.
[0181] ○ Indicator of whether data collection is triggered by the core network: This indicates whether the data collection is triggered by the core network. The core network can include any node in the core network.
[0182] ○ Configuration node and / or cell identifier for data collection: This identifier identifies the configuration node and / or cell for data collection (and / or data collection configuration). In some implementations, for example, after a node completes data collection, this information can be added to a message containing the data collection results. The receiving node can then forward the data collection results to the corresponding configuration node and / or cell for data collection. In other implementations, for example, after a node completes data collection, it can report the data collection results to the configuration node and / or cell for data collection. In some implementations, for example, if a node has an interface with the node and / or cell indicated by the configuration node and / or cell identifier for data collection, the node can subsequently report the data collection results to the configuration node and / or cell for data collection.
[0183] ○ Information about the data collection node and / or cell: This information represents the data collection node and / or cell corresponding to the data collection (and / or the data collection result corresponding to the data collection configuration). For example, the information about the data collection node and / or cell may include one or more of the following: the identifier of the data collection node and / or cell, the address of the data collection node and / or cell, the name of the data collection node and / or cell, etc. The identifier of the data collection node and / or cell may also be called the identifier of the data collection reporting node and / or cell. In some implementations, for example, the address of the data collection node and / or cell may be the IP address of the data collection node and / or cell. This information indicates 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 can be added to a message containing the data collection result, and the receiving node of the data collection result can forward the data collection result to the corresponding data collection node and / or cell. In other implementations, for example, after completing data collection, a node can report the data collection results to the data collection node and / or cell. In some implementations, for example, if the node has an interface with the node and / or cell indicated by the data collection node and / or cell identifier, the node can subsequently report the data collection results to the data collection configuration node and / or cell. In this disclosure, the data collection node / cell can also be referred to as the data collection reporting node / cell.
[0184] ○ Measurement and / or collection items 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 data collection mentioned above.
[0185] ○ Data Collection Configuration Identifier: Used to identify a data collection configuration. This identifier can uniquely identify a data collection configuration. For example, this identifier can be an MDT configuration identifier, which can uniquely identify an MDT configuration. The MDT configuration may include one or more of the data collection configurations described above.
[0186] ○ Trace Reference (TR): Can include one or more of the following: PLMN identifier, Trace ID.
[0187] ○ Trace Recording Session Reference (TRSR)
[0188] ○ Trace Collection Entity ID
[0189] ○ Absolute time information: The absolute time of the cell. In some implementations, for example, it may be the absolute time of the current cell.
[0190] ○ Area Configuration: Represents the area information for data collection. This may include one or more of the following: cell identifier and / or a list of cell identifiers, PLMN identifier, Tracking Area Code, uplink and / or downlink carrier frequencies, etc. The cell identifier can be a Physical Cell ID or a Cell Global ID.
[0191] ○PLMN Identifier (List): Indicates the identifier of the PLMN that the UE is configured to perform measurement recording, related status indication, and information acquisition.
[0192] ○ Bluetooth Name (List): Indicates the name (list) of the Bluetooth beacons that the UE is configured to measure.
[0193] ○WLAN Name (List): Indicates the names (list) of WLAN access points that the UE is configured to measure.
[0194] ○ Sensor Names (List): Indicates the names (list) of sensors that the UE is configured to measure.
[0195] ○ Recording time: Indicates the time when the UE was required to record measurements.
[0196] ○ Reporting type: can include periodic reporting, event-triggered reporting, single reporting, etc.
[0197] ○ Recording interval: Indicates the time period and / or interval for recording measurement results.
[0198] ○ Event trigger configuration: This includes trigger events, thresholds, trigger times, hysteresis, etc. Trigger events can be one or more of the following: being outside coverage area, RRC status change, etc.
[0199] ○MDT Configuration Method: This indicates whether the configuration is signalalling-based or management-based. The configuration method also indicates the MDT type configured. The MDT type can include one or more of the following: Delayed MDT, Immediate MDT, Signalalling-based MDT, Management-based MDT, and combinations thereof.
[0200] ○ Early Measurement Indication: Used to indicate whether the UE is allowed to record relevant measurement results of early measurement frequencies.
[0201] ○ Events and / or conditions triggering data collection: Data collection is performed when the events and / or conditions triggering data collection are met. These events and / or conditions may include one or more of the following: the current data collection has ended, the delayed MDT has ended, etc. In some implementations, for example, these may be events and / or conditions triggering immediate MDT. For instance, the event and / or condition triggering immediate MDT may be the end of a delayed MDT. Therefore, immediate MDT can begin immediately after the delayed MDT ends, thereby achieving the effect of (continuous) data collection.
[0202] Example 2
[0203] One aspect of this disclosure provides a method for supporting (continuous) data collection, which may include one or more of the following steps.
[0204] The third node sends a second message to the fourth node, including all and / or some (continuous) data collection results, to report all and / or some (continuous) data collection results to the fourth node. This scheme can support data collection without distinguishing the UE's RRC status, thereby reducing the complexity of data collection configuration and achieving highly versatile data collection.
[0205] 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 CONTEXTRESPONSE message for Xn; a UE Information Response message for RRC; or another and / or a newly defined RRC message and / or an Xn message and / or an X2 message and / or an F1 message and / or an E1 message and / or an NG message and / or an RRC container and / or a MAC CE, etc.
[0206] In some implementations, the second message may include one or more of the following information and / or fields:
[0207] ●Sending node identifier: Used to identify the node that sent the message.
[0208] ● Receiver node identifier: Used to identify the node that received the message.
[0209] ● Measurement Identifier: Used to identify the measurement corresponding to this message. In some implementations, for example, the measurement identifier may be consistent with the measurement identifier in the first message, used to associate the reporting message with the configuration message.
[0210] ● Request Identifier: Used to identify the request corresponding to this message. In some implementations, for example, the request identifier may be the same as the request identifier in the first message, used to associate the reporting message with the configuration message.
[0211] ●Prediction Identifier: Used to identify the prediction corresponding to this message. In some implementations, for example, the prediction identifier may be consistent with the prediction identifier in the first message, used to associate the reported message with the configuration message.
[0212] ● Reporting Identifier: Used to identify the report corresponding to this message. In some implementations, for example, the reporting identifier may be consistent with the reporting identifier in the first message, used to associate the reporting message with the configuration message.
[0213] ● Configuration Identifier: Used to identify the measurement and / or prediction and / or reporting configuration corresponding to this message. In some implementations, for example, the configuration identifier may be consistent with the configuration identifier in the first message, used to associate the reporting message with the configuration message.
[0214] ● Information regarding whether new data collection is supported: This information indicates whether new data collection is supported. For example, when a node (e.g., a message sending node) and / or a UE can support new data collection, the node (e.g., a message receiving node) can configure a new data collection configuration to enable the node (e.g., the message sending node) and / or the UE to perform new data collection. For example, the node (e.g., the message sending node) and / or the UE may simultaneously perform data collection according to multiple data collection configurations (e.g., a previous data collection configuration and / or a new data collection configuration). In some implementations, for example, when node 1 (e.g., a message sending node) and / or the UE are performing data collection according to a previous data collection configuration, this information can be carried to indicate whether node 1 and / or the UE support new data collection. For example, if node 1 and / or the UE can support new data collection, node 2 (e.g., a message receiving node) can configure new data collection for node 1 and / or the UE.
[0215] ● Configuration for (continuous) data collection: The configuration for (continuous) data collection may be one or more pieces of information from the first message. This (continuous) data collection configuration informs the message receiving node of the configuration for (continuous) data collection. In some implementations, for example, the message receiving node may configure subsequent (continuous) data collection according to this configuration to achieve the effect of (continuous) data collection.
[0216] ● Identifier for (continuous) data collection configuration: This identifier uniquely identifies a (continuous) data collection configuration. For example, the configuration can be an MDT configuration or a continuous MDT configuration. Using this identifier to inform the message receiving node of the configuration corresponding to (continuous) data collection can save signaling. In some implementations, for example, the message receiving node can use this identifier to know the (continuous) data collection configuration and / or MDT configuration, and can continue to configure subsequent data collection according to this configuration to achieve (continuous) data collection. In still other implementations, for example, this identifier can indicate that the data collection and / or the reporting of data collection results does not require anonymization.
[0217] ● Cumulative time of (continuous) data collection: This indicates the time during which (continuous) data collection has been performed. In some implementations, for example, the message receiving node may decide whether to continue configuring subsequent data collection based on the (continuous) data collection time and / or the cumulative time of (continuous) data collection. For example, if the value after subtracting the cumulative time of (continuous) data collection from the (continuous) data collection time 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 after subtracting the cumulative time of (continuous) data collection from the (continuous) data collection time 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 configuring subsequent data collection based on the (continuous) data collection time and / or the cumulative time of (continuous) data collection to achieve (continuous) data collection. For example, the message receiving node may be configured to perform data collection within a first time period. The first time period may be the value after subtracting the cumulative time of (continuous) data collection from the (continuous) data collection time.
[0218] ● 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 (continuous) data collection. For example, the message receiving node may be configured to perform data collection at a second time, wherein the second time may be derived from the time of (continuous) data collection and the start time of (continuous) data collection, for example, the second time may be the remaining time of (continuous) data collection derived from the time of (continuous) data collection and the start time of (continuous) data collection.
[0219] ● (Continuous) Data Collection Time: Indicates the duration of (continuous) data collection. In some implementations, for example, the message receiving node may use this information to decide whether to configure subsequent (continuous) data collection.
[0220] ● Remaining Time for (Continuous) Data Collection: This indicates the remaining time for (continuous) data collection. In some implementations, for example, the message receiving node performs data collection within the remaining time after receiving this information; alternatively, the UE is configured to perform data collection within the remaining time; or the UE is configured to perform data collection within the remaining time. For example, if the remaining time for (continuous) data collection is equal to or less than a threshold, the message receiving node may not perform data collection, and / or may 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 for (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.
[0221] ● Information on completed and / or ongoing (continuous) data collection: Information used to indicate completed and / or ongoing (continuous) data collection. This information may include one or more of the following:
[0222] ○ TRs and / or TRSRs corresponding to completed and / or ongoing (continuous) data collection: This information can be a single TR and / or TRSR, or a set of TRs and / or TRSRs. In some implementations, for example, this information can be used by a node to correlate multiple data collection results to obtain the results of (continuous) data collection. For example, this information can be used by a node to correlate multiple data collection results measured by the same UE to obtain the results of (continuous) data collection.
[0223] ○ Configuration node and / or cell information corresponding to completed and / or ongoing (continuous) data collection: This information indicates from which node and / or cell the configuration information for the completed and / or ongoing data collection was obtained. This information can be a single node and / or cell, or a list of nodes and / or cells. This information may include one or more of the following:
[0224] ■ Node Identifier
[0225] ■ Node Name
[0226] ■Community signage
[0227] ○ Information corresponding to completed and / or ongoing (continuous) data collection: Information corresponding to completed and / or ongoing (continuous) data collection. In some implementations, for example, this information can be used by 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 can be used to determine the corresponding configuration information. It may include one or more of the following:
[0228] ■ Corresponding community identifier and / or identifier list
[0229] ■Number of corresponding residential areas
[0230] ■ Corresponding node identifiers and / or identifier lists
[0231] ■ Number of corresponding nodes
[0232] ■ Corresponding node names and / or name lists
[0233] ■ Corresponding PLMN and / or PLMN list
[0234] ■ Corresponding number of PLMNs
[0235] ■ Corresponding slice identifiers and / or slice identifier lists
[0236] ■ Corresponding number of slices
[0237] ■ Corresponding beam identifiers and / or beam identifier lists
[0238] ■ Corresponding number of beams
[0239] ● Cells corresponding to (continuous) data collection: This can represent cell information corresponding to (continuous) data collection. For example, this information may include one or more of the following: cell identifier and / or a list of cell identifiers, and the number of cells. In some implementations, for example, (continuous) data collection is performed within the cells corresponding to the cell identifier and / or the list of cell identifiers. In other implementations, for example, (continuous) data collection should be stopped when the number of cells corresponding to the completed (continuous) data collection and / or the data collection results reaches the stated number of cells. In some implementations, for example, this information can be used by 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 can be used to determine the corresponding configuration information.
[0240] ● Nodes corresponding to (continuous) data collection: This can represent node information corresponding to (continuous) data collection. For example, this information may include one or more of the following: node identifiers and / or a list of node identifiers, and the number of nodes. In some implementations, for example, (continuous) data collection is performed within the nodes corresponding to the node identifiers and / or the list of node identifiers. In other implementations, for example, (continuous) data collection should be stopped when the number of nodes corresponding to the completed (continuous) data collection and / or the data collection results reaches the stated number of nodes. In some implementations, for example, this information can be used by 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 can be used to determine the corresponding configuration information.
[0241] ● PLMN Information Corresponding to (Continuous) Data Collection: This can represent the PLMN information corresponding to (continuous) data collection. For example, this information may include one or more of the following: PLMNs and / or a list of PLMNs, and the number of PLMNs. In some implementations, for example, (continuous) data collection is performed within the PLMNs corresponding to the PLMNs and / or the list of PLMNs. In other implementations, for example, (continuous) data collection should be stopped when the number of completed (continuous) data collections and / or the number of PLMNs corresponding to the data collection results reaches the stated number of PLMNs. In some implementations, for example, this information can be used by 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 can be used to determine the corresponding configuration information.
[0242] ● Slice information corresponding to (continuous) data collection: This can represent the slice information corresponding to (continuous) data collection. For example, this information may include one or more of the following: slice identifier and / or list of slice identifiers, number of slices. In some implementations, for example, (continuous) data collection is performed within the slices corresponding to the slice identifier and / or list of slice identifiers. In other implementations, for example, (continuous) data collection should be stopped when the number of slices corresponding to the completed (continuous) data collection and / or the data collection results reaches the number of slices. 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 by 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 the corresponding configuration information.
[0243] ● Beam information corresponding to (continuous) data collection: This can represent the beam information corresponding to (continuous) data collection. For example, this information may include one or more of the following: beam identifier and / or beam identifier list, number of beams. In some implementations, for example, (continuous) data collection is performed within the beams corresponding to the beam identifier and / or beam identifier list. In other implementations, for example, (continuous) data collection should be stopped when the number of beams corresponding to the completed (continuous) data collection and / or the data collection results reaches the stated number of beams. For example, the beam may be an SSB beam or any other arbitrary beam. In some implementations, for example, this information may be used by 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 the corresponding configuration information.
[0244] ● Information related to data collection results: This indicates the results of the data collection. These results can be from MDT data collection or other data collection methods. The data collection results may include one or more of the following:
[0245] ○ Cell identifiers and / or identifier lists corresponding to the data collection results
[0246] ○ Number of communities corresponding to the data collection results
[0247] ○ Node identifiers and / or identifier lists corresponding to the data collection results
[0248] ○ Number of nodes corresponding to data collection results
[0249] ○ Node names and / or list of names corresponding to the data collection results
[0250] ○ List of PLMNs and / or PLMNs corresponding to the data collection results
[0251] ○ Number of PLMNs corresponding to the data collection results
[0252] ○ Slice identifiers and / or a list of slice identifiers corresponding to the data collection results
[0253] ○ Number of slices corresponding to the data collection results
[0254] ○ Beam identifiers and / or identifier lists corresponding to the data collection results
[0255] ○ Number of beams corresponding to the data collection results
[0256] ○ Data collection results: The data collection results may include one or more of the data corresponding to the data collection.
[0257] ○ RRC status change time information: This may include one or more of the following: the time of the RRC status change, the time from the RRC status change to the data collection result reporting, the time from data collection configuration to the RRC status change, etc. The RRC status change may be a transition between RRC connected state, RRC idle state, and RRC inactive state. For example, it may be a transition from RRC connected state to RRC idle state and / or RRC inactive state. For example, it may be a transition from RRC idle state and / or RRC inactive state to RRC active state.
[0258] ○ RRC status corresponding to data collection results: This can represent the RRC status corresponding to one or more and / or some and / or all data collection results. The RRC status can include one or more of the following: RRC connected state, RRC idle state, RRC inactive state, etc.
[0259] ○ RRC State Transition Indication: Used to indicate a change in RRC state. For example, it can indicate the data collection result corresponding to the change in RRC state after partial and / or complete data collection. The RRC state change can include any transition between RRC states. The RRC state change can be a transition between RRC connected state, RRC idle state, and RRC inactive state. For example, it can be a transition from RRC connected state to RRC idle state and / or RRC inactive state. For example, it can be a transition from RRC idle state and / or RRC inactive state to RRC active state.
[0260] ○ Time information corresponding to data collection results
[0261] ○ Configuration information corresponding to the data collection results: The configuration information can be referred to in the first message.
[0262] ● First Identifier: Used to identify the collection corresponding to this message. In some implementations, for example, the first identifier of a UE is the same during a (continuous) data collection process. In some implementations, for example, this information can be used by a node to associate multiple data collection results of the same UE.
[0263] ● Node and / or cell identifier corresponding to the start of (continuous) data collection and / or the initial configuration of (continuous) data collection: This identifier indicates the node and / or cell corresponding to the start of (continuous) data collection, or the identifier of the first node and / or cell to configure (continuous) data collection for the UE. In some implementations, for example, this node and / or cell identifier and the first identifier can uniquely identify a UE and / or the UE corresponding to a data collection report in the network. In some implementations, for example, this information can be used by a node to associate multiple data collection results for the same UE, or the combination of this information and the first identifier can be used by a node to associate multiple data collection results for the same UE.
[0264] ● (Continuous) Data Collection Dedicated TR and / or TRSR: In some implementations, the dedicated TR and / or TRSR remain unchanged during a (continuous) data collection process. For example, the dedicated TR and / or TRSR for the same UE remains unchanged during a (continuous) data collection process. In some implementations, for example, a node can associate multiple (continuous) data collection configurations and / or multiple data collection results for the same UE using the dedicated TR and / or TRSR.
[0265] ● Configuration Associations for (Continuous) Data Collection: This represents the configuration relationships within (continuous) data collection. In some implementations, for example, this association may include configuration A and configuration B belonging to the same (continuous) data collection. Nodes can configure subsequent data collections according to this configuration association to achieve the effect of (continuous) data collection. This configuration association can be a single relation or a list of relations. The association can be one or more of the following:
[0266] ○Related TR
[0267] ○Related TRSR
[0268] ○ The node and / or cell identifier corresponding to the configuration of (continuous) data collection.
[0269] ○ Associated data collection configuration identifier
[0270] ○ Associated data collection configuration
[0271] ● Reasons for data collection ending: These may include one or more of the following: receiving a high-priority data collection configuration, ongoing data collection, high priority, low priority, or a new data collection configuration with a lower priority than the ongoing data collection.
[0272] In some implementations, for example, if an RRC status change occurs during data collection, the data collection results before the RRC status change can be reported first, and the data collection results after the RRC status change can be reported in the next report. In other implementations, for example, if the configured data collection targets different collection items for different RRC statuses, the corresponding RRC status can be determined by the reported collection results.
[0273] In some implementations, for example, if a node receives multiple data collection configurations, and if the multiple data collection configurations have the same part, and / or the data collection results corresponding to the multiple data collection configurations have the same part, the data collection results can be reported in the following manner:
[0274] Method 1: Nodes report multiple data collection results, where each data collection result corresponds to a data collection configuration. The data collection results can be referenced from the data collection results in the second message mentioned above.
[0275] Method 2: A node reports a data collection result, and / or multiple data collection configurations corresponding to that result and / or configuration information related to data collection. The configuration information related to data collection can refer to the first message. The data collection result can refer to the data collection result in the second message mentioned above. The node receiving the data collection result organizes and / or processes the data collection result. For example, the data collection result can be organized and / or processed into a data collection result corresponding to one or more of the multiple data collection configurations.
[0276] Example 3
[0277] One aspect of this disclosure provides a method for supporting (continuous) data collection, which may include one or more of the following steps.
[0278] The fifth node sends a third message to the sixth node, including information related to the reporting of (continuous) data collection, to inform the sixth node of the relevant information for (continuous) data collection reporting. In some implementations, for example, the sixth node may send 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 scheme can support data collection without distinguishing the UE's RRC state, thereby reducing the complexity of data collection configuration and achieving highly versatile data collection.
[0279] In some implementations, the third message may be included in one or more of the following: a UE Information Response message for RRC, or an RRC Setup Complete message, or an RRC Resume Complete message, or an RRC Reestablishment Complete message, or an RRC Reconfiguration Complete message; or another and / or a newly defined RRC message and / or an Xn message and / or an X2 message and / or an F1 message and / or an E1 message and / or an NG message and / or an RRC container and / or a MAC CE, etc.
[0280] In some implementations, the third message may include one or more of the following information and / or fields:
[0281] ●Sending node identifier: Used to identify the node that sent the message.
[0282] ● Receiver node identifier: Used to identify the node that received the message.
[0283] ● Estimated Reporting Time: This indicates the predicted and / or expected reporting time. In some implementations, for example, when the message sending node and / or UE are collecting data and cannot report it at the current time, the message sending node and / or UE can send the estimated reporting time to the message receiving node. For example, the message receiving node can request the reporting of data collection results according to the estimated reporting time, or the message sending node and / or UE can inform the message receiving node of the estimated reporting time, and then send the data collection results to the message receiving node at the estimated reporting time. This reporting time can be the reporting time of all information, or it can be the reporting time of other information besides the currently reportable information. The information can be one or more of the second message or data collection results mentioned above.
[0284] ● Indicator of ongoing data collection: This indicates that data collection is currently in progress. In some implementations, for example, the message receiving node can use this information to subsequently request the message sending node and / or the UE to report the data collection results. In other implementations, for example, the message sending node and / or the UE will send the data collection results to the message receiving node after the ongoing data collection is completed.
[0285] ●End time of ongoing data collection: This indicates the end time of the currently ongoing data collection. In some implementations, for example, the message receiving node can use this information to request the message sending node and / or UE to report the data collection results after the end time. In other implementations, for example, the message sending node and / or UE will send the data collection results to the message receiving node at and / or after the end time.
[0286] ●Identifier indicating only partial information can be reported: This indicates that only partial information can be reported at present. In some implementations, for example, the message receiving node can request the reporting of partial information based on this information, and / or request the reporting of the remaining partial information later. In other implementations, for example, the message receiving node can request the reporting of all information at a later time. The information may be one or more of the information in the second message or data collection results described above.
[0287] ● Data collection results are available: This indicates that data collection results are currently available. In some implementations, for example, the message receiving node can use this information to request the message sending node to report the data collection results.
[0288] ●Information regarding whether new data collection is supported: This information indicates whether new data collection is supported. For example, when a node (e.g., a message sending node) and / or a UE can support new data collection, the node (e.g., a message receiving node) can configure a new data collection configuration to enable the node (e.g., the message sending node) and / or the UE to perform new data collection. For example, the node (e.g., the message sending node) and / or the UE may simultaneously perform data collection according to multiple data collection configurations (e.g., the previous data collection configuration and / or the new data collection configuration). In some implementations, for example, when node 1 (e.g., the message sending node) and / or the UE are performing data collection according to a previous data collection configuration, this information can be carried to indicate whether node 1 and / or the UE support new data collection. For example, if node 1 and / or the UE can support new data collection information, node 2 (e.g., the message receiving node) can configure new data collection for node 1 and / or the UE.
[0289] ●
[0290] ●Relevant information regarding the selected and / or decided data collection: This indicates relevant information regarding the selected and / or decided data collection. It may include one or more of the following: the data collection configuration corresponding to the selected and / or decided data collection, the reason, etc. The data collection configuration corresponding to the selected and / or decided data collection can be referenced from the information in the first message. The reason may be the reason for selecting and / or deciding to conduct data collection, and may include one or more of the following: there is ongoing data collection, high priority, low priority, the new data collection configuration has a lower priority than the ongoing data collection, etc.
[0291] ● Indicator of whether the data collection result is RAN-triggered: This indicates whether the data collection result is RAN-triggered. This information can be used for reporting the data collection result. For example, if the data collection result is RAN-triggered, the data collection result should be reported to the corresponding RAN node. Alternatively, if the data collection result is RAN-triggered, 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.
[0292] ● Indicator of whether the data collection result was triggered by OAM: Used to indicate whether the data collection result was triggered by OAM.
[0293] ● Indicator of whether the data collection result was triggered by the core network: This indicates whether the data collection result was triggered by the core network. The core network can include any node in the core network.
[0294] ● Configuration node and / or cell identifier corresponding to the data collection results: The configuration node and / or cell identifier used to identify the data collection (and / or data collection configuration) corresponding to the data collection results. In some implementations, for example, if a node has an interface with the node and / or cell indicated by the configuration node and / or cell identifier of the data collection, the node can subsequently report the data collection results to the configuration node and / or cell of the data collection.
[0295] ● Data collection node and / or cell identifier: Used to identify the collection node and / or cell identifier corresponding to the data collection result. The data collection node and / or cell identifier can also be called the data collection result reporting node and / or cell identifier. It indicates 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 related interface with the node and / or cell indicated by the data collection node and / or cell identifier, the node can subsequently report the data collection result to the data collection configuration node and / or cell.
[0296] ● Measurement and / or collection items corresponding to the data collection results: The measurement and / or collection items of the data collection results may include one or more of the data corresponding to the data collection in the first message.
[0297] Example 4
[0298] One aspect of this disclosure provides a method for supporting (continuous) data collection, which may include one or more of the following steps.
[0299] The seventh node sends a fourth message to the eighth node, including a RAN-triggered (continuous) data collection request, to request RAN-triggered (continuous) data collection. In some implementations, for example, the seventh node may request the eighth node to perform RAN-triggered (continuous) data collection. In other implementations, for example, the seventh node may request the eighth node to allow the seventh node to perform RAN-triggered (continuous) data collection. This scheme enables data collection triggered by the RAN side, achieving highly applicable data collection.
[0300] In some implementations, the fourth message may be included in one or more of the following: a Handover Request message for Xn, or a S-NODE ADDITION REQUEST message, or a S-NODE MODIFICATION REQUEST message, or an NG-RAN NODE CONFIGURATION UPDATE message, or an NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, or an Xn SETUP REQUEST message, or an Xn SETUP RESPONSE message; a UE CONTEXT RELEASE REQUEST message, or a UE CONTEXT MODIFICATION REQUEST message, or a UE CONTEXT MODIFICATION RESPONSE message, or an INITIAL CONTEXT REQUEST message. SETUPREQUEST message; RRC reconfiguration message; or another and / or newly defined RRC message and / or Xn message and / or X2 message and / or F1 message and / or E1 message and / or NG message and / or RRC container and / or MAC CE, etc.
[0301] In some implementations, the fourth message may include one or more of the following information and / or fields:
[0302] ●Sending node identifier: Used to identify the node that sent the message.
[0303] ● Receiver node identifier: Used to identify the node that received the message.
[0304] ● Request Identifier: Used to identify the request corresponding to this message.
[0305] ● Measurement Identifier: Used to identify the measurement request corresponding to this message.
[0306] ● Reporting identifier: Used to identify the reporting request corresponding to this message.
[0307] ●Indication of RAN-triggered (continuous) data collection request: This indicates that the request is for RAN-triggered (continuous) data collection.
[0308] ● Configuration information corresponding to the requested RAN-triggered (continuous) data collection: This refers to the configuration information corresponding to the requested RAN-triggered (continuous) data collection. The configuration information may refer to one or more pieces of information in the first message.
[0309] The eighth node sends a fifth message, including information related to RAN-triggered (continuous) data collection, to the seventh node based on its own circumstances, to inform the seventh node of the relevant information regarding RAN-triggered (continuous) data collection. Alternatively, after receiving a fourth message from the seventh node containing a request for RAN-triggered (continuous) data collection, the eighth node, in response to the fourth message, sends a fifth message to the seventh node including information related to RAN-triggered (continuous) data collection. In some implementations, for example, the eighth node may configure the relevant information for RAN-triggered (continuous) data collection and / or the eighth node may trigger (continuous) data collection. In other implementations, for example, the seventh node may configure the relevant information for RAN-triggered (continuous) data collection and / or the seventh node may trigger (continuous) data collection.
[0310] RAN-triggered (continuous) data collection can support RAN nodes in performing self-optimization and / or artificial intelligence and / or machine learning-related operations. For example, the collected data can be used by RAN nodes to train and / or infer artificial intelligence and / or machine learning models and / or evaluate their performance.
[0311] This scheme enables data collection triggered by the RAN side, achieving highly applicable data collection.
[0312] In some implementations, the fifth message may include one or more of the following: a Handover Request message for Xn, or a S-NODE ADDITION REQUEST message, or a S-NODE MODIFICATION REQUEST message, or an NG-RAN NODE CONFIGURATION UPDATE message, or an NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, or an Xn SETUP REQUEST message, or an Xn SETUP RESPONSE message; a UE CONTEXT RELEASE REQUEST message, or a UE CONTEXT MODIFICATION REQUEST message, or a UE CONTEXT MODIFICATION RESPONSE message, or an INITIAL CONTEXT REQUEST message. SETUPREQUEST message; RRC reconfiguration message; or another and / or newly defined RRC message and / or Xn message and / or X2 message and / or F1 message and / or E1 message and / or NG message and / or RRC container and / or MAC CE, etc.
[0313] In some implementations, the fifth message may include one or more of the following information and / or fields:
[0314] ●Sending node identifier: Used to identify the node that sent the message.
[0315] ● Receiver node identifier: Used to identify the node that received the message.
[0316] ● Request Identifier: Used to identify the request corresponding to this message.
[0317] ● Measurement Identifier: Used to identify the measurement request corresponding to this message.
[0318] ● Reporting identifier: Used to identify the reporting request corresponding to this message.
[0319] ● Indication allowing RAN-triggered (continuous) data collection: Used to indicate that RAN-triggered (continuous) data collection is permitted. In some implementations, for example, the message receiving node is allowed to perform RAN-triggered (continuous) data collection.
[0320] ● Configuration information corresponding to permitted RAN-triggered (continuous) data collection: This refers to the configuration information corresponding to permitted RAN-triggered (continuous) data collection. The configuration information may refer to one or more pieces of information in the first message.
[0321] ● Configuration information corresponding to RAN-triggered (continuous) data collection: This refers to the configuration information corresponding to RAN-triggered (continuous) data collection. The configuration information may refer to one or more pieces of information in the first message.
[0322] Exemplary embodiments of this disclosure are further described below with reference to the accompanying drawings.
[0323] The text and accompanying drawings are provided by way of example only to aid in understanding this disclosure. They should not be construed as limiting the scope of this disclosure in any way. Although certain embodiments and examples have been provided, it will be apparent to those skilled in the art, based on the content disclosed herein, that changes may be made to the illustrated embodiments and examples without departing from the scope of this disclosure.
[0324] Figure 3 A schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 3 The process of two nodes interacting with information related to (continuous) data collection is illustrated, so that the second node can perform data collection based on the information related to (continuous) data collection, and / or configure subsequent data collection, and / or analyze the collected data collection results.
[0325] In some implementations, for example, the first node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB, and the second node may be a UE. In some implementations, for example, the first node may be a UE, and the second node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In other implementations, for example, the first node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the second node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In still other implementations, for example, the first node may be an AMF, SMF, or MME, and the second node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB. In some other implementations, for example, the first node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the second node may be an AMF, SMF, or MME. Alternatively, for example, the first node may be a primary node and the second node a secondary node; for example, the first node may be a secondary node and the second node a primary node; for example, the first node may be a source node and the second node a target node; for example, the first node may be a target node and the second node a source node; for example, the first node may be a node (also called a new node) and the second node may be the last serving node (also called an old node).
[0326] Step 300A: Optionally, the second node sends a request to the first node for information related to (continuous) data collection, requesting the first node to send information related to (continuous) data collection. The request for information related to (continuous) data collection may include one or more of the following: an 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 triggered by the RAN, etc.
[0327] Step 301A: The first node sends information related to (continuous) data collection to the second node. The information related to (continuous) data collection may be the aforementioned first message.
[0328] Step 302A: The second node may perform data collection based on information related to (continuous) data collection, and / or configure subsequent data collection, and / or analyze the collected data collection results.
[0329] For example, the second node can perform subsequent data collection based on information from the information related to (continuous) data collection. In some implementations, for example, the second node can report some and / or all of the information related to (continuous) data collection along with the (continuous) data collection results, so that the receiving node of the data collection results can continue to configure subsequent data collection to achieve the effect of (continuous) data collection.
[0330] For example, the second node can configure subsequent data collection based on information related to (continuous) data collection. In some implementations, for example, during handover, in step 301A, the source node sends information related to (continuous) data collection to the target node; in step 302A, the target node can configure subsequent data collection for the UE based on the information related to (continuous) data collection to achieve the effect of (continuous) data collection. In yet other implementations, during the addition of a secondary node, in step 301A, the primary node sends 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 the effect of (continuous) data collection. In yet other implementations, for example, in step 301A, the secondary node sends information related to (continuous) data collection to the primary node; in step 302A, the primary node configures subsequent data collection for the UE. Alternatively, the primary node can send information related to (continuous) data collection to other nodes for those nodes to configure subsequent data collection for the UE. For example, other nodes could be target secondary nodes. In some other implementations, for example, in step 301A, the last serving node (also referred to as the old node) sends information related to (continuous) data collection to the node (also referred to as the new node). For example, the node (also referred to as the 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 (also referred to as the new node) may use the information in step 301A to forward the (continuous) data collection results to the last serving node (also referred to as the old node) after obtaining them, and / or, the node (also referred to as the new node) may use the information in step 301A to decide to configure the same and / or different (continuous) data collection related information to the UE.
[0331] For example, the second node can analyze the (continuous) data collection results based on information related to (continuous) data collection. In some implementations, for example, the second node can correlate multiple (continuous) data collection results of the same UE based on information related to (continuous) data collection to obtain (continuous) data collection results.
[0332] Figure 4A A schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 4A The process of interactive (continuous) data collection results between two nodes is shown so that a fourth node can perform analysis based on the (continuous) data collection results.
[0333] In some implementations, for example, the third node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB, and the fourth node may be a UE. In some implementations, for example, the third node may be a UE, and the fourth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In other implementations, for example, the third node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the fourth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In still other implementations, for example, the third node may be an AMF, SMF, or MME, and the fourth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB. In some other implementations, for example, the third node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the fourth node may be an AMF, SMF, or MME. Alternatively, for example, the third node may be the primary node and the fourth node the secondary node; for example, the third node may be the secondary node and the fourth node the primary node; for example, the third node may be the source node and the fourth node the target node; for example, the third node may be the target node and the fourth node the source node; for example, the third node may be a node (also called a new node) and the fourth node may be the last serving node (also called an old node).
[0334] Step 401A: The third node sends the (continuous) data collection results to the fourth node. The (continuous) data collection results may be the aforementioned second message.
[0335] Step 402A: The fourth node can perform data analysis based on the (continuous) data collection results, and / or merge the (continuous) data collection results to obtain (continuous) data, and / or configure subsequent data collection to achieve (continuous) data collection.
[0336] For example, the fourth node can perform data analysis based on information from (continuous) data collection results. In some implementations, for example, the fourth node can correlate multiple collected data collection results to obtain a set of (continuous) collection results based on information from (continuous) data collection results. For example, multiple (continuous) data collection results of the same UE can be correlated to obtain (continuous) data for that UE. For example, this (continuous) data can be used to support AI / ML training and / or performance monitoring and / or inference.
[0337] For example, the fourth node can configure subsequent data collection based on information from the (continuous) data collection results. In some implementations, for example, the fourth node can determine the need to configure (continuous) data collection and / or determine the corresponding configuration information based on information from the (continuous) data collection results, and then configure subsequent data collection.
[0338] For example, the fourth node can obtain information on the need to continue data collection based on the information in the (continuous) data collection results, and configure subsequent data collection. In some implementations, for example, during the handover process, in step 401A, the source node sends the (continuous) data collection results to the target node; in step 402A, the target node can configure subsequent data collection for the UE based on the (continuous) data collection results to achieve the effect of (continuous) data collection, and / or merge the subsequently collected data collection results with the already received (continuous) data collection results to obtain (continuous) data, thereby achieving the effect of (continuous) data collection. In yet other implementations, during the process of adding a secondary node, in step 401A, the primary node sends 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 the effect of (continuous) data collection, and / or merges the subsequently collected data collection results with the already received (continuous) data collection results to obtain (continuous) data, thereby achieving the effect of (continuous) data collection. In some other implementations, for example, in step 401A, the secondary node sends information related to (continuous) data collection to the primary node; in step 402A, the primary node configures subsequent data collection for the UE, or the primary node sends information related to (continuous) data collection to other nodes for other nodes to configure subsequent data collection for the UE. For example, other nodes may be target secondary nodes. And / or, the primary node and / or other nodes merge the subsequently collected data collection results with the already received (continuous) data collection results to obtain (continuous) data, thereby achieving the effect of (continuous) data collection. In some other implementations, for example, in step 401A, the last serving node (also called the old node) sends information related to (continuous) data collection to the node (also called the new node); in step 402A, the node (also called the new node) configures subsequent data collection for the UE, or the node (also called the new node) sends information related to (continuous) data collection to other nodes for other nodes to configure subsequent data collection for the UE. For example, a node (also known as a new node) can use the information in step 401A to decide whether to request the UE to report (continuous) data collection results, and / or, after obtaining the (continuous) data collection results, the node (also known as a new node) can use the information in step 401A to forward the (continuous) data collection results to the last serving node (also known as the old node), and / or, the node (also known as a new node) can use the information in step 401A to decide to configure the same and / or different (continuous) data collection related information to the UE.
[0339] Figure 4BA schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 4B The process of interactive (continuous) data collection results between two nodes is shown so that a fourth node can perform analysis based on the (continuous) data collection results.
[0340] In some implementations, for example, the third node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB, and the fourth node may be a UE. In some implementations, for example, the third node may be a UE, and the fourth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In other implementations, for example, the third node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the fourth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In still other implementations, for example, the third node may be an AMF, SMF, or MME, and the fourth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB. In some other implementations, for example, the third node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the fourth node may be an AMF, SMF, or MME. Alternatively, for example, the third node may be the primary node and the fourth node the secondary node; for example, the third node may be the secondary node and the fourth node the primary node; for example, the third node may be the source node and the fourth node the target node; for example, the third node may be the target node and the fourth node the source node; for example, the third node may be a node (also called a new node) and the fourth node may be the last serving node (also called an old node).
[0341] Step 401B: The fourth node sends information related to (continuous) data collection to the third node. The information related to (continuous) data collection may be the aforementioned first message.
[0342] Step 402B: The third node sends the (continuous) data collection result to the fourth node. The (continuous) data collection result may be the aforementioned second message. In some embodiments, for example, the third node collects data according to the information related to (continuous) data collection received in step 401B, obtains the (continuous) data collection result, and sends it to the fourth node via step 402B.
[0343] Step 403B: The fourth node can perform data analysis based on the (continuous) data collection results, and / or merge the (continuous) data collection results to obtain (continuous) data, and / or configure subsequent data collection to achieve (continuous) data collection.
[0344] For example, the fourth node can perform data analysis based on information from (continuous) data collection results. In some implementations, for example, the fourth node can correlate multiple collected data collection results to obtain a set of (continuous) collection results based on information from (continuous) data collection results. For example, multiple (continuous) data collection results of the same UE can be correlated to obtain (continuous) data for that UE. For example, this (continuous) data can be used to support AI / ML training and / or performance monitoring and / or inference.
[0345] For example, the fourth node can configure subsequent data collection based on information from the (continuous) data collection results. In some implementations, for example, the fourth node can determine the need to configure (continuous) data collection and / or determine the corresponding configuration information based on information from the (continuous) data collection results, and then configure subsequent data collection.
[0346] For example, the fourth node can determine the need for continued data collection based on information from the (continuous) data collection results and configure subsequent data collection. In some implementations, for example, during handover, in step 402B, the source node sends the (continuous) data collection results to the target node; in step 403B, the target node can configure subsequent data collection for the UE based on the (continuous) data collection results to achieve the effect of (continuous) data collection, and / or merge the subsequently collected data collection results with the already received (continuous) data collection results to obtain (continuous) data, thus achieving the effect of (continuous) data collection. In yet other implementations, during the addition of a secondary node, in step 402B, the primary node sends 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 the effect of (continuous) data collection, and / or merges the subsequently collected data collection results with the already received (continuous) data collection results to obtain (continuous) data, thus achieving the effect of (continuous) data collection. In some other implementations, for example, in step 402B, the secondary node sends information related to (continuous) data collection to the primary node; in step 403B, the primary node configures subsequent data collection for the UE, or the primary node sends information related to (continuous) data collection to other nodes for other nodes to configure subsequent data collection for the UE. For example, other nodes may be target secondary nodes. And / or, the primary node and / or other nodes merge the subsequently collected data collection results with the already received (continuous) data collection results to obtain (continuous) data, thereby achieving the effect of (continuous) data collection. In some other implementations, for example, in step 401B, the last serving node (also called the old node) sends information related to (continuous) data collection to the node (also called the new node); in step 402B, the node (also called the new node) configures subsequent data collection for the UE, or the node (also called the new node) sends information related to (continuous) data collection to other nodes for other nodes to configure subsequent data collection for the UE. For example, a node (also known as a new node) can use the information in step 401B to decide whether to request the UE to report (continuous) data collection results, and / or, after obtaining the (continuous) data collection results, the node (also known as a new node) can use the information in step 401B to forward the (continuous) data collection results to the last serving node (also known as the old node), and / or, the node (also known as a new node) can use the information in step 401B to decide to configure the same and / or different (continuous) data collection related information to the UE.
[0347] Figure 4CA schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 4C The process of configuring the UE to perform (continuous) data collection between two nodes is shown to obtain (continuous) data.
[0348] Step 400C: Base station 1 and / or base station 2 are configured with information related to (continuous) data collection. This information may be the information from the aforementioned first message, and / or MDT configuration. In some implementations, for example, OAM and / or AMF configure information related to (continuous) data collection for base station 1 and / or base station 2.
[0349] Step 401C: Base station 1 sends 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 MDT configuration.
[0350] Step 402C: The UE performs data collection. Optionally, the UE sends 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... Figure 5B The process replacement in the middle.
[0351] Step 403C: The UE enters the RRC inactive state or the RRC idle state, and the UE performs data collection according to the (continuous) data collection configuration received in step 401C.
[0352] Step 404C: The UE returns to the RRC connection state. For example, the UE connects to base station 2. The UE sends information related to reporting (continuous) data collection to the connected base station (in this example, the connected base station is base station 2). The information related to reporting (continuous) data collection may be the aforementioned third message.
[0353] Step 405C: Base station 2 sends a message containing 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 sends the information related to (continuous) data collection to the UE.
[0354] Step 406C: The UE collects data based on the information related to (continuous) data collection received in step 405C and / or step 401C.
[0355] Step 407C: The UE sends a message to the connected base station (in this example, base station 2) containing information related to the availability of (continuous) data collection results. This message may include information related to one or more of the following: (continuous) data collection results are available, data collection results are available, partial data collection results are available, partial (continuous) data collection results are available, etc. In some implementations, for example, after receiving this message, base station 2 may subsequently request the UE to report the (continuous) data collection results.
[0356] Step 408C: Base station 2 sends a message containing a (continuous) data collection result request to the UE, requesting the UE to report the (continuous) data collection results. This message may include one or more of the following: (continuous) data collection result request, data collection result request, partial data collection result request, partial (continuous) data collection result request, etc.
[0357] Step 409C: The UE sends (continuous) data collection results to base station 2. These (continuous) data collection results can be the aforementioned second message. The (continuous) data collection results can be all (continuous) data collection results, partial (continuous) data collection results, or currently available (continuous) data collection results.
[0358] Figure 4D A schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 4D The process of configuring the UE to perform (continuous) data collection between two nodes is shown to obtain (continuous) data.
[0359] 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 from the aforementioned first message. In some implementations, for example, OAM and / or AMF configure the information related to (continuous) data collection for base station 1 and / or base station 2.
[0360] Step 401D: Base station 1 sends 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 MDT configuration.
[0361] Step 402D: The UE performs data collection. Optionally, the UE sends 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... Figure 5B The process replacement in the middle.
[0362] Step 403D: Base station 1 sends 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 MDT configuration. In some embodiments, for example, during handover, the source node (e.g., base station 1) sends information related to (continuous) data collection to the target node (e.g., base station 2); the target node (e.g., base station 2) can configure subsequent data collection for the UE based on the information related to (continuous) data collection to achieve the effect of (continuous) data collection. In yet other embodiments, during the addition of a secondary node, the primary node (e.g., base station 1) sends 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 the effect of (continuous) data collection. In some other implementations, for example, a secondary node (e.g., base station 1) sends information related to (continuous) data collection to a primary node (e.g., base station 2); the primary node (e.g., base station 2) then configures the UE for subsequent data collection. Alternatively, the primary node (e.g., base station 2) may send information related to (continuous) data collection to other nodes for those nodes to configure the UE for subsequent data collection. For example, these other nodes may be target secondary nodes. In some other implementations, the last serving node (also referred to as the old node) (e.g., base station 1) sends information related to (continuous) data collection to the node the UE is newly connected to (also referred to as the new node) (e.g., base station 2).
[0363] Step 404D: Base station 2 sends information related to (continuous) data collection to the UE. The information related to (continuous) data collection may be the aforementioned first message and / or MDT configuration. In some implementations, for example, base station 2 continues to configure (continuous) data collection to the UE based on the information related to (continuous) data collection, and sends the information related to (continuous) data collection to the UE.
[0364] Step 405D: The UE performs data collection. Optionally, the UE sends the corresponding (continuous) data collection results to base station 2. The (continuous) data collection results may be the aforementioned second message. Step 405D may also be... Figure 5B The process replacement in the middle.
[0365] Figure 4E A schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 4E The process of configuring two auxiliary nodes to perform (continuous) data collection on the UE in order to obtain (continuous) data is shown.
[0366] Step 400E: Auxiliary node 1 and / or auxiliary node 2 are configured with information related to (continuous) data collection. This information related to (continuous) data collection may be the information from the aforementioned first message. In some implementations, for example, OAM and / or AMF configure the information related to (continuous) data collection for auxiliary node 1 and / or auxiliary node 2.
[0367] Step 401E: The secondary node 1 sends 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 MDT configuration.
[0368] Step 402E: The UE performs data collection. Optionally, the UE sends the corresponding (continuous) data collection results to the secondary node 1. The (continuous) data collection results may be the aforementioned second message. Step 402E may also be... Figure 5B The process replacement in the middle.
[0369] Step 403E: The secondary node 1 sends information related to (continuous) data collection to the primary node. This information may be the aforementioned first message and / or MDT configuration. In some implementations, for example, during a secondary node change, the source secondary node (e.g., secondary node 1) sends information related to (continuous) data collection to the primary node.
[0370] Step 404E: The master node sends information related to (continuous) data collection to slave node 2. This information may be the aforementioned first message and / or MDT configuration. In some implementations, for example, during a slave node change, the master node sends information related to (continuous) data collection to the target slave node (e.g., slave node 2).
[0371] Step 405E: The secondary node 2 sends information related to (continuous) data collection to the UE. This information may be the aforementioned first message and / or MDT configuration. In some implementations, for example, the secondary node 2 continues to configure (continuous) data collection for the UE based on the information related to (continuous) data collection received in step 404E and / or the information related to (continuous) data collection in step 400E, and sends this information to the UE. In other implementations, for example, during a secondary node change process, after the UE accesses the secondary node 2, the secondary node 2 can directly send the information related to (continuous) data collection to the UE, for example, via an RRC reconfiguration message. In still other implementations, for example, during a secondary node change process, the secondary node 2 can send the information related to (continuous) data collection to the UE via forwarding from the primary node, for example, via an RRC reconfiguration message.
[0372] Step 406E: The UE performs data collection. Optionally, the UE sends the corresponding (continuous) data collection results to the secondary node 2. The (continuous) data collection results may be the aforementioned second message. Step 406E may also be... Figure 5B The process replacement in the middle.
[0373] Figure 4F A schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 4F The diagram illustrates the interaction between three nodes and information related to (continuous) data collection, outlining the process of configuring the UE to perform (continuous) data collection in order to obtain (continuous) data.
[0374] In some implementations, for example, node 1 can be gNB CU, node 2 can be gNB DU, and node 3 can be gNB DU. In other implementations, for example, node 1 can be gNB CU CP, node 2 can be gNB CU UP, and node 3 can be gNB CU UP. In still other implementations, for example, node 1 can be AMF and / or SMF, node 2 can be gNB and / or gNB CU and / or gNB CU CP, and node 3 can be gNB and / or gNB CU and / or gNB CU CP.
[0375] Step 400F: Node 2 and / or Node 3 are configured with information related to (continuous) data collection. This information may be the information from the aforementioned first message. In some implementations, for example, OAM and / or AMF configure the information related to (continuous) data collection for Node 2 and / or Node 3.
[0376] Step 401F: Node 2 sends 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 MDT configuration.
[0377] Step 402F: The UE performs data collection. Optionally, the UE sends 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... Figure 5B The process replacement in the middle.
[0378] Step 403F: Node 2 sends information related to (continuous) data collection to Node 1. This information may be the aforementioned first message and / or MDT configuration. In some implementations, for example, during the user context release process and / or bearer context release process, Node 2 sends the information related to (continuous) data collection to Node 1.
[0379] Step 404F: Node 1 sends information related to (continuous) data collection to Node 3. This information may be the aforementioned first message and / or MDT configuration. In some implementations, for example, Node 1 sends the information related to (continuous) data collection to Node 3 during the user context establishment and / or user context modification and / or bearer context establishment and / or bearer context modification process.
[0380] Step 405F: Node 3 sends information related to (continuous) data collection to the UE. This information may be the aforementioned first message and / or MDT configuration. In some implementations, for example, Node 3 continues to configure (continuous) data collection to the UE based on the information related to (continuous) data collection received in step 404F and / or the information related to (continuous) data collection in step 400F, and sends the information related to (continuous) data collection to the UE.
[0381] Step 406F: The UE performs data collection. Optionally, the UE sends 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... Figure 5B The process replacement in the middle.
[0382] Figure 4G A schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 4G The process of configuring the UE to perform (continuous) data collection between two nodes is shown to obtain (continuous) data.
[0383] Step 400G: Base station 1 and / or base station 2 are configured with information related to (continuous) data collection. This information may be the information from the aforementioned first message, and / or MDT configuration. In some implementations, for example, OAM and / or AMF configure the information related to (continuous) data collection for base station 1 and / or base station 2.
[0384] Step 401G: Base station 1 sends 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 MDT configuration.
[0385] Step 402G: The UE performs data collection. Optionally, the UE sends 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... Figure 5B The process replacement in the middle.
[0386] Step 403G: The UE enters the RRC inactive state or the RRC idle state, and the UE performs data collection according to the (continuous) data collection configuration received in step 401G.
[0387] Step 404G: The UE returns to the RRC connection state. For example, the UE is connected to base station 2. The UE performs RRC establishment and / or recovery procedures with the connected base station (in this example, the connected base station is base station 2).
[0388] Step 405G: Base station 2 sends a message containing 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 sends the information related to (continuous) data collection to the UE.
[0389] Step 406G: The UE sends information related to reporting (continuous) data collection to the connected base station (in this example, the connected base station is base station 2). The information related to reporting (continuous) data collection may be the aforementioned third message. In some embodiments, 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 send the determined and / or performed data collection information to the connected base station (in this example, the connected base station is base station 2) via the information related to reporting (continuous) data collection.
[0390] Step 407G: The UE collects data based on the information related to (continuous) data collection received in step 405G and / or step 401G. In some embodiments, the UE collects data based on the information related to the reporting of (continuous) data collection sent in step 406G.
[0391] Step 408G: The UE sends a message to the connected base station (in this example, base station 2) containing information related to the availability of (continuous) data collection results. This message may include information related to one or more of the following: (continuous) data collection results are available, data collection results are available, partial data collection results are available, partial (continuous) data collection results are available, etc. In some implementations, for example, after receiving this message, base station 2 may subsequently request the UE to report the (continuous) data collection results.
[0392] Step 409G: Base station 2 sends a message containing a (continuous) data collection result request to the UE, requesting the UE to report the (continuous) data collection results. This message may include one or more of the following: (continuous) data collection result request, data collection result request, partial data collection result request, partial (continuous) data collection result request, etc.
[0393] Step 410G: The UE sends (continuous) data collection results to base station 2. These (continuous) data collection results can be the aforementioned second message. The (continuous) data collection results can be all (continuous) data collection results, partial (continuous) data collection results, or currently available (continuous) data collection results.
[0394] Figure 5A A schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 5A This illustrates the process of information related to the interaction between two nodes and the reporting of (continuous) data collection, so that the sixth node can obtain the (continuous) data collection results.
[0395] In some implementations, for example, the fifth node may be a UE, and the sixth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In other implementations, for example, the fifth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the sixth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In still other implementations, for example, the fifth node may be an AMF, SMF, or MME, and the sixth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB. In yet another implementation, for example, the fifth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the sixth node may be an AMF, SMF, or MME. Alternatively, for example, the fifth node is the primary node and the sixth node is the secondary node; for example, the fifth node is the secondary node and the sixth node is the primary node; for example, the fifth node is the source node and the sixth node is the target node; for example, the fifth node is the target node and the sixth node is the source node.
[0396] Step 501A: The fifth node sends information related to the reporting of (continuous) data collection to the sixth node. This information related to the reporting of (continuous) data collection may be the aforementioned third message.
[0397] Step 502A: The sixth node may wait for and / or request (continuous) data collection results based on information related to the reporting of (continuous) data collection. In some implementations, for example, the sixth node may send a data collection result request to the fifth node according to information in the information related to the reporting of (continuous) data collection.
[0398] Step 503A: The sixth node sends a message containing a (continuous) data collection result request to the fifth node, requesting the fifth node to report the (continuous) data collection results. This (continuous) data collection result request may include one or more of the following: a (continuous) data collection result request, a data collection result request, a partial data collection result request, a partial (continuous) data collection result request, etc. The message can be sent via a UE information request message. In some implementations, for example, the message can be sent based on information related to the reporting of (continuous) data collection received in step 501A.
[0399] Step 504A: The fifth node sends a message containing the (continuous) data collection results to the sixth node. The (continuous) data collection results may be the aforementioned second message. In some embodiments, for example, the message may be sent according to the information related to the reporting of (continuous) data collection in step 501A.
[0400] Step 503A is an optional step.
[0401] Figure 5B A schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 5B This illustrates the process of information related to the interaction between two nodes and the reporting of (continuous) data collection, so that the sixth node can obtain the (continuous) data collection results.
[0402] In some implementations, for example, the fifth node may be a UE, and the sixth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In other implementations, for example, the fifth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the sixth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In still other implementations, for example, the fifth node may be an AMF, SMF, or MME, and the sixth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB. In yet another implementation, for example, the fifth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the sixth node may be an AMF, SMF, or MME. Alternatively, for example, the fifth node is the primary node and the sixth node is the secondary node; for example, the fifth node is the secondary node and the sixth node is the primary node; for example, the fifth node is the source node and the sixth node is the target node; for example, the fifth node is the target node and the sixth node is the source node.
[0403] Step 501B: The fifth node completes data collection, and / or stops data collection, and / or completes partial data collection.
[0404] Step 502B: The fifth node sends information related to the reporting of (continuous) data collection and / or information related to the availability of (continuous) data collection results to the sixth node. The information related to the reporting of (continuous) data collection may be the aforementioned third message.
[0405] Step 503B: The sixth node sends a message containing a (continuous) data collection result request to the fifth node, requesting the fifth node to report the (continuous) data collection results. This (continuous) data collection result request may include one or more of the following: a (continuous) data collection result request, a data collection result request, a partial data collection result request, a partial (continuous) data collection result request, etc. The message can be sent via a UE information request message. In some implementations, for example, the message may be sent based on information related to the reporting of (continuous) data collection received in step 502B.
[0406] Step 504B: The fifth node sends a message containing the (continuous) data collection results to the sixth node. The (continuous) data collection results may be the aforementioned second message. In some embodiments, for example, the message may be sent in accordance with the information related to the reporting of (continuous) data collection in step 502B.
[0407] Step 503B is an optional step.
[0408] Figure 5C A schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 5C This illustrates the process of information related to the interaction between two nodes and the reporting of (continuous) data collection, so that the sixth node can obtain the (continuous) data collection results.
[0409] In some implementations, for example, the fifth node may be a UE, and the sixth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In other implementations, for example, the fifth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the sixth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In still other implementations, for example, the fifth node may be an AMF, SMF, or MME, and the sixth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB. In yet another implementation, for example, the fifth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the sixth node may be an AMF, SMF, or MME. Alternatively, for example, the fifth node is the primary node and the sixth node is the secondary node; for example, the fifth node is the secondary node and the sixth node is the primary node; for example, the fifth node is the source node and the sixth node is the target node; for example, the fifth node is the target node and the sixth node is the source node.
[0410] Step 501C: The fifth node is conducting (continuous) data collection.
[0411] Step 502C: The fifth node sends information related to the reporting of (continuous) data collection to the sixth node. This information related to the reporting of (continuous) data collection may be the aforementioned third message.
[0412] Step 503C: The sixth node sends a message containing a (continuous) data collection result request to the fifth node, requesting the fifth node to report the (continuous) data collection results. This (continuous) data collection result request may include one or more of the following: a (continuous) data collection result request, a data collection result request, a partial data collection result request, a partial (continuous) data collection result request, etc. The message can be sent via a UE information request message. In some implementations, for example, the message may be sent based on information related to the reporting of (continuous) data collection received in step 502C.
[0413] Step 504C: The fifth node sends a message containing the (continuous) data collection results to the sixth node. The (continuous) data collection results may be the aforementioned second message. In some embodiments, for example, the message may be sent according to the information related to the reporting of (continuous) data collection in step 502C. In other embodiments, for example, the fifth node may report the currently available data. In still other embodiments, for example, after receiving the (continuous) data collection result request message in step 503C, the fifth node reports the currently collected and / or available data.
[0414] Step 505C: The fifth node completes data collection, and / or stops data collection, and / or completes partial data collection.
[0415] Step 506C: The fifth node sends information related to the reporting of (continuous) data collection and / or information related to the availability of (continuous) data collection results to the sixth node. The information related to the reporting of (continuous) data collection may be the aforementioned third message.
[0416] Step 507C: The sixth node sends a message containing a (continuous) data collection result request to the fifth node, requesting the fifth node to report the (continuous) data collection results. This (continuous) data collection result request may include one or more of the following: a (continuous) data collection result request, a data collection result request, a partial data collection result request, a partial (continuous) data collection result request, etc. The message can be sent via a UE information request message. In some implementations, for example, the message may be sent based on information related to the reporting of (continuous) data collection received in step 502C and / or step 506C.
[0417] Step 508C: The fifth node sends a message containing the (continuous) data collection results to the sixth node. The (continuous) data collection results may be the aforementioned second message. In some embodiments, for example, this message may be sent according to the information related to the reporting of (continuous) data collection in steps 502C and / or 506C. In other embodiments, for example, the fifth node may report currently available data. In still other embodiments, 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.
[0418] For example, the results obtained in steps 504C and 508C can be combined to form (continuous) data.
[0419] Step 503C is an optional step. Step 506C is an optional step.
[0420] Step 505C is an optional step.
[0421] Figure 6A A schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 6A The process of two nodes interacting with information related to RAN-triggered (continuous) data collection is illustrated, so that the seventh and / or eighth nodes can configure and / or perform RAN-triggered (continuous) data collection.
[0422] In some implementations, for example, the seventh node may be a UE, and the eighth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In other implementations, for example, the seventh node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the eighth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In still other implementations, for example, the seventh node may be an AMF, SMF, or MME, and the eighth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB. In yet another implementation, for example, the seventh node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the eighth node may be an AMF, SMF, or MME. Alternatively, for example, the seventh node is the primary node and the eighth node is the secondary node; for example, the seventh node is the secondary node and the eighth node is the primary node; for example, the seventh node is the source node and the eighth node is the target node; for example, the seventh node is the target node and the eighth node is the source node.
[0423] Step 601A: The seventh node sends a RAN-triggered (continuous) data collection request to the eighth node to request RAN-triggered (continuous) data collection. In some embodiments, for example, the seventh node may request the eighth node to perform RAN-triggered (continuous) data collection. In other embodiments, for example, the seventh node may request the eighth node to allow the seventh node to perform RAN-triggered (continuous) data collection. The RAN-triggered (continuous) data collection request may be the aforementioned fourth message.
[0424] Step 602A: After receiving the RAN-triggered (continuous) data collection request sent by the seventh node, the eighth node, in response to the RAN-triggered (continuous) data collection request, sends information related to the RAN-triggered (continuous) data collection to the seventh node. The information related to the RAN-triggered (continuous) data collection may be the aforementioned fifth message.
[0425] Step 603A: The seventh node and / or the eighth node may configure and / or perform RAN-triggered (continuous) data collection.
[0426] RAN-triggered (continuous) data collection can support RAN nodes in performing self-optimization and / or artificial intelligence and / or machine learning-related operations. For example, the collected data can be used by RAN nodes to train and / or infer artificial intelligence and / or machine learning models and / or evaluate their performance.
[0427] Figure 6B A schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 6B The process of two nodes interacting with information related to RAN-triggered (continuous) data collection is illustrated, so that the seventh and / or eighth nodes can configure and / or perform RAN-triggered (continuous) data collection.
[0428] In some implementations, for example, the seventh node may be a UE, and the eighth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In other implementations, for example, the seventh node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the eighth node may be a gNB, gNB-CU, gNB-DU, gNB CU-CP, gNB CU-UP, en-gNB, eNB, or ng-eNB. In still other implementations, for example, the seventh node may be an AMF, SMF, or MME, and the eighth node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB. In yet another implementation, for example, the seventh node may be a gNB, gNB-CU, gNB CU-CP, en-gNB, eNB, or ng-eNB, and the eighth node may be an AMF, SMF, or MME. Alternatively, for example, the seventh node is the primary node and the eighth node is the secondary node; for example, the seventh node is the secondary node and the eighth node is the primary node; for example, the seventh node is the source node and the eighth node is the target node; for example, the seventh node is the target node and the eighth node is the source node.
[0429] Step 601B: The eighth node sends information related to the RAN-triggered (continuous) data collection to the seventh node. This information may be the aforementioned fifth message.
[0430] Step 602B: The seventh node and / or the eighth node may configure and / or perform RAN-triggered (continuous) data collection.
[0431] RAN-triggered (continuous) data collection can support RAN nodes in performing self-optimization and / or artificial intelligence and / or machine learning-related operations. For example, the collected data can be used by RAN nodes to train and / or infer artificial intelligence and / or machine learning models and / or evaluate their performance.
[0432] Figure 6CA schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 6C The process of configuring two nodes for UE to perform RAN-triggered (continuous) data collection is shown to obtain (continuous) data.
[0433] Step 600C.a: Optionally, base station 1 sends information related to (continuous) data collection to a neighboring base station (e.g., base station 2 in this illustration) to inform the neighboring base station of the information related to (continuous) data collection. In some implementations, for example, the neighboring base station can obtain the data collection-related configuration of base station 1 through this information. For example, after obtaining the data collection results, the neighboring base station can forward the data collection results based on this information.
[0434] Step 600C.b: Optionally, a neighboring base station (e.g., base station 2) sends an acknowledgment to base station 1 regarding information related to (continuous) data collection, to confirm receipt of the information related to (continuous) data collection.
[0435] Step 601C: Base station 1 sends 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 MDT configuration.
[0436] Step 602C: The UE performs data collection. Optionally, the UE sends 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... Figure 5B The process replacement in the middle.
[0437] Step 603C: The UE enters the RRC inactive state or the RRC idle state, and the UE performs data collection according to the (continuous) data collection configuration received in step 601C.
[0438] Step 604C: The UE returns to the RRC connection state. For example, the UE connects to base station 2. The UE sends information related to reporting (continuous) data collection to the connected base station (in this example, base station 2). The information related to reporting (continuous) data collection may be the aforementioned third message. And / or, the UE sends a message to the connected base station (in this example, base station 2) containing information related to the availability of (continuous) data collection results. This message may include information related to one or more of the following: (continuous) data collection results are available, data collection results are available, partial data collection results are available, partial (continuous) data collection results are available, etc. In some implementations, for example, after receiving this message, base station 2 may subsequently request the UE to report (continuous) data collection results.
[0439] Step 605C: Base station 2 sends a message containing a (continuous) data collection result request to the UE, requesting the UE to report the (continuous) data collection results. This message may include one or more of the following: (continuous) data collection result request, data collection result request, partial data collection result request, partial (continuous) data collection result request, etc.
[0440] Step 606C: The UE sends (continuous) data collection results to base station 2. These (continuous) data collection results can be the aforementioned second message. The (continuous) data collection results can be all (continuous) data collection results, partial (continuous) data collection results, or currently available (continuous) data collection results.
[0441] Step 607C: Base station 2 sends (continuous) data collection results to base station 1. These (continuous) data collection results may be the aforementioned second message. Base station 2 may decide to send the received (continuous) data collection results to base station 1 based on the (continuous) data collection-related information received in step 600C.a and / or the (continuous) data collection results received in step 606C and / or the information related to (continuous) data collection reporting received in step 604C.
[0442] RAN-triggered (continuous) data collection can support RAN nodes in performing self-optimization and / or artificial intelligence and / or machine learning-related operations. For example, the collected data can be used by RAN nodes to train and / or infer artificial intelligence and / or machine learning models and / or evaluate their performance.
[0443] Figure 6D A schematic diagram of one aspect of a method for supporting (continuous) data collection according to embodiments of the present disclosure is shown. Specifically, Figure 6D The process of configuring two nodes for UE to perform RAN-triggered (continuous) data collection is shown to obtain (continuous) data.
[0444] 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.
[0445] Information related to RAN-triggered (continuous) data collection can be exchanged via method A and / or method B.
[0446] Method A:
[0447] Step 600D.a: The eleventh node sends information related to the RAN-triggered (continuous) data collection to the ninth node. This information related to the RAN-triggered (continuous) data collection may be the aforementioned fifth message.
[0448] Method B:
[0449] Step 600D.b1: The ninth node sends a RAN-triggered (continuous) data collection request to the eleventh node. The RAN-triggered (continuous) data collection request may be the aforementioned fourth message.
[0450] Step 600D.b2: The eleventh node sends information related to the RAN-triggered (continuous) data collection to the ninth node. This information related to the RAN-triggered (continuous) data collection may be the aforementioned fifth message.
[0451] Step 600D.c and subsequent steps can be referred to Figure 6C Step 600C.a and subsequent steps.
[0452] RAN-triggered (continuous) data collection can support RAN nodes in performing self-optimization and / or artificial intelligence and / or machine learning-related operations. For example, the collected data can be used by RAN nodes to train and / or infer artificial intelligence and / or machine learning models and / or evaluate their performance.
[0453] 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 rearranged in any way.
[0454] In the above examples, if the nodes are in a non-separated architecture, then nodes CU and DU can be considered as one node, and the interaction between nodes CU and DU can be considered as an internal interaction within the node. Alternatively, if the nodes are in a non-separated architecture, then nodes CUCP, CUUP, and DU can be considered as one node, and the interaction between nodes CUCP and CUUP, and / or the interaction between nodes CUCP and DU can be considered as an internal interaction within the node.
[0455] In the above examples, if the node and / or cell that the UE connects to when returning from the RRC inactive state and / or the RRC idle state to the RRC connected state is the same as the node and / or cell that the UE connected to before entering the RRC inactive state and / or the RRC idle state, then in the above examples, base station 1 and base station 2 can be the same base station, and / or, secondary node 1 and secondary node 2 can be the same node, and / or, the ninth node and the tenth node can be the same node.
[0456] In this disclosure, the embodiments are merely illustrative examples, and the above embodiments can be combined, etc.
[0457] In the examples above, for instance, in a non-gNB CU / gNB DU separate architecture, the first node (e.g., gNB CU) and the second node (e.g., gNB DU) can be merged into a single node, such as gNB. In this case, the interaction between gNB CU and gNB DU can be considered as intra-node behavior.
[0458] It should be understood that, depending on the application scenario, the various examples, aspects, methods, steps, processes, etc., described herein can be implemented individually or in combination in any manner, and this document does not impose any limitations. In this disclosure, for the sake of brevity, descriptions of specific steps in one example or embodiment are typically not repeated in corresponding steps of another example or embodiment. However, it should be understood that descriptions of specific steps in one example or embodiment can be applied to corresponding steps in any other example.
[0459] Next, Figure 7 A flowchart of a method 700 performed by a user equipment (UE) in a wireless communication system according to an embodiment of the present disclosure is shown.
[0460] like Figure 7 As shown, a method 700 performed by a user equipment (UE) in a wireless communication system according to an embodiment of this 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, sending fourth information including data collection results related to the data collection to the second node, wherein the data collection results include 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.
[0461] According to embodiments of this disclosure, the configuration information selected by the UE is chosen from the first configuration information and the second configuration information based on the first priority and the second priority.
[0462] According to an embodiment of this disclosure, the method further includes: sending third information related to the reporting of the data collection to the second node, wherein the third information includes the configuration information selected by the UE and the reason for selecting the configuration information.
[0463] According to embodiments of this disclosure, the first information further includes at least one of the following: the Radio Resource Control (RRC) status corresponding to the first configuration information, information related to whether the data collection is triggered by a Radio Access Network (RAN) node, the identification information of the configuration node of the first configuration information, and the identification information of the reporting node of the data collection results corresponding to the first configuration information.
[0464] According to embodiments of this disclosure, the fourth information further includes at least one of the following: time information related to a change in the RRC state of the UE, indication information related to a change in the 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 for the end of the data collection.
[0465] According to embodiments of this disclosure, the third information further includes at least one of the following: information about the data collection that the UE is currently conducting, information about whether the UE supports new data collection, information about whether the data collection result is the result of data collection triggered by a radio access network (RAN) node, and identification information of the node that reported the data collection result.
[0466] Figure 8A A flowchart of a method 800 performed by a second node in a wireless communication system according to an embodiment of the present disclosure is shown.
[0467] like Figure 8A As shown, a method 800 performed by a second node in a wireless communication system according to an embodiment of this disclosure may include: in step S801, sending 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 from the UE fourth information including data collection results related to the data collection, wherein the data collection results include 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 the first priority of the first configuration information are included in the first information related to the data collection received by the UE from the first node.
[0468] According to embodiments of this disclosure, the configuration information selected by the UE is chosen from the first configuration information and the second configuration information based on the first priority and the second priority.
[0469] According to embodiments of this disclosure, the method further includes: receiving third information from the UE related to the reporting of the data collection, wherein the third information includes the configuration information selected by the UE and the reason for selecting the configuration information.
[0470] According to embodiments of this disclosure, the first information further includes at least one of the following: the Radio Resource Control (RRC) status corresponding to the first configuration information, information related to whether the data collection is triggered by a Radio Access Network (RAN) node, the identification information of the configuration node of the first configuration information, and the identification information of the reporting node of the data collection results corresponding to the first configuration information.
[0471] According to embodiments of this disclosure, the fourth information further includes at least one of the following: time information related to a change in the RRC state of the UE, indication information related to a change in the 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 for the end of the data collection.
[0472] According to embodiments of this disclosure, the third information further includes at least one of the following: information about the data collection that the UE is currently conducting, information about whether the UE supports new data collection, information about whether the data collection result is the result of data collection triggered by a radio access network (RAN) node, and identification information of the node that reported the data collection result.
[0473] According to embodiments of this disclosure, the information regarding whether the data collection result is a result of data collection triggered by a Radio Access Network (RAN) node further includes the identification information of the RAN node that triggered the data collection. The method further includes: if the data collection result is a result of data collection triggered by a RAN node, sending the data collection result to the RAN node and / or the reporting node based on the identification information of the RAN node and / or the identification information of the reporting node of the data collection result.
[0474] Figure 8B A flowchart of a method 810 performed by a first node in a wireless communication system according to an embodiment of the present disclosure is shown.
[0475] like Figure 8BAs shown, a method 810 performed by a first node in a wireless communication system according to an embodiment of this disclosure may include: in step S811, sending 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 from the UE the result of the data collection based on the first configuration. In some embodiments, after the UE connects to a second node, second information related to the data collection is sent from the second node to the UE, wherein the second information includes second configuration information for the data collection and a second priority of the second configuration information. In some embodiments, fourth information including the data collection result related to the data collection is sent 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.
[0476] According to embodiments of this disclosure, the configuration information selected by the UE is chosen from the first configuration information and the second configuration information based on the first priority and the second priority.
[0477] According to embodiments of this disclosure, the first information further includes at least one of the following: the Radio Resource Control (RRC) status corresponding to the first configuration information, information related to whether the data collection is triggered by a Radio Access Network (RAN) node, the identification information of the configuration node of the first configuration information, and the identification information of the reporting node of the data collection results corresponding to the first configuration information.
[0478] According to embodiments of this disclosure, the fourth information further includes at least one of the following: time information related to a change in the RRC state of the UE, indication information related to a change in the 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 for the end of the data collection.
[0479] It should be understood that methods 700, 800, 810, etc., according to embodiments of this disclosure may also include any steps described in conjunction with the various examples, aspects, drawings, etc. of this disclosure, or delete one or more of them.
[0480] Next, Figure 9 A schematic diagram of node 900 according to an embodiment of the present disclosure is shown.
[0481] like Figure 9As shown, a node (or node device) 900 according to an embodiment of this 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 (e.g., to control the transceiver 910) to perform methods executed by any node according to an embodiment of this disclosure.
[0482] Figure 10 A schematic diagram of a user equipment (UE) 1000 according to an embodiment of the present disclosure is shown.
[0483] like Figure 10 As shown, a user equipment (UE) 1000 according to an embodiment of this disclosure may include a transceiver 1010 and a processor 1020. The transceiver 1010 may be configured to transmit and receive signals. The processor 1020 may be coupled to the transceiver 1010 and may be configured (e.g., to control the transceiver 1010) to perform methods executed by the user equipment (UE) according to an embodiment of this disclosure. In this disclosure, the processor may also be referred to as a controller.
[0484] Embodiments of this disclosure also provide a computer-readable medium having computer-readable instructions stored thereon, which, when executed by a processor, can be used to implement any method according to embodiments of this disclosure.
[0485] Various embodiments of this disclosure can be implemented as computer-readable code embodied on a computer-readable recording medium from a particular perspective. A computer-readable recording medium is any data storage device capable of storing data readable by a computer system. Examples of computer-readable recording media may include read-only memory (ROM), random access memory (RAM), optical disc read-only memory (CD-ROM), magnetic tape, floppy disk, optical data storage device, carrier wave (e.g., data transmission via the Internet), and the like. Computer-readable recording media can be distributed via computer systems connected via a network, and thus computer-readable code can be stored and executed in a distributed manner. Furthermore, the functional programs, code, and code segments used to implement the various embodiments of this disclosure can be readily interpreted by those skilled in the art applying the embodiments of this disclosure.
[0486] It will be understood that embodiments of this disclosure can be implemented in hardware, software, or a combination of hardware and software. Software can be stored as processor-executable program instructions or computer-readable code on a non-transitory computer-readable medium. Examples of non-transitory computer-readable recording media include magnetic storage media (e.g., ROM, floppy disk, hard disk, etc.) and optical recording media (e.g., CD-ROM, digital video disc (DVD), etc.). Non-transitory computer-readable recording media can also be distributed across a network-coupled computer system, such that the computer-readable code is stored and executed in a distributed manner. The medium can be read by a computer, stored in memory, and executed by a processor. Various embodiments can be implemented by a computer or a portable terminal including a controller and memory, and the memory can be an example of a non-transitory computer-readable recording medium suitable for storing a program(s) having instructions for implementing embodiments of this disclosure. This disclosure can be implemented by a program having code for specifically implementing the apparatus and methods described in the claims, the program being stored in a machine (or computer)-readable storage medium. The program can be carried electronically on any medium, such as communication signals transmitted via wired or wireless connections, and this disclosure suitably includes its equivalents.
[0487] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any person skilled in the art can make various changes or substitutions within the technical scope disclosed in this disclosure, and such changes or substitutions should all be covered within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.
Claims
1. A method performed by a user equipment (UE) in a wireless communication system, comprising: Receive 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; The data collection is performed based on the first configuration information; Connect to the second node; Receive 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 Send to the second node fourth information including data collection results related to the data collection, wherein the data collection results include 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 according to claim 1, wherein, The configuration information selected by the UE is chosen from the first configuration information and the second configuration information based on the first priority and the second priority.
3. The method according to claim 1, further comprising: Send third information related to the reporting of the collected data to the second node, wherein the third information includes the configuration information selected by the UE and the reason for selecting the configuration information.
4. The method according to claim 1, wherein, The first information also includes at least one of the following: The information includes the Radio Resource Control (RRC) status corresponding to the first configuration information, information related to whether the data collection is triggered by a Radio Access Network (RAN) node, the identification information of the configuration node of the first configuration information, and the identification information of the reporting node of the data collection results corresponding to the first configuration information.
5. The method according to claim 1, wherein, The fourth information also includes at least one of the following: The information includes time information related to the change of the RRC state of the UE, indication information related to the change of the RRC state of the UE, the Radio Resource Control (RRC) state corresponding to the data collection result, time information corresponding to the data collection result, and the reason for the end of the data collection.
6. The method according to claim 3, wherein, The third information also includes at least one of the following: Information regarding the data collection being performed by the UE, information regarding whether the UE supports new data collection, information regarding whether the data collection result is the result of data collection triggered by a Radio Access Network (RAN) node, and identification information of the node reporting the data collection result.
7. A method performed by a second node in a wireless communication system, comprising: Sending second information related to data collection to the 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 The UE receives fourth information including data collection results related to the data collection, wherein the data collection results include 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. The first configuration information and the first priority of the first configuration information are included in the first information related to the data collection received by the UE from the first node.
8. The method according to claim 7, wherein, The configuration information selected by the UE is chosen from the first configuration information and the second configuration information based on the first priority and the second priority.
9. The method according to claim 7, further comprising: The UE receives third information related to the reporting of the data collection, wherein the third information includes the configuration information selected by the UE and the reason for selecting the configuration information.
10. The method according to claim 7, wherein, The first information also includes at least one of the following: The information includes the Radio Resource Control (RRC) status corresponding to the first configuration information, information related to whether the data collection is triggered by a Radio Access Network (RAN) node, the identification information of the configuration node of the first configuration information, and the identification information of the reporting node of the data collection results corresponding to the first configuration information.
11. The method according to claim 7, wherein, The fourth information also includes at least one of the following: The information includes time information related to the change of the RRC state of the UE, indication information related to the change of the RRC state of the UE, the Radio Resource Control (RRC) state corresponding to the data collection result, time information corresponding to the data collection result, and the reason for the end of the data collection.
12. The method according to claim 9, wherein, The third information also includes at least one of the following: Information regarding the data collection being performed by the UE, information regarding whether the UE supports new data collection, information regarding whether the data collection result is the result of data collection triggered by a Radio Access Network (RAN) node, and identification information of the node reporting the data collection result.
13. The method according to claim 12, in, Information regarding whether the data collection result was triggered by a Radio Access Network (RAN) node also includes the identification information of the RAN node that triggered the data collection. The method further includes: When the data collection result is the result of data collection triggered by a Radio Access Network (RAN) node, the data collection result is sent to the RAN node and / or the reporting node based on the identification information of the RAN node and / or the identification information of the reporting node of the data collection result.
14. A method performed by a first node in a wireless communication system, comprising: Sending first information related to data collection to the 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 Receive the results of the data collection performed based on the first configuration from the UE. Wherein, after the UE connects to the second node, second information related to the data collection is sent from the second node to the UE, wherein the second information includes second configuration information for the data collection and a second priority of the second configuration information; The fourth information, including data collection results related to the data collection, is sent from the UE to the second node. The data collection results include 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.
15. The method according to claim 14, wherein, The configuration information selected by the UE is chosen from the first configuration information and the second configuration information based on the first priority and the second priority.
16. The method of claim 14, wherein, The first information also includes at least one of the following: The information includes the Radio Resource Control (RRC) status corresponding to the first configuration information, information related to whether the data collection is triggered by a Radio Access Network (RAN) node, the identification information of the configuration node of the first configuration information, and the identification information of the reporting node of the data collection results corresponding to the first configuration information.
17. The method according to claim 14, wherein, The fourth information also includes at least one of the following: The information includes time information related to the change of the RRC state of the UE, indication information related to the change of the RRC state of the UE, the Radio Resource Control (RRC) state corresponding to the data collection result, time information corresponding to the data collection result, and the reason for the end of the data collection.
18. A user equipment (UE) in a wireless communication system, comprising: A transceiver is configured to send and receive signals; as well as A controller, coupled to the transceiver and configured to perform the method as described in any one of claims 1-6.
19. A node in a wireless communication system, comprising: A transceiver is configured to send and receive signals; as well as A controller, coupled to the transceiver and configured to perform the method as described in any one of claims 7-13 or 14-17.
20. A computer-readable medium having stored thereon computer-readable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-6, 7-13, or 14-17.
