Communication method and apparatus

Abstract

A communication method and an apparatus, which are used for a network side to distinguish between measurement data, thereby reducing the possibility of data contamination. The method comprises: a network device sends low-power wake-up signal (LP-WUS) configuration information; and, when receiving the LP-WUS configuration information, a terminal device can record measured first measurement data, and reports the first measurement data to the network device, so that the network device learns that the first measurement data is data related to the LP-WUS, and thus a network side can distinguish between measurement data, reducing the possibility of data contamination. In addition, the terminal device can further record an LP-WUS-related state and / or a satisfied LP-WUS-related condition when the terminal device records the first measurement data, so that the network device can distinguish between measurement data collected in different LP-WUS-related states, thereby further reducing the possibility of data contamination.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202510199777.3, filed on February 20, 2025, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to communication methods and apparatus. Background Technology

[0003] Terminal devices use a minimized drive-tests (MDT) mechanism to collect measurement data, which is then used by the network side for coverage optimization and quality of service (QoS) verification or observation.

[0004] Currently, the measurement data has significant shortcomings. In practical applications, measurement data generated by terminal devices under different measurement conditions are often mixed up, making it impossible for the network side to accurately distinguish the required measurement data. This lack of distinguishing ability makes it difficult for the network side to effectively judge the performance and accuracy of the measurement data, potentially leading to data contamination. Summary of the Invention

[0005] This application provides a communication method and apparatus for enabling the network side to distinguish measurement data and reduce the possibility of data corruption.

[0006] Firstly, a communication method is provided. This method can be executed by a terminal device, a module applied to the terminal device (e.g., a processor, chip, or chip system), or a logic node, logic module, or software capable of implementing all or part of the terminal device's functions. The method includes: receiving a low-power wake-up signal (LP-WUS) configuration information; recording first measurement data; and sending the first measurement data.

[0007] As can be seen from the methods described in the first and second aspects, the network device can send Low Power Wake-up Signal (LP-WUS) configuration information. Upon receiving the LP-WUS configuration information, the terminal device can record the first measurement data obtained from the measurement and report the first measurement data to the network device so that the network device can know that the first measurement data is related to LP-WUS, thereby enabling the network side to distinguish the measurement data and reduce the possibility of data corruption.

[0008] In conjunction with the first aspect above, in one possible implementation, the method further includes: receiving first measurement configuration information, the first measurement configuration information instructing the terminal device to record at least one condition for recording first measurement data; recording the first measurement data includes: recording the first measurement data according to the first measurement configuration information, that is, at least one condition for recording the first measurement data can be dynamically configured by the network side to achieve flexible updating of conditions according to changes in actual needs.

[0009] In conjunction with the first aspect above, in one possible implementation, the first measurement configuration information indicates at least one of the following conditions: whether the terminal device records measurement result information based on a low-power signal, wherein the low-power signal includes LP-WUS and / or a low-power synchronization signal LP-SS; whether the terminal device performs LP-WUS monitoring; whether the terminal device performs Radio Resource Management (RRM) measurement offloading of the serving cell; whether the terminal device performs RRM measurement relaxation of the serving cell; whether the terminal device performs RRM measurement relaxation of neighboring cells; the duration between when the terminal device meets the entry condition for LP-WUS monitoring and when it meets the exit condition for LP-WUS monitoring is less than or equal to a first threshold; the first number of times the terminal device meets the entry condition for LP-WUS monitoring within a first time interval is greater than or equal to a second threshold, or the second number of times it meets the exit condition for LP-WUS monitoring is greater than or equal to a third threshold; the terminal device receives LP-WUS-related group information and does not receive a paging indication or a paging pre-indication; the number of times the terminal device receives LP-WUS-related group information and does not receive a paging indication or a paging pre-indication within a second time interval satisfies a fourth threshold.

[0010] It can be seen that at least one of the above conditions is related to LP-WUS. If the state related to LP-WUS can be described, then the first measurement data recorded by the terminal device according to at least one condition can distinguish different states related to LP-WUS, so that the network device can distinguish the measurement data collected in different states related to LP-WUS, and further reduce the possibility of data contamination.

[0011] For example, recording the first measurement data includes at least one of the following: recording the first measurement data when the terminal device performs or does not perform a measurement based on a low-power signal; recording the first measurement data when the terminal device performs or does not perform LP-WUS monitoring; recording the first measurement data when the terminal device performs or does not perform RRM measurement offloading of the serving cell; recording the first measurement data when the terminal device performs or does not perform RRM measurement relaxation of the serving cell; recording the first measurement data when the terminal device performs or does not perform RRM measurement relaxation of the neighboring cell; and recording the first measurement data when the terminal device meets the entry conditions for LP-WUS monitoring and the exit conditions for LP-WUS monitoring. When the duration between conditions is less than or equal to a first threshold, the first measurement data is recorded; when the number of times the terminal device meets the entry condition of LP-WUS monitoring within the first time interval is greater than or equal to a second threshold, or the number of times it meets the exit condition of LP-WUS monitoring is greater than or equal to a third threshold, the first measurement data is recorded; when the terminal device receives LP-WUS-related group information but does not receive a paging indication or a paging pre-indication, the first measurement data is recorded; or, when the number of times the terminal device receives LP-WUS-related group information within the second time interval but does not receive a paging indication or a paging pre-indication meets a fourth threshold, the first measurement data is recorded.

[0012] In conjunction with the first aspect described above, in one possible implementation, the first measurement data further indicates at least one condition in the first measurement configuration information that is satisfied.

[0013] In the above technical solution, the first measurement data not only reflects the measurement data, but also reflects the conditions met by the terminal device when the measurement data is recorded. This allows the type of the first measurement data to be distinguished based on at least one condition in the first measurement configuration information indicated by the first measurement data, providing a reliable and accurate basis for network performance evaluation, optimization and other related research.

[0014] In conjunction with the first aspect described above, in one possible implementation, the first measurement data further includes at least one of the following: cell identification information for receiving LP-WUS configuration information; information indicating whether the terminal device performs LP-WUS monitoring; information indicating the receiver used by the terminal device to perform RRM measurements of the serving cell, wherein the receiver is a low-power receiver or a master receiver; information indicating whether the terminal device performs RRM measurement relaxation of the serving cell; information indicating whether the terminal device performs RRM measurement relaxation of a neighboring cell; information indicating that the terminal device has received LP-WUS-related group information and has not received a paging indication or paging pre-indication; information indicating that the terminal device has received LP-WUS-related group information within a second time interval and has not received... Information on the number of paging indications or paging pre-indications; information indicating whether the terminal device meets the corresponding access conditions based on the measurement results of the low-power receiver and / or the master receiver; the time interval between the moment the terminal device triggers the master receiver and the moment it receives the paging indication, or the time interval between the moment the master receiver is triggered and the moment random access is initiated; the type of low-power receiver configured on the terminal device; whether it is a low-power receiver based on orthogonal frequency division multiplexing or a low-power receiver based on on / off keying; the measurement results of the terminal device based on low-power signals, and / or, the measurement relaxation results in the serving cell or neighboring cells; information indicating that the terminal device is configured to be based on core network packets, or that the terminal device is configured to be based on packets identified by the terminal device.

[0015] In the above technical solution, the terminal device can record instruction information in a pre-defined manner according to the protocol, and the instruction information indicates the status of the terminal device when recording the first measurement data.

[0016] Furthermore, at least one indication information included in the first measurement data is related to LP-WUS, such as describing the state related to LP-WUS. In this case, the terminal device can distinguish different states related to LP-WUS according to the indication information included in the first measurement data, so that the network device can distinguish the measurement data collected in different states related to LP-WUS, further reducing the possibility of data contamination.

[0017] In conjunction with the first aspect described above, in one possible implementation, recording the first measurement data includes: recording the first measurement data while performing an MDT measurement, where the MDT measurement is a recording MDT or a fast MDT. Thus, the first measurement data recorded by the terminal device corresponds to the data performed during the MDT measurement, for example, the MDT measurement data.

[0018] Secondly, a communication method is provided. This method can be executed by a network device, a module applied to the network device (such as a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of the network device. The method includes: sending LP-WUS configuration information; and receiving first measurement data. The technical effects of the second aspect are analogous to those of the first aspect and will not be elaborated further here.

[0019] In conjunction with the second aspect above, in one possible implementation, the method further includes: sending first measurement configuration information, the first measurement configuration information being used to instruct the terminal device to record at least one condition of the first measurement data.

[0020] In conjunction with the second aspect above, in one possible implementation, the first measurement configuration information indicates at least one of the following conditions: whether the terminal device records measurement result information based on a low-power signal, wherein the low-power signal includes LP-WUS and / or LP-SS; whether the terminal device performs LP-WUS monitoring; whether the terminal device performs RRM measurement offloading of the serving cell; whether the terminal device performs RRM measurement relaxation of the serving cell; whether the terminal device performs RRM measurement relaxation of the neighboring cell; the duration between when the terminal device meets the entry condition for LP-WUS monitoring and when it meets the exit condition for LP-WUS monitoring is less than or equal to a first threshold; the first number of times the terminal device meets the entry condition for LP-WUS monitoring within a first time interval is greater than or equal to a second threshold, or the second number of times it meets the exit condition for LP-WUS monitoring is greater than or equal to a third threshold; the terminal device receives LP-WUS-related group information and does not receive a paging indication or a paging pre-indication; the number of times the terminal device receives LP-WUS-related group information within a second time interval and does not receive a paging indication or a paging pre-indication satisfies a fourth threshold.

[0021] In conjunction with the second aspect above, in one possible implementation, the first measurement data further indicates at least one condition in the first measurement configuration information that is satisfied.

[0022] In conjunction with the second aspect described above, in one possible implementation, the first measurement data further includes at least one of the following: cell identification information for receiving LP-WUS configuration information; information indicating whether the terminal device performs LP-WUS monitoring; information indicating the receiver used by the terminal device to perform RRM measurements of the serving cell, wherein the receiver is a low-power receiver or a master receiver; information indicating whether the terminal device performs RRM measurement relaxation of the serving cell; information indicating whether the terminal device performs RRM measurement relaxation of a neighboring cell; information indicating that the terminal device has received LP-WUS-related group information and has not received a paging indication or paging pre-indication; information indicating that the terminal device has received LP-WUS-related group information within a second time interval and has not received... Information on the number of paging indications or paging pre-indications; information indicating whether the terminal device meets the corresponding access conditions based on the measurement results of the low-power receiver and / or the master receiver; the time interval between the moment the terminal device triggers the master receiver and the moment it receives the paging indication, or the time interval between the moment the master receiver is triggered and the moment random access is initiated; the type of low-power receiver configured on the terminal device; whether it is a low-power receiver based on orthogonal frequency division multiplexing or a low-power receiver based on on / off keying; the measurement results of the terminal device based on low-power signals, and / or, the measurement relaxation results in the serving cell or neighboring cells; information indicating that the terminal device is configured to be based on core network packets, or that the terminal device is configured to be based on packets identified by the terminal device.

[0023] In conjunction with the second aspect above, in one possible implementation, the network device includes a first centralized unit (CU) and a first distributed unit (DU), and the method further includes: the first CU sending first measurement data to the first DU.

[0024] In the above technical solution, the network device can send the first measurement data to the first DU through the first CU, and then process and analyze the first measurement data through the first DU.

[0025] In conjunction with the second aspect above, in one possible implementation, the first measurement data is the measurement data recorded by the terminal device when performing MDT measurement, where the MDT measurement is either a recorded MDT or a fast MDT.

[0026] The technical effects of any possible implementation of the second aspect can be referred to the technical effects of any possible implementation of the first aspect, and will not be repeated here.

[0027] Thirdly, a communication device is provided for implementing various methods. The communication device includes modules, units, or means corresponding to the implementation of the methods, which can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

[0028] In some possible designs, the communication device may include a processing module and a transceiver module. The processing module can be used to implement the processing functions in any of the above aspects and any possible implementations thereof. The transceiver module may include a receiving module and a transmitting module, respectively used to implement the receiving function and the transmitting function in any of the above aspects and any possible implementations thereof.

[0029] In some possible designs, the transceiver module can consist of transceiver circuits, transceivers, transceivers, or communication interfaces.

[0030] Fourthly, a communication device is provided, comprising: a processor and a memory; the memory being used to store computer instructions that, when executed by the processor, cause the communication device to perform the method described in either aspect.

[0031] Fifthly, a communication device is provided, comprising: a processor and a communication interface; the communication interface being used to communicate with a module outside the communication device; the processor being used to execute a computer program or instructions to cause the communication device to perform the method described in any one of these aspects.

[0032] A sixth aspect provides a communication device comprising: at least one processor; said processor being configured to execute a computer program or instructions stored in a memory to cause the communication device to perform the method described in any of the aspects. The memory may be coupled to the processor, or may be independent of the processor.

[0033] In a seventh aspect, a communication device (e.g., the communication device may be a chip or a chip system) is provided, the communication device including a processor for implementing the functions involved in any one of the first to second aspects.

[0034] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0035] In some possible designs, when the device is a chip system, it can be composed of chips or contain chips and other discrete components.

