Communication method and communication device

Abstract

Provided are a communication method and a communication device. The method comprises: a terminal device receiving configuration information sent by a first network device, wherein the configuration information is used for configuring the terminal device to collect and / or report measurement-related data.

Description

Communication methods and communication equipment Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0002] In some cases, terminal devices need to collect (or report) measurement-related data. How terminal devices collect (or report) measurement-related data is a problem that needs to be solved. Summary of the Invention

[0003] This application provides a communication method and a communication device. The various aspects covered by this application are described below.

[0004] In a first aspect, a communication method is provided, comprising: a terminal device receiving configuration information sent by a first network device, the configuration information being used to configure the terminal device to collect and / or report measurement-related data.

[0005] In a second aspect, a communication method is provided, comprising: a first network device sending configuration information to a terminal device, the configuration information being used to configure the terminal device to collect and / or report measurement-related data.

[0006] Thirdly, a communication method is provided, comprising: a second network device receiving measurement-related data sent by a terminal device.

[0007] Fourthly, a communication device is provided, the communication device being a terminal device, the device comprising: a first receiving unit, configured to receive configuration information sent by a first network device, the configuration information being configured for the terminal device to collect and / or report measurement-related data.

[0008] Fifthly, a communication device is provided, the communication device being a first network device, the device comprising: a first transmitting unit, configured to transmit configuration information to a terminal device, the configuration information being configured for the terminal device to collect and / or report measurement-related data.

[0009] In a sixth aspect, a communication device is provided, the communication device being a second network device, the device comprising: a first receiving unit for receiving measurement-related data sent by a terminal device.

[0010] A seventh aspect provides a communication device including a transceiver, a memory, and a processor, wherein the memory is used to store a program, the processor is used to invoke the program in the memory, and to control the transceiver to receive or transmit signals so that the communication device performs the method as described in the first, second, or third aspect.

[0011] Eighthly, an apparatus is provided, including a processor for calling a program from a memory to cause the apparatus to perform the method as described in the first, second, or third aspect.

[0012] A ninth aspect provides a chip including a processor for calling a program from memory to cause a device having said chip mounted to perform the methods described in the first, second, or third aspect.

[0013] A tenth aspect provides a computer-readable storage medium having a program stored thereon that causes a computer to perform the methods described in the first, second, or third aspect.

[0014] Eleventh aspect: A computer program product is provided, characterized in that it includes a program that causes a computer to perform the methods described in the first, second, or third aspect.

[0015] In a twelfth aspect, a computer program is provided that causes a computer to perform the methods described in the first, second, or third aspect.

[0016] In this embodiment, the first network device sends configuration information to the terminal device, which can then collect (or report) measurement-related data based on this configuration information. This embodiment relies on the terminal devices to collect measurement-related data. Since there are a large number of terminal devices, sufficient measurement-related data can be collected, thereby improving the training effect of the subsequent model (a model with measurement prediction capabilities). Attached Figure Description

[0017] Figure 1 is a system architecture example diagram of a communication system applicable to embodiments of this application.

[0018] Figure 2 is a schematic diagram of the measurement process of the terminal device.

[0019] Figure 3 is a schematic flowchart of the Layer 3 switching process.

[0020] Figure 4 shows an example of a measurement task.

[0021] Figure 5 is a schematic flowchart of the LTM cell replacement process.

[0022] Figure 6 shows an example diagram of the observation window and the prediction window (PW).

[0023] Figure 7 is a schematic flowchart of the terminal device reporting capability information proposed in related technologies.

[0024] Figure 8 is a schematic flowchart of a communication method provided in one embodiment of this application.

[0025] Figure 9A is a schematic flowchart of a communication method provided in another embodiment of this application.

[0026] Figure 9B is a schematic flowchart of a communication method provided in another embodiment of this application.

[0027] Figure 9C is a schematic flowchart of a communication method provided in another embodiment of this application.

[0028] Figure 10 is a schematic flowchart of a communication method provided in another embodiment of this application.

[0029] Figure 11 is a schematic flowchart of a communication method provided in another embodiment of this application.

[0030] Figure 12 is a schematic flowchart of a communication method provided in another embodiment of this application.

[0031] Figure 13 is a schematic flowchart of a communication method provided in another embodiment of this application.

[0032] Figure 14 is a schematic flowchart of a communication method provided in another embodiment of this application.

[0033] Figure 15 is a schematic flowchart of a communication method provided in another embodiment of this application.

[0034] Figure 16 is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0035] Figure 17 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.

[0036] Figure 18 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.

[0037] Figure 19 is a schematic diagram of the structure of a device applicable to the embodiments of this application. Detailed Implementation

[0038] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0039] Communication system

[0040] The embodiments of this application can be applied to various communication systems. For example, the embodiments of this application can be applied to Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), Advanced Long Term Evolution (LTE-A), New Radio (NR), evolution systems of NR, LTE-based access to unlicensed spectrum (LTE-U), NR-based access to unlicensed spectrum (NR-U), Universal Mobile Telecommunications System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), and 5th-generation (5G) systems. The embodiments of this application can also be applied to other communication systems, such as future communication systems. This future communication system could be, for example, a sixth-generation mobile communication system or a satellite communication system.

[0041] Traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, communication systems can now support not only traditional cellular communication but also one or more other types of communication. For example, a communication system can support one or more of the following communication methods: device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, and vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to communication systems that support the above-mentioned communication methods.

[0042] The communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

[0043] The communication system in this application embodiment can be applied to unlicensed spectrum. This unlicensed spectrum can also be considered a shared spectrum. Alternatively, the communication system in this application embodiment can also be applied to licensed spectrum. This licensed spectrum can also be considered a dedicated spectrum.

[0044] The embodiments of this application can be applied to terrestrial networks (TN) systems as well as non-terrestrial networks (NTN) systems. As an example, the NTN system can include an NR-based NTN system and an Internet of Things (IoT)-based NTN system.

[0045] A communication system may include one or more terminal devices. The terminal devices mentioned in the embodiments of this application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc.

[0046] In some embodiments, the terminal device may be a station (ST) in a WLAN. In some embodiments, the terminal device may also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a next-generation communication system (e.g., NR system), or terminal device in a future evolved public land mobile network (PLMN) network, etc.

[0047] In some embodiments, the terminal device may be a device that provides voice and / or data connectivity to the user. For example, the terminal device may be a handheld device, an in-vehicle device, etc., with wireless connectivity. As some specific examples, the terminal device may be a mobile phone, tablet, laptop, PDA, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc.

[0048] In some embodiments, the terminal device may be deployed on land. For example, the terminal device may be deployed indoors or outdoors. In some embodiments, the terminal device may be deployed on water, such as on a ship. In some embodiments, the terminal device may be deployed in the air, such as on an airplane, balloon, or satellite.

[0049] In addition to terminal devices, the communication system may also include one or more network devices. In this embodiment, the network device may be a device for communicating with the terminal device; this network device may also be referred to as an access network device or a radio access network (RAN) device. For example, the network device may be a base station. In this embodiment, the network device may refer to an access network node (or device) that connects the terminal device to the wireless network. Access network equipment can broadly encompass various names listed below, or be interchangeable with them, such as: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point (AP), transmitting and receiving point (TRP), transmitting point (TP), master station (MeNB), secondary station (SeNB), multi-mode radio (MSR) node, home base station, network controller, access node, radio node, transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. Base stations can be macro base stations, micro base stations, relay nodes, donor nodes, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0050] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0051] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.

[0052] By way of example and not limitation, in the embodiments of this application, the network device may have mobility characteristics; for example, the network device may be a mobile device. In some embodiments of this application, the network device may be satellite-based or space-based, that is, the network device is installed on a satellite or flying equipment. In some embodiments of this application, the network device may also be a base station installed in locations such as land or water.

[0053] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0054] For example, Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. As shown in Figure 1, the communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within that coverage area.

[0055] Figure 1 illustrates an exemplary network device and two terminal devices. In some embodiments of this application, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area. This application does not limit this aspect.

[0056] In some embodiments of this application, the wireless communication system shown in FIG1 may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but this application does not limit this.

[0057] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Taking the communication system 100 shown in FIG1 as an example, the communication devices may include network devices 110 and terminal devices 120 with communication functions. Network devices 110 and terminal devices 120 can be the specific devices described above, which will not be repeated here. The communication devices may also include other devices in the communication system 100, such as network controllers, mobility management entities, and other network entities, which are not limited in this application embodiment.

[0058] RRM measurement

[0059] In 3GPP cellular communication systems, terminal devices need to obtain the strength or quality of radio signals in the current serving cell and neighboring cells through Reference Memory Management (RRM) measurements. The terminal device can then report the measurement results to the network device via a Radio Resource Control (RRC) message in the form of a measurement report, enabling the network device to make handover decisions based on the report. RRM measurements include intra-frequency measurements, inter-frequency measurements, and inter-radio access technology (RAT) measurements (such as LTE and NR). Regardless of the method, the measurement object is usually a cell within a single frequency. In NR technology, the terminal device actually measures reference signals configured within the cell, such as synchronization signal blocks (SSBs) or channel state information reference signals (CSI-RS). There are often multiple SSBs and CSI-RSs. In this application, a reference signal and a beam are the same thing. 3GPP standards, such as 38.133, specify the performance requirements that terminal devices must meet when performing RRM measurements. This performance requirement mainly includes the absolute and relative accuracy of RRM measurements.

[0060] Section 5.5.3 of 3GPP TS 38.331 describes how terminal equipment performs same-frequency or different-frequency measurements, how it performs measurement sampling at the physical layer (Layer 1, L1) according to beams, and how it makes judgments on measurement events based on parameters configured in the network equipment. The above can be described using the model diagram in section 9.2.4 of TS 38.300 (see Figure 2).

[0061] Figure 2 includes multiple reference points. At reference point A, the terminal device performs physical layer measurement sampling, obtaining measurement results that have not undergone layer 1 filtering. As shown in Figure 2, the terminal device performs physical layer measurement sampling for each beam from the network device.

[0062] At reference point A1, the terminal equipment performs L1 filtering on the obtained beam measurement results. Generally, the terminal equipment must perform at least one measurement sampling within a measurement cycle. The number of samplings is an internal implementation of the terminal equipment. To have a common understanding of performance requirements, 3GPP standards engineers have reached some consensus on this, which is reflected in the standard specifications in a certain way. Generally, for the frequency range (FR) 1 band, 5 samplings are performed; for the FR2-1 band, 8*5 samplings are performed; and for the FR2-2 band, 12*5 samplings are performed. How to perform Layer 1 filtering is the engineering implementation of the terminal equipment.

[0063] At reference point B, the terminal device merges the beam measurement results obtained at reference point A1 within a specific cell to synthesize a Layer 1 cell-level measurement result. This process essentially selects several beams whose measurement results exceed a pre-configured threshold. The threshold and the maximum number of selected beams can be configured by the network device. When no beam meets the criteria, the terminal device selects the measurement result of the beam with the best result as the Layer 1 cell-level measurement result.

[0064] At reference point C, the Layer 1 cell-level measurement results of a certain cell are filtered by L3 to obtain the L3 cell-level measurement results. The Layer 3 filtering process can be described by the following formula: F n = (1–a)*F n-1 +a*M n This formula describes an iterative process. F n-1 This is the result of the previous layer 3 filtering, M. n This is the newly obtained measurement result after layer 1 filtering. The parameter 'a' is a filtering coefficient used to adjust the weight between the new measurement result and the previously obtained layer 3 filtered result.

[0065] At reference point D, the measurement results of the serving cell and / or neighboring cells are used to determine whether a specific measurement event is valid according to certain decision conditions (which can be configured by the network equipment). For example, whether the measurement result of the neighboring cell is higher than the measurement result of the primary cell (PCell) by an offset value.

[0066] The triggering of a measurement event can include the following basic elements:

[0067] 1. Measurement Results. Measurement results may include measurements of the serving cell (Ms) and / or neighboring cells (Mn). For example, measurement results may include the cell's signal strength.

[0068] 2. Comparison Parameters. These include thresholds, hysteresis values, and offset values. Comparison parameters can include one or more of these. In determining whether a measurement event has occurred, either absolute or relative comparisons can be performed based on the comparison parameters. An absolute comparison directly compares the measurement value of a cell with a threshold. In an absolute comparison, if the measurement result is greater than "threshold + hysteresis value," the entry condition for a measurement event is met; if the measurement result is less than "threshold - hysteresis value," the exit condition for a measurement event is met. Relative comparisons typically compare the measurement results of neighboring cells with the measurement results of the serving cell. Before comparison, each cell's measurement result needs to be appended with its respective offset value (ofs, ofn). For the serving cell, the measurement result also needs to be appended with the offset value related to the corresponding event (Off_event). Finally, the hysteresis value (Hys) also needs to be considered when performing relative comparisons. Taking event A3 as an example, assuming the relevant parameters of the serving cell are labeled with 's' and the relevant parameters of neighboring cells are labeled with 'n', then the entry condition for the measurement event can be expressed as: Mn + Ofn > Ms + Ofs + Hys + Off_event, and the departure condition for the measurement event can be expressed as: Mn + Ofn <Ms+Ofs-Hys+Off_event。

[0069] To maintain the robustness of the comparison process, a timer, namely the TTT (time to trigger) timer, can be introduced into the system. The TTT timer starts when a cell meets the entry condition for a certain event. When the TTT timer expires, if the measurement results of that cell continue to meet the entry condition for the event, it indicates that the cell has triggered the measurement event.

[0070] The measurement events mentioned above can include traditional Layer 3 handover, conditional Layer 3 handover, and LTM cell replacement. Handover or cell replacement can be understood as the process by which a terminal device changes its current primary serving cell (PCell) or secondary primary cell (SPCell), as shown in Figure 3.

[0071] Layer 3 measurement events may include the A1, A2, A3, A4, A5 and A6 events described in section 5.5.4 of 3GPP protocol 38.331.

[0072] A1 event: Serving becomes better than the threshold;

[0073] A2 event: Serving becomes worse than the threshold;

[0074] Event A3: Neighbour becomes offset better than SpCell;

[0075] Event A4: Neighbour becomes better than threshold;

[0076] Event A5: The primary cell becomes worse than threshold 1 and the neighboring cell becomes better than threshold 2.

[0077] Event A6: Neighbour becomes offset better than SpCell.

[0078] To enable terminal devices to perform RRM measurements, network devices can configure measurement tasks for terminal devices via RRC messages. A measurement task can be associated with a measurement object and a reporting configuration.

[0079] Network devices can configure multiple measurement objects and multiple reporting configurations for the same terminal device. There can be a many-to-many relationship between measurement objects and reporting configurations. Any such relationship can be illustrated in Figure 4. Figure 4 shows a measurement task, along with the measurement objects and reporting configurations associated with that task. A measurement object can be understood as a reference signal within a cell on a specific frequency point. Generally, the terminal device can first discover neighboring cells by searching for reference signals, and then measure the reference signals of the discovered cells. In the reporting configuration, the network device can configure the terminal device to report in one or more of the following ways: periodic reporting, event-triggered reporting.

[0080] When a terminal device performs measurements according to a measurement task and meets the conditions for periodic reporting or event-triggered reporting, it can report a measurement report to the network device. The network device can then decide whether to trigger a handover based on the received measurement report. When the network device decides to trigger a handover, it can notify the terminal device of the target cell's configuration information via a handover command, thereby triggering the terminal device to initiate the process of accessing the target cell.

[0081] As shown in Figure 5, during LTM cell replacement, network devices can use Layer 3 measurement events reported by terminal devices to configure one or more candidate cells for the terminal devices via handover commands, and configure reference signal information within the candidate cells in the same message. The terminal devices trigger the network devices to send cell replacement commands by measuring and reporting Layer 1 measurement results of the reference signals or by measurement events based on Layer 1 measurement results, thereby achieving the purpose of cell replacement.

[0082] LTM events can include the following events:

[0083] LTM2 event: The beam of the serving cell becomes worse than the absolute threshold.

[0084] LTM3 event: The beam of the candidate cell becomes an amount of offset better than the beam of the serving cell.

[0085] LTM4 event: The beam of candidate cell becomes better than the absolute threshold.

[0086] LTM5 event: The beam of the serving cell becomes worse than absolute threshold 1 and the beam of the candidate cell becomes better than another absolute threshold 2.

[0087] The triggering mechanism based on Layer 1 measurement events may include the following steps 1 to 3.

[0088] In step 1, the terminal device measures the serving reference signal in the serving cell and the candidate reference signal in the candidate cell. When the signal strength of any reference signal in a candidate cell meets the entry condition of the measurement event, the terminal device starts the TTT timer associated with that reference signal.

[0089] In step 2, if the strength of the reference signal of the candidate cell consistently meets the above entry conditions during the TTT timer's operation, the timer will not stop. If the TTT timer eventually times out, a Layer 1 measurement event will be triggered.

[0090] In step 3, after a measurement event is triggered, the terminal device reports the measurement results to the network device via medium access control (MAC) signaling. The reported measurement results include at least the information of the triggered Layer 1 measurement event, the candidate beam of the candidate cell that triggered the Layer 1 measurement event, and the measurement results of that candidate beam. Of course, for LTM cell replacement, the Layer 3 measurement event can also be used to trigger the network device to send a cell replacement command.

[0091] The LTM cell handover mechanism also includes similar measurement tasks to Layer 3 handover. However, in the LTM cell handover mechanism, the measurement object typically refers to the reference signal within the candidate cell. For the reporting configuration, the physical layer mechanism for reporting uplink control information (UCI) can be used, or MAC signaling can be used for reporting. When using MAC signaling for reporting, the terminal device can use one or more of the following reporting methods: periodic reporting and event-triggered reporting.

[0092] Artificial intelligence (AI) / machine learning (ML) in 3GPP

[0093] In Rel 18, 3GPP investigated whether AI / ML models could be applied to key technologies at the physical layer. For example, could AI / ML models compress and decompress channel state information (CSI) of the radio interface? Could they predict optimal beams or beam pairs in the spatial or temporal domains? And could they predict positioning?

[0094] In Release 19, 3GPP applied techniques used for beam measurement prediction to RRM measurements. The following use cases were identified in 3GPP RAN2's study on RRM measurements: RRM measurement prediction, measurement event prediction, and radio link failure (RLF) / handover failure (HOF) event prediction.

[0095] The RRM measurement prediction use case contains three sub-use cases by distinguishing between the model's input and output, as shown in Table 1.

[0096] Table 1

[0097] These sub-use cases use the same performance metric: the average absolute error between the predicted L3 reference signal received power (RSRP) (a cell-level Layer 3 measurement) and the actual L3 RSRP, which is used as the prediction accuracy. The actual L3 RSRP can be understood as the L3 RSRP measured by the terminal equipment following existing measurement procedures. The same approach may be used to define performance metrics in 3GPP RAN4, or it may use absolute or relative measurement accuracy.

[0098] Terminal devices can perform predictions in the time domain, spatial domain, or frequency domain. Prediction in the time domain can be understood as using historical measurement results to predict future measurement results. The timing of the terminal device's measurement in the time domain is referred to as the measurement timing in this application. The measurement timing can be understood as the sampling timing within a measurement cycle, or as the timing of obtaining the measurement results after Layer 1 filtering. Prediction in the spatial domain can be understood as predicting the measurement results of other reference signals by measuring a portion of the reference signals within a cell. Prediction in the frequency domain can be understood as using the measurement results at one frequency point to predict the measurement results at another frequency point.

[0099] Terminal devices can also infer measurement events based on the results of RRM measurement predictions, or directly predict measurement events based on the RRM measurement results.

[0100] If the purpose of RRM measurement prediction is to reduce measurements in a certain domain (time, spatial, or frequency domain), then the prediction accuracy is directly related to the proportion of measurements reduced. For example, the terminal device can measure the reference signal at some measurement opportunities or at all measurement opportunities to obtain partial actual measurement results. Then, based on these partial actual measurement results, the terminal device can use AI / ML algorithms to predict the measurement results of the remaining measurement opportunities or the remaining reference signals. The terminal device no longer performs actual measurements on the predicted portion of the measurement opportunities or reference signals, thus saving the hardware and software resources and energy consumption required for measurement. If the purpose of RRM measurement prediction is to know the measurement results in advance for a period of time, the terminal device can use the actual measurement results at a certain frequency (e.g., f1) within a certain time window (called the observation window) to predict whether a certain measurement event will be triggered at that frequency (f1) in the future (called the prediction window), as shown in Figure 6. In Figure 6, t0 represents the current time. In this way, it is possible to know in advance whether a certain measurement event will be triggered, allowing network devices to begin preparation and execution of handover in advance.

[0101] Terminal device capability reporting process

[0102] Referring to Figure 7, the terminal device can report capability information to the network device through the process described in section 5.6 of part 38.331 of 3GPP.

[0103] As shown in Figure 7, the capability information reported by the terminal device can include the capabilities of various protocol layers (including higher layers and the physical layer) and radio frequency related capabilities of the terminal device. When the terminal device has AI / ML capabilities to perform RRM measurement prediction or measurement event prediction, the terminal device can report the relevant capabilities to the network through a similar process.

[0104] The aforementioned models with measurement prediction or measurement event prediction capabilities require training before deployment. Model training presupposes the collection of sufficient data, which is then used to train the model. If data collection is performed by the terminal device, the terminal device may also need to report the collected data to the network device so that the network device can train the model based on this data.

[0105] In related technologies, 3GPP has discussed solutions for data collection in both the terminal-side and network-side models of beam management (BM). For the terminal-side model, the configuration parameters required for data collection are configured by the base station, involving configuration parameters for the entire and subset reference sets related to the serving cell and BM use cases. From a process perspective, the terminal device can initiate a data collection request, while the network device can control the data collection by the terminal device.

[0106] For use cases related to AI mobility, such as RRM measurement prediction or measurement event prediction, terminal devices need to collect measurement-related data. Furthermore, terminal devices may also need to report the collected measurement-related data. However, relevant technologies have not yet proposed solutions regarding how terminal devices should collect and report measurement-related data.

[0107] To address the aforementioned problems, embodiments of this application provide a communication method. Using this method, a first network device sends configuration information to a terminal device, which can then collect or report measurement-related data based on this configuration information.

[0108] The embodiments of this application will now be described in detail with reference to Figure 8.

[0109] Figure 8 is a schematic flowchart of a communication method provided in an embodiment of this application. The method in Figure 8 is described from the perspective of interaction between a terminal device and a first network device. The terminal device may be a UE. The first network device may be a base station.

[0110] Referring to Figure 8, in step S810, the terminal device receives configuration information sent by the first network device.

[0111] In some cases, configuration information can be used by terminal devices to collect measurement-related data. This measurement-related data can be used to train a model or function with measurement prediction capabilities. For example, the model or function can implement measurement prediction based on artificial intelligence algorithms. In the embodiments of this application, "model" and "function" can be used interchangeably. The description of "model" in the embodiments of this application also applies to "function". The measurement prediction mentioned here can be predicting measurement results. The measurement prediction here can also be predicting measurement events. The predicted measurement results here can include one or more of the following: predicting measurement results in the time domain; predicting measurement results in the frequency domain; predicting measurement results in the spatial domain. The measured quantity of the measurement result can include one or more of the following: RSRP; reference signal received quality (RSRQ); signal-to-interference-plus-noise ratio (SINR). The predicted measurement events here can include one or more of the following: predicting measurement events directly; predicting measurement events indirectly. Predicting measurement events directly can be understood as directly predicting whether a measurement event will be triggered based on the actual input measurement results. Predicting measurement events indirectly can be understood as first predicting the measurement result in a certain domain (time domain, spatial domain, or frequency domain), and then determining whether to trigger a measurement event based on preset rules. If the terminal device's model has one or more of the measurement prediction functions mentioned above, it can also be said that the terminal device has a measurement prediction function. After receiving the configuration information, the terminal device can collect measurement-related data based on the configuration information.

[0112] In other cases, configuration information can also be used by the terminal device to report measurement-related data. Measurement-related data may include one or more of the following: measurement results, measurement event information, timestamp information of the measurement results, and timestamp information of the measurement events. As mentioned above, measurement-related data can be used for model training. Some models may be trained by network devices. For these models, the terminal device needs to report measurement-related data to the network device so that the network device can use this data for model training. For ease of distinction, in this embodiment, the network device receiving the measurement-related data reported by the terminal device is referred to as the second network device. The second network device may be the first network device mentioned above. Alternatively, the second network device may be a core network device. In this embodiment, the core network device may also be referred to as a core network node. Alternatively, the second network device may be a server that has established an application layer channel with the terminal device. After receiving the configuration information, the terminal device can report measurement-related data based on the configuration information.

[0113] Configuration information may include one or more of the following: information about the measurement object; control information. The measurement object here can be understood as the reference signal (or beam) mentioned earlier. The reference signal here may include one or more of the following: reference signal within the serving cell; reference signal within neighboring cells; reference signal within candidate cells. The candidate cell here can be understood as a cell among one or more candidate handover cells pre-configured by the terminal equipment. The reference signal here can be an SSB or CSI-RS. The control information here can be used to control the collection and / or reporting of measurement-related data.

[0114] This configuration information can be carried within an RRC Reconfiguration message. An RRC Reconfiguration message can be understood as a specialized type of RRC message. For example, this configuration information could be carried within a data collection configuration message.

[0115] As described above, the first network device can control the terminal device to collect and / or report measurement-related data through configuration information. The first network device can control the terminal device to collect and / or report measurement-related data by configuring data collection and / or reporting tasks for the terminal device. In other words, the configuration information mentioned in step S810 can be used by the terminal device to perform data collection and / or reporting tasks.

[0116] In some implementations, configuration information can be used not only for the terminal device to perform data collection and / or reporting tasks, but also for the terminal device to perform measurement tasks. That is, the task of collecting and / or reporting measurement-related data can simultaneously be an ongoing measurement task. If the measurement-related data is collected through an ongoing measurement task, the measurement event itself may affect the mobility behavior of the terminal device. In this case, the data collected and / or reported by the terminal device may be data generated in a measurement task. At this time, the first network device can configure both the data collection and / or reporting task and the measurement task. The first network device can configure the data collection and / or reporting task and the measurement task on or off serving frequencies. The configuration information sent by the first network device may include configuration information related to the data collection and / or reporting task, as well as configuration information related to the measurement task. The terminal device can perform the data collection and / or reporting task according to the configuration information related to the data collection and / or reporting task, and perform the measurement task according to the configuration information related to the measurement task.

[0117] In some implementations, the configuration information can be used by the terminal device to perform data collection and / or reporting tasks, but not for the terminal device to perform measurement tasks. That is, the first network device can configure the data collection and / or reporting task as a separate measurement task for data collection and / or reporting. If the measurement-related data is a separate measurement task for data collection, the measurement event itself can be considered a virtual event and will not affect the mobility behavior of the terminal device. The configuration information sent by the first network device may only include configuration information for the data collection and / or reporting task, excluding configuration information related to the measurement task. Alternatively, the configuration information sent by the first network device may include both configuration information for the data collection and / or reporting task and configuration information related to the measurement task. If the configuration information sent by the first network device only includes configuration information for the data collection and / or reporting task, excluding configuration information related to the measurement task, the terminal device can directly perform the data collection and / or reporting task according to the configuration information sent by the first network device. If the configuration information sent by the first network device includes both configuration information for data collection and / or reporting tasks and configuration information related to measurement tasks, the terminal device can ignore the configuration information related to measurement tasks sent by the first network device and perform the data collection and / or reporting tasks according to the configuration information related to data collection and / or reporting tasks sent by the first network device. For example, if the configuration information is configured in an existing information unit for configuring measurement tasks, since some mandatory information units in the information unit for configuring measurement tasks are used to specify how the terminal device reports through the Uu interface, the terminal device can ignore these information units if the measurement task is only set up for data collection purposes.

[0118] As can be seen from step S810, in this embodiment of the application, the first network device sends configuration information to the terminal device, and the terminal device can collect or report measurement-related data according to the configuration information.

[0119] Step S810 states that the configuration information may include one or more of the following: information about the measurement object; control information. The information about the measurement object may include one or more of the following: frequency point information; subcarrier information. Frequency point information may be used to indicate one or more frequency points. Control information may be used to control the collection and / or reporting of measurement-related data.

[0120] Information about the object being measured can be configured in an information unit used to describe the object being measured. In embodiments of this application, the information unit describing the object being measured can be referred to as MO.

[0121] Control information can be configured in an information unit for configuring the collection and / or reporting of measurement-related data. This information unit for configuring the collection and / or reporting of measurement-related data can be an extension of an existing Report Configuration Information Unit (ReportConfigNR). Alternatively, this information unit can be a newly introduced information unit, rather than an extension of an existing Report Configuration Information Unit (ReportConfigNR). This newly introduced information unit can be called a Data Collection Report Configuration (DCRC) information unit.

[0122] Step S810 also mentions that the measurement object can be associated with control information.

[0123] Control information can be associated with a single measurement object. Alternatively, control information can be associated with multiple measurement objects. For example, multiple measurement objects could be two measurement objects.

[0124] Whether the control information is associated with a single measurement object or with multiple measurement objects, the association between the measurement objects and the control information can be achieved through different association methods. This application provides two association methods for achieving the association between measurement objects and control information.

[0125] In the first association method, the measurement object can be associated with control information through an association identifier. That is, the measurement object and control information can correspond to the same association identifier. This association identifier enables the association between control information and the measurement object. This association identifier can be configured by extending an existing MeasIdToAddMod information element. Alternatively, the association identifier can be configured in a newly introduced information element. When the association identifier is configured in a newly introduced information element, the association identifier can be called RRM_DC_ID.

[0126] As mentioned earlier, control information can be associated with a measurement object. When control information is associated with a measurement object, the information unit used to configure the measurement object can be linked to the information unit used to configure the control information associated with that measurement object using either `measId` or `RRM_DC_ID`, thus achieving the association between control information and a measurement object. For example, if the information of a measurement object is configured in an `MO`, and the control information associated with that measurement object is configured in `ReportConfigNR`, the `MO` and `ReportConfigNR` can be associated using `measId`. As another example, if the information of a measurement object is configured in an `MO`, and the control information associated with that measurement object is configured in a `DCRC`, the `MO` and `DCRC` can be associated using `RRM_DC_ID`.

[0127] If the configuration information includes information on multiple measurement objects, and these measurement objects are associated with multiple control information entries, then multiple association identifiers used to associate these measurement objects with the control information entries can be linked together. For ease of understanding, the following example uses two measurement objects. For instance, the information for the first measurement object is configured in the first MO, and the control information associated with this first measurement object is configured in ReportConfigNR. The measId associates the first MO with this ReportConfigNR. The information for the second measurement object is configured in the second MO, and the control information associated with the second measurement object is configured in DCRC. RRM_DC_ID associates the second MO with DCRC. Then, the measId can be associated with RRM_DC_ID. For example, the measId can be configured in DCRC.

[0128] As mentioned earlier, control information can be associated with multiple measurement objects. For ease of understanding, the following example illustrates the association of control information with two measurement objects. When control information is associated with two measurement objects, the `measId` can be used to associate two information units used to configure the information of the two measurement objects with the information unit used to configure the control information associated with those two measurement objects, thus achieving the association between the control information and the two measurement objects. For example, if the information of the two measurement objects is configured in two separate `MOs`, and the control information associated with these two measurement objects is configured in `ReportConfigNR`, then the `measId` can be used to associate these two `MOs` with `ReportConfigNR`.