[0036] It is understood that the communication device provided in the third to seventh aspects may be the terminal device in the first aspect, or a module or unit (e.g., a chip, chip system, or circuit) in the terminal device that performs the methods / operations / steps / actions described in the first aspect, or a module or unit that can be used in conjunction with the terminal device, or a logical node, logical module, or software that can realize all or part of the functions of the terminal device; or, the communication device may be the network device in the second aspect, or a module or unit (e.g., a chip, chip system, or circuit) in the network device that performs the methods / operations / steps / actions described in the second aspect, or a module or unit that can be used in conjunction with the network device, or a logical node, logical module, or software that can realize all or part of the functions of the network device.

[0037] It is understandable that when the communication device provided by any of the third to seventh aspects is a chip, the sending action / function of the communication device can be understood as outputting information, and the receiving action / function of the communication device can be understood as inputting information.

[0038] Eighthly, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the method described in any one of the first to second aspects.

[0039] A ninth aspect provides a computer program product containing instructions that, when run on a communication device, enables the communication device to perform the method described in any one of the first to second aspects.

[0040] A tenth aspect provides a communication system comprising a terminal device and a network device. The terminal device is configured to perform the method described in the first aspect and any possible design thereof, and the network device is configured to perform the method described in the second aspect and any possible design thereof.

[0041] The technical effects of any of the third to tenth aspects can be found in the technical effects of different embodiments in the first to second aspects, and will not be repeated here. Attached Figure Description

[0042] Figure 1 is a schematic diagram of a terminal device transmitting signals including a low-power wake-up receiver;

[0043] Figure 2 is a schematic diagram of an LP-WUS wake-up master receiver;

[0044] Figure 3 is a schematic diagram of LP-WUS detection for RRC idle / inactive terminal devices;

[0045] Figure 4 is a schematic diagram of the behavior of an RRC idle / inactive terminal device detecting LP-WUS;

[0046] Figure 5 is a schematic diagram of LP-WUS detection in an RRC connected state terminal device;

[0047] Figure 6 is a schematic diagram of the architecture of a communication system provided in this application;

[0048] Figure 7 is a schematic diagram of the protocol stack and network element modules of a wireless access network device provided in this application;

[0049] Figure 8 is a schematic diagram of an O-RAN architecture provided in this application;

[0050] Figures 9-11 are schematic flowcharts of the communication method provided in this application;

[0051] Figures 12-14 are schematic diagrams of the communication device provided in this application. Detailed Implementation

[0052] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0053] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0054] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0055] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0056] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process 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.

[0057] It is understood that in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require a judgment action to be performed during implementation, nor do they imply any other limitations.

[0058] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0059] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of this application.

[0060] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.

[0061] I. Minimization of drive-tests (MDT).

[0062] Minimized drive testing (MDT) is a technology introduced by New Radio (NR). It automates drive testing by configuring terminal devices within the network to collect, report, and preprocess measurement data. This measurement data has wide applications in mobile communication networks, including but not limited to coverage optimization (e.g., discovering coverage vulnerabilities, weak coverage, excessive coverage, and uplink coverage) and Quality of Service (QoS) verification (e.g., evaluating user QoS experience through throughput information in MDT data).

[0063] Based on the data collection target, MDTs can be divided into management-based MDTs and signaling-based MDTs. Management-based MDTs collect MDT data from terminal devices within a specific area, which can be specified through timing advance (TA) and / or a common gateway interface list (CGI List). Signaling-based MDTs collect MDT data from specific terminal devices, which can be specified by Operation Administration and Maintenance (OAM).

[0064] Based on the RRC status of the terminal device, MDT has two working modes: logged MDT and immediated MDT.

[0065] 1) Record the MDT:

[0066] Measurement recording (MDT) is performed on terminal devices in the Unlimited Resource Control (RRC) idle state and idle devices in the RRC inactive state. Specifically, the network side sends MDT recording configurations to the terminal devices, instructing them to perform MDT recording during RRC idle and inactive states. The parameters of the MDT recording configuration include: trigger recording conditions (time-triggered, periodic-triggered), recording duration, and recording area. The recording area can be an area listed in the Public Land Mobile Network (PLMN) list, TA list, CGI list, or frequency point list. The terminal device collects MDT recording data within the recording area. When the recording duration expires or the terminal device receives a new MDT recording configuration, it stops collecting MDT recording data.

[0067] The MDT data collected by the terminal device includes measurement results of the service / neighboring cells related to the coverage, cell identification information, location information, time information, tracking information, etc. When the terminal device reports the recorded MDT data to the network side, the terminal device first indicates the existence of the recorded MDT data to the network side in an RRC message. The network side then requests the terminal device to report the recorded MDT data, and the terminal device then reports the recorded MDT data to the network side.

[0068] 2) Rapid MDT:

[0069] Fast MDT records measurements performed by terminal devices in RRC connected mode. This mode is more real-time and can quickly report measurement results to the network side.

[0070] Fast MDT collects MDT data on both the terminal device side and the access network device side. The terminal device measurement configuration process for Fast MDT incorporates location information and can also include range information for the recording area to instruct the terminal device to collect Fast MDT data in a specific area.

[0071] Measurement data on the terminal device side includes, but is not limited to, measurement results of coverage-related services / neighboring cells, location information, power margin measurements, and packet data convergence protocol (PDCP) latency measurement results at the data link layer (L2). Measurement results on the access network device side, i.e., L2 measurement results, include, but are not limited to, physical resource block (PRB) utilization, throughput, PDCP data volume, packet loss rate, packet drop rate, number of active terminal devices, and packet loss latency.

[0072] 2. Low power wake-up signal (LP-WUS).

[0073] With the development of communication technology, the energy efficiency of communication equipment (including terminal equipment and access network equipment) has become increasingly prominent. How to reduce power consumption while ensuring the performance of terminal equipment has become a key focus of the industry. Regarding terminal equipment performance, the international standards organization 3GPP, in Release 18 and Release 19, first explored and researched low-power wake-up receivers (LP-WURs) and low-power wake-up signals. LP-WURs can be used to receive low-power wake-up signals, which can wake up terminal equipment in a low-power manner, enabling it to respond quickly when necessary and maintain a low-power state when not needed, thereby achieving energy saving.

[0074] Specifically, terminal devices supporting low-power receivers and / or low-power wake-up signals support two types of receivers: main receiver (MR) and low-power wake-up receiver. In practical applications, access network devices can transmit two types of signals, and terminal devices can receive the corresponding transmission signals through different receivers. For example, as shown in Figure 1, access network devices can transmit existing downlink signals from NR and low-power signals. Terminal devices can receive existing downlink signals from NR through the main receiver and receive low-power signals through the low-power wake-up receiver.

[0075] The two receivers will be described below.

[0076] Main receiver:

[0077] The master receiver is used to receive existing downlink signals for NR. The master receiver has strong receiving performance and can achieve high transmission rates; however, it is also more complex and consumes more power. When there is no communication request, the master receiver is generally in sleep mode to reduce power consumption.

[0078] Low-power wake-up receiver:

[0079] A low-power wake-up receiver is an auxiliary receiver used to reduce system standby power consumption. It can receive low-power signals. Specifically, low-power signals include low-power wake-up signals and low-power synchronization signals (LP-SS). Because low-power wake-up receivers are simple to implement and have low complexity, but their receiving performance is relatively weak and their transmission rate is relatively limited, their power consumption is much lower than that of the main receiver.

[0080] It should be noted that, as shown in Figure 2, when the terminal device meets the entry conditions for LP-WUS monitoring, it continuously monitors low-power signals (including low-power wake-up signals and low-power synchronization signals) through a low-power wake-up receiver to reduce the power consumption of the terminal device. When the terminal device's low-power wake-up receiver receives a low-power wake-up signal, it wakes up the main receiver to detect relevant signals. Conversely, when the terminal device meets the exit conditions for LP-WUS monitoring, it continuously monitors signals through the main receiver.

[0081] Low-power wake-up signals and low-power synchronization signals have different characteristics and functions. The following is a comparison and explanation of the characteristics and functions of low-power wake-up signals and low-power synchronization signals.

[0082] Both the low-power wake-up signal and the low-power synchronization signal are on-off keying (OOK) signals, or OOK signals superimposed with time-domain sequences. OOK is a digital modulation method that controls the presence or absence of a signal through a switch; for example, "signal present" represents 1, and "no signal" represents 0. Correspondingly, because the signal is of OOK type, the demodulation method of the receiver is relatively simple. The low-power wake-up receiver only needs to perform basic envelope detection or time-domain correlation detection to demodulate the signal. Therefore, the overall power consumption of the low-power wake-up receiver is extremely low.

[0083] Low-power synchronization signals are not sent randomly, but rather at fixed time intervals. For example, with a time interval of 320 milliseconds (ms), the low-power synchronization signal is sent every 320 ms.

[0084] In terminal devices, the main receiver can be in a sleep state when not in operation to save power. The low-power wake-up signal is mainly used to indicate whether the terminal device needs to turn on the main receiver to receive signals. At the same time, the low-power wake-up signal is also used to detect relevant control signals, such as determining whether there are tasks that the main receiver needs to execute, thereby controlling and guiding the working state of the terminal device.

[0085] The following is a detailed explanation of the LP-WUS process.

[0086] Scenario 1:

[0087] For terminal devices in RRC idle state and / or RRC inactive state, the low-power wake-up signal is used to indicate whether the terminal device should detect the paging indication. Specifically, as shown in Figure 3, the network side configures the LP-WUS monitoring occasion (LO) before the paging occasion (PO) corresponding to the terminal device in each paging cycle. The terminal device detects the LO based on the low-power wake-up receiver in each paging cycle. When LP-WUS is detected and indicates that the terminal device should wake up and detect the paging indication, the terminal device starts detecting the paging indication based on the master receiver; otherwise, the terminal device does not detect the paging indication if LP-WUS is not detected.

[0088] LP-WUS includes group information or terminal device information. Group information and terminal device information in LP-WUS are used for terminal device indication at different levels. Group information instructs the network side to group multiple terminal devices with similar attributes or needs into a group, and then send unified indication information to the terminal devices within this group via LP-WUS. Terminal device information refers to specific indication information for an individual terminal device. Unlike group information, terminal device information is customized for the target terminal device and includes instructions, configurations, or notifications that are only related to that terminal device.

[0089] As shown in Figure 4(a), the access network device (e.g., gNB) sends an LP-WUS carrying group information to the terminal device. This LP-WUS is received by the low-power wake-up receiver in the terminal device. Upon receiving the LP-WUS carrying group information, the low-power wake-up receiver sends an LP-WUS based on the group information, which can wake up the master receiver. The access network device indicates to the master receiver that there is a large legacy paging delay. The master receiver initiates a paging and / or access operation with the access network device. As shown in Figure 4(b), the access network device sends an LP-WUS carrying terminal device information to the terminal device. This LP-WUS is received by the low-power wake-up receiver in the terminal device. The master receiver in the terminal device then initiates access with the access network device.

[0090] When LP-WUS wakes up the master receiver, the terminal device can detect a paging indication, a paging pre-indication, or initiate random access. When LP-WUS carries group information, if the master receiver is woken up but does not detect a paging indication or a paging pre-indication, unnecessary master receiver wake-ups may occur, resulting in frequent switching (i.e., ping-pong switching) between the master receiver and the low-power wake-up receiver.

[0091] Scenario 2:

[0092] For terminal devices in RRC connected state, the low-power wake-up signal is mainly used to indicate whether the terminal device should detect the physical downlink control channel (PDCCH). Specifically, as shown in Figure 5, the network side configures a low-power receiver (LO) before each connected discontinuous reception (C-DRX) cycle. The terminal device detects the LO based on the low-power receiver before each C-DRX cycle. When LP-WUS information is detected on LO1 and indicates that the terminal device should not wake up, the terminal device does not start the on-duration timer in the next C-DRX cycle. Alternatively, the network side configures periodic LOs (during the inactive time of the C-DRX cycle). Correspondingly, the terminal device periodically detects LP-WUS on LO2. When LP-WUS is detected and indicates that the terminal device should wake up, the terminal device starts detecting the PDCCH based on the master receiver.

[0093] In addition to the focus on the LP-WUS procedures and configuration methods in the RRC idle and / or inactive and / or connected states, the radio resource management (RRM) relaxation measurement and RRM measurement offloading mechanisms in the RRC idle and / or inactive states are also related to LP-WUS.

[0094] A) RRM relaxation measurement.

[0095] The introduction of RRM relaxation measurement stems from the fact that terminal devices in the RRC idle and / or inactive states periodically measure the serving cell and neighboring cells, generating a significant portion of power consumption. This periodic measurement results in wasted power. When the measurement relaxation conditions are met, terminal devices in the RRC idle and / or inactive states can perform RRM relaxation measurement to reduce power consumption.

[0096] There are two methods for RRM relaxation measurement of terminal equipment. Method 1: Relaxation measurement is performed in the time domain, i.e., the measurement interval is increased. Method 2: Relaxation measurement is performed in the frequency domain, i.e., the number of frequencies / carriers to be measured is reduced. The measurement relaxation conditions for the serving cell and neighboring cells may share the same condition or be configured separately.

[0097] It should be noted that the result of RRM measurement relaxation affects the entry conditions for LP-WUS monitoring. For example, if, after RRM measurement relaxation, the measurement results still meet the corresponding entry conditions for LP-WUS monitoring, consisting of the measurement results from the master receiver and / or the low-power wake-up receiver, then the terminal device will enter LP-WUS monitoring state. It will then perform subsequent operations according to LP-WUS instructions. For instance, if, after RRM measurement relaxation in the serving cell of the terminal device, two parameters such as signal strength reach the entry condition threshold for LP-WUS monitoring based on the master receiver, then LP-WUS monitoring may be triggered.

[0098] Alternatively, LP-WUS can be used to instruct terminal devices whether to perform RRM measurement relaxation for the serving cell or neighboring cells. When LP-WUS is in a preset state or receives specific instruction information, the terminal device will decide whether to perform RRM measurement relaxation based on its instruction. For example, the network side may use LP-WUS to inform the terminal device that the current network load is low and the wireless environment is good. After receiving LP-WUS, the terminal device will perform RRM measurement relaxation according to the LP-WUS instruction to reduce overhead and save power consumption.

[0099] B) RRM measurement unloading.

[0100] RRM measurement offloading refers to the process where the receiver of the terminal device performing RRM measurements changes from the primary receiver to a low-power wake-up receiver. When the RRM measurement offloading conditions are met, the RRM measurement of the serving cell is changed from being performed by the primary receiver to being performed by the low-power wake-up receiver.

[0101] The above provides a brief overview of the relevant technologies involved in this application. Currently, measurement data (such as MDT data) has significant shortcomings. In practical applications, it is impossible to accurately distinguish whether the MDT data was obtained by the low-power wireless receiver of the terminal device, or by the main receiver of the terminal device, or by a conventional terminal device that has not been configured with a low-power wake-up signal procedure.

[0102] This lack of discernment makes it difficult for the network side to effectively assess the performance and accuracy of MDT data, potentially leading to data contamination. For example, due to unclear sources, MDT data generated by different types of terminal devices may become mixed up; or, MDT data recorded by terminal devices under different circumstances may become mixed up, thereby affecting the accuracy of the analysis, decisions, and network optimization results made by the network side based on this MDT data.

[0103] In view of this, this application provides a communication method in which a network device can send Low Power Wake-up Signal (LP-WUS) configuration information. Upon receiving the LP-WUS configuration information, a terminal device can record the first measurement data obtained from the measurement and report the first measurement data to the network device, so that the network device can know that the first measurement data is related to LP-WUS, thereby enabling the network side to distinguish the measurement data and reduce the possibility of data corruption.

[0104] To facilitate understanding of the embodiments of this application, the following points will be explained before introducing the embodiments of this application.

[0105] 1. In the embodiments of this application, "instruction" can include direct instruction and indirect instruction, as well as explicit instruction and implicit instruction. The information indicated by a certain piece of information (hereinafter referred to as instruction information) is called the information to be instructed. In the specific implementation process, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is an association between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement order of various pieces of information, thereby reducing instruction overhead to a certain extent. At the same time, the common parts of various pieces of information can be identified and indicated uniformly to reduce the instruction overhead caused by individually indicating the same information.

[0106] Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be repeated here. As can be seen from the above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method; therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated.

[0107] It should be understood that the information to be indicated can be sent as a whole or divided into multiple sub-information messages sent separately, and the sending period and / or timing of these sub-information messages can be the same or different. The specific sending method is not limited in this application embodiment. The sending period and / or timing of these sub-information messages can be predefined, for example, predefined according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device. This configuration information can include, for example, but not limited to, radio resource control signaling, such as RRC signaling, MAC layer signaling, physical layer signaling, or DCI, or a combination of at least two of these.

[0108] 2. "Predefined" or "pre-configured" can be achieved by pre-saving corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., terminal device or network device). This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. The one or more memories can be separate settings or integrated into the encoder or decoder, processor, or communication device. Alternatively, some memories can be separately set up, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0109] The technical solutions of this application embodiment can be used in various communication systems, including third-generation partnership project (3GPP) communication systems, such as fourth-generation (4G) systems like long-term evolution (LTE), 5G systems like new radio (NR), hybrid LTE and 5G networks, non-terrestrial networks (NTN), or other future communication systems. The communication system can also be a non-3GPP communication system; there is no limitation on this.

[0110] The communication systems described above are merely illustrative examples, and are not limited to those described herein. The communication systems provided in this application do not impose any limitations on the solutions described herein. This will be explained uniformly here and will not be repeated below.