[0129] In the second association method, the control information may include an identifier for the measured object. That is, each measured object corresponds to an identifier; if the control information includes or adds the identifier corresponding to that measured object, it indicates that the control information is associated with that measured object. For example, the measured object can be associated with the control information by referencing the identifier of a measured object within a unit of control information.

[0130] As mentioned earlier, the first network device can control the terminal device's collection and / or reporting of measurement-related data by configuring data collection and / or reporting tasks for the terminal device. That is, configuration information can be used to configure measurement-related data collection and / or reporting tasks. In this case, the association identifier mentioned in the first association method can be the identifier of the measurement-related data collection and / or reporting task. In other words, through the identifier of the measurement-related data collection and / or reporting task, a measurement-related data collection and / or reporting task can be associated with a measurement object and control information. A measurement-related data collection and / or reporting task can be associated with control information and a measurement object. In this case, there is an association between a measurement-related data collection and / or reporting task, a measurement object, and control information. Alternatively, a measurement-related data collection and / or reporting task can be associated with control information and multiple measurement objects. In this case, there is an association between a measurement-related data collection and / or reporting task, multiple measurement objects, and control information. For example, by identifying a task for collecting and / or reporting measurement-related data, a task for collecting and / or reporting measurement-related data, two measurement objects, and control information can be linked together.

[0131] As mentioned earlier, a data collection and / or reporting task can be a standalone measurement task for data collection and / or reporting, or it can be an ongoing measurement task. In this case, the association identifier mentioned in the first association method can be the identifier of the measurement task. Alternatively, the association identifier mentioned in the first association method and the identifier of the measurement task can be the same identifier. If the data collection and / or reporting task is a standalone measurement task for data collection and / or reporting, the association identifier can be used to associate the measurement-related data collection and / or reporting task, the measurement object, and the control information corresponding to the measurement-related data collection and / or reporting task. If the data collection and / or reporting task is also an ongoing measurement task, the association identifier can be used to associate the measurement-related data collection and / or reporting task, the measurement task, the measurement object, and the control information corresponding to the measurement-related data collection and / or reporting task.

[0132] As mentioned above, the information of the measured object may include one or more of the following: frequency information; subcarrier information.

[0133] The frequency point information here can be used to indicate one or more frequency points. This frequency point information can be configured in the MO (Multiple Information Unit). Alternatively, the frequency point information can also be configured in a newly introduced information unit. Multiple frequency points here can be, for example, two frequency points. When the frequency point information configured by the first network device is used to indicate one frequency point, that frequency point can be a serving frequency point or a non-serving frequency point. A serving frequency point can be understood as the frequency point where the terminal device's current serving cell is located. A non-serving frequency point can also be called a neighboring frequency point. When the frequency point information configured by the first network device is used to indicate two frequency points, one of the two frequency points can be a serving frequency point, and the other frequency point can be a frequency point that requires the configuration of an additional measurement interval. Subcarrier information can be used to indicate the subcarrier interval corresponding to the one or more frequency points. For example, if measurement-related data is used to train a model predicting measurement results in the time or spatial domain, the frequency point information configured by the first network device can be used to indicate one frequency point. As another example, if measurement-related data is used to train a model predicting measurement results in the frequency domain, the frequency point information configured by the first network device can be used to indicate two frequency points. For example, measurement-related data is used to train a model that predicts measurement events directly. Such a model does not generalize across different types of measurement events. If the type of measurement event involves non-serving frequencies of neighboring cells, then the first network device needs to configure the non-serving frequency information. Of course, in some cases, the first network device may not need to configure frequency information. For example, measurement-related data is used to train a model that predicts measurement events indirectly. Such a model generalizes across different types of measurement events, and in this case, the first network device may not need to configure frequency information.

[0134] As mentioned above, configuration information may include control information. This control information may include one or more of the following: the type of measurement-related data; the collection cycle of measurement-related data; the triggering conditions for collecting measurement-related data; the reporting cycle of measurement-related data; the triggering conditions for reporting measurement-related data; and measurement control parameters.

[0135] The type information of the measurement-related data mentioned above may include one or more of the following: type information of measurement results, type information of measurement events.

[0136] The type information of the measurement results can be used to indicate whether the collected measurement results are cell-level or beam-level measurements. It can also indicate whether the collected measurement results are layer 1 or layer 3 measurements. The type information can include one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. Layer 1 measurement results can be measured and collected at the granularity of the reference signal. If the performance of the model trained using measurement-related data is evaluated based on the prediction accuracy of the layer 1 measurement results, the type information of the measurement results configured in the first network device can include beam-level layer 1 measurement results and / or cell-level layer 1 measurement results. Similarly, if the performance of the model trained using measurement-related data is evaluated based on the prediction accuracy of the layer 3 measurement results, the type information of the measurement results configured in the first network device can include beam-level layer 3 measurement results and / or cell-level layer 3 measurement results. Generally, layer 3 measurement results are essential for layer 3 handover mechanisms. If the model is used for predicting measurement events for Layer 3 handover, the type information of the measurement results configured in the first network device may include beam-level Layer 3 measurement results and / or cell-level Layer 3 measurement results, but not beam-level Layer 1 measurement results and / or cell-level Layer 1 measurement results. If the model is used for predicting measurement events for LTM cell replacement, the type information of the measurement results configured in the first network device may include beam-level Layer 1 measurement results and / or cell-level Layer 1 measurement results, but not beam-level Layer 3 measurement results and / or cell-level Layer 3 measurement results.

[0137] The type information of a measurement event can be used to indicate the type of one or more measurement events. The type information of a measurement event can include one or more of the following: Layer 1 measurement event, Layer 3 measurement event. A Layer 1 measurement event can be an LTM cell replacement measurement event. A Layer 3 measurement event can be, for example, a Layer 3 handover measurement event. An LTM cell replacement measurement event can include one or more of the following: LTM2 event, LTM3 event, LTM4 event, LTM5 event. A Layer 3 handover measurement events can include one or more of the following: A1 event, A2 event, A3 event, A4 event, A5 event, A6 event.

[0138] Different types of measurement events may involve different cells (e.g., serving cell or neighboring cells). They may also involve different frequencies (e.g., serving frequency or neighboring frequency). For example, an A1 event involves the serving frequency of the serving cell, while an A3 event involves the serving frequency of the serving cell, the serving frequency of a neighboring cell, and the neighboring frequency of a neighboring cell. Given this, the first network device can configure the type information of the measurement events to allow terminal devices to collect and / or report measurement-related data in a targeted manner.

[0139] The first network device can be configured to periodically collect measurement-related data from the terminal device. In this case, the first network device can configure the collection period of the measurement-related data in the control information to instruct the terminal device on the period or time interval for collecting the measurement-related data.

[0140] The first network device can also be configured to allow the terminal device to collect data in a condition-triggered manner. In this case, the first network device can configure the triggering conditions for collecting measurement-related data in the control information, which instructs the conditions that trigger the terminal device to collect measurement-related data. For example, the first network device can be configured to allow the terminal device to collect data in a signal-triggered manner. In this case, the triggering conditions for collecting measurement-related data may include a signal threshold for collecting measurement-related data.

[0141] Of course, the first network device can be configured to collect measurement-related data by combining periodic collection with condition-triggered methods. In this case, the first network device can configure the collection period and triggering conditions for the collection of measurement-related data in the control information.

[0142] The first network device can be configured to periodically report measurement-related data by the terminal devices. In this case, the first network device can configure the reporting period of measurement-related data in the control information to indicate the period or time interval for the terminal devices to report measurement-related data.

[0143] The first network device can also be configured to allow terminal devices to report data based on conditional triggering. In this case, the first network device can configure the triggering conditions for reporting measurement-related data in the control information, which indicates the conditions that trigger the terminal devices to report measurement-related data.

[0144] Of course, the first network device can be configured to allow terminal devices to report measurement-related data using a combination of periodic reporting and condition-triggered methods. In this case, the first network device can configure the reporting cycle for measurement-related data and the triggering conditions for reporting measurement-related data in the control information.

[0145] Measurement control parameters can be used to control how terminal devices perform measurements. Measurement control parameters may include one or more of the following: parameters for merging Layer 1 measurement results, and parameters for performing Layer 3 filtering. For example, if the type information of the measurement results includes cell-level Layer 3 measurement results, the measurement control parameters configured for the first network device may include parameters for merging Layer 1 measurement results. As another example, if it is necessary to collect Layer 3 measurement results, the measurement control parameters configured for the first network device may need to include parameters for performing Layer 3 filtering.

[0146] The configuration information sent by the first network device has been described in detail above. The measurement-related data collected or reported by the terminal device will be described below.

[0147] Measurement-related data may include one or more of the following: measurement results, information about measurement events, timestamp information of measurement results, and timestamp information of measurement events.

[0148] The measurement results collected or reported by the terminal device can be related to the type information of the measurement results configured in the first network device. In other words, the terminal device can collect or report the types of measurement results configured in the first network device. As mentioned earlier, the type information of the measurement results configured in the first network device can include one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. Therefore, the measurement results collected or reported by the terminal device can include one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results.

[0149] As mentioned above, the type information of the measurement events configured in the first network device may include one or more of the following: Layer 1 measurement events, Layer 3 measurement events. Correspondingly, the information of the measurement events collected or reported by the terminal device may include one or more of the following: Layer 1 measurement events, Layer 3 measurement events, the identifier of the beam that triggered the Layer 1 measurement event, the measurement result corresponding to the beam that triggered the Layer 1 measurement event, the identifier of the cell that triggered the Layer 1 measurement event, the measurement result corresponding to the cell that triggered the Layer 1 measurement event, the identifier of the beam that triggered the Layer 3 measurement event, the measurement result corresponding to the beam that triggered the Layer 3 measurement event, the identifier of the cell that triggered the Layer 3 measurement event, and the measurement result corresponding to the cell that triggered the Layer 3 measurement event.

[0150] The timestamp information of the measurement results can be used to indicate the timestamp of the measurement results. As mentioned earlier, the frequency point information configured in the first network device can be used to indicate one or more frequency points. These multiple frequency points can, for example, be two frequency points. In the case of two frequency points, the measurement-related data can include the timestamp information of the measurement results corresponding to both frequency points. The timestamp information of the measurement results corresponding to the two frequency points can indicate the same timestamp.

[0151] Step S810 mentions that the terminal device can collect measurement-related data based on the configuration information sent by the first network device. After step S810, the communication method provided in this application embodiment may further include: the terminal device sending measurement-related data to the second network device.

[0152] In some implementations, the second network device can be the first network device. In this case, measurement-related data can be transmitted to the first network device via data radio bearers and / or signaling radio bearers. See Figure 9A for further explanation.

[0153] Figure 9A is a schematic flowchart of a communication method provided in another embodiment of this application. The communication method shown in Figure 9A includes steps S810 and S910a.

[0154] In step S810, the first network device sends configuration information to the terminal device. This configuration information is used by the terminal device to collect measurement-related data.

[0155] In step S910a, the terminal device transmits the collected measurement-related data to the first network device via a data wireless bearer.

[0156] In some implementations, the second network device can be a core network device. In this case, measurement-related data can be transmitted to the core network device via an Internet Protocol (IP) channel. See Figure 9B for further explanation.

[0157] Figure 9B is a schematic flowchart of a communication method provided in another embodiment of this application. The communication method shown in Figure 9B includes steps S810 and S910b.

[0158] In step S810, the first network device sends configuration information to the terminal device. This configuration information is used by the terminal device to collect measurement-related data.

[0159] In step S910b, the terminal device transmits the collected measurement-related data to the core network device via the IP channel.

[0160] In some implementations, the second network device can be a server that has established an application-layer channel with the terminal device. The terminal device can communicate with the server at the application layer. In this case, measurement-related data can be transmitted to the server through the application-layer channel. This server can be, for example, an OTT (over-the-top) server. See Figure 9C for further explanation.

[0161] Figure 9C is a schematic flowchart of a communication method provided in another embodiment of this application. The communication method shown in Figure 9C includes steps S810 and S910c. The server in Figure 9C is a server that has established an application layer channel with the terminal device.

[0162] In step S810, the first network device sends configuration information to the terminal device. This configuration information is used by the terminal device to collect measurement-related data.

[0163] In step S910c, the terminal device sends the collected measurement-related data to the server through the application layer channel.

[0164] In step S810, the configuration information sent by the first network device to the terminal device can be determined based on the first information.

[0165] As shown in Figure 10, before step S810, the communication method provided in this embodiment may further include step S1010: the terminal device sends first information to the first network device. This first information may be carried in a Data Collection Request message. This first information may be used to determine configuration information. Here, the configuration information is the configuration information sent by the first network device to the terminal device in step S810. That is, before the first network device sends configuration information to the terminal device, the terminal device may first send first information to the first network device to assist the first network device in determining the configuration information. The first network device can determine the configuration information based on the first information. The first information can also be called auxiliary information.

[0166] The first piece of information here may include one or more of the following: the type of measurement event, the type of measurement result, and the frequency point.

[0167] The measurement event type information included in the first information can be used to determine the measurement event type information included in the configuration information. The measurement event type information included in the first information can include one or more of the following: Layer 1 measurement event type information; Layer 3 measurement event type information. The Layer 1 measurement event type information here can be used to assist the terminal device in determining which Layer 1 measurement events(s) to configure in the configuration information. The Layer 3 measurement event type information here can be used to assist the terminal device in determining which Layer 3 measurement events(s) to configure in the configuration information. Layer 1 measurement events can include one or more of the following: LTM2 events, LTM3 events, LTM4 events, LTM5 events. Layer 3 measurement events can include one or more of the following: A1 events, A2 events, A3 events, A4 events, A5 events, A6 events.

[0168] The type information of the measurement results included in the first information can be used to determine the type information of the measurement results included in the configuration information. The type information of the measurement results included in the first information can be used to indicate one or more of the following: whether Layer 1 measurement results are required; whether Layer 3 measurement results are required; and whether the required measurement results are beam-level or cell-level measurement results. The first network device can determine the type information of the measurement results in the configuration information based on the type information of the measurement results included in the first information.

[0169] The frequency information included in the first information can be used to indicate one or more frequency points. For example, multiple frequency points can be two frequency points. When the frequency information included in the first information indicates one frequency point, that frequency point can be a serving frequency point or a non-serving frequency point. A serving frequency point can be understood as the frequency point where the terminal device's current serving cell is located. A non-serving frequency point can also be called a neighboring frequency point. When the frequency information included in the first information indicates two frequency points, these two frequency points can be used to predict measurement results between frequencies. One of these two frequency points can be a serving frequency point, and the other frequency point can be a frequency point that requires the configuration of additional measurement intervals. The first network device can determine the information of one or more frequency points in the configuration information based on the one or more frequency points indicated by the frequency information included in the first information. That is, the terminal device can recommend frequency points to the network device, and the first network device can configure frequency point information based on the frequency points recommended by the terminal device. For example, if the collection of measurement-related data is performed when the terminal device is in a radio resource control connected (RRC_CONNECTED) state, the terminal device can recommend the frequency points it is measuring to the first network device. The frequency being measured can be a serving frequency or a non-serving frequency, i.e., a neighboring frequency.

[0170] The frequency information included in the first information may include one or more of the following: frequency range information, frequency band information, and absolute radio frequency channel number (ARFCN) information. In some cases, the frequency information included in the first information may include frequency range information, which can be used to indicate one or more frequency ranges. Frequency ranges may include one or more of the following: frequency range 1 (FR1), frequency range 2 (FR2), frequency range 2-1 (FR2-1), and frequency range 2-2 (FR2-2). In other cases, the frequency information included in the first information may include frequency band information, which can be used to indicate one or more frequency bands. In still other cases, the frequency information included in the first information may include ARFCN information, which can be used to indicate one or more frequency points. Where the frequency information included in the first information includes ARFCN information, the frequency information included in the first information may also include subcarrier spacing information.