[0111] Figure 6 illustrates a possible, non-limiting system diagram. As shown in Figure 6, the communication system includes a radio access network (RAN) 600 and a core network (CN) 700. Optionally, the communication system may also include an Internet 800. The RAN 600 includes at least one network device (610a and 610b in Figure 6, collectively referred to as 610) and at least one terminal device (620a-620j in Figure 6, collectively referred to as 620). The RAN 600 may also include other network devices, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 6). The terminal device 620 is wirelessly connected to the network device 610. The network device 610 is wirelessly or wiredly connected to the core network 300. The core network device in the core network 300 and the network device 610 in the RAN 600 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0112] RAN 600 can be a 3GPP-related cellular system, such as 4G or 5G mobile communication systems, or future-oriented evolution systems (such as future communication networks). RAN 600 can also be an open access network (open RAN, O-RAN, or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN 600 can also be a communication system that integrates two or more of the above systems.

[0113] Terminal device 620 can also be referred to as user equipment (UE), mobile station, mobile terminal device, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the device form of the terminal device.

[0114] Network device 610, sometimes also referred to as access network device, RAN entity, or access node, constitutes part of the communication system and is used to help terminal devices achieve wireless access. Multiple network devices 610 in the communication system can be nodes of the same type or different types. In some scenarios, the roles of network device 610 and terminal device 620 are relative. For example, network element 620i in Figure 6 can be a helicopter or drone, which can be configured as a mobile base station. For terminal devices 620j accessing RAN 600 through network element 620i, network element 620i is a base station; but for base station 610a, network element 620i is a terminal device. Network device 610 and terminal device 620 are sometimes both referred to as communication devices. For example, network elements 610a and 610b in Figure 6 can be understood as communication devices with base station functions, and network elements 620a-620j can be understood as communication devices with terminal device functions.

[0115] In one possible scenario, the network device can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a future communication network, a base station in a future mobile communication system, or an access node in a WiFi system. The network device can be a macro base station (as shown in Figure 6, 610a), a micro base station or indoor station (as shown in Figure 6, 610b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, the network device can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the network device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The network device in this application can also be a logical node, logical module, or software capable of implementing all or part of the network device functions.

[0116] In another possible scenario, multiple network devices collaborate to assist terminal devices in achieving wireless access, with each network device performing a portion of the base station's functions. For example, these network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs). CUs and DUs can be configured separately or included in the same network element, such as the baseband unit (BBU). The CU and DU nodes separate the gNB's protocol layers; some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed in the DU, which is centrally controlled by the CU. As one implementation, the CU deploys the Radio Resource Control (RRC) layer, PDCP layer, and Service Data Adaptation Protocol (SDAP) layer in the protocol stack; the DU deploys the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical Layer (PHY) in the protocol stack. Thus, the CU has the processing capabilities for RRC, PDCP, and SDAP. The DU has the processing capabilities for RLC, MAC, and PHY. It is understood that the above functional division is merely an example and does not constitute a limitation on the CU and DU. The RU can be included in radio frequency equipment or radio frequency units, such as in a remote radio unit (RRU), active antenna unit (AAU), or remote radio head (RRH).

[0117] Figure 7 is a schematic diagram of the protocol stack and network element modules of a wireless access network device provided in an embodiment of this application.

[0118] In one network architecture, access network equipment may include CU nodes, DU nodes, or RAN equipment including both CU and DU nodes. RAN equipment including CU and DU nodes separates the protocol layer of the gNB in ​​the NR system, with some protocol layer functions centrally controlled by the CU, and the remaining partial or complete protocol layer functions distributed in the DU, which is centrally controlled by the CU.

[0119] As shown in Figure 7(a), the CU is deployed with the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, and the service data adaptation protocol (SDAP) layer in the protocol stack; the DU is deployed with the radio link control (RLC) layer, the media access control (MAC) layer, and the physical layer (PHY) in the protocol stack.

[0120] The CU (Access Controller) has RRC, PDCP, and SDAP processing capabilities. The DU (Access Controller) has RLC, MAC, and PHY processing capabilities. The CU and DU communicate via the F1 interface. The CU, representing the access network device, connects to the core network via the Ng interface.

[0121] It should be understood that the above functional division (or segmentation) is only an example and does not constitute a limitation of the CU and DU in this application. That is to say, there can be other ways to segment the functions between the CU and DU, and the embodiments of this application do not limit this. The function of the CU can be implemented by one entity or by different entities. For example, referring to Figure 7(b), the function of the CU can be further segmented, for example, by separating the control plane (CP) and the user plane (UP), that is, splitting the CU into the CU control plane (i.e., CU-CP) and the CU user plane (i.e., CU-UP). For example, CU-CP and CU-UP can be implemented by different functional entities, and CU-CP and CU-UP can be coupled with DU to jointly complete the functions of the base station. Optionally, the CU control plane CU-CP also includes a further segmentation architecture, that is, further segmenting the existing CU-CP into CU-CP1 and CU-CP2. CU-CP1 includes various radio resource management functions, while CU-CP2 only includes RRC functions and PDCP control plane (PDCP-C) functions (i.e., the basic functions of control plane signaling at the PDCP layer). In one possible configuration, CU-CP is responsible for control plane functions, mainly including RRC and PDCP-C functions. PDCP-C is mainly responsible for control plane data encryption / decryption, integrity protection, and data transmission. CU-UP is responsible for user plane functions, mainly including SDAP and PDCP user plane (PDCP-U) functions. SDAP is mainly responsible for processing core network data and mapping data flows to bearers. PDCP-U is mainly responsible for data plane encryption / decryption, integrity protection, header compression, sequence number maintenance, and data transmission. CU-CP and CU-UP are connected via the E1 interface. CU-CP represents the base station connecting to the core network via the Ng interface and to the DU via the F1 control plane (F1-C) interface. The CU-UP connects to the DU via the F1 user plane (F1-U) interface. Alternatively, the PDCP-C could also be located within the CU-UP.

[0122] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0123] O-RAN aims to achieve an intelligent and open access network. The main characteristic of the O-RAN architecture is the separation of hardware and software, realizing the virtualization of network functions and the standardization of hardware. Furthermore, O-RAN introduces artificial intelligence (AI). As shown in Figure 8, the O-RAN architecture includes a Non-Real Time RAN Intelligent Controller (Non-Real Time RIC), a Near-Real Time RAN Intelligent Controller (Near-Real Time RIC), O-eNB, O-CU-CP, O-CU-UP, O-DU, O-RU, and O-Cloud. The O-RAN architecture also includes 3GPP interfaces (including X2-c, X2-u, NG-u, Xn-u, Xn-, NG-c, F1-u, F1-c, and E1 interfaces), O-RAN interfaces (including O1, O2, A1, E2, the Open FH user plane (Open FH cus-Plane), and the Open FH management plane (Open FH M-Plane), as well as interfaces for future research. The non-real-time RAN intelligent controller is configured within the service management and orchestration framework.

[0124] The following table 1 illustrates the correspondence between access network devices (network element modules) and their achievable protocol layer functions in the ORAN architecture.

[0125] Table 1

[0126] Core network 700 refers to the equipment in the core network (CN) that provides service support for terminals. Examples of core network equipment include: Access and Mobility Management Function (AMF) entities, Session Management Function (SMF) entities, User Plane Function (UPF) entities, etc., which will not be listed here. The AMF entity is responsible for terminal access management and mobility management; the SMF entity is responsible for session management, such as user session establishment; and the UPF entity can be a user plane functional entity, primarily responsible for connecting to external networks. It should be noted that in this application, entities can also be referred to as network elements or functional entities. For example, an AMF entity can also be called an AMF network element or an AMF functional entity, and similarly, an SMF entity can also be called an SMF network element or an SMF functional entity.

[0127] In the aforementioned communication system, the network device is used to send LP-WUS configuration information and / or first measurement configuration information to the terminal device. In this way, the terminal device can record the first measurement data obtained from the measurement upon receiving the LP-WUS configuration information, and report the first measurement data to the network device. This allows the network device to know that the first measurement data is related to LP-WUS, thereby enabling the network side to distinguish the measurement data and reduce the possibility of data contamination.

[0128] It should be noted that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0129] The communication method provided in this application will be described below with reference to the communication system shown in Figure 6, taking the interaction between the terminal device and the network device as an example. It should be noted that in the following embodiments of this application, the message names, parameter names, or information names between the terminal device and the network device are just examples, and other names may be used in other embodiments. The method provided in this application does not specifically limit these names.

[0130] It is understood that in the embodiments of this application, the terminal device or network device may execute some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also execute other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments of this application, and it is not necessarily necessary to execute all the operations in the embodiments of this application.

[0131] It is understood that this application uses network devices and terminal devices as examples to illustrate the execution of the interaction, but this application does not limit the execution subject of the interaction. For example, the method executed by the network device in this application can also be executed by a module applied to the network device (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software that can implement all or part of the functions of the network device; similarly, the method executed by the terminal device in this application can also be executed by a module applied to the terminal device (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software that can implement all or part of the functions of the terminal device.

[0132] Furthermore, in this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For example, "network device sending information" can be understood as a network device sending information to another device (such as a terminal device), or it can be understood as logical module 1 (such as a processing module) in the network device sending information to logical module 2 (such as a transceiver module) in the network device.

[0133] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "terminal device receiving information" can be understood as a terminal device receiving information from another device (such as a network device), or it can be understood as logical module 1 (such as a processing module) in the terminal device receiving information from logical module 2 (such as a transceiver module) in the terminal device.

[0134] In this application, phrases such as "sending information to... (e.g., a terminal device)" or related illustrations in the accompanying drawings can be understood as the destination of the information being the terminal device. This can include sending information directly or indirectly to the terminal device. Similarly, phrases such as "receiving information from... (e.g., a network device)," "receiving information from... (e.g., a network device)," or "receiving information sent (e.g., by a network device)," or related illustrations in the accompanying drawings, can be understood as the source of the information being the network device. This can include receiving information directly or indirectly from the network device. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be elaborated further here.

[0135] Referring to Figure 9, which is a flowchart of a communication method provided in an embodiment of this application, the method may include the following steps S901-S903.

[0136] S901, the network device sends LP-WUS configuration information. Correspondingly, the terminal device receives the LP-WUS configuration information.

[0137] The LP-WUS configuration information may include at least one of the following: LP-SS configuration, LP-WUS configuration, LP-WUS monitoring entry conditions and / or LP-WUS monitoring exit conditions, serving cell measurement offloading configuration, and neighbor cell measurement relaxation configuration.

[0138] In one possible implementation, the S901 process includes: when the terminal device is in a radio resource control (RRC) connected state, the terminal device receives LP-WUS configuration information through the network device's system information block (SIB) or RRC message. Alternatively, when the terminal device is in an RRC idle state and / or an RRC inactive state, it receives LP-WUS configuration information through the system information block.

[0139] It should be noted that after receiving the LP-WUS configuration information, the terminal device can determine whether to enter LP-WUS monitoring, exit LP-WUS monitoring, perform RRM measurement offloading of the serving cell, perform RRM measurement relaxation of the serving cell, and perform RRM measurement relaxation of neighboring cells based on the LP-WUS configuration information.

[0140] S902, The terminal device records the first measurement data.

[0141] In one possible implementation, the terminal device may record first measurement data while performing MDT measurement recording, where the MDT measurement is either a recorded MDT or a fast MDT. The first measurement data is the measurement data recorded by the terminal device during the MDT measurement recording process; for example, the first measurement data is MDT data, or in other words, the MDT data includes the first measurement data.

[0142] Of course, the above is only an exemplary description of the first measurement data. When the terminal device performs other information recording or reporting, it may also record or include the first measurement data. Other information, such as wireless link failure reports, handover success reports, measurement report data, wireless layer measurement data, network layer signaling data, device status data, location and mobility data, environmental data, application layer performance data, etc., are not limited in this application.

[0143] In one possible implementation, the terminal device can also record MDT measurements under at least one condition, thereby recording first measurement data. This at least one condition can also be referred to as at least one condition for recording the first measurement data, or at least one condition that triggers the recording of the first measurement data. In another possible implementation, the network device can configure at least one condition for recording the first measurement data for the terminal device. This at least one condition can be related to LP-WUS. Then, the terminal device can perform measurement (e.g., MDT measurement) recording under at least one condition, thereby recording the first measurement data. The first measurement data can include at least one condition satisfied when the terminal device records the first measurement data, or at least one cause value that triggers the terminal device to record the first measurement data. See Embodiment 1 below for details, which will not be repeated here. Alternatively, in another possible implementation, the terminal device can also record the first measurement data itself based on a protocol-defined method. The recorded first measurement data includes LP-WUS information. See Embodiment 2 below for details, which will not be repeated here.

[0144] S903, The terminal device sends the first measurement data. Correspondingly, the network device receives the first measurement data.

[0145] Understandably, according to S902, the first measurement data includes "at least one condition satisfied when the terminal device records the first measurement data" or "the situation when the terminal device performs measurement recording". Therefore, the network side can distinguish the first measurement data based on "at least one condition satisfied when the terminal device records the first measurement data" or "the situation when the terminal device performs measurement recording", and then select specific first measurement data for different performance optimization needs, so as to provide accurate data support for performance optimization.

[0146] For example, when the network side needs to evaluate and optimize LP-WUS-related network performance, it can select LP-WUS-related first measurement data based on "at least one condition satisfied when the terminal device records the first measurement data" or "LP-WUS information included in the first measurement data". In this case, since the data type corresponds to the type of service requirement, it can provide accurate data support for services such as network performance evaluation and optimization.

[0147] In one possible implementation, the S903 process includes: the terminal device sending the first measurement data to the network device via transparent transmission; alternatively, the terminal device sending the first measurement data to the network device via relay transmission; or alternatively, the terminal device sending the first measurement data to the network device via encrypted transmission.

[0148] Of course, the above is only an exemplary description of transmitting the first measurement data. The implementation process of transmitting the first measurement data can also be implemented in the future by other transmission methods, and this application embodiment does not impose any restrictions on this.

[0149] In the above technical solution, the network device can send Low Power Wake-up Signal (LP-WUS) configuration information. Upon receiving the LP-WUS configuration information, the terminal device can record the first measurement data obtained and report the first measurement data to the network device. This allows the network device to know that the first measurement data is related to LP-WUS, thereby enabling the network side to distinguish the measurement data and reduce the possibility of data corruption.

[0150] Optionally, in some embodiments, when the network device includes a first CU and a first DU, the communication method provided in this application further includes: the first CU sending first measurement data to the first DU, and correspondingly, the first DU receiving the first measurement data from the first CU.

[0151] In the above technical solution, the network device can send the first measurement data to the first DU through the first CU, and then process and analyze the first measurement data through the first DU.

[0152] The following are detailed descriptions using Examples 1 and 2:

[0153] Example 1:

[0154] As one possible embodiment of this application, referring to FIG9 above and FIG10, the communication method provided by this application may include a network configuring at least one condition for a terminal device to record first measurement data, and a process by which the terminal device records the first measurement data based on the condition. The implementation process of configuring the terminal device for measurement will be described below through S1001-S1004.

[0155] S1001, The first network device sends LP-WUS configuration information. Correspondingly, the terminal device receives the LP-WUS configuration information.

[0156] The specific functions of the LP-WUS configuration information in S1001 can be referred to in the embodiment shown in S901, and will not be repeated here.

[0157] It should be noted that the terminal device moves into the coverage area of ​​the first network device at this time. Therefore, the terminal device can obtain LP-WUS configuration information based on the first network device corresponding to its current location.

[0158] In one possible implementation, the process of S1001 includes: when the terminal device is always in RRC connected state, the first network device (i.e., the second network device and the first network device are the same network device) can send LP-WUS configuration information through system information blocks or RRC messages. Correspondingly, the terminal device can receive LP-WUS configuration information through the system information blocks or RRC messages of the first network device (i.e., the second network device and the first network device are the same network device).

[0159] In another possible implementation, the S1001 process includes: after the terminal device in the RRC connected state receives the first measurement configuration information from the second network device, if the terminal device is currently in the RRC idle state and / or the RRC inactive state, and the terminal device is camped in the cell managed by the first network device, the first network device can send LP-WUS configuration information to the terminal device through a system information block. Correspondingly, the terminal device can receive the LP-WUS configuration information through the system information block of the first network device. The second network device and the first network device can be the same network device or different network devices.

[0160] S1002, the second network device sends the first measurement configuration information. Correspondingly, the terminal device receives the first measurement configuration information.

[0161] In one possible implementation, the terminal device is in RRC connection state and obtains the first measurement configuration information from the second network device.

[0162] It should be noted that the embodiments of this application do not impose any restrictions on the execution order of S1001 and S1002. That is, S1001 can be executed before S1002, S1001 can be executed after S1002, and S1001 can also be executed simultaneously with S1002.

[0163] The first measurement configuration information indicates at least one condition for recording the first measurement data.

[0164] When the first measurement data is collected through a recording MDT, the first measurement configuration information may include trigger recording conditions (e.g., time-triggered conditions, periodic trigger conditions), recording duration, and recording area to instruct the terminal device to perform a recording MDT in the RRC idle state and the RRC inactive state. When the first measurement data is collected through a fast MDT, the first measurement configuration information may include location information, recording area range information, etc., in addition to trigger recording conditions, recording duration, and recording area to instruct the terminal device to perform a fast MDT in a specific area.

[0165] Optionally, the first measurement configuration information can be sent from the second network device to the terminal device through a separate message; the first measurement configuration information can also be sent in the same message as the LP-WUS configuration information, and this application does not impose any restrictions on this.

[0166] Optionally, in some embodiments, the first measurement configuration information indicates at least one of the following conditions:

[0167] Condition 1: Does the terminal device record measurement result information performed based on low-power signals, where low-power signals include LP-WUS and / or low-power synchronization signals LP-SS? Measurement result information performed based on low-power signals can also be referred to as measurement result information of low-power signals, or measurement result information related to low-power information. Alternatively, Condition 1 indicates whether the first measurement result information includes measurement result information performed based on low-power signals. Here, measurement result information can be understood as the measurement results obtained by the terminal device performing measurements based on low-power signals.

[0168] Optionally, the values ​​of the above conditions can be indicated in the form of 1 bit information, for example, using "1" or "true" to indicate that the terminal device records the measurement result information of the low power signal, or using "0" or "false" to indicate that the terminal device does not record the measurement result information of the low power signal.

[0169] It should be noted that, in one possible approach, condition 1 above may instruct the terminal device to record the measurement results of the low-power signal, or not to record the measurement results of the low-power signal. Alternatively, condition 1 may instruct the first measurement data to include the measurement results of the low-power signal, or not to include the measurement results of the low-power signal. Another possible implementation is that condition 1 implicitly instructs the terminal device to record the first measurement data under this condition. Yet another possible approach is that condition 1 may also instruct the terminal device to record the first measurement data whether or not the measurement is performed based on the low-power signal. That is, under this condition, the first measurement data collected by the terminal device may include measurement data obtained from measurements performed based on the low-power signal, or may not include measurement data obtained from measurements performed based on the low-power signal, thereby indicating the type of the first measurement data.

[0170] Furthermore, the network side can understand the wireless environment measurement data under low-power mechanisms such as LP-WUS and / or LP-SS based on the condition that "the terminal device records the measurement result information performed based on the low-power signal". This facilitates the network side to analyze the impact of the low-power mechanism on the overall network performance. For example, the network side can analyze the signal coverage, intensity changes and interference under the action of the low-power signal based on the first measurement data corresponding to "the terminal device records the measurement result information performed based on the low-power signal", thereby providing a basis for optimizing network configuration and improving network performance.

[0171] The network side can collect measurement result information of non-low power signals from terminal devices based on the condition that "terminal devices do not record measurement result information performed based on low power signals". This avoids the problems of measurement data pollution and fuzziness caused by the poor performance and accuracy of low power signal measurement result information.

[0172] Optionally, the terminal device's recording of the fulfillment of this condition (i.e., information indicating that condition 1 is met, or information indicating condition 1 that triggers the recording of the first measurement data) can be included in the first measurement data. This allows the network to distinguish the first measurement data and, based on this condition, determine whether the first measurement data will be biased due to the measurement results of the low-power signal. Specifically, based on the terminal device's information indicating that condition 1 is met, or the information indicating condition 1 that triggers the recording of the first measurement data, it can be determined that the first measurement data is collected based on a low-power signal. Compared to the measurement data collected by the terminal device based on a downlink signal (e.g., the existing downlink signal in NR), if there is a discrepancy between the two, it indicates the influence of the low-power signal on the collection of the first measurement data. This allows the network to distinguish data collected under different conditions to avoid confusion.

[0173] Condition 2: Is the terminal device executing LP-WUS monitoring and recording of the first measurement data?

[0174] In one example, regarding the conditions under which a terminal device performs LP-WUS monitoring, or in other words, the conditions under which a terminal device is in LP-WUS monitoring mode, the terminal device records first measurement data when these conditions are met. Under these conditions, the first measurement data recorded by the terminal device reflects various aspects of the LP-WUS signal during actual operation, such as the stability and accuracy of the LP-WUS signal, and the interaction between the terminal device and the network side during monitoring. Therefore, configuring this condition for the terminal device allows the terminal device to record measurement data under these conditions, enabling the network side to perform network analysis based on the first measurement data corresponding to these conditions.

[0175] When the terminal device is not performing LP-WUS monitoring, or in other words, is not in LP-WUS monitoring mode, the terminal device records first measurement data when this condition is met. Under this condition, the first measurement data recorded by the terminal device is collected without the LP-WUS monitoring mechanism, and this first measurement data usually differs from the measurement data collected under the LP-WUS monitoring mechanism. This avoids the problems of measurement data contamination and / or ambiguity caused by poor measurement performance and accuracy depending on whether the LP-WUS monitoring mechanism is performed.

[0176] Optionally, the terminal device's recording of whether the condition is met (i.e., information indicating that condition 2 is met, or information indicating condition 2 that triggers the recording of the first measurement data) can be included in the first measurement data. This allows the network side to distinguish the first measurement data and, based on this condition, assess whether the measurement data will be biased due to LP-WUS monitoring. Specifically, based on the terminal device's information indicating that condition 2 is met, or the information indicating that condition 2 triggers the recording of the first measurement data, it can be determined that the first measurement data is the measurement data recorded by the terminal device when condition 2 is met. Compared to the measurement data recorded by the terminal device when condition 2 is not met, if there is a discrepancy between the two, it indicates the impact of LP-WUS monitoring on the collection of the first measurement data. This allows the network to distinguish data collected under different conditions to avoid confusion.

[0177] Condition 3: Does the terminal device perform RRM measurement offloading for the serving cell?

[0178] In one example, the terminal device performs RRM measurement offloading for the serving cell, or in other words, the terminal device is in the RRM measurement offloading state for the serving cell. When this condition is met, the terminal device records the first measurement data. Under this condition, it indicates that the receiver of the terminal device performing the RRM measurement changes from a master receiver to a low-power wake-up receiver, and the first measurement result includes the serving cell measurement result measured by the low-power wake-up receiver.

[0179] For terminal devices that do not perform RRM measurement offloading for the serving cell, or in other words, are not in the RRM measurement offloading state for the serving cell, the receiver of the terminal device performing RRM measurements remains the primary receiver. This avoids the problems of measurement data contamination and fuzziness caused by poor measurement performance and accuracy during the RRM measurement offloading state for the serving cell.

[0180] Optionally, the terminal device can record whether the condition is met (i.e., information indicating that condition 3 is met, or information indicating condition 3 that triggers the recording of the first measurement data). This information can be included in the first measurement data, allowing the network to differentiate the first measurement data and assess whether deviations in the measurement data may occur due to whether RRM measurement offloading is performed. Specifically, based on the terminal device's information indicating that condition 3 is met, or information indicating that condition 3 triggers the recording of the first measurement data, it can be determined that the first measurement data is the measurement data recorded by the terminal device when condition 3 is met. Compared to the measurement data recorded by the terminal device when condition 3 is not met, if there is a deviation between the two, it indicates the impact of RRM measurement offloading of the serving cell on the collection of the first measurement data. This allows the network to differentiate data collected under different conditions to avoid confusion.

[0181] Condition 4: Does the terminal device perform RRM measurement relaxation for the serving cell?

[0182] In one example, when the terminal device performs RRM measurement relaxation for the serving cell, or in other words, when the terminal device is in an RRM measurement relaxation state, the terminal device records the first measurement data when this condition is met. That is, this condition can control the terminal device to collect the first measurement data related to the RRM measurement relaxation mechanism of the serving cell.

[0183] For terminal devices that do not perform RRM measurement relaxation for the serving cell, or in other words, are not in an RRM measurement relaxation state, the terminal device can perform RRM measurements for the serving cell according to normal measurement requirements and record the first measurement data. This avoids the problem of measurement data contamination caused by poor measurement performance and accuracy in the RRM measurement relaxation state of the serving cell.

[0184] Optionally, the terminal device reporting the fulfillment of this condition (i.e., information indicating that condition 4 is met, or information indicating condition 4 that triggers the recording of the first measurement data) can be included in the first measurement data. This allows the network to differentiate the first measurement data and, based on this condition, determine whether the evaluation of the first measurement data will be affected by whether or not the RRM measurement relaxation of the serving cell is performed, leading to deviations in the measurement data. Specifically, based on the terminal device's information indicating that condition 4 is met, or in other words, information indicating condition 4 that triggers the recording of the first measurement data, it can be determined that the first measurement data is the measurement data recorded by the terminal device when condition 4 is met. Compared to the measurement data recorded by the terminal device when condition 4 is not met, if there is a deviation between the two, it indicates the impact of RRM measurement relaxation of the serving cell on the collection of the first measurement data. This allows the network to differentiate data collected under different conditions to avoid confusion.

[0185] It should be understood that, based on the first measurement data corresponding to condition 4 above, the network side can also determine the impact of the RRM measurement relaxation mechanism on the first measurement data, such as changes in measurement accuracy and fluctuation range of the first measurement data, so as to reasonably adjust the relevant parameters of the RRM measurement relaxation mechanism of the serving cell according to these changes, and ensure the availability of measurement results as much as possible while reducing the power consumption of terminal devices.

[0186] Condition 5: Does the terminal device perform RRM measurement relaxation in the neighboring cell?

[0187] In one example, RRM measurement relaxation is performed on the terminal device in the neighboring cell, or in other words, the terminal device is in the RRM measurement relaxation state in the neighboring cell, and the terminal device records the first measurement data when the condition is met.

[0188] To address the issue of the terminal device not performing RRM measurement relaxation in neighboring cells, or in other words, the terminal device not being in the RRM measurement relaxation state in neighboring cells, the terminal device records the first measurement data when this condition is met. This avoids the problems of measurement data contamination and / or fuzzy data caused by poor measurement performance and accuracy in the RRM measurement relaxation state in neighboring cells.

[0189] Optionally, the terminal device reporting the fulfillment of this condition (i.e., information indicating that condition 5 is met, or information indicating condition 5 that triggers the recording of the first measurement data) can be included in the first measurement data. This allows the network to differentiate the first measurement data and, based on this condition, determine whether the evaluation of the first measurement data will be affected by whether or not neighboring cell RRM measurement relaxation is performed, leading to deviations in the measurement data. Specifically, based on the terminal device's indication that condition 5 is met, or the information indicating condition 5 that triggers the recording of the first measurement data, it can be determined that the first measurement data is the measurement data recorded by the terminal device when condition 5 is met. Compared to the measurement data recorded by the terminal device when condition 5 is not met, if there is a deviation between the two, it indicates the impact of neighboring cell RRM measurement relaxation on the collection of the first measurement data. This allows the network to differentiate data collected under different conditions to avoid confusion.

[0190] It should be understood that when the terminal device is in a relaxed RRM measurement state in a neighboring cell, the first measurement data can reflect the approximate signal distribution of the neighboring cell, assisting in the initial planning and adjustment of network coverage. When the terminal device is not in a relaxed RRM measurement state in a neighboring cell, the first measurement data includes accurate and real-time measurement results, enabling the terminal device to switch to a neighboring cell with better signal in a timely and accurate manner based on the first measurement data, reducing the probability of dropped calls and handover failures, and optimizing the stability of network connectivity.

[0191] Condition 6: The time interval between when the terminal device meets the entry condition for LP-WUS monitoring and when it meets the exit condition for LP-WUS monitoring is less than or equal to the first threshold.

[0192] In one example, if the duration between when a terminal device meets the LP-WUS monitoring entry condition and when it meets the LP-WUS monitoring exit condition is less than or equal to a first threshold, or in other words, if the terminal device remains in the LP-WUS monitoring communication state for a short period, then the energy-saving effect of the terminal device is limited. When this condition is met, the terminal device records the first measurement data. This reflects the measurement results of the main receiver under this condition, and / or the measurement results of the low-power wake-up receiver. The network side can analyze the measurement data under this condition and optimize the corresponding parameters.

[0193] Optionally, the terminal device reporting the fulfillment of this condition (i.e., information indicating that condition 6 is met, or information indicating that condition 6 triggers the recording of the first measurement data) can be included in the first measurement data. This allows the network side to distinguish whether the LP-WUS monitoring state duration is too short, thus avoiding confusion. Furthermore, it assesses whether unreasonable LP-WUS monitoring entry and / or exit conditions would make it difficult for the terminal device to maintain LP-WUS monitoring and would degrade power-saving performance.

[0194] It should be understood that the first measurement data can reflect situations where the terminal device spends a short time in the communication state monitored by LP-WUS. Furthermore, based on the first measurement data recorded under this condition, the network side can analyze the reasons for the terminal device's communication state and take corresponding optimization and adjustment measures. For example, it can adjust the entry and exit conditions of LP-WUS monitoring, optimize network coverage, etc., to ensure that the LP-WUS monitoring mechanism can operate normally and effectively.

[0195] Condition 7: Within the first time interval, the number of times the terminal device meets the entry condition of LP-WUS monitoring is greater than or equal to the second threshold, or the number of times it meets the exit condition of LP-WUS monitoring is greater than or equal to the third threshold.

[0196] In one example, for a terminal device, within a first time interval, the number of times it meets the entry condition for LP-WUS monitoring is greater than or equal to a second threshold, or the number of times it meets the exit condition for LP-WUS monitoring is greater than or equal to a third threshold. Alternatively, within the first time interval, the number of times the terminal device is in LP-WUS monitoring state is greater than or equal to the second threshold, or the number of times it is in non-LP-WUS monitoring state is greater than or equal to the third threshold. Or, within the first time interval, the number of times the terminal device enters LP-WUS monitoring state is the first count and the first count is greater than or equal to the second threshold, or the number of times it leaves LP-WUS monitoring state is the second count and the second count is greater than or equal to the third threshold. Meeting this condition indicates that the LP-WUS state changes frequently. The first time interval can be configured by the network for the terminal device or it can be predefined; this scheme does not restrict this. When the terminal device meets this condition, it records the first measurement data, thus reflecting the measurement results of the main receiver under this condition, and / or the measurement results of the low-power wake-up receiver, to avoid confusion. The network side can analyze and optimize the corresponding parameters based on the measurement data under this condition.

[0197] Optionally, the terminal device reporting the fulfillment of this condition (i.e., information indicating that condition 7 is met, or information indicating that condition 7 triggers the recording of the first measurement data) can be included in the first measurement data. This allows the network side to distinguish whether frequent switching of LP-WUS monitoring state has occurred in the first measurement data, thus avoiding confusion. Furthermore, it allows for an assessment of whether unreasonable settings for LP-WUS monitoring entry and / or exit conditions would make it difficult for the terminal device to maintain LP-WUS monitoring state and would lead to a decrease in power-saving performance.

[0198] It should be understood that the first measurement data recorded by the terminal device when condition 7 is met can reflect the activity level and frequency of change of LP-WUS monitoring. Therefore, when the network side needs to analyze the reasons for frequent changes in the state of LP-WUS, it can use the first measurement data corresponding to this condition to analyze the reasons for the frequent changes in the state of LP-WUS and optimize the corresponding parameters.

[0199] Condition 8: The terminal device receives LP-WUS related group information and does not receive a paging instruction or paging pre-instruction.

[0200] In one example, when the terminal device receives LP-WUS-related group information but does not receive a paging indication or pre-paging indication, the terminal device records the first measurement data. This reflects the measurement data under the condition of invalid LP-WUS signal wake-up of the master receiver. The network side can analyze the measurement data under this condition and optimize the corresponding parameters.

[0201] Optionally, the terminal device may report the fulfillment of the condition (i.e., information indicating that condition 8 is met, or information indicating condition 8 that triggers the recording of the first measurement data), which may be included in the first measurement data. This may enable the network side to distinguish whether the first measurement data has resulted in an invalid LP-WUS signal waking up the main receiver, in order to avoid confusion.

[0202] It should be understood that when the terminal device meets condition 8, it indicates that the terminal device has experienced an invalid wake-up of the main receiver based on the LP-WUS signal. The network side can perform cause analysis and corresponding parameter optimization based on the first measurement data.

[0203] Condition 9: The number of times the terminal device receives LP-WUS-related group information within the second time interval and does not receive a paging indication or a paging pre-indication meets the fourth threshold.

[0204] In one example, if the number of times a terminal device receives LP-WUS-related group information within a second time interval and does not receive a paging indication or a pre-paging indication meets a fourth threshold, the terminal device records first measurement data if this condition is met. The second time interval can be configured by the network for the terminal device or predefined; this scheme does not impose any restrictions. This reflects measurement data under conditions where LP-WUS signal invalid wake-up of the master receiver occurs frequently. The network side can analyze the measurement data under this condition and optimize the corresponding parameters. Optionally, the terminal device reporting the satisfaction of this condition (i.e., information indicating that condition 9 is met, or information indicating condition 9 that triggers the recording of the first measurement data) can be included in the first measurement data. This allows the network side to distinguish whether frequent LP-WUS signal invalid wake-up of the master receiver has occurred, thus avoiding confusion.

[0205] It should be understood that when the terminal device meets condition 9 above, it indicates that there are frequent instances of not receiving paging instructions or paging pre-instructions, which leads to wasted power consumption of the terminal device. The first measurement data recorded by the terminal device when condition 9 is met can reflect the reasons for the frequent instances of not receiving paging instructions or paging pre-instructions. Furthermore, the network side can select the first measurement data based on this condition, and then analyze the reasons for the frequent invalid wake-ups based on the first measurement data, and optimize the relevant parameters.

[0206] Optionally, when collecting the first measurement data via MDT, the MDT can be a fast MDT or a recording MDT, and the first measurement configuration information can include one or more of conditions 1-9.

[0207] As can be seen from conditions 1-9 indicated by the first measurement configuration information above, at least one of the above conditions is related to LP-WUS. For example, it can control whether the terminal device records measurement data related to the LP-WUS state (the various states described above). In this case, the first measurement data recorded by the terminal device according to at least one condition can distinguish different states related to LP-WUS, so that the network device can distinguish the first measurement data collected in different states related to LP-WUS, and further reduce the possibility of data corruption.

[0208] The above is merely an exemplary description of the use of the conditions indicated by the first measurement configuration information. The conditions indicated by the first measurement configuration information can also be applied to other scenarios, and this application does not impose any restrictions on them.

[0209] S1003, The terminal device records the first measurement data.

[0210] In one possible implementation, when the first measurement configuration information indicates at least one condition for recording the first measurement data, the process of the terminal device recording the first measurement data in S902 above may include: the terminal device recording the first measurement data according to the first measurement configuration information. For example, the terminal device determines whether at least one condition indicated in the first measurement configuration information is met according to the first measurement configuration information. If at least one condition is met, the terminal device records the first measurement data and records the at least one condition that the terminal device satisfies when the first measurement data is satisfied.

[0211] The first measurement data can also indicate at least one condition in the first measurement configuration information that is met. Therefore, the first measurement data, while reflecting measurement data, can also reflect the conditions met by the terminal device when the measurement data was recorded. This allows for subsequent differentiation of the type of the first measurement data based on at least one condition in the first measurement configuration information indicated by the first measurement data, and for distinguishing whether the first measurement data is subject to deviations due to various possible states of the terminal device. This provides a reliable and accurate basis for network performance evaluation, optimization, and other related research.

[0212] The condition that the terminal device meets when recording the first measurement data can be included in the first measurement data, or it can be a separate indication that can be reported together with the first measurement data or reported separately, without restriction.

[0213] Optionally, in some embodiments, the specific implementation process of the terminal device recording the first measurement data according to the first measurement configuration information includes at least one of the following:

[0214] Implementation process 1: When the terminal device performs or does not perform a measurement based on a low-power signal, it records the first measurement data.

[0215] Implementation process 2: The terminal device records the first measurement data whether or not it performs LP-WUS monitoring.

[0216] Implementation process 3: When the terminal device performs or does not perform RRM measurement offloading of the serving cell, it records the first measurement data.

[0217] Implementation process 4: When the terminal device performs or does not perform RRM measurement relaxation of the serving cell, it records the first measurement data.

[0218] Implementation process 5: When the terminal device performs or does not perform RRM measurement relaxation in the neighboring cell, it records the first measurement data.

[0219] Implementation process 6: When the time between when the terminal device meets the entry condition of LP-WUS monitoring and when it meets the exit condition of LP-WUS monitoring is less than or equal to the first threshold, the first measurement data is recorded.

[0220] Implementation process 7: When the number of times the terminal device meets the entry condition of LP-WUS monitoring within the first time interval is greater than or equal to the second threshold, or the number of times it meets the exit condition of LP-WUS monitoring is greater than or equal to the third threshold, the first measurement data is recorded.

[0221] In the implementation process 8, when the terminal device receives the LP-WUS related group information but does not receive a paging indication or a paging pre-indication, it records the first measurement data.

[0222] Alternatively, in process 9, when the terminal device receives LP-WUS-related group information within the second time interval and the number of times it does not receive a paging indication or a paging pre-indication meets the fourth threshold, it records the first measurement data.

[0223] S1004, The terminal device sends the first measurement data. Correspondingly, the first network device receives the first measurement data.

[0224] Optionally, the specific implementation process of S1004 above can be referred to the embodiment shown in S903, which will not be repeated here.

[0225] Optionally, the terminal device can directly send the first measurement data to the connected first network device, and the first network device receives the first measurement data from the terminal device. Alternatively, the terminal device can send the first measurement data to the connected third network device, and the third network device receives the first measurement data. Furthermore, the third network device sends the first measurement data to the first network device, and the first network device receives the first measurement data from the third network device.

[0226] Optionally, when the first network device includes a first CU module and a first DU module, after receiving the first measurement data, the first CU module in the first network device can send the first measurement data to the first DU module in the first network device, so that the first DU module can perform network performance evaluation or optimization based on the first measurement data.

[0227] In the above technical solution, at least one condition for recording the first measurement data can be configured by the network side.

[0228] In some embodiments, when the terminal device is in a mobile state, it may reside in an area covered by different network devices. In this case, the network device sending the LP-WUS configuration information and the network device sending the first measurement configuration information may be the same or different, and this application does not impose any restrictions on this.

[0229] For example, the following describes, in conjunction with the embodiments shown in S1001-S1004, the implementation scheme of sending LP-WUS configuration information and first measurement configuration information by different network devices when the terminal device resides in the area covered by different network devices through steps 01-05.

[0230] Step 01: The second network device sends first measurement configuration information to the terminal device. Correspondingly, the terminal device receives the first measurement configuration information from the second network device. The first measurement configuration information indicates at least one condition for recording measurement data.

[0231] Specifically, the implementation process of step 01 above can be referred to the embodiment shown in S1002, and will not be repeated here.

[0232] Step 02: The first network device sends LP-WUS configuration information to the terminal device. Correspondingly, the terminal device receives the LP-WUS configuration information from the first network device.

[0233] Optionally, the specific implementation process of step 02 above can be referred to the embodiment shown in S1001, which will not be repeated here.

[0234] Step 03: The terminal device can determine whether it is in LP-WUS-related status based on the LP-WUS configuration information.

[0235] In one possible implementation, the terminal device can determine whether to enter LP-WUS monitoring, exit LP-WUS monitoring, perform RRM measurement offloading of the serving cell, perform RRM measurement relaxation of the serving cell, or perform RRM measurement relaxation of the neighboring cell based on LP-WUS configuration information.

[0236] Step 04: The terminal device records the first measurement data according to the first measurement configuration information.

[0237] Specifically, the implementation of step 04 above is described in the embodiment shown in S1003, and will not be repeated here.

[0238] Step 05: The terminal device sends the first measurement data. Correspondingly, the network device receives the first measurement data. The first measurement data may also indicate at least one condition from the first measurement configuration information that is satisfied.

[0239] Specifically, the implementation of step 05 above is described in the embodiment shown in S1004, and will not be repeated here.

[0240] In the technical solutions provided in steps 01-05 above, when the terminal is in a mobile state, the terminal device will establish connections with different network devices or camp on cells managed by different network devices. Therefore, the terminal device can perform operations such as receiving first measurement configuration information, LP-WUS configuration information, and sending first measurement data through different network devices.

[0241] Furthermore, if the terminal device is instructed to record at least one condition in the first measurement configuration information, the terminal device may record the condition satisfied when recording the first measurement data, so that the network side can distinguish the first measurement data according to the condition.

[0242] Example 2:

[0243] As a possible embodiment of this application, referring to FIG9 and FIG11, in the communication method provided by this application, the process of the terminal device recording the first measurement data including LP-WUS information can be implemented by S1101-S1104.

[0244] S1101, The first network device sends LP-WUS configuration information. Correspondingly, the terminal device receives the LP-WUS configuration information.

[0245] Optionally, the specific implementation process of the first network device sending LP-WUS configuration information in S1101 above can be referred to the embodiment shown in S1001, and will not be repeated here.

[0246] S1102, the second network device sends the first measurement configuration information. Correspondingly, the terminal device receives the first measurement configuration information.

[0247] Specifically, when the first measurement data is collected through recording MDT, the first measurement configuration information may include trigger recording conditions (e.g., time trigger conditions, periodic trigger conditions), recording duration, and recording area to instruct the terminal device to perform recording MDT in RRC idle state and RRC inactive state; when the first measurement data is collected through fast MDT, the first measurement configuration information may include location information, recording area range information, etc., in addition to trigger recording conditions, recording duration, and recording area to instruct the terminal device to perform fast MDT in a specific area.

[0248] Optionally, the network device may configure at least one condition related to LP-WUS for the terminal device to record the first measurement data (that is, the first measurement configuration information may include at least one condition related to LP-WUS for the terminal device to record the first measurement data), or it may not configure at least one condition related to LP-WUS for the terminal device to record the first measurement data (that is, the first measurement configuration information may not include at least one condition related to LP-WUS for the terminal device to record the first measurement data). Embodiment 2 does not limit the first measurement configuration information.

[0249] Optionally, if the first measurement configuration information includes at least one condition related to LP-WUS for the terminal device to record the first measurement data, the description of the first measurement configuration information can be referred to the embodiment shown in S1002 above, and will not be repeated here.

[0250] It should be noted that the embodiments of this application do not impose any restrictions on the execution order of S1101 and S1102. That is, S1101 can be executed before S1102, S1101 can be executed after S1102, and S1101 can also be executed simultaneously with S1102.

[0251] S1103, The terminal device records the first measurement data.

[0252] Optionally, when recording the first measurement data, the terminal device may record at least one indication message to indicate the state of the terminal device when recording the first measurement data (these states may also be related to LP-WUS).

[0253] Optionally, the first measurement data may also include at least one of the following indications:

[0254] Instruction 1: Cell identifier information for receiving LP-WUS configuration information.

[0255] In one example, the terminal device can record "cell identification information for receiving LP-WUS configuration information" in the first measurement data. The network side can then use this information to clarify the implementation status of LP-WUS configuration in different cells. For example, the network side can determine whether the LP-WUS configuration of the target cell has been correctly transmitted to the terminal device, and which cells are using LP-WUS technology, thereby optimizing the management of LP-WUS configurations in different cells.

[0256] Instruction Message 2: Instructions on whether the terminal device should perform LP-WUS monitoring.

[0257] In one example, the information instructing the terminal device to perform LP-WUS monitoring can characterize the first measurement data as measurement data recorded by the terminal device while performing LP-WUS monitoring, or in other words, while in LP-WUS monitoring state.

[0258] The information instructing the terminal device not to perform LP-WUS monitoring indicates that the first measurement data was recorded by the terminal device without performing LP-WUS monitoring, or in other words, not under LP-WUS monitoring conditions. Corresponding to this instruction, the first measurement data was measured and recorded without LP-WUS monitoring or without the LP-WUS monitoring mechanism being executed. This first measurement data may differ from the first measurement data recorded under LP-WUS monitoring or with the LP-WUS monitoring mechanism being executed. If a difference exists, it can be used to explain the impact of whether or not LP-WUS monitoring is performed on the first measurement data, allowing the network to distinguish between first measurement data collected under different communication states to avoid confusion.

[0259] It should be understood that, corresponding to the information instructing the terminal device to perform LP-WUS monitoring, the first measurement data can reflect various aspects of the LP-WUS signal during actual operation, such as the stability and accuracy of the LP-WUS signal, and the interaction between the terminal device and the network side during monitoring. Furthermore, the network side can perform network analysis based on the first measurement data corresponding to this instruction information.

[0260] Instruction 3: Information about the receiver used by the terminal device to perform RRM measurements of the serving cell, wherein the receiver is a low-power receiver or a main receiver.

[0261] In one example, the terminal device uses the recorded indication information to inform the network side whether the RRM measurement in the serving cell is performed by the low-power wake-up receiver or by the main receiver, thus implicitly indicating whether to perform an RRM measurement offload operation.

[0262] In other words, the receiver indicated by instruction information 3 is a low-power receiver, and the first measurement data is the measurement data recorded when the terminal device performs the RRM measurement offload operation, or in other words, when it is in the RRM measurement offload state.

[0263] The receiver indicated by instruction information 3 is the main receiver. The first measurement data is the measurement data recorded by the terminal device when it is not performing the RRM measurement offload operation, or in other words, when it is not in the RRM measurement offload operation state.

[0264] Thus, the first measurement data may deviate depending on the receiver indicated in the instruction information. If there is a deviation, the difference can be used to explain the impact of whether or not RRM measurement offloading information is performed on the first measurement data, so that the network can distinguish the first measurement data collected using different communication states to avoid confusion.

[0265] Instruction Message 4: Instruction message indicating whether the terminal device should perform RRM measurement relaxation for the serving cell.

[0266] In one example, information instructing the terminal device to perform RRM measurement relaxation of the serving cell can indicate that the first measurement data is measurement data recorded when the terminal device is performing RRM measurement relaxation of the serving cell, or when it is in a state of RRM measurement relaxation of the serving cell. Information instructing the terminal device not to perform RRM measurement relaxation of the serving cell can indicate that the first measurement data is measurement data recorded when the terminal device is not performing RRM measurement relaxation of the serving cell, or when it is not in a state of performing RRM measurement relaxation of the serving cell. This avoids the problems of measurement data contamination and / or measurement data ambiguity caused by poor measurement performance and accuracy depending on whether the device is in a state of RRM measurement relaxation of the serving cell.

[0267] Optionally, based on the aforementioned indication information 4, the network side can determine that the first measurement data is the measurement data recorded by the terminal device under the communication state corresponding to indication information 4. Compared with the measurement data recorded by the terminal device under the communication state without indication information 4, if there is a deviation between the two, it indicates the impact of the RRM measurement relaxation of the serving cell on the collection of the first measurement data, so that the network can distinguish the data collected under different conditions to avoid confusion.

[0268] Instruction Message 5: Instruction message indicating whether the terminal device should perform RRM measurement relaxation in the neighboring cell.

[0269] In one example, information instructing the terminal device to perform RRM measurement relaxation in the neighboring cell can indicate that the first measurement data was recorded when the terminal device performed RRM measurement relaxation in the neighboring cell, or when it was in a state of RRM measurement relaxation in the neighboring cell. Conversely, information instructing the terminal device not to perform RRM measurement relaxation in the neighboring cell can indicate that the first measurement data was recorded when the terminal device did not perform RRM measurement relaxation in the neighboring cell, or when it was not in a state of RRM measurement relaxation in the neighboring cell. This avoids the problems of measurement data contamination and / or fuzzy measurement data caused by poor measurement performance and accuracy depending on whether the device is in a state of RRM measurement relaxation in the neighboring cell.

[0270] Optionally, based on the aforementioned indication information 5, the network side can determine that the first measurement data is the measurement data recorded by the terminal device under the communication state corresponding to indication information 5. Compared with the measurement data recorded by the terminal device under the communication state without indication information 5, if there is a deviation between the two, it indicates the impact of the relaxation of RRM measurement in the neighboring cells of the serving cell on the collection of the first measurement data, so that the network can distinguish the data collected under different conditions to avoid confusion.

[0271] Instruction 6 indicates that the terminal device has received LP-WUS related group information, but has not received paging indication or paging pre-indication information.

[0272] In one example, the aforementioned indication information can indicate that the first measurement data was recorded by the terminal device when it received LP-WUS-related group information but did not receive a paging indication or a pre-paging indication. Thus, the first measurement data indicates a situation where the LP-WUS signal invalidally wakes up the main receiver. The network side can distinguish whether the above situation has occurred based on the first measurement data, avoiding confusion. Furthermore, the network side can analyze and optimize the corresponding parameters based on the measurement data under this condition. Optionally, according to the aforementioned indication information 6, the network side can determine that the first measurement data is measurement data recorded by the terminal device under the communication state corresponding to indication information 6. Compared to measurement data recorded by the terminal device under a communication state without indication information 6, if there is a discrepancy between the two, the network can distinguish data collected under different situations or states to avoid confusion.

[0273] Instruction Message 7 indicates the number of times the terminal device received LP-WUS-related group information within the second time interval and did not receive paging instructions or paging pre-instructions.

[0274] In one example, the above indication information indicates the number of times the terminal device received LP-WUS-related group information within the second time interval but did not receive a paging indication or a paging pre-indication. Alternatively, it can indicate whether the number of times within the second time interval is greater than or equal to the fourth threshold mentioned above, thereby indicating whether there has been a frequent failure to receive a paging indication or a paging pre-indication. If so, it indicates the possibility of wasted power consumption of the terminal device, and the network side needs to analyze the reasons for frequent invalid wake-ups and perform optimization of the corresponding parameters.

[0275] Instruction Message 8: Information indicating whether the terminal device meets the corresponding entry conditions based on the measurement results of the low-power receiver and / or the main receiver.

[0276] In one example, the aforementioned indication information may specifically be: information indicating whether the terminal device meets the corresponding entry conditions based on the measurement results of the low-power wake-up receiver and / or the main receiver when the entry conditions for LP-WUS monitoring are not met. More specifically, it may indicate whether the measurement results based on the low-power receiver meet the entry conditions for the low-power receiver, and / or whether the measurement results based on the main receiver meet the entry conditions for the main receiver.

[0277] Since the entry conditions for LP-WUS monitoring are related to whether the main receiver's measurement results meet the corresponding entry conditions and / or whether the low-power wake-up receiver meets the corresponding entry conditions, the network can analyze the reasons why the LP-WUS monitoring entry conditions are not met based on this indication information.

[0278] Instruction information 9: The time interval between the moment the terminal device triggers the main receiver and the moment it receives the paging instruction, or the time interval between the moment the main receiver is triggered and the moment random access is initiated.

[0279] In one example, the network side can evaluate the efficiency of network signaling and resource allocation based on this time interval.

[0280] Instruction information 10: The type of low-power receiver configured in the terminal device; the type is a low-power receiver based on orthogonal frequency division multiplexing, or a low-power receiver based on on / off keying.

[0281] It should be noted that when the cell supports the above two types of receivers, the entry and exit conditions for each type of receiver are configured independently. The terminal device can report the entry and exit conditions for different types of receivers in the network, so that the network side can analyze and optimize the configuration conditions for the type of receiver used by the terminal.

[0282] Instruction Message 11: Measurement results of the terminal device based on low-power signals, and / or measurement relaxation results in the serving cell or neighboring cells.

[0283] In one example, the terminal device can accurately identify the first measurement data related to RRM measurement relaxation based on the measurement results, thereby providing precise data support for resource allocation, network performance estimation, optimization, etc.

[0284] Instruction information 12 indicates that the terminal device is configured to be based on core network packets, or that the terminal device is configured to be based on packets identified by the terminal device.

[0285] In one example, the indication information may also indicate that the information contained in the LP-WUS is group information or information specific to a particular terminal device. Specifically, the information contained in the LP-WUS is associated with the packets configured for the terminal device. When the terminal device is configured for core network-based packets, the information contained in the LP-WUS is group information; when the terminal device is configured for terminal identifier-based packets, the information contained in the LP-WUS is information specific to a particular terminal device.

[0286] As a supplementary explanation, the "at least one indication information that the first measurement data also includes" recorded by the terminal device in S1103 above can be included in the first measurement data, or it can be reported as a separate piece of information together with the first measurement data, or it can be reported separately. This application does not limit this.

[0287] S1104. The terminal device sends the first measurement data. Correspondingly, the first network device receives the first measurement data.

[0288] The first measurement data also includes at least one indication message to indicate the state of the terminal device when recording the first measurement data.

[0289] Optionally, the specific implementation process of S1104 above can be referred to the embodiment shown in S1004, and will not be repeated here.

[0290] In the above technical solution, the terminal device can record indication information in a predefined manner according to the protocol, and the indication information can indicate the state of the terminal device when recording the first measurement data (these states can also be related to LP-WUS).

[0291] Furthermore, at least one indication information included in the first measurement data is related to LP-WUS, such as describing the state related to LP-WUS. In this case, the network side can distinguish different states related to LP-WUS according to the indication information included in the first measurement data, so that the network device can distinguish the measurement data collected in different states related to LP-WUS, further reducing the possibility of data contamination.

[0292] In some embodiments, when the terminal device is in a mobile state, it may reside in an area covered by different network devices. In this case, the network device sending the LP-WUS configuration information and the network device sending the first measurement configuration information may be the same or different, and this application does not impose any restrictions on this.

[0293] For example, the following describes, in conjunction with the embodiments shown in S1101-S1104 above, an exemplary implementation scheme for different network devices to send LP-WUS configuration information and first measurement configuration information when the terminal device resides in an area covered by different network devices, through steps 11-15.

[0294] Step 11: The second network device sends first measurement configuration information to the terminal device. Correspondingly, the terminal device receives the first measurement configuration information from the second network device. The first measurement configuration information does not include at least one condition instructing the terminal device to record the first measurement data.

[0295] Optionally, the specific implementation process of step 11 above can be referred to the embodiment shown in S1102, which will not be repeated here.

[0296] Step 12: The first network device sends LP-WUS configuration information to the terminal device. Correspondingly, the terminal device receives the LP-WUS configuration information from the first network device.

[0297] Optionally, the specific implementation process of step 12 above can be referred to the embodiment shown in S1101, which will not be repeated here.

[0298] Step 13: The terminal device can determine whether it is in the relevant LP-WUS situation based on the LP-WUS configuration information.

[0299] In one possible implementation, the terminal device can determine whether to enter LP-WUS monitoring, exit LP-WUS monitoring, perform RRM measurement offloading of the serving cell, perform RRM measurement relaxation of the serving cell, and perform RRM measurement relaxation of neighboring cells based on LP-WUS configuration information.

[0300] Step 14: The terminal device records the first measurement data.

[0301] Optionally, the specific implementation of step 14 above can be referred to the embodiment shown in S1103, which will not be repeated here.

[0302] Step 15: The terminal device sends the first measurement data. Correspondingly, the network device receives the first measurement data.

[0303] Optionally, the specific implementation of step 15 above can be referred to the embodiment shown in S1104, which will not be repeated here.

[0304] In the technical solutions described in steps 11-15 above, when the terminal is in a mobile state, the terminal device will establish connections with different network devices or camp on cells managed by different network devices. Therefore, the terminal device can perform operations such as receiving first measurement configuration information, LP-WUS configuration information, and sending first measurement data through different network devices.

[0305] The method provided in this application has been described above. In addition, this application also provides a communication device for implementing the functions described in the above method embodiments.

[0306] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0307] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0308] Figure 12 shows a schematic diagram of a communication device 120. The communication device 120 includes a processing module 1201 and a transceiver module 1202. This communication device 120 can be used to implement the functions of the aforementioned terminal equipment or network equipment.

[0309] In some embodiments, the communication device 120 may further include a storage module (not shown in FIG12) for storing program instructions and data.

[0310] In some embodiments, the transceiver module 1202, also referred to as a transceiver unit, is used to implement sending and / or receiving functions. The transceiver module 1202 may consist of a transceiver circuit, a transceiver, a transceiver unit, or a communication interface.

[0311] In some embodiments, the transceiver module 1202 may include a receiving module and a sending module, respectively configured to perform the receiving and sending steps performed by the terminal device or network device in the above method embodiments, and / or other processes to support the technology described herein; the processing module 1201 may be configured to perform the processing steps performed by the terminal device or network device in the above method embodiments, and / or other processes to support the technology described herein.

[0312] When the communication device 120 is used to implement the functions of a terminal device:

[0313] In one possible implementation, the transceiver module 1202 is used to receive low-power wake-up signal LP-WUS configuration information; the processing module 1201 is used to record first measurement data; and the transceiver module 1202 is also used to send the first measurement data.

[0314] In one possible implementation, the transceiver module 1202 is further configured to receive first measurement configuration information, the first measurement configuration information instructing the terminal device to record at least one condition for recording the first measurement data; the processing module 1201 is specifically configured to record the first measurement data according to the first measurement configuration information.

[0315] In one possible implementation, the processing module 1201 is specifically configured to: record first measurement data when the terminal device performs or does not perform measurements based on low-power signals; record first measurement data when the terminal device performs or does not perform LP-WUS monitoring; record first measurement data when the terminal device performs or does not perform RRM measurement offloading of the serving cell; record first measurement data when the terminal device performs or does not perform RRM measurement relaxation of the serving cell; record first measurement data when the terminal device performs or does not perform RRM measurement relaxation of neighboring cells; and record first measurement data when the terminal device meets the entry conditions for LP-WUS monitoring and the conditions for LP-WUS monitoring. When the time interval between exit conditions is less than or equal to a first threshold, the first measurement data is recorded; when the number of times the terminal device meets the entry conditions of LP-WUS monitoring within a first time interval is greater than or equal to a second threshold, or the number of times it meets the exit conditions of LP-WUS monitoring is greater than or equal to a third threshold, the first measurement data is recorded; when the terminal device receives LP-WUS-related group information but does not receive a paging indication or a paging pre-indication, the first measurement data is recorded; or, when the number of times the terminal device receives LP-WUS-related group information but does not receive a paging indication or a paging pre-indication within a second time interval meets a fourth threshold, the first measurement data is recorded.

[0316] In one possible implementation, the processing module 1201 is specifically configured to: record first measurement data when performing MDT measurement recording, wherein the MDT measurement is either a recording MDT or a fast MDT.

[0317] When the communication device 120 is used to implement the functions of a network device:

[0318] In one possible implementation, the transceiver module 1202 is used to send LP-WUS configuration information and receive first measurement data.

[0319] In one possible implementation, the transceiver module 1202 is further configured to send first measurement configuration information, which is used to instruct the terminal device to record at least one condition for the first measurement data.

[0320] In one possible implementation, the network device includes a first centralized unit (CU) and a first distributed unit (DU), wherein the first CU sends first measurement data to the first DU via a transceiver module 1202.

[0321] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0322] In this application, the communication device 120 can be presented in an integrated manner by dividing it into various functional modules. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.