[0171] As mentioned earlier, the first network device can determine configuration information based on the first information sent by the terminal device. In some implementations, the terminal device can send the first information upon triggering by the second network device. In this case, the communication method provided in this application embodiment may further include: the terminal device receiving second information sent by the second network device. The second information may be carried in a DataCollectionTrigger message. The second network device may be a core network device. When the second network device is a core network device, the core network device can select a suitable terminal device based on the measurement-related data collection and / or reporting capabilities supported by the terminal device mentioned below. Alternatively, the second network device may also be a server that has established an application layer channel with the terminal device, such as an OTT server. The following description is in conjunction with Figure 11.

[0172] As shown in Figure 11, the communication method provided in this application embodiment may further include steps S1110, S1010, and S810.

[0173] In step S1110, the terminal device receives second information sent by the second network device. This second information is used to trigger the terminal device to send first information to the first network device.

[0174] In step S1010, the terminal device sends first information to the first network device upon being triggered by the second information. The first information is used by the first network device to determine configuration information.

[0175] In step S810, the first network device determines configuration information based on the received first information and sends the determined configuration information to the terminal device. After receiving the configuration information, the terminal device collects measurement-related data based on the configuration information.

[0176] The above describes how a terminal device sends first information when triggered by a second network device. In other implementations, the terminal device can directly obtain the first information from the second network and forward it to the first network device. In this case, before the terminal device sends the first information to the first network device, the communication method provided in this application embodiment may further include: the terminal device receiving the first information from the second network device. Here, the second network device can be a core network device. Alternatively, the second network device can also be a server that has established an application layer channel with the terminal device, such as an OTT server. The following description is in conjunction with Figure 12.

[0177] As shown in Figure 12, the communication method provided in this application embodiment may further include steps S1210, S1010, and S810.

[0178] In step S1210, the second network device sends first information to the terminal device. The first information is used by the first network device to determine configuration information.

[0179] In step S1010, the terminal device forwards the received first information to the first network device so that the first network device can determine the configuration information based on the first information.

[0180] In step S810, the first network device sends the determined configuration information to the terminal device so that the terminal device can collect and / or report measurement-related data according to the configuration information.

[0181] As mentioned earlier, in some implementations, the first network device can determine the configuration information based on the first information (auxiliary information) sent by the terminal device. In other implementations, the first network device can also determine the configuration information based on the capability information of the terminal device. For example, the first network device can determine one or more frequency points indicated by the frequency point information included in the configuration information based on the capability information of the terminal device.

[0182] In some embodiments, the terminal device's capability information can be sent from the terminal device to the first network device. The terminal device can send its own capability information to the first network device via uplink signaling.

[0183] In other embodiments, the terminal device's capability information can be sent from a second network device to a first network device. Here, the second network device is a core network device. The second network device may store the terminal device's capability information, and the first network device can download the terminal device's capability information stored by the second network device.

[0184] The capability information here may include one or more of the following: measurement prediction-related capability information supported by the terminal device; measurement-related data collection and / or reporting-related capability information supported by the terminal device; frequency bands or combinations of frequency bands supported by the terminal device; and measurement-related capability information supported by the terminal device. The first network device can determine the relevant information in the configuration information based on one or more of these capability information. For example, the first network device can determine one or more frequency points indicated by the frequency point information included in the configuration information based on one or more of the four types of capability information mentioned here. In this case, the frequency point information in the configuration information is configured by the first network device according to the capabilities of the terminal device.

[0185] Capability information related to measurement prediction can be used to indicate the measurement prediction-related capabilities supported by the terminal device. Capabilities related to measurement prediction may include one or more of the following: the ability to predict measurement results within a frequency range; the ability to predict measurement results between frequencies; the ability to predict measurement events within a frequency range; and the ability to predict measurement events between frequencies. For prediction of measurement results within a frequency range, the actual measurement result and the predicted measurement result correspond to the same frequency. This frequency can be the terminal device's current service frequency or non-service frequency. The ability to predict measurement results within a frequency range can be used to reduce measurement load or to predict measurement results within a future time window. Prediction for reducing measurement load can be performed in the time domain or the spatial domain. For prediction of measurement results between frequencies, the actual measurement result and the predicted measurement result correspond to different frequencies.

[0186] Accordingly, the capability information related to measurement prediction can be used to indicate that the terminal device supports one or more of the following: prediction of measurement results within a frequency range; prediction of measurement results between frequencies; prediction of measurement events within a frequency range; and prediction of measurement events between frequencies. The first network device can learn which measurement prediction capability the terminal device supports through the measurement prediction-related capability information, and thus configure the terminal device within the scope of its capabilities.

[0187] Capability information related to measurement-related data collection and / or reporting can be used to indicate that the terminal device has the ability to collect and / or report measurement-related data. The measurement-related data collected and / or reported by the terminal device can be used to train a model with the measurement prediction capabilities mentioned above. As mentioned above, the second network device may store capability information of the terminal device. In this case, the capability information related to measurement-related data collection and / or reporting can also be used by the second network device to select a suitable terminal device so that the second network device can send the second information mentioned above to the terminal device, thereby triggering the terminal device to send the first information (auxiliary information) mentioned above to the first network device.

[0188] As mentioned earlier, the configuration information sent by the first network device may include information about the measurement object, which may include frequency information. If the capability information sent by the terminal device or the second network device to the first network device includes frequency bands or combinations of frequency bands supported by the terminal device, the first network device can determine the frequency information included in the configuration information based on the frequency bands or combinations of frequency bands included in the capability information. The frequency bands or combinations of frequency bands supported by the terminal device can be considered as the wireless capability information of the terminal device.

[0189] The measurement-related capability information supported by the terminal device can also be regarded as the wireless capability information of the terminal device.

[0190] To facilitate understanding of the communication method provided in the embodiments of this application, the communication method provided in the embodiments of this application will be described in more detail below with reference to more specific examples.

[0191] Example 1

[0192] In Example 1, measurement-related data is used to train a model with time-domain measurement prediction capabilities. For this type of model, Example 1 specifies that the measurement-related data that the terminal device needs to report may include Layer 1 measurement results and / or Layer 3 measurement results. Accordingly, the configuration information of the network device (corresponding to the first network device mentioned above) may include information about the type of measurement-related data collected and / or reported by the terminal device, indicating whether the terminal device should report Layer 1 and / or Layer 3 measurement results.

[0193] For example, the relationship between the input measurement results and the output measurement results of a model with time-domain measurement prediction capabilities is shown in the table below:

[0194] For scenario 1, if the model's performance is evaluated based on the prediction accuracy of Layer 1 measurement results, then only Layer 1 measurement results are needed. If the model's performance is evaluated based on the prediction accuracy of Layer 3 measurement results, then Layer 3 measurement results are also required. For scenarios 2 and 3, Layer 3 measurement results are required, while Layer 1 measurement results are optional. In typical measurement tasks, existing specifications stipulate that the UE will generate Layer 3 measurement results, while Layer 1 measurement results are often only used as intermediate measurement results. In existing physical layer beam management and higher-layer supported LTM cell handover processes, the UE will also report Layer 1 measurement results according to the network device configuration. The UE will only report Layer 1 measurement results when the relevant Layer 1 measurement task is configured. For Layer 1 measurement tasks, Layer 3 measurement results are not required.

[0195] Network devices need to be configured to determine whether the collected data should include Layer 1 and / or Layer 3 measurement results. Layer 1 measurement results are measured and collected at the granularity of the reference signal. Generally, Layer 3 measurement results are essential for Layer 3 handover mechanisms. Layer 3 measurement results serve not only as input to the model but also as its label information. For LTM cell handover processes based on Layer 1 measurement results, the model's input, output, and label information are all Layer 1 measurement results; therefore, Layer 3 measurement results are optional.

[0196] Example 2

[0197] In Example 2, measurement-related data is used to train a model with spatial measurement prediction capabilities. For this type of model, Example 2 specifies that the measurement-related data that the terminal device needs to report may include Layer 1 measurement results and / or Layer 3 measurement results. Accordingly, the configuration information of the network device (corresponding to the first network device mentioned above) may include information about the type of measurement-related data collected and / or reported by the terminal device, indicating that the terminal device should report Layer 1 and / or Layer 3 measurement results.

[0198] For example, spatial measurement prediction can be understood as measuring a subset within the entire set of reference signals for the object being measured. The reference signal can be an SSB or a CSI-RS. The relationship between the input and output measurement results of a model with spatial measurement prediction capabilities is shown in the table below:

[0199] Network devices need to be configured to determine whether the collected data should include Layer 1 and / or Layer 3 measurement results. Layer 1 measurement results are measured and collected at the granularity of the reference signal. Generally, Layer 3 measurement results are essential for Layer 3 handover mechanisms. Layer 3 measurement results serve not only as input to the model but also as its labeling information. For LTM cell handover processes based on Layer 1 measurement results, the model's input, output, and labeling information are all Layer 1 measurement results; therefore, Layer 3 measurement results are optional.

[0200] Example 3

[0201] In Example 3, measurement-related data is used to train a model with measurement prediction capabilities in the frequency domain. For this type of model with measurement prediction capabilities, Example 3 specifies that the measurement-related data to be reported by the terminal device includes measurement results corresponding to multiple frequency points. Accordingly, the configuration information of the network device (corresponding to the first network device mentioned above) indicates the frequency point information of the measurement object, and this frequency point information can indicate multiple frequency points (e.g., two frequency points).

[0202] For example, the relationship between the input measurement results and the output measurement results of a model with measurement prediction capabilities in the frequency domain is shown in the table below:

[0203] In addition to the layer 1 measurement results or layer 3 measurement results mentioned in Examples 1 and 2, the network device needs to know the information of frequency point 1 and frequency point 2.

[0204] The method by which network devices obtain frequency point information can be referred to in Example 4 below. The difference between Example 3 and Example 4 is that in Example 3, the network device needs to know the information of two frequency points. Generally, frequency point 1 is the service frequency point, and frequency point 2 is the frequency point for which additional measurement intervals need to be configured according to the UE's measurement capabilities.

[0205] Example 4

[0206] Example 4 provides a specific example of the capability information of the terminal device mentioned above.

[0207] In Examples 1, 2, and 3, the network device needs to know on which frequency point the data collection measurement task should be configured. The network device can obtain frequency point information through the following methods:

[0208] Approach 1: Based on the UE capability that supports data collection, corresponding to the terminal device's capabilities related to measurement-related data collection and / or reporting mentioned above;

[0209] Approach 2: Based on the UE's capabilities that support measurement prediction, corresponding to the measurement prediction-related capability information supported by the terminal device mentioned above;

[0210] Approach 3: Based on the UE's supported frequency band information, the corresponding frequency bands or combinations of frequency bands supported by the terminal device mentioned above;

[0211] Method 4: The UE temporarily notifies the network device via an uplink signaling.

[0212] In Pathways 1, 2, and 3, the frequency information is actually configured by the network device based on the UE's capabilities. In Pathway 4, the frequency information is recommended by the UE. When recommending a frequency, if data collection is performed in the Radio Resource Control (RRC) connection in the RRC_CONNECTED state, the UE can recommend the frequency it is currently measuring. This frequency can be a serving frequency or a non-serving frequency, i.e., a neighboring frequency. A serving frequency can be understood as the frequency of the UE's current serving cell.

[0213] Example 5

[0214] In Embodiment 5, the UE has the ability to predict measurement events, and the UE predicts measurement events indirectly. That is, the UE first uses a model to predict the measurement result in a certain domain (time domain, spatial domain, or frequency domain), and then determines whether to trigger a measurement event based on existing rules and parameter configurations. For this type of measurement prediction function model, Embodiment 5 specifies that the terminal device needs to report measurement-related data including the information mentioned in Embodiments 1 to 3 and the type information of the measurement event. In addition, correspondingly, the configuration information of the network device (corresponding to the first network device mentioned above) indicates that in addition to including the configuration information mentioned in Embodiments 1 to 3, it also needs to include the type information of the measurement event.

[0215] For example, models that support this functionality generally exhibit generalization across different measurement event types. Different measurement event types may involve the serving cell and / or neighboring cells, serving frequency points and / or neighboring frequency points, as shown in the table below:

[0216] The network device is configured with the following information: information configured in Embodiment 1, Embodiment 2, Embodiment 3, and Embodiment 4; and type information of one or more measurement events.

[0217] Example 6

[0218] In Example 6, the UE has the ability to predict measurement events, and this prediction is done directly. That is, the UE directly predicts whether a measurement event will be triggered based on the actual input measurement results. Models supporting this function generally lack generalization ability across different measurement event types. This is because different training datasets are required for predicting different measurement events. Different measurement event types may involve the serving cell and / or neighboring cells, serving frequency points and / or neighboring frequency points, as detailed in the table in Example 5. The network device needs to configure the information configured in Example 5. Furthermore, if the measurement event type involves neighboring cells and the frequency point is a non-serving frequency point, the network device also needs to know the information about the non-serving frequency point. The network device can obtain the information about the non-serving frequency point through the methods listed in Example 4.

[0219] Example 7

[0220] After obtaining the relevant information, the network device needs to configure the UE to collect, store, and report data in a targeted manner. For Embodiments 1, 2, and 3, the network device needs to perform the following configurations (the configuration content mentioned below corresponds to the configuration information of the first network device mentioned above).

[0221] 1. Measurement tasks configured on the frequency point

[0222] This frequency point may be a serving frequency point or a non-serving frequency point. The information about this frequency point can be configured in an information unit describing the object being measured. Alternatively, the information about this frequency point can also be configured in a newly introduced information unit.

[0223] 2. Configure the details of the measurement results that the UE needs to collect.

[0224] The details of the measurement results that the UE needs to collect include one or more of the following:

[0225] a) Whether it is necessary to collect and report Layer 1 measurement results; whether the Layer 1 measurement results are beam-level or cell-level measurement results;

[0226] b) Whether it is necessary to collect and report Layer 3 measurement results; whether the Layer 3 measurement results are beam-level or cell-level measurement results;

[0227] c) Other standard configurations for data collection, such as the data collection cycle, data collection signal thresholds, and data reporting trigger conditions;

[0228] d) These parameters can be configured in a configuration data collection / reporting information unit.

[0229] i. This information unit is not an extension of the existing ReportConfigNR information unit, but a newly introduced information unit, abbreviated as DCRC.

[0230] ii. This information unit is an extension of the existing Report Configuration Information Unit (ReportConfigNR).

[0231] 3. Control information and measurement objects can be linked together using a single identifier.

[0232] a) This identifier can be extended on the existing MeasIdToAddMod cell.

[0233] b) This identifier can be a newly introduced associated information unit used to specify the data collection / reporting task; this identifier is called RRM_DC_ID.

[0234] Example 8

[0235] In Example 8, MO corresponds to the information of the measurement object mentioned above, and the reporting configuration corresponds to the control information mentioned above. measId or RRM_DC_ID corresponds to the association identifier mentioned above used to associate the measurement object and the control information together.

[0236] For Example 3, the network device performs the necessary configuration for the UE to collect data.

[0237] After obtaining the relevant information, the network device needs to configure information on two frequency points so that the UE can collect, store, and report data in a targeted manner.

[0238] The network device needs to be configured as follows:

[0239] 1. Refer to all configurations in Implementation Example 7;

[0240] 2. The network device needs to be configured for the UE to perform measurements on frequency point 1 and frequency point 2, and the measurements on these two frequency points need to be associated. The association method is shown in the table below: (Measurement object cell is abbreviated as MO, and collected / reported cell is abbreviated as DCRC)

[0241] In Method 1, the two frequency points actually share all information about the same measurement object, except for the frequency point information. In Method 1, the frequency point information also includes subcarrier information. Because they share the same ReportConfigNR, the measurement results on these two frequency points are collected, stored, and reported in the same way in subsequent processes.

[0242] Method 2 adopts a approach that has less impact on the protocol. It is also more flexible.

[0243] In Method 3, the measurement results at the two frequency points can be collected separately using different methods in subsequent processes.