[0323] In some embodiments, when the communication device 120 in FIG12 is a chip or chip system, the function / implementation process of the transceiver module 1202 can be implemented through the input / output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 1201 can be implemented through the processor (or processing circuit) of the chip or chip system.

[0324] Since the communication device 120 provided in this embodiment can execute the above method, the technical effects it can achieve can be referred to the above method embodiment, and will not be repeated here.

[0325] As a possible product form, the terminal device or network device described in the embodiments of this application can be implemented using the following: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

[0326] As another possible product form, the terminal device or network device described in this application embodiment can be implemented using a general bus architecture. For ease of explanation, refer to FIG13, which is a schematic diagram of the structure of a communication device 1300 provided in an embodiment of this application. The communication device 1300 includes a processor 1301 and a transceiver 1302. The communication device 1300 can be a terminal device, or a chip or chip system therein; or, the communication device 1300 can be a network device, or a chip or module therein. FIG13 only shows the main components of the communication device 1300. In addition to the processor 1301 and transceiver 1302, the communication device may further include a memory 1303 and input / output devices (not shown in the figure).

[0327] Optionally, the processor 1301 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs, thereby implementing the methods provided in the above-described method embodiments. The memory 1303 is mainly used to store software programs and data. The transceiver 1302 may include a radio frequency (RF) circuit and an antenna. The RF circuit is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. Input / output devices, such as touch screens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0328] Optionally, the processor 1301, transceiver 1302, and memory 1303 can be connected via a communication bus.

[0329] When the communication device is powered on, the processor 1301 can read the software program in the memory 1303, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1301 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit then performs RF processing on the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1301. The processor 1301 converts the baseband signal into data and processes the data.

[0330] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0331] In some embodiments, those skilled in the art will recognize that the above-described communication device 120 can take the form of the communication device 1300 shown in FIG13 in terms of hardware implementation.

[0332] As an example, the function / implementation of the processing module 1201 in Figure 12 can be achieved by the processor 1301 in the communication device 1300 shown in Figure 13 calling computer execution instructions stored in the memory 1303. The function / implementation of the transceiver module 1202 in Figure 12 can be achieved by the transceiver 1302 in the communication device 1300 shown in Figure 13.

[0333] As another possible product form, the terminal device or network device in this application may adopt the composition structure shown in FIG14, or include the components shown in FIG14. FIG14 is a schematic diagram of the composition of a communication device 1400 provided in this application. The communication device 1400 may be a terminal device or a chip or system-on-a-chip in a terminal device; or, it may be a network device or a module or chip or system-on-a-chip in a network device.

[0334] As shown in FIG14, the communication device 1400 includes at least one processor 1401 and at least one communication interface (FIG14 is merely an example illustrating the inclusion of a communication interface 1404 and a processor 1401). Optionally, the communication device 1400 may further include a communication bus 1402 and a memory 1403.