[0244] Example 9

[0245] Example 9 provides several examples of the triggering conditions for the collection of the measurement-related data mentioned above.

[0246] The necessary configurations for network devices in Embodiments 5 and 6.

[0247] Once the network device receives relevant information (including the type of measurement event), it needs to configure the UE to collect, store, and report data in a targeted manner.

[0248] The network device is configured using the configuration method described in Example 7. That is, the network device is configured to allow the UE to collect and report Layer 1 measurement results or Layer 3 measurement results.

[0249] In addition, network devices can be configured as follows.

[0250] 1. Configure the triggering conditions for measurement events

[0251] The configuration method can refer to the method in Example 7. Existing event trigger configuration (EventTriggerConfig) information units can be reused or extended (this information unit can be in the existing ReportConfigNR or a newly defined DCRC). Alternatively, new information units can be defined. Multiple measurement event types can be configured in one ReportConfigNR or one DCRC.

[0252] 2. Configure UE to collect measurement event information

[0253] If the data is collected through an ongoing measurement task, then the measurement event itself will affect the UE's mobility behavior. If the data is collected by a separate measurement task, then the measurement event itself is a virtual event, meaning it will not affect the UE's mobility behavior.

[0254] In Examples 7, 8, and 9, if the existing ReportConfigNR is extended, there are mandatory information elements in EventTriggerConfig and PeriodicReportConfig that specify how the UE reports via the Uu interface. When the measurement task is set up solely for data collection purposes, the UE needs to ignore these mandatory information elements, which may increase the complexity of UE behavior.

[0255] Example 10

[0256] Example 10 provides a first signaling flow scheme. In Example 10, the information in the data collection trigger message that implements the trigger function corresponds to the second information mentioned above; the information in the data collection configuration message corresponds to the configuration information mentioned above; and the data in the recorded data reporting message corresponds to the measurement-related data mentioned above.

[0257] In Example 10, the UE may support measurement prediction or measurement event prediction, or it may not support either. Furthermore, the UE supports data collection functionality, which is confirmed at the application layer, meaning that the relevant UE capabilities do not need to be defined at the 3GPP level. Before the following procedure begins, the UE has established an RRC connection with the base station and an application layer dialogue with the server.

[0258] The server that communicates with the UE at the application layer is outside the scope of the communication system; that is, the application layer object is transparent to the cellular communication system. This server that communicates with the UE is generally an OTT server (over-the-top server). Referring to Figure 13, the signaling flow provided in Embodiment 10 includes the following steps S1310 to S1350.

[0259] In step S1310, the server selects a UE for data collection and sends a DataCollectionTrigger message to the UE at the application layer to trigger the UE to collect data.

[0260] In step S1320, the UE sends a Data Collection Request message to the base station, requesting the base station to configure appropriate parameters for data collection. In this case, the auxiliary information provided by the UE includes one or more of the following:

[0261] 1. Frequency information for measurement and data collection. Information representing the frequency point 1 (f1) of the measurement object may include subcarrier information.

[0262] 2. Information about the predicted frequency point. Information representing the frequency point 2 (f2) of the measurement object may include subcarrier information. (See Example 3)

[0263] 3. Measurement Event Information. Measurement events can be Layer 3 measurement events, such as A1-A6 events or LTM measurement events. If the measurement event type is A1, A2, LTM2, or other measurement events mentioned in related technologies, and it is an in-frequency measurement event (the serving cell and neighboring cells being compared are on the same frequency), and the purpose of the measurement is to reuse the current serving frequency, then the measurement object is the frequency where the PCell or SPCell is located. In this case, the f1 information is not needed (because the network device knows which frequency or frequencies are the serving frequency). If the measurement event type is A6, it indicates that the base station must at least configure carrier aggregation for the UE.

[0264] 4. Is it necessary to collect Layer 1 or Layer 3 measurement results? If it is necessary to collect Layer 3 measurement results, the base station needs to configure the relevant Layer 3 filtering parameters. For Layer 3 cell-level measurement results, consolidation parameters also need to be provided.

[0265] In step S1330, the base station configures measurement parameters for the UE according to the method provided in this application based on the received information, sends a Data Collection Configuration message to the UE, and notifies the UE that the purpose of the configured measurement task is at least to perform data collection.

[0266] In step S1340, the UE begins collecting and logging data according to the base station's configuration. The logged data includes at least Layer 1 measurement results and / or Layer 3 measurement results, measurement event information, timestamp information related to the measurement results, and timestamp information related to the measurement events.

[0267] In step S1350, the UE sends a LoggedDataReport message to the server, transmitting the collected data to the server through the application layer. The UE also needs to send the parameters configured for it by the base station to the server.

[0268] Example 11

[0269] Example 11 provides a second signaling flow scheme. In Example 11, the information in the data collection trigger message that implements the trigger function corresponds to the second information mentioned above; the information in the data collection configuration message corresponds to the configuration information mentioned above; and the data in the recorded data reporting message corresponds to the measurement-related data mentioned above.

[0270] In Embodiment 11, the UE may support measurement prediction or measurement event prediction, or it may not support either. Furthermore, the UE supports data collection and has reported its radio capabilities to the network device. These radio capabilities include supported radio frequency bands, measurement intervals, etc. Before the following procedure begins, an RRC connection is established between the UE and the base station, and an application layer dialogue is established between the UE and the server. Referring to Figure 14, the signaling flow provided in Embodiment 11 includes the following steps S1410 to S1470.

[0271] In step S1410, the server selects a UE for data collection and sends a DataCollectionTrigger message to the UE at the application layer to trigger the UE to collect data.

[0272] In step S1420, the UE sends a Data Collection Request message to the base station, requesting the base station to configure appropriate parameters for data collection. In this case, the auxiliary information provided by the UE includes information other than frequency point information as described in Embodiment 10.

[0273] In step S1430a, after receiving the data collection request message, the base station sends a UE radio capability trigger message to the server.

[0274] In step S1430b, the UE receives a UE Radio Capability message sent by the base station.

[0275] Through steps S1430a and S1430b, the base station downloads the radio capabilities already reported by the UE from the server. If the UE supports measurement prediction and / or measurement event prediction capabilities, then these capabilities are also included in the radio capabilities.

[0276] In step S1430c, the base station determines frequency point 1 and / or frequency point 2 from Embodiment 10 that can be configured for the UE based on its radio capabilities and / or the UE's support for measurement prediction and / or measurement event prediction capabilities. Other configuration details are as described in Embodiment 10. The base station sends the configuration information to the UE via a Data Collection Configuration message.

[0277] If the base station already knows the capabilities of the UE, then the handshake process described in steps S1430a and S1430b can be skipped.

[0278] In step S1440, the UE starts collecting and recording data according to the base station configuration. The collected and recorded data includes at least Layer 1 measurement results and / or Layer 3 measurement results, measurement event information, timestamp information related to the measurement results, and timestamp information related to the measurement events.

[0279] In step S1450, the UE sends a LoggedDataReport message to the server, transmitting the collected data to the server through the application layer. The UE also needs to send the parameters configured for it by the base station to the server.

[0280] Example 12

[0281] Example 12 provides a third signaling flow scheme.

[0282] The server in Example 12 is not an OTT server, but a core network server. The UE may or may not support measurement prediction or measurement event prediction. Furthermore, the UE supports data collection capabilities, and has already shared its supported data collection capabilities with the core network server. Before the following procedure begins, an RRC connection is established between the UE and the base station, and a non-access stratum (NAS) connection is established between the UE and the server. The signaling procedure provided in Example 12 includes the following steps.

[0283] In step 1, the core network server selects UEs based on the data collection capability information stored in the core network and sends a trigger message to the selected UEs.

[0284] In step 2, the UE sends a request message to the base station. The content of the request message is provided to the UE by the core network.

[0285] The intermediate steps are the same as those in Examples 10 and 11.

[0286] In step x, the UE sends the collected data to the core network through an IP channel. Before sending the data, the UE needs to initiate a regular IP channel establishment process, which can be established in an existing protocol data unit (PDU) session or in a different PDU session.

[0287] Example 13

[0288] Example 13 provides a fourth signaling flow scheme. The information in the data collection configuration message in Example 13 corresponds to the configuration information mentioned above; the data in the recorded data reporting message corresponds to the measurement-related data mentioned above.

[0289] The server in Example 13 is not an OTT server, but a core network server. The UE may or may not support measurement prediction or measurement event prediction. Furthermore, the UE supports data collection capabilities, and has already shared its supported data collection capabilities with the core network server. Before the following procedure begins, an RRC connection is established between the UE and the base station, and a non-access stratum (NAS) connection is established between the UE and the server. Referring to Figure 14, the signaling flow provided in Example 13 includes the following steps S1510 to S1540.

[0290] In step S1510, the core network server selects a UE based on the data collection capability information stored in the core network and sends a data collection trigger message to the UE's current serving base station. If the base station does not yet have the capability to download radio capabilities or measurement (measurement event) predictions, the server sends this information to the base station before sending the data collection trigger message. The data collection trigger message includes at least the auxiliary information provided by the UE in Embodiment 11.

[0291] In step S1520, the base station configures appropriate data collection parameters for the UE based on the auxiliary information provided in the data collection trigger message and the UE's capability information. The base station sends the data collection parameters to the UE via a data collection configuration message.

[0292] In step S1530, the UE collects and records data based on the received configuration information.

[0293] In step S1540, the UE sends the collected data and related configuration information to the server that initiated the data collection via a record data reporting message.

[0294] Example 14

[0295] In Example 14, the UE collects data in the idle / inactive state.

[0296] After leaving the RRC_CONNECTED state, the UE continues to collect or report data.

[0297] When a UE undergoes a state transition and the network releases the RRC connection, the UE retains its configuration. The UE continues to perform measurements and data collection as required by the configuration. When the UE returns to the RRC_CONNETED state, it reports the collected data to the server.

[0298] The communication method provided by the embodiments of this application has been described in detail above with reference to Figures 1 to 15. The communication device provided by the embodiments of this application will be described in detail below with reference to Figures 16 to 19.

[0299] Figure 16 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device 1600 shown in Figure 16 is a terminal device. The communication device 1600 includes a first receiving unit 1610. The first receiving unit 1610 is used to receive configuration information sent by a first network device, the configuration information being used to configure the terminal device to collect and / or report measurement-related data.

[0300] In some implementations, the configuration information includes one or more of the following: information about the measurement object; control information for controlling the collection and / or reporting of the measurement-related data; wherein the measurement object and the control information are associated.

[0301] In some implementations, the measurement object and the control information are associated, including: the measurement object and the control information are associated through an association identifier; or, the control information includes an identifier of the measurement object.

[0302] In some implementations, the information of the measurement object includes one or more of the following: frequency point information, which indicates one or more frequency points; and subcarrier information, which indicates the subcarrier spacing corresponding to the one or more frequency points.

[0303] In some implementations, the control information includes one or more of the following: type information of the measurement-related data; collection cycle of the measurement-related data; triggering conditions for collecting the measurement-related data; reporting cycle of the measurement-related data; triggering conditions for reporting the measurement-related data; and measurement control parameters.

[0304] In some implementations, the type information of the measurement-related data includes one or more of the following: type information of the measurement result, and type information of the measurement event.

[0305] In some implementations, the type information of the measurement results includes one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results.

[0306] In some implementations, the type information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event.

[0307] In some implementations, the measurement control parameters include one or more of the following: parameters for merging layer 1 measurement results, and parameters for performing layer 3 filtering.

[0308] In some implementations, one measurement object is associated with one control information; or, multiple measurement objects are associated with one control information.

[0309] In some implementations, the configuration information is used to configure the task of collecting and / or reporting the measurement-related data, and the association identifier is the identifier of the task of collecting and / or reporting the measurement-related data.

[0310] In some implementations, the task of collecting and / or reporting measurement-related data is associated with the measurement task, and the association identifier is the same as the identifier of the measurement task.

[0311] In some implementations, the measurement-related data includes one or more of the following: measurement results, information about measurement events, timestamp information of the measurement results, and timestamp information of the measurement events.

[0312] In some implementations, the measurement results include one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results.

[0313] In some implementations, the information of the measurement event includes one or more of the following: a Layer 1 measurement event, a Layer 3 measurement event, an identifier of the beam that triggered the Layer 1 measurement event, a measurement result corresponding to the beam that triggered the Layer 1 measurement event, an identifier of the cell that triggered the Layer 1 measurement event, a measurement result corresponding to the cell that triggered the Layer 1 measurement event, an identifier of the beam that triggered the Layer 3 measurement event, a measurement result corresponding to the beam that triggered the Layer 3 measurement event, an identifier of the cell that triggered the Layer 3 measurement event, and a measurement result corresponding to the cell that triggered the Layer 3 measurement event.

[0314] In some implementations, the device further includes: a first transmitting unit, configured to transmit the measurement-related data to a second network device, wherein the second network device is one of the following: the first network device; a core network device; or a server that has established an application layer channel with the terminal device.

[0315] In some implementations, the second network device is the first network device, and the measurement-related data is transmitted to the first network device via a data radio bearer and / or a signaling radio bearer; or, the second network device is the core network device, and the measurement-related data is transmitted to the core network device via an IP channel; or, the second network device is the server, and the measurement-related data is transmitted to the server via the application layer channel.

[0316] In some implementations, the device further includes a second sending unit, configured to send first information to the first network device, the first information being used to determine the configuration information.

[0317] In some implementations, the first information includes one or more of the following: type information of the measurement event, type information of the measurement result, and frequency point information.

[0318] In some implementations, the type information of the measurement event includes the type information of layer 1 measurement events and / or the type information of layer 3 measurement events.

[0319] In some implementations, the type information of the measurement results is used to indicate one or more of the following: whether layer 1 measurement results are required; whether layer 3 measurement results are required; and whether the required measurement results are beam-level or cell-level measurement results.

[0320] In some implementations, the frequency point information is used to indicate one or more frequency points.

[0321] In some implementations, the frequency point information includes one or more of the following: frequency range information, frequency band information, and ARFCN information.

[0322] In some implementations, the device further includes: a second receiving unit, configured to receive second information sent by a second network device, the second information being used to trigger the terminal device to send the first information to the first network device; wherein the second network device is a core network device or a server that has established an application layer channel with the terminal device.

[0323] In some implementations, the device further includes a third receiving unit, configured to receive the first information from a second network device, wherein the second network device is a core network device or a server that has established an application layer channel with the terminal device.

[0324] In some implementations, the configuration information is determined based on the capability information of the terminal device, which includes one or more of the following: measurement prediction-related capability information supported by the terminal device; measurement-related data collection and / or reporting-related capability information supported by the terminal device; frequency bands or combinations of frequency bands supported by the terminal device; and measurement-related capability information supported by the terminal device.

[0325] In some implementations, the capability information related to measurement prediction is used to indicate that the terminal device supports one or more of the following: prediction of measurement results within a frequency; prediction of measurement results between frequencies; prediction of measurement events within a frequency; and prediction of measurement events between frequencies.

[0326] In some implementations, the configuration information includes information about the measurement object, which includes frequency point information, and the capability information is used to determine the frequency point information.

[0327] In some implementations, the capability information is sent from the terminal device to the first network device; or, the capability information is sent from a second network device to the first network device, where the second network device is a core network device.

[0328] In some implementations, the configuration information is carried in an RRC reconfiguration message.

[0329] In some implementations, the configuration information is used by the terminal device to perform data collection and / or reporting tasks, but not by the terminal device to perform measurement tasks; or, the configuration information is used by the terminal device to perform data collection and / or reporting tasks, as well as measurement tasks.

[0330] In some implementations, the configuration information is not used by the terminal device to perform measurement tasks, and the terminal device ignores the configuration information related to the measurement task.

[0331] In some implementations, the measurement-related data is used to train a model with measurement prediction capabilities.