[0335] Processor 1401 can be a general-purpose central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a PLD, or any combination thereof. Processor 1401 can also be other devices with processing capabilities, such as circuits, devices, or software modules, without limitation. As one possible implementation, processor 1401 may include one or more CPUs, such as CPU0 and CPU1 in Figure 14.

[0336] Communication bus 1402 is used to connect different components in communication device 1400, enabling communication between them. Communication bus 1402 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 14, but this does not indicate that there is only one bus or one type of bus.

[0337] Communication interface 1404 is used for communicating with other devices or communication networks. For example, communication interface 1404 can be a module, circuit, transceiver, or any device capable of communication. Optionally, the communication interface 1404 can also be an input / output interface located within processor 1401, used to implement signal input and signal output for the processor.

[0338] The memory 1403 may be a device with storage function, used to store instructions and / or data. The instructions may be computer programs.

[0339] For example, the memory 1403 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and / or instructions; it may also be a random access memory (RAM) or other type of dynamic storage device capable of storing information and / or instructions; it may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, etc., without limitation.

[0340] It should be noted that the memory 1403 may exist independently of the processor 1401 or may be integrated with the processor 1401. The memory 1403 may be located within or outside the communication device 1400, without limitation. The processor 1401 may be used to execute the instructions stored in the memory 1403 to implement the methods provided in the following embodiments of this application.

[0341] As an optional implementation, the communication device 1400 may also include an output device 1405 and an input device 1406. The output device 1405 communicates with the processor 1401 and can display information in various ways. For example, the output device 1405 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 1406 communicates with the processor 1401 and can receive user input in various ways. For example, the input device 1406 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0342] In some embodiments, those skilled in the art will recognize that the communication device 120 shown in FIG12 can take the form of the communication device 1400 shown in FIG14 in terms of hardware implementation.

[0343] As an example, the function / implementation process of the processing module 1201 in Figure 12 can be implemented by the processor 1401 in the communication device 1400 shown in Figure 14 calling computer execution instructions stored in the memory 1403. The function / implementation process of the transceiver module 1202 in Figure 12 can be implemented by the communication interface 1404 in the communication device 1400 shown in Figure 14.

[0344] It should be noted that the structure shown in Figure 14 does not constitute a specific limitation on the terminal device or network device. For example, in other embodiments of this application, the terminal device or network device may include more or fewer components than shown in the figure, or combine some components, or split some components, or have different component arrangements. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0345] In some embodiments, this application also provides a communication device, which includes a processor for implementing the methods in any of the above method embodiments.

[0346] As one possible implementation, the communication device also includes a memory. This memory stores necessary computer programs and data. The computer program may include instructions, which a processor can invoke to instruct the communication device to execute the methods described in any of the above method embodiments. Alternatively, the memory may not be present in the communication device.

[0347] As another possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, used to receive computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmit them to the processor.

[0348] As another possible implementation, the communication device also includes a communication interface for communicating with modules outside the communication device.

[0349] It is understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete devices. This application does not specifically limit this.

[0350] This application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a computer, implements the functions of any of the above-described method embodiments.

[0351] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0352] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0353] It is understood that the systems, apparatuses, and methods described in this application can also 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 couplings or direct couplings or communication connections shown or discussed may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

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

[0355] 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.

[0356] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This 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 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 accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive (SSD)). In embodiments of this application, the computer may include the aforementioned apparatus.

[0357] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0358] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of this application. Accordingly, this specification and drawings are merely illustrative descriptions of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method characterized by comprising: The method comprises: receiving low-power wake-up signal, LP-WUS, configuration information; recording first measurement data; sending the first measurement data.

2. The method of claim 1, wherein, The method further comprises: receiving first measurement configuration information, the first measurement configuration information indicating at least one condition for the terminal device to record first measurement data; the recording of the first measurement data comprises: recording the first measurement data according to the first measurement configuration information.

3. The method of claim 2, wherein, The first measurement configuration information indicates at least one condition as follows: whether the terminal device records measurement result information performed based on a low-power signal, wherein the low-power signal comprises a LP-WUS and / or a low-power synchronization signal, LP-SS; whether the terminal device performs LP-WUS monitoring; whether the terminal device performs radio resource management, RRM, measurement offloading of a serving cell; whether the terminal device performs RRM measurement relaxation of the serving cell; whether the terminal device performs RRM measurement relaxation of a neighbor cell; a time length between when the terminal device meets an entering condition of LP-WUS monitoring and when the terminal device meets an exiting condition of LP-WUS monitoring is less than or equal to a first threshold value; a first number of times that the terminal device meets the entering condition of LP-WUS monitoring within a first time interval is greater than or equal to a second threshold value, or a second number of times that the terminal device meets the exiting condition of LP-WUS monitoring is greater than or equal to a third threshold value; the terminal device receives group information related to a LP-WUS, and does not receive a paging indication or a paging pre-indication; a number of times that the terminal device receives group information related to a LP-WUS within a second time interval and does not receive the paging indication or the paging pre-indication meets a fourth threshold value.

4. The method of claim 3, wherein, The recording of the first measurement data comprises at least one of the following: the terminal device records the first measurement data when performing or not performing measurement based on a low-power signal; the terminal device records the first measurement data when performing or not performing LP-WUS monitoring; the terminal device records the first measurement data when performing or not performing RRM measurement offloading of a serving cell; the terminal device records the first measurement data when performing or not performing RRM measurement relaxation of the serving cell; the terminal device records the first measurement data when performing or not performing RRM measurement offloading in a neighbor cell; the terminal device records the first measurement data when a time length between when the terminal device meets an entering condition of LP-WUS monitoring and when the terminal device meets an exiting condition of LP-WUS monitoring is less than or equal to a first threshold; the terminal device records the first measurement data when a first number of times that the terminal device meets the entering condition of LP-WUS monitoring within a first time interval is greater than or equal to a second threshold value, or a second number of times that the terminal device meets the exiting condition of LP-WUS monitoring is greater than or equal to a third threshold value; the terminal device records the first measurement data when the terminal device receives group information related to a LP-WUS and does not receive a paging indication or a paging pre-indication; or, The terminal device records the first measurement data when the terminal device receives the group information related to the LP-WUS in a second time interval and the number of times that the terminal device does not receive the paging indication or the paging pre-indication satisfies a fourth threshold.

5. The method according to any one of claims 1 to 4, characterized in that, The first measurement data further indicates that at least one condition in the first measurement configuration information is satisfied.

6. The method according to any one of claims 1 to 5, characterized in that, The first measurement data further includes at least one of the following: cell identification information of a cell receiving the LP-WUS configuration information; information indicating whether the terminal device performs LP-WUS monitoring; information indicating a receiver of the terminal device for performing RRM measurement of a serving cell, wherein the receiver is a low-power consumption receiver or a main receiver; information indicating whether the terminal device performs RRM measurement relaxation of the serving cell; information indicating whether the terminal device performs RRM measurement relaxation of a neighbor cell; information indicating that the terminal device receives the group information related to the LP-WUS and does not receive the paging indication or the paging pre-indication; information indicating that the terminal device receives the group information related to the LP-WUS in a second time interval and the number of times that the terminal device does not receive the paging indication or the paging pre-indication satisfies a fourth threshold; information indicating whether the terminal device satisfies a corresponding entering condition based on a measurement result of a low-power consumption receiver and / or a main receiver; a time interval between a time when the terminal device triggers the main receiver and a time when the terminal device receives the paging indication, or a time interval between a time when the terminal device triggers the main receiver and a time when the terminal device initiates random access; a type of the low-power consumption receiver configured by the terminal device, wherein the type is an orthogonal frequency division multiplexing-based low-power consumption receiver or an on-off keying-based low-power consumption receiver; a measurement result of the terminal device based on a low-power consumption signal, and / or a measurement relaxation result of the serving cell or the neighbor cell; information indicating that the terminal device is configured to be grouped based on a core network, or the terminal device is configured to be grouped based on an identity of the terminal device.

7. The method according to any one of claims 1 to 6, characterized in that, The recording of the first measurement data includes: recording the first measurement data when performing a recording of a minimization of drive test (MDT) measurement, wherein the MDT measurement is a logged MDT or a fast MDT.

8. A communication method characterized by comprising: The method includes: sending the LP-WUS configuration information; receiving the first measurement data.

9. The method of claim 8, wherein, The method further includes: sending first measurement configuration information, wherein the first measurement configuration information is used to indicate at least one condition for the terminal device to record the first measurement data.

10. The method of claim 9, wherein, The first measurement configuration information indicates at least one of the following: whether the terminal device records a measurement result based on a low-power consumption signal, wherein the low-power consumption signal includes the LP-WUS and / or the LP-SS; whether the terminal device performs LP-WUS monitoring; whether the terminal device performs RRM measurement offloading of a serving cell; whether the terminal device performs RRM measurement relaxation of the serving cell; whether the terminal device performs RRM measurement relaxation of a neighbor cell; a time length between when the terminal device satisfies an entering condition of the LP-WUS monitoring and when the terminal device satisfies an exiting condition of the LP-WUS monitoring is less than or equal to a first threshold. a first number of times that the terminal device satisfies an entering condition of the LP-WUS monitoring in a first time interval is greater than or equal to a second threshold, or a second number of times that the terminal device satisfies an exiting condition of the LP-WUS monitoring is greater than or equal to a third threshold; the terminal device receives group information related to LP-WUS, and does not receive a paging indication or a paging pre-indication; a number of times that the terminal device receives group information related to LP-WUS in a second time interval and does not receive the paging indication or the paging pre-indication satisfies a fourth threshold.

11. The method according to any one of claims 8-10, characterized in that, the first measurement data further indicates at least one condition in the first measurement configuration information that is satisfied.

12. The method according to any one of claims 8-11, characterized in that, the first measurement data further includes at least one of: cell identification information of a cell receiving LP-WUS configuration information; information indicating whether the terminal device performs LP-WUS monitoring; information indicating a receiver of the terminal device for performing RRM measurement of a serving cell, wherein the receiver is a low-power consumption receiver or a main receiver; information indicating whether the terminal device performs RRM measurement relaxation of the serving cell; information indicating whether the terminal device performs RRM measurement relaxation of a neighbor cell; information indicating that the terminal device receives group information related to LP-WUS, and does not receive a paging indication or a paging pre-indication; information indicating a number of times that the terminal device receives group information related to LP-WUS in a second time interval and does not receive the paging indication or the paging pre-indication; information indicating whether the terminal device satisfies a corresponding entering condition based on a measurement result of a low-power consumption receiver and / or a main receiver; a time interval between a time when the terminal device triggers a main receiver and a time when a paging indication is received, or a time interval between a time when the terminal device triggers the main receiver and a time when a random access is initiated; a type of a low-power consumption receiver configured by the terminal device, wherein the type is an orthogonal frequency division multiplexing-based low-power consumption receiver or an on-off keying-based low-power consumption receiver; a measurement result of a low-power consumption signal by the terminal device, and / or a measurement relaxation result of the serving cell or the neighbor cell; information indicating that the terminal device is configured to be grouped based on a core network, or the terminal device is configured to be grouped based on an identity of the terminal device.

13. The method of any one of claims 8-12, wherein: the network device comprises a first centralized unit (CU) and a first distributed unit (DU), and the method further comprises: the first CU sending the first measurement data to the first DU.

14. The method of any one of claims 8-13, wherein: the first measurement data is measurement data recorded by the terminal device when performing a record of a MDT measurement, and the MDT measurement is a record MDT or a fast MDT.

15. A communications device, characterized by the communication apparatus comprises a module for performing the method of any one of claims 1-7, or a module for performing the method of any one of claims 8-14.

16. A communications device, characterized by The communication device comprises a processor; the processor is configured to run computer programs or instructions, so that the communication device performs the method according to any one of claims 1-7, or so that the communication device performs the method according to any one of claims 8-14.

17. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions or programs, when the computer instructions or programs are run on a computer, so that the method according to any one of claims 1-7 is performed, or so that the method according to any one of claims 8-14 is performed.

18. A computer program product, characterised in that, The computer program product comprises computer instructions; when part or all of the computer instructions are run on a computer, so that the method according to any one of claims 1-7 is performed, or so that the method according to any one of claims 8-14 is performed.

Images