[0332] Figure 17 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device 1700 shown in Figure 17 is a network device. The communication device 1700 includes a first transmitting unit 1710. The first transmitting unit 1710 is used to send configuration information to a terminal device, the configuration information being used to configure the terminal device to collect and / or report measurement-related data.

[0333] In some implementations, the configuration information includes one or more of the following: information about the measurement object; control information for controlling the collection and / or reporting of the measurement-related data; wherein the measurement object and the control information are associated.

[0334] In some implementations, the measurement object and the control information are associated, including: the measurement object and the control information are associated through an association identifier; or, the control information includes an identifier of the measurement object.

[0335] In some implementations, the information of the measurement object includes one or more of the following: frequency point information, which indicates one or more frequency points; and subcarrier information, which indicates the subcarrier spacing corresponding to the one or more frequency points.

[0336] In some implementations, the control information includes one or more of the following: type information of the measurement-related data; collection cycle of the measurement-related data; triggering conditions for collecting the measurement-related data; reporting cycle of the measurement-related data; triggering conditions for reporting the measurement-related data; and measurement control parameters.

[0337] In some implementations, the type information of the measurement-related data includes one or more of the following: type information of the measurement result, and type information of the measurement event.

[0338] In some implementations, the type information of the measurement results includes one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results.

[0339] In some implementations, the type information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event.

[0340] In some implementations, the measurement control parameters include one or more of the following: parameters for merging layer 1 measurement results, and parameters for performing layer 3 filtering.

[0341] In some implementations, one measurement object is associated with one control information; or, multiple measurement objects are associated with one control information.

[0342] In some implementations, the configuration information is used to configure the task of collecting and / or reporting the measurement-related data, and the association identifier is the identifier of the task of collecting and / or reporting the measurement-related data.

[0343] In some implementations, the task of collecting and / or reporting measurement-related data is associated with the measurement task, and the association identifier is the same as the identifier of the measurement task.

[0344] In some implementations, the measurement-related data includes one or more of the following: measurement results, information about measurement events, timestamp information of the measurement results, and timestamp information of the measurement events.

[0345] In some implementations, the measurement results include one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results.

[0346] In some implementations, the information of the measurement event includes one or more of the following: a Layer 1 measurement event, a Layer 3 measurement event, an identifier of the beam that triggered the Layer 1 measurement event, a measurement result corresponding to the beam that triggered the Layer 1 measurement event, an identifier of the cell that triggered the Layer 1 measurement event, a measurement result corresponding to the cell that triggered the Layer 1 measurement event, an identifier of the beam that triggered the Layer 3 measurement event, a measurement result corresponding to the beam that triggered the Layer 3 measurement event, an identifier of the cell that triggered the Layer 3 measurement event, and a measurement result corresponding to the cell that triggered the Layer 3 measurement event.

[0347] In some implementations, the device further includes: a first receiving unit, configured to receive the measurement-related data sent by the terminal device.

[0348] In some implementations, the device further includes: a second receiving unit, configured to receive first information sent by the terminal device or a second network device, the first information being used to determine the configuration information; wherein the second network device is a core network device or a server that has established an application layer channel with the terminal device.

[0349] In some implementations, the first information includes one or more of the following: type information of the measurement event, type information of the measurement result, and frequency point information.

[0350] In some implementations, the type information of the measurement event includes the type information of layer 1 measurement events and / or the type information of layer 3 measurement events.

[0351] In some implementations, the type information of the measurement results is used to indicate one or more of the following: whether layer 1 measurement results are required; whether layer 3 measurement results are required; and whether the required measurement results are beam-level or cell-level measurement results.

[0352] In some implementations, the frequency point information is used to indicate one or more frequency points.

[0353] In some implementations, the frequency point information includes one or more of the following: frequency range information, frequency band information, and ARFCN information.

[0354] In some implementations, the configuration information is determined based on the capability information of the terminal device, which includes one or more of the following: measurement prediction-related capability information supported by the terminal device; measurement-related data collection and / or reporting-related capability information supported by the terminal device; frequency bands or combinations of frequency bands supported by the terminal device; and measurement-related capability information supported by the terminal device.

[0355] In some implementations, the capability information related to measurement prediction is used to indicate that the terminal device supports one or more of the following: prediction of measurement results within a frequency; prediction of measurement results between frequencies; prediction of measurement events within a frequency; and prediction of measurement events between frequencies.

[0356] In some implementations, the configuration information includes information about the measurement object, which includes frequency point information, and the capability information is used to determine the frequency point information.

[0357] In some implementations, the capability information is sent from the terminal device to the first network device; or, the capability information is sent from a second network device to the first network device, where the second network device is a core network device.

[0358] In some implementations, the configuration information is carried in an RRC reconfiguration message.

[0359] In some implementations, the configuration information is used by the terminal device to perform data collection and / or reporting tasks, but not by the terminal device to perform measurement tasks; or, the configuration information is used by the terminal device to perform data collection and / or reporting tasks, as well as measurement tasks.

[0360] In some implementations, the configuration information is not used by the terminal device to perform measurement tasks, and the terminal device ignores the configuration information related to the measurement task.

[0361] In some implementations, the measurement-related data is used to train a model with measurement prediction capabilities.

[0362] Figure 18 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device 1800 shown in Figure 18 is a second network device. The communication device 1800 includes a first receiving unit 1810. The first receiving unit 1810 is used to receive measurement-related data sent by a terminal device.

[0363] In some implementations, the measurement-related data includes one or more of the following: measurement results, information about measurement events, timestamp information of the measurement results, and timestamp information of the measurement events.

[0364] In some implementations, the measurement results include one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results.

[0365] In some implementations, the information of the measurement event includes one or more of the following: a Layer 1 measurement event, a Layer 3 measurement event, an identifier of the beam that triggered the Layer 1 measurement event, a measurement result corresponding to the beam that triggered the Layer 1 measurement event, an identifier of the cell that triggered the Layer 1 measurement event, a measurement result corresponding to the cell that triggered the Layer 1 measurement event, an identifier of the beam that triggered the Layer 3 measurement event, a measurement result corresponding to the beam that triggered the Layer 3 measurement event, an identifier of the cell that triggered the Layer 3 measurement event, and a measurement result corresponding to the cell that triggered the Layer 3 measurement event.

[0366] In some implementations, the device further includes: a first sending unit, configured to send second information to the terminal device, the second information being used to trigger the terminal device to send first information to the first network device, the first information being used to determine configuration information.

[0367] In some implementations, the configuration information includes one or more of the following: information about the measurement object; control information for controlling the collection and / or reporting of the measurement-related data; wherein the measurement object and the control information are associated.

[0368] In some implementations, the measurement object and the control information are associated, including: the measurement object and the control information are associated through an association identifier; or, the control information includes an identifier of the measurement object.

[0369] In some implementations, the information of the measurement object includes one or more of the following: frequency point information, which indicates one or more frequency points; and subcarrier information, which indicates the subcarrier spacing corresponding to the one or more frequency points.

[0370] In some implementations, the control information includes one or more of the following: type information of the measurement-related data; collection cycle of the measurement-related data; triggering conditions for collecting the measurement-related data; reporting cycle of the measurement-related data; triggering conditions for reporting the measurement-related data; and measurement control parameters.

[0371] In some implementations, the type information of the measurement-related data includes one or more of the following: type information of the measurement result, and type information of the measurement event.

[0372] In some implementations, the type information of the measurement results includes one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results.

[0373] In some implementations, the type information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event.

[0374] In some implementations, the measurement control parameters include one or more of the following: parameters for merging layer 1 measurement results, and parameters for performing layer 3 filtering.

[0375] In some implementations, one measurement object is associated with one control information; or, multiple measurement objects are associated with one control information.

[0376] In some implementations, the configuration information is used to configure the task of collecting and / or reporting the measurement-related data, and the association identifier is the identifier of the task of collecting and / or reporting the measurement-related data.

[0377] In some implementations, the task of collecting and / or reporting measurement-related data is associated with the measurement task, and the association identifier is the same as the identifier of the measurement task.

[0378] In some implementations, the configuration information is determined based on the capability information of the terminal device, which includes one or more of the following: measurement prediction-related capability information supported by the terminal device; measurement-related data collection and / or reporting-related capability information supported by the terminal device; frequency bands or combinations of frequency bands supported by the terminal device; and measurement-related capability information supported by the terminal device.

[0379] In some implementations, the capability information related to measurement prediction is used to indicate that the terminal device supports one or more of the following: prediction of measurement results within a frequency; prediction of measurement results between frequencies; prediction of measurement events within a frequency; and prediction of measurement events between frequencies.

[0380] In some implementations, the configuration information includes information about the measurement object, which includes frequency point information, and the capability information is used to determine the frequency point information.

[0381] In some implementations, the capability information is sent from the second network device to the first network device.

[0382] In some implementations, the configuration information is carried in an RRC reconfiguration message.

[0383] In some implementations, the configuration information is used by the terminal device to perform data collection and / or reporting tasks, but not by the terminal device to perform measurement tasks; or, the configuration information is used by the terminal device to perform data collection and / or reporting tasks, as well as measurement tasks.

[0384] In some implementations, the configuration information is not used by the terminal device to perform measurement tasks, and the terminal device ignores the configuration information related to the measurement task.

[0385] In some implementations, the first information includes one or more of the following: type information of the measurement event, type information of the measurement result, and frequency point information.

[0386] In some implementations, the type information of the measurement event includes the type information of layer 1 measurement events and / or the type information of layer 3 measurement events.

[0387] In some implementations, the type information of the measurement results is used to indicate one or more of the following: whether layer 1 measurement results are required; whether layer 3 measurement results are required; and whether the required measurement results are beam-level or cell-level measurement results.

[0388] In some implementations, the frequency point information is used to indicate one or more frequency points.

[0389] In some implementations, the frequency point information includes one or more of the following: frequency range information, frequency band information, and ARFCN information.

[0390] In some implementations, the device further includes a second sending unit for sending the first information to the terminal device.

[0391] In some implementations, the second network device is a core network device or a server that establishes an application layer channel with the terminal device.

[0392] In some implementations, the second network device is the core network device, and the measurement-related data is transmitted to the core network device via an IP channel; or, the second network device is the server, and the measurement-related data is transmitted to the server via the application layer channel.

[0393] In some implementations, the measurement-related data is used to train a model with measurement prediction capabilities.

[0394] Figure 19 is a schematic structural diagram of a communication device applicable to embodiments of this application. The dashed lines in Figure 19 indicate that the unit or module is optional. This device 1900 can be used to implement the methods described in the above method embodiments. Device 1900 can be a chip, a terminal device, or a network device.

[0395] Apparatus 1900 may include one or more processors 1910. The processor 1910 may support apparatus 1900 in implementing the methods described in the preceding method embodiments. The processor 1910 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0396] The apparatus 1900 may further include one or more memories 1920. The memories 1920 store a program that can be executed by the processor 1910, causing the processor 1910 to perform the methods described in the preceding method embodiments. The memories 1920 may be independent of the processor 1910 or integrated within the processor 1910.

[0397] The device 1900 may also include a transceiver 1930. The processor 1910 can communicate with other devices or chips via the transceiver 1930. For example, the processor 1910 can send and receive data with other devices or chips via the transceiver 1930.

[0398] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to the communication device provided in this application, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0399] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in this application embodiment, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0400] This application also provides a computer program. This computer program can be applied to the communication device provided in this application, and causes the computer to execute the methods performed by the communication device in various embodiments of this application.

[0401] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0402] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0403] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0404] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0405] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0406] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0407] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0408] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0409] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0410] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0411] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0412] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0413] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

A communication method, characterized in that, include: The terminal device receives configuration information sent by the first network device, the configuration information being used to configure the terminal device to collect and / or report measurement-related data. The method according to claim 1, characterized in that, The configuration information includes one or more of the following: Information about the object being measured; Control information, used to control the collection and / or reporting of the measurement-related data; The measurement object and the control information are associated. The method according to claim 2, characterized in that, The association between the measurement object and the control information includes: The measurement object and the control information are associated through an association identifier; or... The control information includes the identifier of the object being measured. The method according to claim 2 or 3, characterized in that, The information of the object being measured includes one or more of the following: Frequency point information, wherein the frequency point information is used to indicate one or more frequency points; Subcarrier information is used to indicate the subcarrier spacing corresponding to the one or more frequency points. The method according to any one of claims 2 to 4, characterized in that, The control information includes one or more of the following: The type information of the measurement-related data; The collection cycle of the measurement-related data; The triggering conditions for collecting the measurement-related data; The reporting cycle for the measurement-related data; The triggering conditions for reporting the measurement-related data; Measure control parameters. The method according to claim 5, characterized in that, The type information of the measurement-related data includes one or more of the following: type information of measurement results, type information of measurement events. The method according to claim 6, characterized in that, The type information of the measurement results includes one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. The method according to claim 6 or 7, characterized in that, The type information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event. The method according to any one of claims 5 to 8, characterized in that, The measurement control parameters include one or more of the following: parameters for merging layer 1 measurement results, and parameters for performing layer 3 filtering. The method according to any one of claims 2 to 9, characterized in that: One of the measurement objects is associated with one of the control information; or, Multiple measurement objects are associated with one control information. The method according to any one of claims 2 to 10, characterized in that, The configuration information is used to configure the task of collecting and / or reporting the measurement-related data, and the association identifier is the identifier of the task of collecting and / or reporting the measurement-related data. The method according to claim 11, characterized in that, The task of collecting and / or reporting measurement-related data is associated with the measurement task, and the association identifier is the same as the identifier of the measurement task. The method according to any one of claims 1 to 12, characterized in that, The measurement-related data includes one or more of the following: measurement results, information about measurement events, timestamp information of the measurement results, and timestamp information of the measurement events. The method according to claim 13, characterized in that, The measurement results include one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. The method according to claim 13 or 14 is characterized in that, The information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event, identifier of the beam that triggered the Layer 1 measurement event, measurement result corresponding to the beam that triggered the Layer 1 measurement event, identifier of the cell that triggered the Layer 1 measurement event, measurement result corresponding to the cell that triggered the Layer 1 measurement event, identifier of the beam that triggered the Layer 3 measurement event, measurement result corresponding to the beam that triggered the Layer 3 measurement event, identifier of the cell that triggered the Layer 3 measurement event, and measurement result corresponding to the cell that triggered the Layer 3 measurement event. The method according to any one of claims 1 to 15, characterized in that, The method further includes: The terminal device sends the measurement-related data to a second network device, wherein the second network device is one of the following: The first network device; Core network equipment; A server that has established an application layer channel with the terminal device. The method according to claim 16, characterized in that: The second network device is the first network device, and the measurement-related data is transmitted to the first network device via a data radio bearer and / or a signaling radio bearer; or, The second network device is the core network device, and the measurement-related data is transmitted to the core network device via the Internet Protocol (IP) channel; or, The second network device is the server, and the measurement-related data is transmitted to the server through the application layer channel. The method according to any one of claims 1 to 17, characterized in that, The method further includes: The terminal device sends first information to the first network device, the first information being used to determine the configuration information. The method according to claim 18, characterized in that, The first information includes one or more of the following: measurement event type information, measurement result type information, and frequency point information. The method according to claim 19, characterized in that, The type information of the measurement event includes the type information of layer 1 measurement events and / or the type information of layer 3 measurement events. The method according to claim 19 or 20 is characterized in that, The type information of the measurement result is used to indicate one or more of the following: Do we need the layer 1 measurement results? Do we need the layer 3 measurement results? The required measurement results are beam-level or cell-level measurements. The method according to any one of claims 19 to 21 is characterized in that, The frequency point information is used to indicate one or more frequency points. The method according to any one of claims 19 to 22 is characterized in that, The frequency point information includes one or more of the following: frequency range information, frequency band information, and absolute radio frequency channel number (ARFCN) information. The method according to any one of claims 18 to 23 is characterized in that, The method further includes: The terminal device receives second information sent by the second network device, and the second information is used to trigger the terminal device to send the first information to the first network device. The second network device is either a core network device or a server that has established an application layer channel with the terminal device. The method according to any one of claims 18 to 24, characterized in that, The method further includes: Before sending the first information to the first network device, the terminal device receives the first information from a second network device, which is either a core network device or a server that has established an application layer channel with the terminal device. The method according to any one of claims 1 to 25, characterized in that, The configuration information is determined based on the capability information of the terminal device, and the capability information includes one or more of the following: The terminal device supports measurement prediction-related capability information; The terminal device supports capabilities related to the collection and / or reporting of measurement-related data. The terminal device supports frequency bands or combinations of frequency bands; The terminal device supports measurement-related capability information. The method according to claim 26, characterized in that, The capability information related to measurement prediction is used to indicate that the terminal device supports one or more of the following: Prediction of measurement results within the frequency range; Prediction of measurement results between frequencies; Prediction of measurement events within a frequency range; Prediction of measurement events between frequencies. The method according to claim 26 or 27 is characterized in that, The configuration information includes information about the measurement object, which includes frequency information. The capability information is used to determine the frequency information. The method according to any one of claims 26 to 28, characterized in that: The capability information is sent from the terminal device to the first network device; or... The capability information is sent from the second network device to the first network device, where the second network device is a core network device. The method according to any one of claims 1 to 29, characterized in that, The configuration information is carried in the Radio Resource Control (RRC) reconfiguration message. The method according to any one of claims 1 to 30, characterized in that: The configuration information is used by the terminal device to perform data collection and / or reporting tasks, but not for the terminal device to perform measurement tasks; or... The configuration information is used by the terminal device to perform data collection and / or reporting tasks, as well as measurement tasks. The method according to claim 31, characterized in that, The configuration information is not used by the terminal device to perform measurement tasks, and the terminal device ignores the configuration information related to the measurement task. The method according to any one of claims 1 to 32, characterized in that, The measurement-related data is used to train a model with measurement prediction capabilities. A communication method, characterized in that, include: The first network device sends configuration information to the terminal device, the configuration information being used to configure the terminal device to collect and / or report measurement-related data. The method according to claim 34, characterized in that, The configuration information includes one or more of the following: Information about the object being measured; Control information, used to control the collection and / or reporting of the measurement-related data; The measurement object and the control information are associated. The method according to claim 35, characterized in that, The association between the measurement object and the control information includes: The measurement object and the control information are associated through an association identifier; or... The control information includes the identifier of the object being measured. The method according to claim 35 or 36 is characterized in that, The information of the object being measured includes one or more of the following: Frequency point information, wherein the frequency point information is used to indicate one or more frequency points; Subcarrier information is used to indicate the subcarrier spacing corresponding to the one or more frequency points. The method according to any one of claims 35 to 37, characterized in that, The control information includes one or more of the following: The type information of the measurement-related data; The collection cycle of the measurement-related data; The triggering conditions for collecting the measurement-related data; The reporting cycle for the measurement-related data; The triggering conditions for reporting the measurement-related data; Measure control parameters. The method according to claim 38, characterized in that, The type information of the measurement-related data includes one or more of the following: type information of measurement results, type information of measurement events. The method according to claim 39, characterized in that, The type information of the measurement results includes one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. The method according to claim 39 or 40 is characterized in that, The type information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event. The method according to any one of claims 38 to 41, characterized in that, The measurement control parameters include one or more of the following: parameters for merging layer 1 measurement results, and parameters for performing layer 3 filtering. The method according to any one of claims 35 to 42 is characterized in that: One of the measurement objects is associated with one of the control information; or, Multiple measurement objects are associated with one control information. The method according to any one of claims 35 to 43 is characterized in that, The configuration information is used to configure the task of collecting and / or reporting the measurement-related data, and the association identifier is the identifier of the task of collecting and / or reporting the measurement-related data. The method according to claim 44, characterized in that, The task of collecting and / or reporting measurement-related data is associated with the measurement task, and the association identifier is the same as the identifier of the measurement task. The method according to any one of claims 34 to 45, characterized in that, The measurement-related data includes one or more of the following: measurement results, information about measurement events, timestamp information of the measurement results, and timestamp information of the measurement events. The method according to claim 46, characterized in that, The measurement results include one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. The method according to claim 46 or 47 is characterized in that, The information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event, identifier of the beam that triggered the Layer 1 measurement event, measurement result corresponding to the beam that triggered the Layer 1 measurement event, identifier of the cell that triggered the Layer 1 measurement event, measurement result corresponding to the cell that triggered the Layer 1 measurement event, identifier of the beam that triggered the Layer 3 measurement event, measurement result corresponding to the beam that triggered the Layer 3 measurement event, identifier of the cell that triggered the Layer 3 measurement event, and measurement result corresponding to the cell that triggered the Layer 3 measurement event. The method according to any one of claims 34 to 48, characterized in that, The method further includes: The first network device receives the measurement-related data sent by the terminal device. The method according to any one of claims 34 to 49, characterized in that, The method further includes: The first network device receives first information sent by the terminal device or the second network device, the first information being used to determine the configuration information; The second network device is either a core network device or a server that has established an application layer channel with the terminal device. The method according to claim 50, characterized in that, The first information includes one or more of the following: measurement event type information, measurement result type information, and frequency point information. The method according to claim 51, characterized in that, The type information of the measurement event includes the type information of layer 1 measurement events and / or the type information of layer 3 measurement events. The method according to claim 51 or 52 is characterized in that, The type information of the measurement result is used to indicate one or more of the following: Do we need the layer 1 measurement results? Do we need the layer 3 measurement results? The required measurement results are beam-level or cell-level measurements. The method according to any one of claims 51 to 53 is characterized in that, The frequency point information is used to indicate one or more frequency points. The method according to any one of claims 51 to 54 is characterized in that, The frequency point information includes one or more of the following: frequency range information, frequency band information, and absolute radio frequency channel number (ARFCN) information. The method according to any one of claims 34 to 55, characterized in that, The configuration information is determined based on the capability information of the terminal device, and the capability information includes one or more of the following: The terminal device supports measurement prediction-related capability information; The terminal device supports capabilities related to the collection and / or reporting of measurement-related data. The terminal device supports frequency bands or combinations of frequency bands; The terminal device supports measurement-related capability information. The method according to claim 56, characterized in that, The capability information related to measurement prediction is used to indicate that the terminal device supports one or more of the following: Prediction of measurement results within the frequency range; Prediction of measurement results between frequencies; Prediction of measurement events within a frequency range; Prediction of measurement events between frequencies. The method according to claim 56 or 57 is characterized in that, The configuration information includes information about the measurement object, which includes frequency information. The capability information is used to determine the frequency information. The method according to any one of claims 56 to 58 is characterized in that: The capability information is sent from the terminal device to the first network device; or... The capability information is sent from the second network device to the first network device, where the second network device is a core network device. The method according to any one of claims 34 to 59 is characterized in that, The configuration information is carried in the Radio Resource Control (RRC) reconfiguration message. The method according to any one of claims 34 to 60, characterized in that: The configuration information is used by the terminal device to perform data collection and / or reporting tasks, but not for the terminal device to perform measurement tasks; or... The configuration information is used by the terminal device to perform data collection and / or reporting tasks, as well as measurement tasks. The method according to claim 61, characterized in that, The configuration information is not used by the terminal device to perform measurement tasks, and the terminal device ignores the configuration information related to the measurement task. The method according to any one of claims 34 to 62, characterized in that, The measurement-related data is used to train a model with measurement prediction capabilities. A communication method, characterized in that, include: The second network device receives measurement-related data sent by the terminal device. The method according to claim 63, characterized in that, The measurement-related data includes one or more of the following: measurement results, information about measurement events, timestamp information of the measurement results, and timestamp information of the measurement events. The method according to claim 65, characterized in that, The measurement results include one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. The method according to claim 65 or 66 is characterized in that, The information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event, identifier of the beam that triggered the Layer 1 measurement event, measurement result corresponding to the beam that triggered the Layer 1 measurement event, identifier of the cell that triggered the Layer 1 measurement event, measurement result corresponding to the cell that triggered the Layer 1 measurement event, identifier of the beam that triggered the Layer 3 measurement event, measurement result corresponding to the beam that triggered the Layer 3 measurement event, identifier of the cell that triggered the Layer 3 measurement event, and measurement result corresponding to the cell that triggered the Layer 3 measurement event. The method according to any one of claims 64 to 67, characterized in that, The method further includes: The second network device sends second information to the terminal device, the second information being used to trigger the terminal device to send first information to the first network device, the first information being used to determine configuration information. The method according to claim 68, characterized in that, The configuration information includes one or more of the following: Information about the object being measured; Control information, used to control the collection and / or reporting of the measurement-related data; The measurement object and the control information are associated. The method according to claim 69, characterized in that, The association between the measurement object and the control information includes: The measurement object and the control information are associated through an association identifier; or... The control information includes the identifier of the object being measured. The method according to claim 69 or 70 is characterized in that, The information of the object being measured includes one or more of the following: Frequency point information, wherein the frequency point information is used to indicate one or more frequency points; Subcarrier information is used to indicate the subcarrier spacing corresponding to the one or more frequency points. The method according to any one of claims 69 to 71, characterized in that, The control information includes one or more of the following: The type information of the measurement-related data; The collection cycle of the measurement-related data; The triggering conditions for collecting the measurement-related data; The reporting cycle for the measurement-related data; The triggering conditions for reporting the measurement-related data; Measure control parameters. The method according to claim 72, characterized in that, The type information of the measurement-related data includes one or more of the following: type information of measurement results, type information of measurement events. The method according to claim 73, characterized in that, The type information of the measurement results includes one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. The method according to claim 73 or 74 is characterized in that, The type information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event. The method according to any one of claims 72 to 75, characterized in that, The measurement control parameters include one or more of the following: parameters for merging layer 1 measurement results, and parameters for performing layer 3 filtering. The method according to any one of claims 69 to 76, characterized in that: One of the measurement objects is associated with one of the control information; or, Multiple measurement objects are associated with one control information. The method according to any one of claims 70 to 77, characterized in that, The configuration information is used to configure the task of collecting and / or reporting the measurement-related data, and the association identifier is the identifier of the task of collecting and / or reporting the measurement-related data. The method according to claim 78, characterized in that, The task of collecting and / or reporting measurement-related data is associated with the measurement task, and the association identifier is the same as the identifier of the measurement task. The method according to any one of claims 68 to 79, characterized in that, The configuration information is determined based on the capability information of the terminal device, and the capability information includes one or more of the following: The terminal device supports measurement prediction-related capability information; The terminal device supports capabilities related to the collection and / or reporting of measurement-related data. The terminal device supports frequency bands or combinations of frequency bands; The terminal device supports measurement-related capability information. The method according to claim 80, characterized in that, The capability information related to measurement prediction is used to indicate that the terminal device supports one or more of the following: Prediction of measurement results within the frequency range; Prediction of measurement results between frequencies; Prediction of measurement events within a frequency range; Prediction of measurement events between frequencies. The method according to claim 80 or 81, characterized in that, The configuration information includes information about the measurement object, which includes frequency information. The capability information is used to determine the frequency information. The method according to any one of claims 80 to 82, characterized in that, The capability information is sent from the second network device to the first network device. The method according to any one of claims 68 to 83, characterized in that, The configuration information is carried in the Radio Resource Control (RRC) reconfiguration message. The method according to any one of claims 68 to 84, characterized in that: The configuration information is used by the terminal device to perform data collection and / or reporting tasks, but not for the terminal device to perform measurement tasks; or... The configuration information is used by the terminal device to perform data collection and / or reporting tasks, as well as measurement tasks. The method according to claim 85, characterized in that, The configuration information is not used by the terminal device to perform measurement tasks, and the terminal device ignores the configuration information related to the measurement task. The method according to any one of claims 68 to 86, characterized in that, The first information includes one or more of the following: measurement event type information, measurement result type information, and frequency point information. The method according to claim 87, characterized in that, The type information of the measurement event includes the type information of layer 1 measurement events and / or the type information of layer 3 measurement events. The method according to claim 87 or 88 is characterized in that, The type information of the measurement result is used to indicate one or more of the following: Do we need the layer 1 measurement results? Do we need the layer 3 measurement results? The required measurement results are beam-level or cell-level measurements. The method according to any one of claims 87 to 89, characterized in that, The frequency point information is used to indicate one or more frequency points. The method according to any one of claims 87 to 90, characterized in that, The frequency point information includes one or more of the following: frequency range information, frequency band information, and absolute radio frequency channel number (ARFCN) information. The method according to any one of claims 68 to 91, characterized in that, The method further includes: The second network device sends the first information to the terminal device. The method according to any one of claims 64 to 92 is characterized in that, The second network device is a core network device or a server that establishes an application layer channel with the terminal device. The method according to claim 93 is characterized in that: The second network device is the core network device, and the measurement-related data is transmitted to the core network device via the Internet Protocol (IP) channel; or, The second network device is the server, and the measurement-related data is transmitted to the server through the application layer channel. The method according to any one of claims 64 to 94, characterized in that, The measurement-related data is used to train a model with measurement prediction capabilities. A communication device, characterized in that, The communication device is a terminal device, and the device includes: The first receiving unit is configured to receive configuration information sent by the first network device, wherein the configuration information is configured to allow the terminal device to collect and / or report measurement-related data. The device according to claim 96 is characterized in that, The configuration information includes one or more of the following: Information about the object being measured; Control information, used to control the collection and / or reporting of the measurement-related data; The measurement object and the control information are associated. The device according to claim 97 is characterized in that, The association between the measurement object and the control information includes: The measurement object and the control information are associated through an association identifier; or... The control information includes the identifier of the object being measured. The device according to claim 97 or 98 is characterized in that, The information of the object being measured includes one or more of the following: Frequency point information, wherein the frequency point information is used to indicate one or more frequency points; Subcarrier information is used to indicate the subcarrier spacing corresponding to the one or more frequency points. The device according to any one of claims 97 to 99, characterized in that, The control information includes one or more of the following: The type information of the measurement-related data; The collection cycle of the measurement-related data; The triggering conditions for collecting the measurement-related data; The reporting cycle for the measurement-related data; The triggering conditions for reporting the measurement-related data; Measure control parameters. The device according to claim 100 is characterized in that, The type information of the measurement-related data includes one or more of the following: type information of measurement results, type information of measurement events. The device according to claim 101 is characterized in that, The type information of the measurement results includes one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. The device according to claim 101 or 102 is characterized in that, The type information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event. The device according to any one of claims 100 to 103 is characterized in that, The measurement control parameters include one or more of the following: parameters for merging layer 1 measurement results, and parameters for performing layer 3 filtering. The device according to any one of claims 97 to 104, characterized in that: One of the measurement objects is associated with one of the control information; or, Multiple measurement objects are associated with one control information. The device according to any one of claims 97 to 105, characterized in that, The configuration information is used to configure the task of collecting and / or reporting the measurement-related data, and the association identifier is the identifier of the task of collecting and / or reporting the measurement-related data. The device according to claim 106 is characterized in that, The task of collecting and / or reporting measurement-related data is associated with the measurement task, and the association identifier is the same as the identifier of the measurement task. The device according to any one of claims 96 to 107 is characterized in that, The measurement-related data includes one or more of the following: measurement results, information about measurement events, timestamp information of the measurement results, and timestamp information of the measurement events. The device according to claim 108 is characterized in that, The measurement results include one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. The device according to claim 108 or 109 is characterized in that, The information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event, identifier of the beam that triggered the Layer 1 measurement event, measurement result corresponding to the beam that triggered the Layer 1 measurement event, identifier of the cell that triggered the Layer 1 measurement event, measurement result corresponding to the cell that triggered the Layer 1 measurement event, identifier of the beam that triggered the Layer 3 measurement event, measurement result corresponding to the beam that triggered the Layer 3 measurement event, identifier of the cell that triggered the Layer 3 measurement event, and measurement result corresponding to the cell that triggered the Layer 3 measurement event. The device according to any one of claims 96 to 110, characterized in that, The device also includes: The first transmitting unit is configured to transmit the measurement-related data to the second network device, wherein the second network device is one of the following: The first network device; Core network equipment; A server that has established an application layer channel with the terminal device. The device according to claim 111, characterized in that: The second network device is the first network device, and the measurement-related data is transmitted to the first network device via a data radio bearer and / or a signaling radio bearer; or, The second network device is the core network device, and the measurement-related data is transmitted to the core network device via the Internet Protocol (IP) channel; or, The second network device is the server, and the measurement-related data is transmitted to the server through the application layer channel. The device according to any one of claims 96 to 112, characterized in that, The device also includes: The second sending unit is configured to send first information to the first network device, wherein the first information is used to determine the configuration information. The device according to claim 113 is characterized in that, The first information includes one or more of the following: measurement event type information, measurement result type information, and frequency point information. The device according to claim 114 is characterized in that, The type information of the measurement event includes the type information of layer 1 measurement events and / or the type information of layer 3 measurement events. The device according to claim 114 or 115 is characterized in that, The type information of the measurement result is used to indicate one or more of the following: Do we need the layer 1 measurement results? Do we need the layer 3 measurement results? The required measurement results are beam-level or cell-level measurements. The device according to any one of claims 114 to 116, characterized in that, The frequency point information is used to indicate one or more frequency points. The device according to any one of claims 114 to 117 is characterized in that, The frequency point information includes one or more of the following: frequency range information, frequency band information, and absolute radio frequency channel number (ARFCN) information. The device according to any one of claims 113 to 118, characterized in that, The device also includes: The second receiving unit is configured to receive second information sent by the second network device, wherein the second information is used to trigger the terminal device to send the first information to the first network device. The second network device is either a core network device or a server that has established an application layer channel with the terminal device. The device according to any one of claims 113 to 119 is characterized in that, The device also includes: The third receiving unit is used to receive the first information from the second network device, which is either a core network device or a server that has established an application layer channel with the terminal device. The device according to any one of claims 96 to 120, characterized in that, The configuration information is determined based on the capability information of the terminal device, and the capability information includes one or more of the following: The terminal device supports measurement prediction-related capability information; The terminal device supports capabilities related to the collection and / or reporting of measurement-related data. The terminal device supports frequency bands or combinations of frequency bands; The terminal device supports measurement-related capability information. The device according to claim 121 is characterized in that, The capability information related to measurement prediction is used to indicate that the terminal device supports one or more of the following: Prediction of measurement results within the frequency range; Prediction of measurement results between frequencies; Prediction of measurement events within a frequency range; Prediction of measurement events between frequencies. The device according to claim 121 or 122 is characterized in that, The configuration information includes information about the measurement object, which includes frequency information. The capability information is used to determine the frequency information. The device according to any one of claims 121 to 123 is characterized in that: The capability information is sent from the terminal device to the first network device; or... The capability information is sent from the second network device to the first network device, where the second network device is a core network device. The device according to any one of claims 96 to 124, characterized in that, The configuration information is carried in the Radio Resource Control (RRC) reconfiguration message. The device according to any one of claims 96 to 125, characterized in that: The configuration information is used by the terminal device to perform data collection and / or reporting tasks, but not for the terminal device to perform measurement tasks; or... The configuration information is used by the terminal device to perform data collection and / or reporting tasks, as well as measurement tasks. The device according to claim 126 is characterized in that, The configuration information is not used by the terminal device to perform measurement tasks, and the terminal device ignores the configuration information related to the measurement task. The device according to any one of claims 96 to 127 is characterized in that, The measurement-related data is used to train a model with measurement prediction capabilities. A communication device, characterized in that, The communication device is a first network device, and the device includes: The first sending unit is used to send configuration information to the terminal device, the configuration information being used to configure the terminal device to collect and / or report measurement-related data. The device according to claim 129 is characterized in that, The configuration information includes one or more of the following: Information about the object being measured; Control information, used to control the collection and / or reporting of the measurement-related data; The measurement object and the control information are associated. The device according to claim 130 is characterized in that, The association between the measurement object and the control information includes: The measurement object and the control information are associated through an association identifier; or... The control information includes the identifier of the object being measured. The device according to claim 130 or 131 is characterized in that, The information of the object being measured includes one or more of the following: Frequency point information, wherein the frequency point information is used to indicate one or more frequency points; Subcarrier information is used to indicate the subcarrier spacing corresponding to the one or more frequency points. The device according to any one of claims 130 to 132 is characterized in that, The control information includes one or more of the following: The type information of the measurement-related data; The collection cycle of the measurement-related data; The triggering conditions for collecting the measurement-related data; The reporting cycle for the measurement-related data; The triggering conditions for reporting the measurement-related data; Measure control parameters. The device according to claim 133 is characterized in that, The type information of the measurement-related data includes one or more of the following: type information of measurement results, type information of measurement events. The device according to claim 134 is characterized in that, The type information of the measurement results includes one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. The device according to claim 134 or 135 is characterized in that, The type information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event. The device according to any one of claims 133 to 136, characterized in that, The measurement control parameters include one or more of the following: parameters for merging layer 1 measurement results, and parameters for performing layer 3 filtering. The device according to any one of claims 130 to 137, characterized in that: One of the measurement objects is associated with one of the control information; or, Multiple measurement objects are associated with one control information. The device according to any one of claims 130 to 138, characterized in that, The configuration information is used to configure the task of collecting and / or reporting the measurement-related data, and the association identifier is the identifier of the task of collecting and / or reporting the measurement-related data. The device according to claim 139 is characterized in that, The task of collecting and / or reporting measurement-related data is associated with the measurement task, and the association identifier is the same as the identifier of the measurement task. The device according to any one of claims 129 to 140 is characterized in that, The measurement-related data includes one or more of the following: measurement results, information about measurement events, timestamp information of the measurement results, and timestamp information of the measurement events. The device according to claim 141 is characterized in that, The measurement results include one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. The device according to claim 141 or 142 is characterized in that, The information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event, identifier of the beam that triggered the Layer 1 measurement event, measurement result corresponding to the beam that triggered the Layer 1 measurement event, identifier of the cell that triggered the Layer 1 measurement event, measurement result corresponding to the cell that triggered the Layer 1 measurement event, identifier of the beam that triggered the Layer 3 measurement event, measurement result corresponding to the beam that triggered the Layer 3 measurement event, identifier of the cell that triggered the Layer 3 measurement event, and measurement result corresponding to the cell that triggered the Layer 3 measurement event. The device according to any one of claims 129 to 143 is characterized in that, The device also includes: The first receiving unit is used to receive the measurement-related data sent by the terminal device. The device according to any one of claims 129 to 144 is characterized in that, The device also includes: The second receiving unit is configured to receive first information sent by the terminal device or the second network device, wherein the first information is used to determine the configuration information. The second network device is either a core network device or a server that has established an application layer channel with the terminal device. The device according to claim 145 is characterized in that, The first information includes one or more of the following: measurement event type information, measurement result type information, and frequency point information. The device according to claim 146 is characterized in that, The type information of the measurement event includes the type information of layer 1 measurement events and / or the type information of layer 3 measurement events. The device according to claim 146 or 147 is characterized in that, The type information of the measurement result is used to indicate one or more of the following: Do we need the layer 1 measurement results? Do we need the layer 3 measurement results? The required measurement results are beam-level or cell-level measurements. The device according to any one of claims 146 to 148, characterized in that, The frequency point information is used to indicate one or more frequency points. The device according to any one of claims 146 to 149 is characterized in that, The frequency point information includes one or more of the following: frequency range information, frequency band information, and absolute radio frequency channel number (ARFCN) information. The device according to any one of claims 129 to 150 is characterized in that, The configuration information is determined based on the capability information of the terminal device, and the capability information includes one or more of the following: The terminal device supports measurement prediction-related capability information; The terminal device supports capabilities related to the collection and / or reporting of measurement-related data. The terminal device supports frequency bands or combinations of frequency bands; The terminal device supports measurement-related capability information. The device according to claim 151 is characterized in that, The capability information related to measurement prediction is used to indicate that the terminal device supports one or more of the following: Prediction of measurement results within the frequency range; Prediction of measurement results between frequencies; Prediction of measurement events within a frequency range; Prediction of measurement events between frequencies. The device according to claim 151 or 152 is characterized in that, The configuration information includes information about the measurement object, which includes frequency information. The capability information is used to determine the frequency information. The device according to any one of claims 151 to 153 is characterized in that: The capability information is sent from the terminal device to the first network device; or... The capability information is sent from the second network device to the first network device, where the second network device is a core network device. The device according to any one of claims 129 to 154, characterized in that, The configuration information is carried in the Radio Resource Control (RRC) reconfiguration message. The device according to any one of claims 129 to 155 is characterized in that: The configuration information is used by the terminal device to perform data collection and / or reporting tasks, but not for the terminal device to perform measurement tasks; or... The configuration information is used by the terminal device to perform data collection and / or reporting tasks, as well as measurement tasks. The device according to claim 156 is characterized in that, The configuration information is not used by the terminal device to perform measurement tasks, and the terminal device ignores the configuration information related to the measurement task. The device according to any one of claims 129 to 157 is characterized in that, The measurement-related data is used to train a model with measurement prediction capabilities. A communication device, characterized in that, The communication device is a second network device, and the device includes: The first receiving unit is used to receive measurement-related data sent by the terminal device. The device according to claim 157 is characterized in that, The measurement-related data includes one or more of the following: measurement results, information about measurement events, timestamp information of the measurement results, and timestamp information of the measurement events. The device according to claim 160 is characterized in that, The measurement results include one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. The device according to claim 160 or 161 is characterized in that, The information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event, identifier of the beam that triggered the Layer 1 measurement event, measurement result corresponding to the beam that triggered the Layer 1 measurement event, identifier of the cell that triggered the Layer 1 measurement event, measurement result corresponding to the cell that triggered the Layer 1 measurement event, identifier of the beam that triggered the Layer 3 measurement event, measurement result corresponding to the beam that triggered the Layer 3 measurement event, identifier of the cell that triggered the Layer 3 measurement event, and measurement result corresponding to the cell that triggered the Layer 3 measurement event. The device according to any one of claims 159 to 162 is characterized in that, The device also includes: The first sending unit is used to send second information to the terminal device, the second information being used to trigger the terminal device to send first information to the first network device, the first information being used to determine configuration information. The device according to claim 163 is characterized in that, The configuration information includes one or more of the following: Information about the object being measured; Control information, used to control the collection and / or reporting of the measurement-related data; The measurement object and the control information are associated. The device according to claim 164 is characterized in that, The association between the measurement object and the control information includes: The measurement object and the control information are associated through an association identifier; or... The control information includes the identifier of the object being measured. The device according to claim 164 or 165 is characterized in that, The information of the object being measured includes one or more of the following: Frequency point information, wherein the frequency point information is used to indicate one or more frequency points; Subcarrier information is used to indicate the subcarrier spacing corresponding to the one or more frequency points. The device according to any one of claims 164 to 166, characterized in that, The control information includes one or more of the following: The type information of the measurement-related data; The collection cycle of the measurement-related data; The triggering conditions for collecting the measurement-related data; The reporting cycle for the measurement-related data; The triggering conditions for reporting the measurement-related data; Measure control parameters. The device according to claim 167 is characterized in that, The type information of the measurement-related data includes one or more of the following: type information of measurement results, type information of measurement events. The device according to claim 168 is characterized in that, The type information of the measurement results includes one or more of the following: beam-level layer 1 measurement results, cell-level layer 1 measurement results, beam-level layer 3 measurement results, and cell-level layer 3 measurement results. The device according to claim 168 or 169 is characterized in that, The type information of the measurement event includes one or more of the following: Layer 1 measurement event, Layer 3 measurement event. The device according to any one of claims 167 to 170 is characterized in that, The measurement control parameters include one or more of the following: parameters for merging layer 1 measurement results, and parameters for performing layer 3 filtering. The device according to any one of claims 164 to 171, characterized in that: One of the measurement objects is associated with one of the control information; or, Multiple measurement objects are associated with one control information. The device according to any one of claims 165 to 172 is characterized in that, The configuration information is used to configure the task of collecting and / or reporting the measurement-related data, and the association identifier is the identifier of the task of collecting and / or reporting the measurement-related data. The device according to claim 173 is characterized in that, The task of collecting and / or reporting measurement-related data is associated with the measurement task, and the association identifier is the same as the identifier of the measurement task. The device according to any one of claims 163 to 174 is characterized in that, The configuration information is determined based on the capability information of the terminal device, and the capability information includes one or more of the following: The terminal device supports measurement prediction-related capability information; The terminal device supports capabilities related to the collection and / or reporting of measurement-related data. The terminal device supports frequency bands or combinations of frequency bands; The terminal device supports measurement-related capability information. The device according to claim 175 is characterized in that, The capability information related to measurement prediction is used to indicate that the terminal device supports one or more of the following: Prediction of measurement results within the frequency range; Prediction of measurement results between frequencies; Prediction of measurement events within a frequency range; Prediction of measurement events between frequencies. The device according to claim 175 or 176 is characterized in that, The configuration information includes information about the measurement object, which includes frequency information. The capability information is used to determine the frequency information. The device according to any one of claims 175 to 177 is characterized in that, The capability information is sent from the second network device to the first network device. The device according to any one of claims 163 to 178 is characterized in that, The configuration information is carried in the Radio Resource Control (RRC) reconfiguration message. The device according to any one of claims 163 to 179 is characterized in that: The configuration information is used by the terminal device to perform data collection and / or reporting tasks, but not for the terminal device to perform measurement tasks; or... The configuration information is used by the terminal device to perform data collection and / or reporting tasks, as well as measurement tasks. The device according to claim 180 is characterized in that, The configuration information is not used by the terminal device to perform measurement tasks, and the terminal device ignores the configuration information related to the measurement task. The device according to any one of claims 163 to 181, characterized in that, The first information includes one or more of the following: measurement event type information, measurement result type information, and frequency point information. The device according to claim 182 is characterized in that, The type information of the measurement event includes the type information of layer 1 measurement events and / or the type information of layer 3 measurement events. The device according to claim 182 or 183 is characterized in that, The type information of the measurement result is used to indicate one or more of the following: Do we need the layer 1 measurement results? Do we need the layer 3 measurement results? The required measurement results are beam-level or cell-level measurements. The device according to any one of claims 182 to 184, characterized in that, The frequency point information is used to indicate one or more frequency points. The device according to any one of claims 182 to 185, characterized in that, The frequency point information includes one or more of the following: frequency range information, frequency band information, and absolute radio frequency channel number (ARFCN) information. The device according to any one of claims 163 to 186, characterized in that, The device also includes: The second sending unit is used to send the first information to the terminal device. The device according to any one of claims 159 to 187 is characterized in that, The second network device is a core network device or a server that establishes an application layer channel with the terminal device. The device according to claim 188 is characterized in that: The second network device is the core network device, and the measurement-related data is transmitted to the core network device via the Internet Protocol (IP) channel; or, The second network device is the server, and the measurement-related data is transmitted to the server through the application layer channel. The device according to any one of claims 159 to 189 is characterized in that, The measurement-related data is used to train a model with measurement prediction capabilities. A communication device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the communication device performs the method as described in any one of claims 1 to 33, 34 to 63, or 64 to 95. An apparatus characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as claimed in any one of claims 1 to 33, 34 to 63, or 64 to 95. A chip characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as claimed in any one of claims 1 to 33, 34 to 63, or 64 to 95. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1 to 33, 34 to 63, or 64 to 95. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as claimed in any one of claims 1 to 19, 1 to 33, 34 to 63, or 64 to 95. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1 to 33, 34 to 63, or 64 to 95.

Images