Communication method and apparatus

Abstract

A communication method and apparatus, which relate to the technical field of communications. In the method, a terminal can report capability information, such that a network device can determine configuration information on the basis of the capability information. That is, the network device can generate rational configuration parameters on the basis of the capability of the terminal. Thus, the terminal can execute data collection on the basis of the configuration information from the network device, and data collection failures caused by irrational configuration parameters can also be reduced, improving the data collection efficiency.

Description

A communication method and apparatus

[0001] This application claims priority to Chinese Patent Application No. 202411605309.3, filed on November 8, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0003] To improve the efficiency of network planning, configuration, and resource scheduling, artificial intelligence (AI) technology has been introduced into mobile networks. With the introduction of AI, the data collected by the terminal may differ depending on the AI ​​model used. Currently, terminals can collect data based on parameters configured by other devices. That is, the method used by the terminal to collect data is decided by other devices. However, these other devices cannot know whether their configured parameters are reasonable. If the terminal collects data based on unreasonable configuration parameters, it may affect the efficiency of data collection. Therefore, improving the efficiency of terminal data collection has become a pressing technical problem to be solved. Summary of the Invention

[0004] This application provides a communication method and apparatus that reduces data collection failures caused by unreasonable configuration parameters and improves data collection efficiency.

[0005] Firstly, a communication method is provided. This method can be executed by a terminal, or by a module applied to the terminal (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the terminal's functions. Taking the application of this method to a terminal as an example, the terminal can send capability information and receive configuration information determined based on the capability information, thereby enabling data collection based on the configuration information. The capability information indicates at least one of the following: application use cases for data collection supported by the terminal, functions for data collection supported by the terminal, the number of condition identifiers, the type of condition identifiers, the available storage space of the terminal, or the terminal's battery level. The condition identifiers indicate the network conditions applicable to the application use cases and / or functions for data collection supported by the terminal.

[0006] As can be seen from the above embodiments, the terminal can report capability information, enabling the network device to determine configuration information based on this capability information. That is, the network device can generate reasonable configuration parameters through the terminal's capabilities. This reduces the likelihood of data collection failures due to unreasonable configuration parameters when the terminal performs data collection based on the configuration information from the network device, thus improving data collection efficiency.

[0007] Optionally, the configuration information includes at least one of the following: a first condition identifier, a first duration, a first data volume, or a first storage space. The first condition identifier indicates a network condition applicable to at least one application use case and / or at least one function; the first duration is the duration of data collection; the first data volume is the amount of data collected; and the first storage space is used to store the data collected during the data collection process.

[0008] As can be seen from the above embodiments, the configuration information includes a first condition identifier, which allows the terminal to know that data collection should be performed under the network conditions indicated by the first condition identifier. This reduces the problem of re-performing data collection due to the network conditions not meeting the network device's requirements, thereby improving data collection efficiency. The configuration information also includes a first duration, which allows the terminal to know that the data collection duration is limited. This not only reduces the energy consumption caused by continuous data collection but also ensures that the terminal collects enough data, reducing the latency caused by the network device needing to re-send configuration information after insufficient data collection and deletion of configuration information, thus improving data collection efficiency. Finally, the configuration information includes a first data volume, which allows the terminal to know that the amount of data collected is limited, reducing the energy consumption caused by continuous data collection and ensuring that the amount of data collected meets the network device's requirements. This also reduces the latency caused by the network device needing to re-send configuration information after insufficient data collection and deletion of configuration information, thus improving data collection efficiency. The configuration information includes a first storage space, which indicates that the storage space used for storing data is limited. This reduces the possibility that the terminal will endlessly collect data, causing the first storage space to be full and other storage spaces to be occupied as well. In other words, it can ensure that the terminal still has other storage space to store other information.

[0009] Optionally, the configuration information can also be used to indicate at least one application use case and / or at least one function.

[0010] Optionally, the configuration information is also used to indicate at least one of the following: a first priority for performing data collection, whether the first storage space can be used to store data corresponding to the second priority, whether subsequently collected data can be stored in the second storage space when the first storage space is full, or a first condition for stopping data collection. Wherein, the second priority is the priority for performing data collection, and the second priority is higher than the first priority; the first storage space is different from the second storage space; and the first condition includes the terminal's remaining battery power being less than a first threshold and / or the remaining storage space of the first storage space being less than the second threshold.

[0011] As can be seen, in the above embodiments, the configuration information indicating the first priority for data collection indicates that the terminal executes data collection tasks in a sequential order. This can reduce data collection conflicts and improve data collection efficiency. For example, due to limitations in the terminal's capabilities, the terminal may not be able to support the simultaneous execution of different data collection tasks. If no priority is set, the terminal may not be able to determine which data collection task should be executed first, thus affecting data collection efficiency. The configuration information indicating that the first storage space can be used to store data corresponding to the second priority allows the terminal to allocate more resources for collecting higher-priority data, ensuring sufficient amounts of higher-priority data and reducing insufficient data collection due to insufficient storage space. The configuration information indicating that the first storage space cannot be used to store data corresponding to the second priority ensures sufficient amounts of lower-priority data and reduces insufficient data collection due to insufficient storage space. The configuration information indicating that when the first storage space is full, subsequently collected data can be stored in the second storage space, ensuring sufficient amounts of higher-priority data and reducing insufficient data collection due to insufficient storage space. The configuration information indicating that when the first storage space is full, subsequently collected data cannot be stored in the second storage space reduces energy consumption caused by continuous data collection by the terminal. The configuration information indicates the first condition for stopping data collection; that is, when the first condition is met, the terminal stops data collection. This can reduce the problem of data collection failure caused by abnormal storage space and / or battery power.

[0012] Optionally, the configuration information is also used to indicate a second condition for triggering data reporting, the second condition including at least one of the following: the amount of data collected is greater than a third threshold, the duration of data collection is greater than a fourth threshold, or the remaining battery power of the terminal is less than a fifth threshold.

[0013] As can be seen, in the above embodiments, the configuration information is also used to indicate a second condition for triggering data reporting, that is, when the second condition is met, the terminal reports data to the network device. This allows the data collected by the terminal to be reported to the network device in a timely manner, reducing the power consumption caused by the terminal collecting data without restriction.

[0014] Optionally, the configuration information is also used to indicate whether to delete or retain the configuration information if the remaining battery power of the terminal is less than a sixth threshold.

[0015] As can be seen from the above embodiments, the configuration information indicates that the configuration information should be deleted when the remaining battery power of the terminal is less than or equal to the sixth threshold. This means the terminal can delete the configuration information when its remaining battery power is less than or equal to the sixth threshold, thus freeing up storage space. Alternatively, the configuration information can be retained when the remaining battery power is less than or equal to the sixth threshold, allowing the terminal to continue data collection based on the configuration information when the battery power subsequently exceeds the sixth threshold. This reduces the likelihood of insufficient data collection due to low battery power.

[0016] Optionally, the configuration information is also used to indicate a third condition that triggers the terminal to re-report its capabilities (such as data collection capabilities). The third condition includes at least one of the following: the time for data reporting arrives, a capability reporting trigger event occurs, or the capability reporting cycle arrives. For example, the terminal can re-report its capabilities when the third condition is met. Optionally, the capability reporting trigger event can be a change in the terminal's capabilities (such as data collection capabilities). That is, the terminal can re-report its capabilities when or after a change in its capabilities.

[0017] As can be seen from the above embodiments, the configuration information is also used to indicate a third condition that triggers the terminal to re-report its capabilities, meaning that the terminal can re-report its capabilities when the third condition is met. This ensures that the terminal and network devices have a consistent understanding of the terminal's capabilities, reducing the likelihood of network devices misconfiguring parameters due to a lack of understanding of the terminal's capabilities, leading to terminal data collection failures.

[0018] Optionally, the configuration information is also used to instruct the terminal to report cell information and / or network information for performing data collection.

[0019] In one possible implementation, cell information can be a cell ID. The cell ID can be used to uniquely identify a cell, such as a physical cell identifier (PCI) or a cell global identifier (CGI), and is not limited thereto. Alternatively, cell information can be a group identifier. A group identifier can be used to identify a group of cells, which may include one or more cells. Alternatively, cell information can be a cell list, which may include one or more cells.

[0020] In one possible implementation, network information may include one or more network identifiers. The network identifier may be a public land mobile network (PLMN) identifier. Alternatively, network information may include one or more networks. It can also be said that network information may include a network list, which may include one or more networks. Here, the network is an operator network; that is, a network identifier can be used to identify an operator network. For example, PLMN identifier 1 is used to identify a China Unicom network, PLMN identifier 2 is used to identify a China Mobile network, and PLMN identifier 3 is used to identify a China Telecom network.

[0021] Optionally, the capability information is also used to instruct the terminal to autonomously complete data collection.

[0022] Optionally, the configuration information is also used to allow the terminal to handle data collection anomalies autonomously, and / or, the configuration information is also used to indicate the type of data collection anomalies that the terminal can handle autonomously.

[0023] As can be seen, in the above embodiments, the configuration information is also used to allow the terminal to autonomously handle data collection anomalies. That is, through the configuration information, the terminal can learn which data collection anomalies it can autonomously handle. This means that the network device does not instruct the terminal on how to handle data collection anomalies, saving signaling overhead. The configuration information is also used to indicate the types of data collection anomalies the terminal can autonomously handle; that is, the terminal can learn which data collection anomalies it can handle, improving the efficiency of the terminal's autonomous handling of data collection anomalies.

[0024] Optionally, the above method further includes: the terminal can send indication information, which is used to indicate the reason for the data collection anomaly and / or the method for handling the data collection anomaly.

[0025] As can be seen, in the above embodiments, the terminal can send instruction information so that the network device can know the reason for the abnormal data collection and / or the way the terminal handles the abnormal data collection. This helps the terminal and the network device to have a consistent understanding of the 'reason for the abnormal data collection and / or the way the terminal handles the abnormal data collection', thereby helping the network device to better configure reasonable parameters, reduce the situation of data collection failure due to unreasonable configuration parameters, and improve data collection efficiency.

[0026] Optionally, the indication information is also used to indicate the time when the terminal expects to report data and / or the existence of data to be reported in the terminal.

[0027] It can be seen that in the above embodiments, the terminal can also indicate to the network device the time at which the terminal expects to perform data reporting and / or the presence of data to be reported in the terminal through the indication information, thereby helping the network device to timely issue resources for data reporting and reducing the problem of data reporting failure due to insufficient timeliness of the resource issue. For example, the terminal may have been powered off before receiving the resources, which will cause data reporting failure.

[0028] Optionally, the manner of processing the data collection exception further includes at least one of the following: stopping data collection when the time at which the terminal expects to perform data reporting arrives, overwriting data in the third storage space when the third storage space for storing data is full and the time at which the terminal expects to perform data reporting arrives, or deleting configuration information when the time at which the terminal expects to perform data reporting arrives. In a possible implementation, the 'deleting configuration information' herein can be replaced by retaining the configuration information.

[0029] It can be seen that in the above embodiments, the terminal can indicate to the network device the relevant content in the manner of processing the data collection exception, which is beneficial to enabling the network device to know the current data collection state, thereby better managing the data collection process.

[0030] In a second aspect, a communication method is provided, which can be executed by a network device, or can also be executed by a module (such as a processor, a chip, or a chip system, etc.) applied to the network device, and can also be implemented by a logic node, a logic module, or software that can implement all or part of the functions of the network device. Optionally, the network device can be a core network device, an access network device, or an operation, administration and maintenance (OAM) device. Taking the case that the method is applied to the network device as an example, the network device can receive capability information, and then transmit configuration information. The capability information is used to indicate at least one of the following: an application use case supported by the terminal for data collection, a function supported by the terminal for data collection, a number of condition identifiers, a type of the condition identifiers, an available storage space of the terminal, or a power level of the terminal, and the condition identifier is used to indicate a network condition to which the application use case and / or the function supported by the terminal for data collection is applicable. The configuration information is determined based on the capability information, and the configuration information is used to perform data collection.

[0031] Optionally, the configuration information includes at least one of the following: a first condition identifier, a first time length, a first data amount, or a first storage space. The network condition indicated by the first condition identifier is at least one network condition to which at least one application use case and / or at least one function is applicable, the first time length is a time length for performing data collection, the first data amount is a data amount for performing data collection, and the first storage space is used to store data collected by performing data collection.

[0032] Optionally, the configuration information is further used to indicate at least one of the following: a first priority of performing the data collection, whether a first storage space can be used to store data corresponding to a second priority, whether data collected subsequently can be stored in a second storage space when the first storage space is full, or a first condition under which the data collection is stopped. The second priority is a priority of performing the data collection, the second priority is higher than the first priority, the first storage space is different from the second storage space, and the first condition includes that a remaining power of the terminal is less than a first threshold value and / or a remaining storage space of the first storage space is less than a second threshold value.

[0033] Optionally, the configuration information is further used to indicate a second condition of triggering the data reporting, and the second condition includes at least one of the following: a quantity of data collected is greater than a third threshold value, a time length of performing the data collection is greater than a fourth threshold value, or a remaining power of the terminal is less than a fifth threshold value.

[0034] Optionally, the configuration information is further used to indicate that the configuration information is deleted or retained when a remaining power of the terminal is less than a sixth threshold value.

[0035] Optionally, the configuration information is further used to indicate a third condition of triggering the terminal to re-report the capability. The third condition includes at least one of the following: a time of the data reporting is reached, a capability reporting triggering event occurs, or a period of the capability reporting is reached.

[0036] Optionally, the configuration information is further used to indicate that the terminal reports cell information and / or network information of performing the data collection.

[0037] Optionally, the capability information is further used to indicate that the terminal supports to autonomously complete the data collection.

[0038] Optionally, the configuration information is further used to allow the terminal to autonomously handle an abnormal situation of the data collection, and / or the configuration information is further used to indicate a type of the terminal autonomously handling the abnormal situation of the data collection.

[0039] Optionally, the method further includes that the network device receives indication information, the indication information being used to indicate a reason of the data collection being abnormal and / or a manner of handling the abnormality of the data collection.

[0040] Optionally, the indication information is further used to indicate a time at which the terminal expects to perform the data reporting and / or that there is data to be reported in the terminal.

[0041] Optionally, the manner of handling the abnormality of the data collection includes at least one of the following: stopping the data collection when the time at which the terminal expects to perform the data reporting is reached, overwriting data in a third storage space for storing data when the third storage space is full and the time at which the terminal expects to perform the data reporting is reached, or deleting the configuration information when the time at which the terminal expects to perform the data reporting is reached.

[0042] In a third aspect, a communication apparatus is provided, which comprises means or modules or units for implementing the method in any one of the first aspect or the second aspect. The communication apparatus can be a terminal, or a module (for example, a processor, a chip, or a chip system, etc.) of the terminal, or a logic node, a logic module, or software capable of implementing all or part of the terminal functions. Alternatively, the communication apparatus can be a network device, or a module (for example, a processor, a chip, or a chip system, etc.) of the network device, or a logic node, a logic module, or software capable of implementing all or part of the network device functions.

[0043] In a fourth aspect, a communication apparatus is provided, which comprises at least one processor. The at least one processor is configured to cause the communication apparatus to perform the method in any one of the first aspect or the second aspect. The communication apparatus can be a terminal, or a module (for example, a processor, a chip, or a chip system, etc.) of the terminal, or a logic node, a logic module, or software capable of implementing all or part of the terminal functions. Alternatively, the communication apparatus can be a network device, or a module (for example, a processor, a chip, or a chip system, etc.) of the network device, or a logic node, a logic module, or software capable of implementing all or part of the network device functions. The at least one processor can execute computer programs or instructions in a memory to cause the above method to be performed. The memory can be included in the communication apparatus, or located outside the communication apparatus. In addition, the communication apparatus can further comprise an interface.

[0044] In a fifth aspect, a computer readable storage medium is provided, which stores computer instructions or programs. When the computer instructions or programs are executed, the computer is caused to perform the method in any one of the first aspect or the second aspect.

[0045] In a sixth aspect, a computer program product is provided, which comprises computer programs or programs. When the computer programs or programs are run by a computer, the computer is caused to perform the method in any one of the first aspect or the second aspect.

[0046] In a seventh aspect, a chip is provided, which comprises at least one processor. The processor is configured to execute computer instructions or programs. When the computer instructions or programs are run, the chip is caused to perform the method in any one of the first aspect or the second aspect. The processor can execute computer programs or instructions in a memory to cause the above method to be performed. The memory can be included in the chip, or located outside the chip. In addition, the chip can further comprise an interface.

[0047] In an eighth aspect, a communication system is provided, which comprises a terminal for performing the method in any one of the first aspect, and a network device for performing the method in any one of the second aspect.

[0048] Among them, the second aspect to the eighth aspect of the present application correspond to the technical solutions of the first aspect of the present application, and the beneficial effects obtained by each aspect and the corresponding feasible implementation manner are similar, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0049] FIG. 1 is a basic architecture of a communication system;

[0050] FIG. 2 is a schematic diagram of a device in the communication system shown in FIG. 1 implementing an AI function in an ORAN system according to an embodiment of the present application;

[0051] FIG. 3 is a flow diagram of a communication method according to an embodiment of the present application;

[0052] FIG. 4 is a structural schematic diagram of a communication apparatus according to an embodiment of the present application;

[0053] FIG. 5 is a structural schematic diagram of another communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0054] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings. In the embodiments of the present application, the terms "system" and "network" can be used interchangeably. Unless otherwise specified, " / " represents an "or" relationship between the objects associated before and after it, for example, A / B can represent A or B; in the present application, "and / or" is only a description of the associated relationship between the associated objects, which means that there can be three relationships, for example, A and / or B, which means that there are three cases of A alone, A and B together, and B alone, where A and B can be singular or plural. And in the description of the present application, unless otherwise specified, "multiple" means two or more than two. "At least one of the following" or similar expressions means any combination of these items, including any combination of single item or multiple items. For example, at least one of a, b, or c can mean a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be one or more. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, the same items or similar items with basically the same function are distinguished by "first", "second", etc. in the embodiments of the present application. Those skilled in the art can understand that "first", "second", etc. do not limit the number and execution order, and "first", "second", etc. also do not necessarily mean different.

[0055] Reference to "one embodiment" or "some embodiments" or "an embodiment" or "some embodiments" etc. in the present application means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. The appearances of the phrases "in one embodiment" or "in some embodiments" or "in an embodiments" or "in some embodiments" in various places in the specification are not necessarily all referring to the same embodiment, but can refer to different embodiments, although they can be in some cases referring to the same embodiment. The terms "including", "comprising", "having" and their variants are meant to be construed as "including but not limited to", unless otherwise noted.

[0056] The following detailed description is provided to provide further understanding of the objects, technical solutions and advantages of the present application. It should be understood that the following is merely a specific embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made on the basis of the technical solutions of the present application shall be included in the protection scope of the present application.

[0057] In various embodiments of the present application, the terms and / or descriptions of different embodiments are consistent and can be mutually referred to if there is no special description and logical conflict. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0058] The method provided by the embodiments of the present application can be applied to various communication systems, for example, an internet of things (IoT) system, a narrow band internet of things (NB-IoT) system, a long term evolution (LTE) system, a 5th-generation (5G) communication system, a new radio (NR) system, or a new communication system in future communication development. The IoT network may, for example, include but is not limited to a vehicle-to-everything (V2X) system. The communication mode in the V2X system may, for example, include vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, vehicle-to-network (V2N) communication, or the like. The method provided by the embodiments of the present application can also be applied to non-terrestrial network (NTN) communication, or a scenario in which the NTN is integrated with a terrestrial network (TN).

[0059] The method provided by the embodiments of the present application can be applied to a wireless local area network (WLAN) system, such as Wi-Fi.

[0060] The method provided by the embodiments of the present application can be applied to two entities in a communication system, for example, one of the two entities can send information to the other entity, or receive information sent by the other entity. In a wireless communication system, communication devices can be included, and the communication devices can perform wireless communication by using air interface resources. The air interface resources may, for example, include at least one of a time domain resource, a frequency domain resource, a code resource, and a space resource, and the present application is not limited in this regard. For example, the two entities may, for example, include a network device and a terminal, or a chip that can be placed in the network device, and a chip that can be placed in the terminal, and the like. Of course, with the development of standards, other types of entities may also appear in the future, and the embodiments of the present application are not limited in this regard.

[0061] The basic architecture of the communication system provided by the embodiments of the present application is described below. The communication system provided by the present application may, for example, include one or more network devices and one or more terminals.

[0062] The following will be explained exemplarily with the system architecture shown in Fig. 1. In Fig. 1, the communication system comprises a network device 10 and a terminal 20 in communication with the network device 10.

[0063] It should be noted that the number of network devices and terminals in Fig. 1 is only illustrative and should not be regarded as a specific limitation of the present application. The following will be explained in detail the various devices involved in the system architecture.

[0064] I. Terminal

[0065] A terminal is an entity that receives a signal or transmits a signal or receives a signal and transmits a signal on a user side. The terminal is used to provide one or more of voice services and data connectivity services to a user. The terminal can be a device that includes a wireless transceiving function and can cooperate with a network device to provide communication services to a user. Specifically, the terminal can refer to a user equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, a remote terminal, a mobile device, a terminal, a wireless communication device, a user agent, a user apparatus, or a road side unit (RSU). The terminal can also be a drone, an internet of things (IoT) device, a station (ST) in a wireless local area network (WLAN), a cellular phone, a smart phone, a cordless phone, a wireless data card, a tablet computer, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a laptop computer, a machine type communication (MTC) terminal, a handheld device with a wireless communication function, a computing device, or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device (which can also be referred to as a wearable smart device), a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in remote medical treatment, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, and the like. The terminal can also be a terminal in a 5G system or a terminal in a next-generation communication system, and embodiments of the present application do not limit the same.

[0066] Embodiments of the present application do not limit the device form of the terminal, and the device for implementing the function of the terminal can be a terminal; or can be a device capable of supporting the terminal to implement the function, such as a chip system. The device can be installed in the terminal or used with the terminal. In embodiments of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices.

[0067] II. Network device

[0068] The network device is an entity for transmitting a signal, or receiving a signal, or transmitting and receiving a signal on the network side. For example, the network device can be a core network device, an access network device, or an OAM device.

[0069] 1. Core network device

[0070] The core network device refers to a device in a core network (CN) that provides service support for a terminal. The core network device can be a core network device in an LTE, 5G or other communication system, which is not limited herein. For example, the core network device can be a user plane function network element (also referred to as a user plane network element) or a control plane function network element (also referred to as a control plane network element).

[0071] The user plane network element is responsible for forwarding and receiving user data in the terminal. In the 5G communication system, the user plane network element can be a user plane function (UPF) network element. In future communication systems, the user plane network element can still be a UPF network element, or can have other names, which are not limited in embodiments of the present application.

[0072] The control plane network element can be an access management network element, a session management network element, or other network elements, which are not listed here. Among them, the access management network element is a control plane network element provided by an operator network, responsible for access control and mobility management of terminal devices accessing the operator network, including functions such as mobile state management, allocation of user temporary identity, authentication, and user management. In the 5G communication system, the access management network element can be an access and mobility management function (AMF) network element. In future communication systems, the access management network element can still be an AMF network element, or it can also have other names, which are not limited by the embodiments of the present application. The session management network element is mainly responsible for session management in the mobile network, such as session establishment, session modification, and session release. Specific functions include allocating IP addresses for users, selecting user plane network elements that provide message forwarding functions, and the like. In the 5G communication system, the session management network element can be a session management function (SMF) network element. In future communication systems, the session management network element can still be an SMF network element, or it can also have other names, which are not limited by the embodiments of the present application.

[0073] Optionally, the core network device and the terminal can communicate through non-access stratum (NAS) messages or other messages, which are not limited by the present application.

[0074] In the embodiments of the present application, the form of the core network device is not limited, and the device for realizing the function of the core network device can be the core network device; or it can be a device capable of supporting the core network device to realize the function, such as a chip system. The device can be installed in the core network device or used in matching with the core network device.

[0075] Optionally, in the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0076] 2. Access network device

[0077] The access network device can be a device deployed in a radio access network (RAN) to provide wireless communication functions for terminals.

[0078] In a possible scenario, the access network device can be a device with base station functions, such as an evolved NodeB (eNodeB), a transmitting and receiving point (TRP), a transmitting point (TP), a next generation NodeB (gNB), a base station in a future mobile communication system, an integrated access and backhaul (IAB) node, a non-ground network device, that is, a device that can be deployed on a high-altitude platform or a satellite, and the like. The access network device can be a transmission reception point (TRP), a base station, various forms of control nodes. For example, a network controller, a radio controller, and the like. Specifically, the access network device can be various forms of macro base stations, micro base stations (also referred to as small stations) in a heterogeneous network (HetNet) scenario, relay stations, access points (APs), radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (for example, home evolved nodeBs, or home node Bs, HNBs), baseband units (BBUs) and remote radio units (RRUs) in a distributed base station scenario, transmitting and receiving points (TRPs), transmitting points (TPs), mobile switching centers, and the like, and can also be an antenna panel of a base station. The control node can connect multiple base stations and configure resources for multiple terminals under the coverage of the multiple base stations. In systems using different wireless access technologies, the names of devices with base station functions can be different. For example, it can be a gNB in 5G, or a network side device in a network after 5G or an access network device in a future evolved public land mobile (communication) network (PLMN) network, or a device assuming base station functions in device-to-device (D2D) communication, machine-to-machine (M2M) communication, vehicle-to-vehicle communication, and the like. The specific name of the access network device is not limited in the present application.The access network device can also be a baseband pool (BBU pool) and RRU under an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (CRAN), and the like.

[0079] In another possible scenario, multiple access network devices cooperate to assist a terminal to implement wireless access, and different access network devices respectively implement part of the functions of a base station. For example, the access network device can include a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), and the like. The CU and the DU can be separately arranged, or can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a radio frequency remote unit (RRU), an active antenna processing unit (AAU), or a remote radio head (RRH). Alternatively, the access network device can be a CU node, or a DU node, or a device including a CU node and a DU node. In addition, the CU can be divided into an access network device in the access network RAN, or the CU can be divided into an access network device in the core network (CN), which is not limited here.

[0080] In different systems, the CU (or CU-CP and CU-UP), DU or RU can also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, the CU can also be referred to as O-CU (open CU), the DU can also be referred to as O-DU, the CU-CP can also be referred to as O-CU-CP, the CU-UP can also be referred to as O-CU-UP, and the RU can also be referred to as O-RU. For the convenience of description, the CU, CU-CP, CU-UP, DU and RU are taken as examples for description in this application.

[0081] Optionally, the access network device can further include a service unit (SU). Alternatively, the access network device can not include the SU, that is, the SU and the access network device can be independently deployed. The service unit can provide AI-related services, including running a model, obtaining input from other network elements, and providing the output of the model to other nodes. In addition, joint training can also be performed with the model of the terminal, or model-related messages such as input and output, model or function control messages, etc. are exchanged. Optionally, the SU can establish a link with the O-CU-CP and the O-CU-UP, respectively.

[0082] Any of the CUs (or CU-CP, CU-UP), DUs, RUs, and SUs in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0083] In the embodiments of this application, the form of the access network device is not limited, and the device for implementing the function of the access network device can be the access network device; or it can be a device capable of supporting the access network device to implement the function, such as a chip system. The device can be installed in the access network device or used in matching with the access network device.

[0084] 3. OAM device

[0085] The OAM device can also be referred to as an OAM network management, which is controlled by an operator to configure and adjust the actual running network. For example, operation and maintenance (OM) can be performed on the access network device, such as viewing and analyzing at least one of the configuration information, conversation information, alarm information, tracking information, and log information, etc.

[0086] Optionally, the OAM device and the terminal can communicate through an internet protocol (IP) pipe message or other messages, which is not limited in this application.

[0087] The embodiments of this application do not limit the device form of the OAM device, and the device for implementing the function of the OAM device can be the OAM device; or it can be a device capable of supporting the OAM device to implement the function, such as a chip system. The device can be installed in the OAM device or used in matching with the OAM device.

[0088] Optionally, the network element or function shown in Figure 1 can be a network component in a hardware device, a software function running on dedicated hardware, a virtualization function instantiated on a platform (e.g., a cloud platform), or a combination of both. One possible implementation is that the aforementioned network element or function can be implemented by one device, multiple devices working together, or a functional module within a single device; this application embodiment does not specifically limit this. Furthermore, for ease of description, the term "network element" can be omitted below. For example, in this application embodiment, the AMF network element and AMF have the same meaning; the word "network element" is omitted for ease of description, and the rest are similar. It should also be noted that this application embodiment does not limit the names of each network element in the communication system. For example, in communication systems of different standards, each network element can have other names; or, for example, when multiple network elements are integrated into the same physical device, that physical device can also have other names.

[0089] To facilitate understanding of the content of this solution, some terms used in the embodiments of this application will be explained below, so that those skilled in the art can understand them. This part is only for the purpose of understanding and should not be regarded as a specific limitation of this application.

[0090] I. Artificial Intelligence (AI)

[0091] AI can endow machines with human-like intelligence, for example, allowing them to use computer hardware and software to simulate certain intelligent human behaviors. To achieve artificial intelligence, machine learning (ML) methods can be employed. In machine learning, machines learn (or train) models using training data. These models represent the mapping relationship or function between the model's inputs and outputs. The learned model can be used for reasoning (or prediction), that is, it can be used to predict the output corresponding to a given input. This output can also be called the reasoning result (or prediction result).

[0092] Optionally, the above-mentioned model may be referred to as an AI model, ML model, rule, deep learning model, reinforcement learning model, federated learning model, or other names. A model can be considered a specific method for implementing AI functionality. Optionally, functionality may include one or more of the following: data collection, model training (or model learning), model information dissemination, model inference (or model inference, reasoning, or prediction, etc.), model monitoring or model validation, or inference result dissemination, etc. In one possible implementation, model and functionality can be described interchangeably.

[0093] Optionally, a model can be uniquely identified by a model identifier (also known as an index or number, etc.). The model identifier can directly identify the model, such as a model identity (ID). Alternatively, the model identifier can indirectly identify the model, such as information used to identify the model's parameters. In one possible implementation, the parameters here include at least one of the following: model structural parameters, model input parameters, or model output parameters. Model structural parameters can include at least one of the following: the number of neural network layers, neural network width, inter-layer connections, neuron weights, neuron activation functions, or biases in activation functions. Model input parameters can include at least one of the following: the type of input parameters or the dimension of input parameters. Model output parameters can include at least one of the following: the type of output parameters or the dimension of output parameters.

[0094] Optionally, when AI technology is introduced into the wireless field, the devices in the communication system shown in Figure 1 can possess AI capabilities (or ML capabilities). For example, at least one of the terminal, access network equipment, core network equipment, and OAM equipment can have AI capabilities. That is, at least one of the terminal, access network equipment, core network equipment, and OAM equipment can include one or more built-in AI modules to implement functions. The AI ​​module can also be called an AI entity, AI unit, or other names, mainly used to implement some or all of the functions; this application does not limit its specific name. The AI ​​module can implement different functions depending on the different parameter configurations. The AI ​​module can have one or more models. Therefore, it can also be said that at least one of the terminal, access network equipment, core network equipment, and OAM equipment can deploy one or more models.

[0095] For example, in Figure 2-1, the terminal, access network device, and core network device can each deploy one or more AI modules. The access network device can include a CU and a DU; each CU and DU can deploy one or more AI modules. Optionally, the CU can also be split into CU-CP and CU-UP. One or more AI modules can be deployed in CU-CP and / or CU-UP.

[0096] For example, in Figure 2-2, the access network equipment may include a CU, a DU, and a RAN intelligent controller (RIC). The RIC includes near-real-time RICs (near-RT RICs) and / or non-real-time RICs (non-RT RICs). The near-real-time or non-real-time RIC can be used for model training and inference. For example, it can be used to train an artificial intelligence (AI) model and then use that AI model for inference. The near-real-time or non-real-time RIC can obtain relevant information from the access network equipment (e.g., at least one of CU, CU-CP, CU-UP, DU, RU, etc.) and / or terminals as training data or inference data. Optionally, the near-real-time or non-real-time RIC can deliver the inference results to the access network equipment and / or terminals. Optionally, the CU and DU, and / or the DU and RU, can exchange inference results. For example, near real-time or non-real-time RICs submit the inference results to DUs, which then send them to RUs to enable near real-time intelligent management of access network devices.

[0097] Optionally, near real-time RIC and non-real-time RIC can be configured as separate network elements, or they can be integrated into other devices. For example, near real-time RIC can be configured in access network devices, such as CU or DU. Non-real-time RIC can be configured in OAM devices, cloud servers, core network devices, or other devices. Optionally, the RIC in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules; this application does not limit the implementation in this regard.

[0098] The following section introduces use cases of AI in the wireless field.

[0099] Application use cases refer to the application scenarios of AI on the network side. For example, energy saving, load balancing, and mobility optimization mentioned by the RAN3 working group. Or, channel state information (CSI) feedback enhancement, beam management enhancement, and positioning enhancement mentioned by the RAN1 working group. These application use cases are described below.

[0100] 1. Energy Saving: By collecting load, energy consumption, energy efficiency information, terminal path information, or measurement results from its own and neighboring cells through access network equipment, the network can predict its own load trends. Combined with cell usage and key performance indicator (KPI) requirements, appropriate energy-saving measures can be implemented in a timely manner without affecting network coverage and user access. The simplest energy-saving strategy includes directly deactivating the cell. Other strategies include carrier shutdown, channel shutdown, time slot shutdown, or reduced transmit power. More complex strategies involve combining these measures. When network coverage is affected or cannot meet terminal access and service requirements, the current energy-saving strategy can be modified, or the network can be restored to normal operating conditions. The load can then be re-predicted, or the model used can be changed for re-inference.

[0101] 2. The purpose of load balancing is to distribute the load evenly between cells and across different areas within a cell, or to transfer some traffic from congested cells, or to offload terminal devices onto a single cell, carrier, or access standard, thereby improving network performance. This can be achieved by optimizing handover parameters and handover actions. This automated optimization can provide a high-quality user experience while increasing system capacity and minimizing manual intervention in network management and optimization tasks. Currently, load balancing decisions based on the current / past cell load status are insufficient. Furthermore, overall network and service performance is difficult to guarantee during load balancing. Therefore, model-based solutions can be introduced to improve load balancing performance, such as inputting various user and network node measurements and feedback, historical data, etc., into the model to improve load balancing performance, thereby providing a higher-quality user experience and increasing system capacity.

[0102] 3. Mobility Optimization: By collecting historical path information from the terminal through access network equipment and combining it with the terminal's measurement information, the future path of the terminal is predicted. Based on the predicted path, it is determined in advance whether the terminal needs to handover, and handover configuration is issued in advance, and the target cell is notified to prepare access resources, reducing the latency of the terminal during the handover process and lowering the probability of handover or access failure. However, since the accuracy of path prediction is not 100%, when the predicted path is incorrect, it will lead to terminal handover failure and service interruption. In this case, it is necessary to consider retraining the model and inference based on the abnormal situation, or consider replacing the model to avoid similar abnormal situations from occurring again in the future. In R19, the RAN2 working group re-planned a new mobility optimization topic and set several application use cases as research objectives. Among them, the most critical application use case is to predict the terminal's measurement results, such as predicting the reference signal received power (RSRP) of the synchronization signal and physical broadcast channel block (SSB). The granularity of prediction can be at the cell level, for example, predicting for the cell where the terminal is located, or predicting for neighboring cells. Alternatively, the prediction granularity can be beam-level. Optionally, two additional application cases are introduced: one is predicting the occurrence of anomalous events such as handover failure (HOF) or radiolink failure (RLF), and the other is predicting measurement events such as A1 to A5. The current research direction for these two application cases in the standard considers the terminal-side model, where the terminal reports the prediction results to the network device, and the network device then decides what adjustments need to be made based on the prediction results.

[0103] 4. CSI Feedback Enhancement refers to treating the high-dimensional channel information feedback task as an end-to-end CSI image compression and reconstruction task. For example, the encoder (e.g., a terminal) uses an encoder to compress the complete channel information into a bitstream that meets the feedback requirements after feature extraction. This bitstream is then sent to the decoder (e.g., an access network device) via a feedback link. The decoder uses a decoder to decompress the bitstream and reconstruct its features, ultimately recovering the complete channel information. The encoder and decoder are jointly optimized during end-to-end training to achieve the best CSI reconstruction performance. In practical deployment, the encoder and decoder can be paired according to the training process; that is, the compressed CSI output by one encoder can be recovered using the corresponding decoder.

[0104] 5. Beam management enhancement refers to the discovery of the strongest transmit / receive beam pair. AI-based beam prediction (or CSI prediction) can improve prediction accuracy.

[0105] 6. Positioning enhancement refers to achieving higher positioning accuracy with a smaller number of antennas.

[0106] Optionally, the above-mentioned functions may be a subset of application use cases. For example, the application use case is beam management enhancement, which includes a model that predicts 16 beams based on 4 beams and a model that predicts 64 beams based on 16 beams. The model that predicts 16 beams based on 4 beams may correspond to one function, and the model that predicts 64 beams based on 16 beams may correspond to another function.

[0107] II. Condition Identifier

[0108] A condition identifier, also known as an associated ID, is used to indicate the network conditions applicable to an application use case and / or function. Network conditions, also known as network status, include at least one of the following: the power consumption of the network device, the number of antennas activated on the network device, the antenna downtilt angle of the network device, or the number of beams, etc.

[0109] Optionally, in this application, the condition identifier can be used interchangeably with the condition index, condition number, association index, or association number. As an example, the condition identifier can be any numerical value or symbol that can distinguish, mark, or locate the network conditions applicable to the application use case and / or function; this application does not limit this.

[0110] Optionally, the same application use case can correspond to one or more condition identifiers. That is, the network conditions applicable to the application use case can be different. The same function can correspond to one or more condition identifiers, meaning that the network conditions applicable to the function can be different.

[0111] Optionally, different application use cases can correspond to the same condition identifier. That is, the network conditions applicable to different application use cases can be the same. Different functions can correspond to the same condition identifier, meaning that the network conditions applicable to different functions can be the same.

[0112] Optionally, when a function can be a subset of an application use case, the condition identifier corresponding to that application use case includes the condition identifier corresponding to that function. For example, an application use case for beam management enhancement includes a model predicting 16 beams based on 4 beams and a model predicting 64 beams based on 16 beams. The model predicting 16 beams based on 4 beams can correspond to function 1, and the model predicting 64 beams based on 16 beams can correspond to function 2. Function 1 corresponds to two condition identifiers, and function 2 corresponds to three condition identifiers. The condition identifier corresponding to this application use case includes the two condition identifiers corresponding to function 1 and the three condition identifiers corresponding to function 2. That is, the condition identifiers corresponding to the application use case and the condition identifiers corresponding to the function have some identical condition identifiers. These condition identifiers can be considered as both the condition identifiers corresponding to the application use case and the condition identifiers corresponding to the function. Or, to simplify, the condition identifiers corresponding to the application use case and the condition identifiers corresponding to the function are partially identical.

[0113] Optionally, when the network conditions applicable to the application use case and / or function differ, different network conditions can be represented by the type of condition identifier. That is, the type of condition identifier can be used to indicate the type of network conditions applicable to the application use case and / or function. For example, condition identifier 1 indicates the power consumption of the network device to which the function applies, and the type of condition identifier 1 is type 1. Condition identifier 2 indicates the number of antennas activated by the network device to which the function applies, and the type of condition identifier 2 is type 2. In one possible implementation, the type of condition identifier can be used interchangeably with 'the type of network conditions applicable to the application use case and / or function'.

[0114] The embodiments of this application are described in detail below. The executing entities involved in the embodiments of this application can be a first communication device and a second communication device. The first communication device or the second communication device can be any two devices capable of communication shown in Figure 1. The specific names of the first communication device and the second communication device are not limited in the embodiments of this application. As an example, the first communication device can be a terminal or a chip or functional module of a terminal, etc., and the second communication device can be a network device or a chip or functional module of a network device, etc. As another example, the first communication device can be a network device or a chip or functional module of a network device, and the second communication device can be a terminal or a chip or functional module of a terminal. As yet another example, the first communication device and the second communication device can be different terminals or network devices, etc. Specific forms of the first communication device and the second communication device are not listed here. For ease of description, the embodiments of this application are described using the first communication device as a terminal and the second communication device as a network device as an example, and this should not be considered a limitation of this application.

[0115] Referring to Figure 3, which is a flowchart illustrating a communication method provided in an embodiment of this application, the method includes, but is not limited to, the following steps:

[0116] 301. The terminal sends capability information, which indicates at least one of the following: the application use case for data collection supported by the terminal, the function for data collection supported by the terminal, the number of condition identifiers, the type of condition identifiers, the available storage space of the terminal, or the battery level of the terminal. The condition identifiers are used to indicate the network conditions applicable to the application use case and / or function for data collection supported by the terminal.

[0117] Accordingly, information on the network device's receiving capabilities.

[0118] In one possible implementation, the terminal can send capability information to the network device in any of the following ways:

[0119] Method 1: The terminal sends capability information to the network device based on a request message from the network device (the request message is used to obtain capability information).

[0120] Method 2: If the terminal does not receive a request message from the network device, it actively sends capability information to the network device.

[0121] Optionally, in Method 1 or Method 2, the request message can be a NAS message, an RRC message (such as a protocol-defined UE capability enquiry message), a media access control-control element (MAC CE) message, downlink control information (DCI) message, an IP pipe message, or other messages. For example, if the network device is a core network device, the request message can be a NAS message or other messages. If the network device is an access network device, the request message can be the RRC message, MAC CE, DCI, or other messages. If the network device is an OAM device, the request message can be an IP pipe message or other messages.

[0122] Optionally, in either Method 1 or Method 2, capability information can be carried in NAS messages, RRC messages (such as UE capability information messages or user assistantance information (UAI) messages), uplink control information (UCI), IP pipe messages, or other messages. For example, if the network device is a core network device, capability information can be carried in NAS messages or other messages. If the network device is an access network device, capability information can be carried in the RRC message, MAC CE, DCI, or other messages. If the network device is an OAM device, capability information can be carried in IP pipe messages or other messages.

[0123] Optionally, in Method 1 or Method 2, one or more contents indicated by the capability information can be implemented in at least one of the following ways: by the terminal directly or indirectly instructing the network device, or predefined, which is not limited in this application.

[0124] For example, capability information is used to indicate application use cases that the terminal supports for data collection. That is, capability information may include the identifier (also known as an index or number, etc.) or name of the application use case that the terminal supports for data collection. Thus, the application use case that the terminal supports for data collection can be determined by the network device based on the identifier or name of the application use case. Optionally, the number of application use cases that the terminal supports for data collection can be one or more; this application does not limit this. Optionally, the identifier of the application use case can be any numerical value or symbol that can distinguish, mark, or locate the application use case; this application does not limit this.

[0125] For example, capability information is used to indicate the data collection functions supported by the terminal. That is, capability information may include an identifier (also known as an index or number, etc.) or name of the data collection functions supported by the terminal. Thus, the data collection functions supported by the terminal can be determined by the network device based on the identifier of that function. Optionally, the number of data collection functions supported by the terminal can be one or more; this application does not limit this. Optionally, the identifier of a function can be any numerical value or symbol that can distinguish, mark, or locate a function; this application does not limit this.

[0126] For example, capability information used to indicate the terminal's battery level can include: the capability information directly including the terminal's battery level; or the capability information indirectly including the terminal's battery level. For instance, the capability information can include an identifier (also called an index or number) of the terminal's battery level, so that the terminal's battery level can be determined by the network device based on the battery level identifier. In the latter case, the terminal's battery level can be interchangeably described as the terminal's battery state. That is, different battery level identifiers can represent different battery states. For example, three battery level identifiers can be used to represent three battery states: battery level identifier 1 represents a high battery state, battery level identifier 2 represents a medium battery state, and battery level identifier 3 represents a low battery state, etc.

[0127] The following section provides a detailed explanation of the condition identifiers in the capability information, using application use cases and / or functions that support data collection on the terminal.

[0128] As an example, capability information is used to indicate application use cases that the terminal supports for data collection. The number of condition identifiers in the capability information can be the total, maximum, minimum, or average number of condition identifiers corresponding to that application use case, and the type of condition identifier in the capability information indicates the type of network conditions applicable to that application use case. Alternatively, the number of condition identifiers in the capability information can be the total, maximum, minimum, or average number of condition identifiers corresponding to all functions in the application use cases that the terminal supports for data collection, and the type of condition identifier in the capability information indicates the type of network conditions applicable to these functions.

[0129] As another example, capability information is used to indicate that the terminal supports data collection functions. The number of condition identifiers in the capability information can be the total number, maximum number, minimum number, or average number of condition identifiers corresponding to that function, and the type of condition identifier in the capability information indicates the type of network conditions to which that function applies.

[0130] As another example, capability information is used to indicate both the application use cases that the terminal supports for data collection and the functions that the terminal supports for data collection. The number of condition identifiers in the capability information can be determined based on the number of condition identifiers corresponding to the application use case and the number of condition identifiers corresponding to the function, and the type of condition identifier in the capability information is determined based on the type of network conditions applicable to the application use case and the type of network conditions applicable to the function.

[0131] For example, the terminal's data collection-supporting functions may be a subset of application use cases that support data collection, and the condition identifiers corresponding to these application use cases include the condition identifiers corresponding to the terminal's data collection-supporting functions. In this case, the number of condition identifiers in the capability information may be the total, maximum, minimum, or average number of condition identifiers corresponding to the application use case, or the number of condition identifiers in the capability information may be the number of condition identifiers currently supported by the application use case, and the type of condition identifier in the capability information indicates the type of network conditions applicable to the application use case. Alternatively, the number of condition identifiers in the capability information may be the total, maximum, minimum, or average number of condition identifiers corresponding to all functions of the application use case (including the terminal's data collection-supporting functions), or the number of condition identifiers in the capability information may be the number of condition identifiers currently supported by all functions of the application use case, and the type of condition identifier in the capability information indicates the type of network conditions applicable to these functions. Alternatively, the number of condition identifiers in the capability information can be the total, maximum, minimum, or average number of condition identifiers corresponding to the functions supported by the terminal for data collection. Or, the number of condition identifiers in the capability information can be the number of condition identifiers currently supported by the function, and the type of the condition identifier in the capability information is the type of network condition applicable to the functions supported by the terminal for data collection. Alternatively, the number of condition identifiers in the capability information can be the sum of the number of condition identifiers corresponding to the application use cases supported by the terminal for data collection and the number of condition identifiers corresponding to the functions supported by the terminal for data collection. For example, the number of condition identifiers in the capability information can be the sum of the total number of condition identifiers corresponding to the application use case and the total number of condition identifiers corresponding to the function; or, the number of condition identifiers in the capability information can be the sum of the maximum number of condition identifiers corresponding to the application use case and the maximum number of condition identifiers corresponding to the function; or, the number of condition identifiers in the capability information can be the sum of the minimum number of condition identifiers corresponding to the application use case and the minimum number of condition identifiers corresponding to the function; or, the number of condition identifiers in the capability information can be the sum of the average number of condition identifiers corresponding to the application use case and the average number of condition identifiers corresponding to the function, etc. The types of condition identifiers in the capability information include the types of network conditions applicable to the application use case and the types of network conditions applicable to the function.

[0132] The following example illustrates the 'Available Storage Space of the Terminal' indicated by the capability information.

[0133] Optionally, the available storage space of the terminal may include at least one of the following: access stratum (AS) storage space, NAS storage space, or other storage space. The other storage space here can be any storage space available in the terminal other than AS storage space and NAS storage space.

[0134] Optionally, capability information is also used to indicate whether the terminal supports autonomous data collection.

[0135] When a terminal supports autonomous data collection, the capability information may indicate that the terminal supports autonomous data collection, or it may not. For the former, 'the terminal supports autonomous data collection' is explicitly indicated by the capability information. For the latter, 'the terminal supports autonomous data collection' is implicitly indicated by the capability information. In other words, when the capability information received by the network device indicates at least one of the following: the application use case for data collection supported by the terminal, the function supported by the terminal for data collection, the number of condition identifiers, the type of condition identifiers, the available storage space of the terminal, or the battery level of the terminal, the network device may assume that the terminal supports autonomous data collection.

[0136] When a terminal does not support autonomous data collection, the capability information may indicate that the terminal does not support autonomous data collection, or it may not indicate that the terminal does not support autonomous data collection. For the former, the 'terminal does not support autonomous data collection' is explicitly indicated by the capability information. For the latter, the 'terminal does not support autonomous data collection' is implicitly indicated by the capability information. In other words, when the capability information received by the network device indicates at least one of the following: the application use case for data collection supported by the terminal, the function supported by the terminal for data collection, the number of condition identifiers, the type of condition identifiers, the available storage space of the terminal, or the battery level of the terminal, the network device may assume that the terminal does not support autonomous data collection.

[0137] Specifically, the aforementioned content regarding 'whether the capability information indicates that the terminal supports autonomous data collection' and / or 'whether the capability information indicates that the terminal does not support autonomous data collection' can be combined to achieve 'capability information is used to indicate whether the terminal supports autonomous data collection'. For example, 'the terminal supports autonomous data collection' is explicitly indicated by the capability information, and 'the terminal does not support autonomous data collection' is implicitly indicated by the capability information. Alternatively, 'the terminal does not support autonomous data collection' is explicitly indicated by the capability information, and 'the terminal supports autonomous data collection' is implicitly indicated by the capability information. Or, 'the terminal does not support autonomous data collection' is explicitly indicated by the capability information, and 'the terminal does not support autonomous data collection' is explicitly indicated by the capability information.

[0138] Optionally, capability information may also indicate other content besides those listed above. For example, application use cases where the terminal does not support data collection, functions where the terminal does not support data collection, whether the terminal supports minimized drive-tests (MDT) measurements, or other existing capabilities. Here, "other existing capabilities" refers to terminal capabilities in existing versions of the communication standard and is not limited here.

[0139] 302. Network devices send configuration information, which is determined based on capability information.

[0140] Accordingly, the terminal receives the configuration information.

[0141] Optionally, the network device may send one or more configuration information. Each configuration information may be determined based on capability information. For example, each configuration information may be determined based on capability information and the network device's data collection requirements. These data collection requirements may include at least one of the following: duration requirements, quantity requirements, or storage space requirements, etc., which are not listed here. Optionally, storage space requirements may include at least one of the following: AS storage space requirements, NAS storage space requirements, or other storage space requirements, where other storage space requirements refer to storage space requirements other than AS and NAS storage space requirements. Each of the above configuration information pieces includes similar content. For ease of description, this application uses one configuration information piece as an example and should not be considered a limitation of this application.

[0142] Optionally, the configuration information may include at least one of the following: a first condition identifier, a first duration, a first data volume, or a first storage space.

[0143] The network condition indicated by the first condition identifier is a network condition to which at least one application use case and / or at least one function is applicable. Optionally, the at least one application use case may belong to an application use case that supports terminal data collection. Alternatively, the at least one application use case may include a function that supports terminal data collection, or at least one function may belong to a function that supports terminal data collection.

[0144] The first duration is the time allotted for data collection, such as 30 minutes (minute, min). Optionally, the first duration can be the maximum or minimum duration for which the terminal performs data collection. Alternatively, the first duration can be the maximum or minimum duration that the network device expects the terminal to perform data collection. When the first duration is the maximum duration for which the terminal performs data collection or the maximum duration that the network device expects the terminal to perform data collection, there is a maximum limit to the duration of data collection. This not only reduces the energy consumption caused by continuous data collection by the terminal but also ensures that the terminal collects enough data, reducing the latency caused by the network device needing to reissue configuration information if the terminal collects insufficient data or the configuration information is deleted, thus improving data collection efficiency. When the first duration is the minimum duration for which the terminal performs data collection or the minimum duration that the network device expects the terminal to perform data collection, there is a minimum limit to the duration of data collection. This ensures that the amount of data collected by the terminal meets the needs of the network device, reducing the latency caused by the network device needing to reissue configuration information if the terminal collects insufficient data or the configuration information is deleted, thus improving data collection efficiency.

[0145] The first data volume is the amount of data collected during the data collection process, such as 32 kilobytes (KB). Optionally, the first data volume can be the maximum or minimum data volume that the terminal can collect. Alternatively, the first data volume can be the maximum or minimum data volume that the network device expects the terminal to collect. When the first data volume is the maximum data volume that the terminal can collect or the maximum data volume that the network device expects the terminal to collect, there is a maximum limit to the amount of data collected by the terminal. This reduces the energy consumption caused by continuous data collection by the terminal and ensures that the terminal collects enough data. This also reduces the latency caused by the network device having to re-send configuration information if the terminal collects insufficient data or the configuration information is deleted, thus improving data collection efficiency. When the first data volume is the minimum data volume that the terminal can collect or the minimum data volume that the network device expects the terminal to collect, there is a minimum limit to the amount of data collected by the terminal. This ensures that the amount of data collected by the terminal meets the needs of the network device, reduces the latency caused by the network device having to re-send configuration information if the terminal collects insufficient data or the configuration information is deleted, thus improving data collection efficiency.

[0146] The first storage space includes at least one of the following: AS storage space, NAS storage space, or other storage space (i.e., storage space other than AS and NAS storage space in the first storage space), used to store the data collected during data collection. For example, the first storage space can be the maximum storage space or the minimum storage space. When the first storage space is the maximum storage space, it means that there is a maximum limit to the storage space used for storing data, reducing the possibility that the terminal will endlessly collect data and fill up the first storage space, thus occupying other storage spaces as well. This ensures that the terminal still has other storage space to store other information. When the first storage space is the minimum storage space, it means that there is a minimum limit to the storage space used for storing data. In other words, when the first storage space is full, the amount of data collected by the terminal already meets the needs of the network device, reducing the latency caused by the network device having to reissue configuration information after the terminal collects insufficient data and the configuration information is deleted, thereby improving data collection efficiency.

[0147] Optionally, the configuration information may also be used to indicate at least one application use case and / or at least one function. For example, the configuration information may include the identifier or name of at least one application use case. For instance, the configuration information may include CSI prediction. For example, the configuration information may include the identifier or name of at least one function. For instance, the configuration information may include function 1, etc. Alternatively, the configuration information may not be used to indicate at least one application use case and at least one function. For the former, the configuration information applies to at least one application use case and / or at least one function. For the latter, the configuration information may apply to all application use cases and / or functions.

[0148] Optionally, the configuration information may also include a data collection task identifier. Alternatively, the configuration information may not include a data collection task identifier. In the former case, the terminal distinguishes different configuration information based on the data collection task identifier. In the latter case, the terminal may distinguish different configuration information based on the specific configuration content within the configuration information. For example, the terminal may distinguish different configuration information based on the identifiers of application use cases and / or functions within the configuration information. The data collection task identifier can be referred to as a data collection task index or a data collection task number, used to uniquely identify a data collection task. For example, a network device may assign different data collection task identifiers to different data collection tasks, with each data collection task corresponding to one configuration information. That is, each configuration information may include one data collection task identifier.

[0149] Optionally, in addition to the contents listed above, the configuration information may also indicate other contents. For example, if the terminal does not support autonomous data collection, the contents indicated by the configuration information can be referred to in method ①. If the terminal supports autonomous data collection, the contents indicated by the configuration information can be referred to in method ②.

[0150] Method ①: The configuration information is also used to indicate the battery threshold or first battery range for performing data collection. For example, if the terminal's remaining battery power is greater than or equal to the battery threshold (e.g., 50%), or if the terminal's remaining battery power is within the first battery range, the terminal can perform data collection. This can reduce the possibility of data collection failure due to insufficient terminal battery power.

[0151] Optionally, the first power range may include an interval determined by the highest power threshold and the lowest power threshold. The first power range may include boundary points or may not include boundary points, such as the highest power threshold and / or the lowest power threshold, which is not limited here.

[0152] Optionally, in mode ①, the configuration information is also used to indicate at least one of the following: a first priority for performing data collection, whether the first storage space can be used to store data corresponding to the second priority, whether the data collected subsequently can be stored in the second storage space when the first storage space is full, or a first condition for stopping data collection.

[0153] In this context, the second priority is the priority for performing data collection, and it is higher than the first priority. That is, if the configuration information indicates that the first storage space can be used to store data corresponding to the second priority, then the terminal can store this data in the first storage space. If the configuration information indicates that the first storage space cannot be used to store data corresponding to the second priority, then the terminal cannot store this data in the first storage space. For the former, the terminal can allocate more resources to collect higher-priority data, ensuring sufficient amounts of higher-priority data and reducing the possibility of insufficient data collection due to insufficient storage space. For the latter, it ensures sufficient amounts of lower-priority data, reducing the possibility of insufficient data collection due to insufficient storage space.

[0154] Optionally, when the configuration information indicates whether the first storage space can be used to store data corresponding to the second priority, the configuration information can also be used to indicate a fourth condition, that is, the fourth condition is the condition under which the first storage space can be used to store data corresponding to the second priority. For example, the fourth condition may include that the remaining storage space in the first storage space is less than or equal to a seventh threshold, and the first storage space can be used to store data corresponding to the second priority. Alternatively, the fourth condition may include that the remaining storage space in the first storage space is greater than or equal to the seventh threshold, and the first storage space cannot be used to store data corresponding to the second priority. For example, if the storage space occupied by the data corresponding to the first priority is within 50% of the first storage space, the first storage space can still be used to store data corresponding to the second priority. Conversely, if the storage space occupied by the data corresponding to the first priority exceeds 50% of the first storage space, the first storage space cannot be used to store data corresponding to the second priority. In other words, the terminal can determine whether the first storage space can be used to store data corresponding to the second priority under the corresponding conditions, which reduces the problem of reduced collection efficiency of data corresponding to the first priority due to the terminal storing data corresponding to the second priority in the first storage space under all circumstances. That is, by setting and adjusting the condition of 'whether the first storage space can be used to store data corresponding to the second priority', the collection efficiency of data corresponding to the first priority can be improved.

[0155] Optionally, the second storage space includes at least one of the following: AS storage space, NAS storage space, or other storage space (i.e., storage space other than AS storage space and NAS storage space in the second storage space). The first storage space is different from the second storage space. For example, the size of the first storage space is larger or smaller than the size of the second storage space. Alternatively, the second storage space is used to store data corresponding to the third priority, which is the priority for performing data collection, and the third priority is lower than the first priority. That is, when the first storage space is full, the data collected subsequently can be stored in the lower-priority second storage space. This helps ensure that higher-priority data is available in sufficient quantities, reduces the situation of insufficient data collection due to insufficient storage space, and also helps reduce the energy consumption problem caused by the continuous data collection by the terminal.

[0156] Optionally, the first condition may include the terminal's remaining battery power being less than or equal to a first threshold, and / or the remaining storage space in the first storage space being less than or equal to a second threshold. That is, when the first condition is met, the terminal stops collecting data.

[0157] Optionally, in method ①, the configuration information is also used to indicate a second condition for triggering data reporting. The second condition may include at least one of the following: the amount of data collected is greater than or equal to a third threshold, the duration of data collection is greater than or equal to a fourth threshold, or the remaining battery power of the terminal is less than or equal to a fifth threshold. That is, when the second condition is met, the terminal reports data to the network device. For example, the terminal indicates to the network device that there is data to be reported. Or, it can be described as: the terminal can indicate to the network device that there is data to be reported locally. This allows the data collected by the terminal to be reported to the network device in a timely manner, reducing the power consumption caused by the terminal collecting data without restriction.

[0158] In one possible implementation, the aforementioned collected quantity can be replaced by: the percentage of collected data in the first storage space, or the percentage of collected data in the terminal's total storage space. That is, if the collected quantity is greater than or equal to a third threshold, for example, if the collected quantity is greater than 20kB, the terminal can report the data to the network device. Alternatively, if the percentage of collected data in the first storage space is greater than or equal to the third threshold, for example, if the percentage of collected data in the first storage space is greater than 50%, the terminal can report the data to the network device. Or, if the percentage of collected data in the terminal's total storage space is greater than or equal to the third threshold, for example, if the percentage of collected data in the terminal's total storage space is greater than 50%, the terminal can report the data to the network device.

[0159] In one possible implementation, the statement that the terminal's remaining battery power is less than or equal to the fifth threshold can be replaced by stating that the terminal's remaining battery power is within the second battery power range. That is, the terminal reports data to the network device when its remaining battery power is less than or equal to the fifth threshold, or when its remaining battery power is within the second battery power range.

[0160] Optionally, the second power range may include an interval determined by the highest power threshold and the lowest power threshold. The second power range may include boundary points or may not include boundary points, such as the highest power threshold and / or the lowest power threshold, which is not limited here.

[0161] Optionally, in method ①, the configuration information is also used to indicate whether to delete or retain the configuration information when the remaining battery power of the terminal is less than or equal to the sixth threshold. When the configuration information indicates that the configuration information should be retained when the remaining battery power of the terminal is less than or equal to the sixth threshold, the terminal can continue to perform data collection based on the configuration information when the battery power is greater than the sixth threshold later. This can reduce the situation where insufficient data collection is caused by insufficient terminal battery power.

[0162] Optionally, in method ①, the configuration information is also used to indicate a third condition that triggers the terminal to re-report its capabilities (such as data collection capabilities). Alternatively, the configuration information may not indicate a third condition that triggers the terminal to re-report its capabilities. For the former, the terminal can re-report its capabilities when the third condition is met. For the latter, the terminal can proactively report its capabilities. For example, the terminal can re-report its capabilities when or after its capabilities change. Or, the terminal can re-report its capabilities when or after the data reporting time arrives. Or, the terminal can re-report its capabilities when its capabilities change and the data reporting time arrives. This ensures that the terminal and network devices have a consistent understanding of the terminal's capabilities, reducing the likelihood of network devices misconfiguring parameters due to a lack of understanding of the terminal's capabilities, leading to terminal data collection failures.

[0163] The third condition includes at least one of the following: the time for data reporting has arrived, a capability reporting trigger event has occurred, or the capability reporting cycle has arrived.

[0164] For example, a terminal can re-report its capabilities when the data reporting time arrives or later. Alternatively, data and capabilities can be sent by the terminal together or separately to the network device.

[0165] For example, a terminal can re-report its capabilities when or after a capability reporting trigger event occurs. For instance, a capability reporting trigger event could be a change in the terminal's capabilities (such as data collection capabilities). In other words, the terminal can re-report its capabilities when or after a change in its capabilities.

[0166] For example, a terminal can re-report its capabilities when or after the capability reporting period has ended.

[0167] Optionally, in the examples above, the terminal can re-report all capabilities. Alternatively, compared to the previously reported capabilities, the terminal can report the capabilities that have changed. For example, if the previously reported application use cases supporting data collection were application use cases 1 to 3, and the application use cases supporting data collection have changed, such as application use cases 2 to 5, then the terminal can resend the capability information, which indicates application use cases 4 and 5. This can reduce signaling overhead.

[0168] Optionally, in method ①, the configuration information is also used to instruct the terminal to report cell information and / or network information for which data collection has been performed. That is, the terminal can report cell information and / or network information for which data collection has already been performed based on the configuration information.

[0169] In one possible implementation, cell information can be a cell identifier. The cell identifier can be used to uniquely identify a cell, such as a PCI or CGI identifier, and is not limited thereto. Alternatively, cell information can be a group identifier. The group identifier can be used to identify a cell group, which may include one or more cells. Alternatively, cell information can be a cell list, which may include one or more cells.

[0170] In one possible implementation, network information may include one or more network identifiers. The network identifier may be a PLMN identifier. Alternatively, network information may include one or more networks. It can also be said that network information may include a network list, which may include one or more networks. Here, the network is a carrier network; that is, a network identifier can be used to identify a carrier network. For example, PLMN identifier 1 is used to identify a China Unicom network, PLMN identifier 2 is used to identify a China Mobile network, and PLMN identifier 3 is used to identify a China Telecom network.

[0171] The relationship between the thresholds involved in method ① above is introduced below.

[0172] Optionally, the first threshold, the fifth threshold, and the sixth threshold may be the same or different. For example, the first threshold may be greater than or equal to the sixth threshold, and the fifth threshold may be greater than or equal to the sixth threshold.

[0173] Optionally, the second threshold and the seventh threshold can be the same or different. The second threshold can be greater than, equal to, or less than the seventh threshold.

[0174] The threshold mentioned in this application (such as any one of the first to eighth thresholds) may be predefined or indicated to the terminal by the network device, and is not limited here.

[0175] The relationship between the power ranges involved in method ① above is explained below.

[0176] Optionally, the first power range and the second power range can be the same or different. For example, the lowest power threshold of the first power range is less than or equal to the lowest power threshold of the second power range, and the highest power threshold of the first power range is less than or equal to the highest power threshold of the second power range.

[0177] Method ②: The configuration information is also used to indicate whether the terminal is allowed to handle data collection anomalies autonomously, and / or, the configuration information is also used to indicate the type of data collection anomalies that the terminal can handle autonomously.

[0178] When the configuration information indicates that the terminal is allowed to handle data collection anomalies autonomously, the terminal can handle data collection anomalies autonomously. When the configuration information indicates that the terminal is not allowed to handle data collection anomalies autonomously, the terminal cannot handle data collection anomalies autonomously. For example, the terminal can handle data collection anomalies based on the configuration information in method ① above. That is, 'the configuration information is also used to indicate at least one of the following: a first priority for performing data collection, whether the first storage space can be used to store data corresponding to the second priority, whether subsequently collected data can be stored in the second storage space when the first storage space is full, or a first condition for stopping data collection', the terminal can handle data collection anomalies based on these contents.

[0179] Optionally, the types of data collection anomalies that the terminal can autonomously handle may include at least one of the following: data collection anomaly, data storage anomaly, or other anomalies.

[0180] Data collection anomalies refer to data collection conflicts. For example, the terminal cannot collect data from different application use cases simultaneously, and / or the terminal cannot collect data from different functions simultaneously.

[0181] Data storage anomalies refer to data storage conflicts. For example, a terminal may have limited available storage space; it's important to determine which data can be stored together in the same storage space and which cannot.

[0182] Other anomalies refer to abnormal battery levels on the terminal during data collection. For example, if the terminal has low remaining battery power, which data should be collected first?

[0183] Optionally, in method ② above, the configuration information may further include cell information and / or network information for which data collection is performed. That is, the terminal can perform data collection in at least one cell indicated by the cell information and / or at least one network indicated by the network information. In one possible implementation, the terminal may also report the cell information and / or network information for which data collection has been performed to the network device. Wherein, the at least one cell indicated by the cell information for which data collection has been performed belongs to the at least one cell indicated by the cell information in the configuration information, and the at least one network indicated by the network information for which data collection has been performed belongs to the at least one network indicated by the network information in the configuration information.

[0184] Optionally, in method ① or method ② above, the configuration information can be carried in NAS messages, RRC messages (such as protocol-defined RRC configuration messages or RRC reconfiguration messages), MAC CE, DCI, IP pipe messages, or other messages. For example, if the network device is a core network device, the configuration information can be carried in NAS messages or other messages. If the network device is an access network device, the configuration information can be carried in RRC messages, MAC CE, DCI, or other messages. If the network device is an OAM device, the configuration information can be carried in IP pipe messages or other messages.

[0185] 303. The terminal performs data collection based on the configuration information.

[0186] Optionally, when the configuration information is the same as in method ① above, the terminal can indicate to the network device that there is data to be reported in the terminal. For example, when or after the terminal performs data collection based on the configuration information, the terminal can indicate to the network device that there is data to be reported in the terminal.

[0187] Optionally, when the configuration information is the same as in method ① above, the terminal can also indicate to the network device the duration of data collection and / or the amount of data collected. For example, the duration of data collection may be the duration used to collect data for at least one application use case and / or at least one function, and the amount of data collected may be the amount of data collected for at least one application use case and / or at least one function. The network device can then determine whether the amount of data collected by the terminal meets the network device's data collection requirements based on the duration of data collection and / or the amount of data collected. For example, whether the duration of data collection meets the network device's duration requirement, and / or whether the amount of data collected meets the network device's quantity requirement, etc.

[0188] When a network device determines that the amount of data collected by the terminal meets its data collection requirements based on the duration of data collection and / or the amount of data collected, the network device can instruct the terminal to report data. For example, the network device can indicate resources (including time-domain and / or frequency-domain resources) for data reporting to the terminal, allowing the terminal to report data based on these resources. Optionally, the resources for data reporting can be carried in NAS messages, RRC messages, DCI messages, IP pipe messages, or other messages. For example, if the network device is a core network device, the indication information can be carried in NAS messages or other messages. If the network device is an access network device, the indication information can be carried in RRC messages (such as RRC configuration messages or RRC reconfiguration messages), MAC CE, DCI, or other messages. If the network device is an OAM device, the indication information can be carried in IP pipe messages or other messages.

[0189] When a network device determines, based on the duration of data collection already performed and / or the amount of data collected, that the amount of data collected by the terminal does not meet the network device's data collection requirements, the network device may instruct the terminal to continue data collection. For example, the network device may instruct the terminal to continue data collection for at least one application use case and / or at least one function.

[0190] Optionally, the aforementioned 'data to be reported in the terminal', 'duration of data collection', and 'amount of data collected' can be carried in the same message or different messages. These messages can be NAS messages, RRC messages, UCIs, IP pipe messages, or other messages. For example, if the network device is a core network device, 'data to be reported in the terminal', 'duration of data collection', and 'amount of data collected' can be carried in the same NAS message or different NAS messages. If the network device is an access network device, 'data to be reported in the terminal', 'duration of data collection', and 'amount of data collected' can be carried in the same RRC message, different RRC messages, the same MAC CE, different MAC CEs, the same UCI, or different UCIs. If the network device is an OAM device, 'data to be reported in the terminal', 'duration of data collection', and 'amount of data collected' can be carried in the same IP pipe message or different IP pipe messages.

[0191] Optionally, when the configuration information is the same as that in method ② above, the terminal can send indication information. For example, when the terminal cannot complete the data collection task due to an anomaly, the terminal can send indication information. This indication information can be used to indicate the reason for the data collection anomaly and / or the method for handling the anomaly.

[0192] For example, the reason for data collection anomalies could be that storage space (such as third-party storage space, including AS storage space and / or NAS storage space) is saturated or about to be saturated. Storage space saturation can mean that the storage space is full. Storage space about to be saturated can mean that the remaining storage space is greater than or equal to an eighth threshold. In this case, the terminal can configure the priority of performing data collection itself. And / or, configure the storage space used to store the data, such as third-party storage space, etc. For example, high-priority data is collected first, and low-priority data is collected later. Or, when high-priority data fills the storage space, it can be stored in the storage space corresponding to low-priority data, and the storage space corresponding to low-priority data can be cleared, etc. Therefore, the above-mentioned 'method of handling data collection anomalies' can include: freeing up storage space to store the collected data, and / or deleting the data collection task. Optionally, when the 'method of handling data collection anomalies' includes deleting the data collection task, the indication information can also be used to indicate the priority of the deleted data collection task. Here, the data collection task can refer to performing data collection against at least one application use case and / or at least one function.

[0193] For example, the reason for the data collection anomaly could be that the terminal's battery is low. Alternatively, the reason for the data collection anomaly could be that the terminal's battery status drops from battery status A to battery status B. Battery status A can be a high battery status, and battery status B can be a medium battery status or a low battery status. Or, battery status A can be a medium battery status, and battery status B can be a low battery status.

[0194] Alternatively, in the two examples above, the 'method of handling data collection anomalies' may also include: stopping data collection, overwriting the data in the third storage space when the third storage space used to store the data is full, or deleting the configuration information.

[0195] For example, data collection can be stopped when or after the time when the terminal expects to report data. In other words, the terminal can stop data collection when or after the time when it expects to report data. For example, if the data collection anomaly is due to storage space saturation / or near saturation, or if the data collection anomaly is due to insufficient battery power, the terminal can stop data collection when or after the time when it expects to report data.

[0196] For example, when the third storage space used for storing data is full and the time for the terminal to report data arrives or later, the data in the third storage space can be overwritten. In other words, when the third storage space used for storing data is full and the time for the terminal to report data arrives or later, the terminal can overwrite the data in the third storage space. For example, if the data collection anomaly is due to storage space saturation / or near saturation, and the third storage space used for storing data is full and the time for the terminal to report data arrives or later, the terminal can overwrite the data in the third storage space. For example, the data in the third storage space can be cleared, and then the newly collected data can be stored in the third storage space. Alternatively, the data in the third storage space can be gradually overwritten using the newly collected data. That is, when new data is collected, the new data size is used to overwrite a portion of the data in the third storage space. When new data is collected again, the new data size continues to be used to overwrite a portion of the data in the third storage space.

[0197] For example, configuration information can be deleted when or after the time when the terminal expects to report data. In other words, the terminal can delete configuration information when or after the time when it expects to report data. For instance, if the data collection anomaly is due to storage space saturation / imminent saturation, or if the terminal's battery is low, the terminal can delete the configuration information when or after the time when it expects to report data. Alternatively, if the terminal receives new configuration information (data collection-related configuration), it can delete the configuration information. Or, if the data collected by the terminal is not reported before the time when it expects to report data, the terminal can delete the configuration information.

[0198] In one possible implementation, the aforementioned 'delete configuration information' can be replaced with retaining the configuration information. For example, if the data collection anomaly is caused by insufficient battery power, the terminal can retain the configuration information. For instance, if the data collection anomaly is caused by storage space saturation / or nearing saturation, or if the data collection anomaly is caused by insufficient battery power, and the terminal expects to report data at or after this time, the terminal can retain the configuration information. That is, the terminal can continue performing data collection based on the configuration information when or after sufficient battery power. Alternatively, the terminal can continue performing data collection based on the configuration information when or after free storage space is available.

[0199] Optionally, the aforementioned indication information is also used to indicate the time at which the terminal expects to report data and / or the existence of data to be reported in the terminal. In one possible implementation, 'the time at which the terminal expects to report data' can be described as: the time period during which the terminal expects the network device to allocate resources (including time-domain resources and / or frequency-domain resources, etc.) for data reporting. For example, the terminal expects the network device to allocate resources for data reporting within 5 minutes.

[0200] Optionally, the above-mentioned indication information can also be used to indicate changes in the terminal's capabilities (such as data collection capabilities).

[0201] Optionally, the aforementioned indication information can be carried in NAS messages, RRC messages, UCI, IP pipe messages, or other messages. For example, if the network device is a core network device, the indication information can be carried in NAS messages or other messages. If the network device is an access network device, the indication information can be carried in RRC messages, MAC CE, UCI, or other messages. If the network device is an OAM device, the indication information can be carried in IP pipe messages or other messages.

[0202] Optionally, when the network device learns through indication information that there is data to be reported in the terminal, the network device may instruct the terminal to report the data. For example, the network device may indicate to the terminal resources (including time-domain resources and / or frequency-domain resources) for data reporting, so that the terminal can report data based on the resources.

[0203] Optionally, when the network device learns through indication information that the terminal's capabilities (such as data collection capabilities) have changed, the network device can also instruct the terminal to re-report the capabilities (such as data collection capabilities). Alternatively, the network device may not instruct the terminal to re-report the capabilities (such as data collection capabilities). In the former case, the terminal can re-report all capabilities based on the network device's instruction, or, compared to the previously reported capabilities, the terminal can report the changed capabilities. In the latter case, the terminal can decide independently whether to re-report the capabilities (such as data collection capabilities). For example, the terminal can proactively report all capabilities, or, compared to the previously reported capabilities, the terminal can proactively report the changed capabilities.

[0204] In one possible implementation, 'resources for data reporting' and 'indication of terminal re-reporting capability' can be carried in the same message or different messages. These messages can be NAS messages, RRC messages, UCIs, IP pipe messages, or other messages. For example, if the network device is a core network device, 'resources for data reporting' and 'indication of terminal re-reporting capability' can be carried in the same NAS message or different NAS messages. If the network device is an access network device, 'resources for data reporting' and 'indication of terminal re-reporting capability' can be carried in the same RRC message, different RRC messages, the same MAC CE, different MAC CEs, the same UCI, or different UCIs. If the network device is an OAM device, 'resources for data reporting' and 'indication of terminal re-reporting capability' can be carried in the same IP pipe message or different IP pipe messages.

[0205] As can be seen from the above embodiments, the terminal can report capability information, enabling the network device to determine configuration information based on this capability information. That is, the network device can generate reasonable configuration parameters through the terminal's capabilities. This reduces the likelihood of data collection failures due to unreasonable configuration parameters when the terminal performs data collection based on the configuration information from the network device, thus improving data collection efficiency.

[0206] Optionally, to achieve the aforementioned functions, the device includes corresponding hardware structures and / or software modules for performing each function. Those skilled in the art will 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.

[0207] This application embodiment can divide the terminal or network device into functional modules according to the above method examples. For example, each function can be divided into its own functional modules, 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.

[0208] Referring to Figure 4, which is a schematic diagram of the structure of a communication device provided in an embodiment of this application, the communication device 400 can be applied to the method shown in the embodiment of Figure 3 above. As shown in Figure 4, the communication device 400 includes a processing module 401 and a transceiver module 402. The processing module 401 may be one or more processors, and the transceiver module 402 may be a transceiver or a communication interface. The communication device can be used to implement the terminal or network device involved in any of the above method embodiments, or to implement the function of the network element involved in any of the above method embodiments. The network element or network function may be a network element in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). Optionally, the communication device 400 may also include a storage module 403 for storing the program code and data of the communication device 400. It should be understood that regardless of whether these functional modules are subdivided or combined, the general process executed by the communication device 400 in implementing any of the above method embodiments is the same. For example, the transceiver module 402 in the aforementioned communication device 400 may include a receiving module and / or a transmitting module. Of course, the transceiver module may also be called a communication module. In one implementation, each module may have its own program code (or program instructions). When the program code corresponding to each module is run on the processor, it causes the unit to execute the corresponding process to achieve the corresponding function.

[0209] In one example, the communication device functions as a terminal or as a chip applied within a terminal, i.e., a chip used in a terminal, and executes the steps performed by the terminal in the above method embodiments. The transceiver module 402 is used to specifically execute the sending and / or receiving actions performed by the terminal in the embodiment shown in FIG3, for example, supporting the terminal in performing other processes of the technology described herein. The processing module 401 can be used to support the communication device 400 in performing the processing actions in the above method embodiments, for example, supporting the terminal in performing other processes of the technology described herein.

[0210] For example, transceiver module 402 is used to send capability information, which indicates at least one of the following: application use cases for data collection supported by the terminal, functions for data collection supported by the terminal, number of condition identifiers, type of condition identifiers, available storage space of the terminal, or battery level of the terminal. The condition identifiers indicate the network conditions applicable to the application use cases and / or functions for data collection supported by the terminal. Transceiver module 402 is also used to receive configuration information. Processing module 401 is used to perform data collection based on the configuration information.

[0211] Optionally, the transceiver module 402 is also used to send indication information, which indicates the reason for the data collection anomaly and / or the method for handling the data collection anomaly.

[0212] In one example, when the communication device functions as a network device or as a chip applied within a network device (i.e., a chip used in a network device), it executes the steps performed by the network device in the above method embodiments. The transceiver module 402 is used to specifically execute the sending and / or receiving actions performed by the network device in the embodiment shown in FIG3, for example, supporting the network device in performing other processes of the technology described herein. The processing module 401 can be used to support the communication device 400 in performing the processing actions in the above method embodiments, for example, supporting the network device in performing other processes of the technology described herein.

[0213] For example, transceiver module 402 is configured to: receive capability information, which indicates at least one of the following: application use cases for data collection supported by the terminal, functions for data collection supported by the terminal, number of condition identifiers, type of condition identifiers, available storage space of the terminal, or battery level of the terminal, wherein the condition identifiers indicate the network conditions applicable to the application use cases and / or functions for data collection supported by the terminal; and send configuration information, which is determined based on the capability information and is used to perform data collection.

[0214] Optionally, the transceiver module 402 is also used to receive indication information, which indicates the reason for the data collection anomaly and / or the method for handling the data collection anomaly.

[0215] In one possible implementation, when the aforementioned device is a chip, such as a modem chip, a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip; or when the aforementioned device is a communication module, the transceiver module 402 can be a communication interface, pins, or circuits. The communication interface can be used to input data to be processed to the processor and can output the processor's processing results. Specifically, the communication interface can be a general-purpose input / output (GPIO) interface, which can connect to multiple peripheral devices (such as a liquid crystal display (LCD), camera, radio frequency (RF) module, antenna, etc.). The communication interface is connected to the processor via a bus.

[0216] The processing module 401 can be a processing circuit, which can be one or more processors, or all or part of the circuitry in one or more processors used for control and / or processing. The processing circuit or processor can execute computer execution instructions stored in the storage module to cause the chip to execute the method involved in the embodiment shown in FIG3. Further, the processor can include a controller, an arithmetic logic unit (ALU), and registers. For example, the controller is mainly responsible for instruction decoding and issuing control signals for the operations corresponding to the instructions. The ALU is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations, and logical operations, and can also perform address operations and conversions. The registers are mainly responsible for storing register operands and intermediate operation results temporarily stored during instruction execution. In specific implementations, the processor's hardware architecture can be an application-specific integrated circuit (ASIC) architecture, a microprocessor without interlocked piped stages architecture (MIPS) architecture, an advanced reduced instruction set machine (RISC) machine (ARM) architecture, or a network processor (NP) architecture, etc. The processor can be single-core or multi-core. The storage module can be an internal storage module of the chip, such as a register or cache. Alternatively, the storage module can be an external storage module, such as read-only memory (ROM) or other types of static storage devices that can store static information and instructions, or random access memory (RAM).

[0217] Optionally, the functions of the processor and interface can be implemented through hardware design, software design, or a combination of hardware and software; no restrictions are imposed here.

[0218] Figure 5 is a schematic diagram of another communication device provided in an embodiment of this application. It is understood that the communication device 510 includes necessary means such as modules, units, elements, circuits, or interfaces, appropriately configured together to execute this solution. The communication device 510 can be the aforementioned terminal or network device, or a component (e.g., a chip) within these devices, used to implement the methods described in the above method embodiments. The communication device 510 includes one or more processors 511. The processor 511 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device (e.g., a terminal, network device, or chip), execute software programs, and process data from the software programs.

[0219] Optionally, in one design, the processor 511 may include a program 513 (sometimes also referred to as code or instructions), which can be executed on the processor 511 to cause the communication device 510 to perform the methods described in the above embodiments. In yet another possible design, the communication device 510 includes circuitry (not shown in FIG. 5) for implementing the terminal, network device, and other functions described in the above embodiments. Optionally, the communication device 510 may include one or more memories 512 storing a program 514 (sometimes also referred to as code or instructions), which can be executed on the memory 512 to cause the communication device 510 to perform the methods described in the above method embodiments.

[0220] Optionally, data may also be stored in the processor 511 and / or the memory 512. The processor and memory may be configured separately or integrated together.

[0221] Optionally, if the communication device 510 is a terminal or network device, it may also include a transceiver 515 and / or an antenna 516. The processor 511, sometimes referred to as a processing unit, controls the communication device (e.g., a terminal or network device). The transceiver 515, sometimes referred to as a transceiver unit, transceiver, or transceiver circuit, is used to implement the transmission and reception functions of the communication device via the antenna 516. Optionally, the transceiver 515 may include a receiver and / or a transmitter. The receiver may be referred to as a receiving unit, receiver, or receiving circuit. The transmitter may be referred to as a transmitting unit, transmitter, or transmitting circuit.

[0222] Optionally, if the communication device 510 is a chip for a terminal or network device, the transceiver 515 may be a transceiver circuit, such as an input / output interface, or a transceiver interface.

[0223] This application also provides a communication device, which includes at least one processor; wherein the at least one processor is configured to perform the method described in any of the embodiments shown in FIG3.

[0224] This application also provides a computer-readable storage medium storing computer instructions that, when executed, cause the computer to perform the method described in any of the embodiments shown in FIG3.

[0225] This application also provides a computer program product, which includes computer program code. When the computer program code is run, it causes the computer to perform the method described in any of the embodiments shown in FIG3.

[0226] This application also provides a chip, which includes at least one processor and an interface. The processor is used to read and execute instructions stored in a memory. When the instructions are executed, the chip causes the chip to perform the method described in any of the embodiments shown in FIG3.

[0227] Optionally, the processing performed by a single execution entity (terminal or network device) shown in any of the above embodiments can also be divided into multiple execution entities, which can be logically and / or physically separated.

[0228] For example, if the network device is an access network device, the processing performed by the network device can be divided into execution by at least one of CU, DU, RU, non-real-time RIC, near-real-time RIC, and SU. Alternatively, the processing performed by the network device can be executed by the SU, for example, if the SU and access network device are deployed independently, the processing performed by the network device can be executed by the SU. For instance, the O-RU can act as an intermediate node for interaction between the terminal and the O-CU-CP. The O-CU is used to generate and send the aforementioned configuration information to the terminal via the O-RU. Alternatively, the O-CU can be used to generate configuration information, some or all of which can come from a non-real-time RIC or a near-real-time RIC. Optionally, when the processing performed by the network device can be divided into execution by at least one of CU, DU, RU, non-real-time RIC, near-real-time RIC, and SU, at least one of CU, DU, RU, non-real-time RIC, near-real-time RIC, and SU can also send data to other nodes. These other nodes can be any network-side node that needs to collect data from the terminal, such as core network devices or OAM devices.

[0229] For example, if the network device is an OAM device, the processing performed by the network device can be divided and performed by the trace collection entity (TCE).

[0230] Furthermore, the various embodiments of this application are merely illustrative examples of executing all the steps included, and should not be considered as specific limitations on this application. For example, the order of steps in various embodiments can be simply changed according to their function and internal logic; or, for example, all steps in various embodiments can be executed, or only a portion of them can be executed, as long as the same function as in the embodiments of this application can be achieved.

[0231] In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to a network device" can be understood as the destination of the information being the network device, which can include direct transmission via the air interface or indirect transmission via the air interface from other units or modules. "Receive information from a network device" can be understood as the source of the information being the network device, which can include direct reception from the network device via the air interface or indirect reception from the network device via the air interface from other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface.

[0232] In other words, sending and receiving can occur between devices, such as between network devices and terminals; or they can occur within a device, such as between components, modules, chips, software modules, or hardware modules within a device via a bus, wiring, or interface.

[0233] In the embodiments of this application, "when," "if," "if," and "in the case of" all refer to the device making corresponding processing under certain objective circumstances, and are not limited to a time, nor do they require the device to make a judgment action when it is implemented, nor do they mean that there are other limitations.

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

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

Claims

1. A communication method, characterized in that, include: Send capability information, which indicates at least one of the following: application use cases for data collection supported by the terminal, functions for data collection supported by the terminal, number of condition identifiers, type of condition identifiers, available storage space of the terminal or battery level of the terminal, wherein the condition identifiers indicate the network conditions applicable to the application use cases and / or functions for data collection supported by the terminal; Receive configuration information, which is determined based on the capability information; Data collection is performed based on the configuration information.

2. The method according to claim 1, characterized in that, The configuration information includes at least one of the following: a first condition identifier, a first duration, a first data volume, or a first storage space; Wherein, the network condition indicated by the first condition identifier is the network condition applicable to at least one application use case and / or at least one function, the first duration is the duration of data collection, the first data volume is the data volume of data collection, and the first storage space is used to store the data collected during data collection.

3. The method according to claim 1 or 2, characterized in that, The configuration information is also used to indicate at least one of the following: a first priority for performing data collection, whether the first storage space can be used to store data corresponding to the second priority, whether data collected subsequently can be stored in the second storage space when the first storage space is full, or a first condition for stopping data collection; Wherein, the second priority is the priority for performing data collection, the second priority is higher than the first priority, the first storage space is different from the second storage space, and the first condition includes the remaining battery power of the terminal being less than a first threshold and / or the remaining storage space of the first storage space being less than a second threshold.

4. The method according to any one of claims 1-3, characterized in that, The configuration information is also used to indicate a second condition for triggering data reporting, the second condition including at least one of the following: the amount of data collected is greater than a third threshold, the duration of data collection is greater than a fourth threshold, or the remaining battery power of the terminal is less than a fifth threshold.

5. The method according to any one of claims 1-4, characterized in that, The configuration information is also used to indicate whether to delete or retain the configuration information if the remaining battery power of the terminal is less than a sixth threshold.

6. The method according to any one of claims 1-5, characterized in that, The configuration information is also used to indicate a third condition that triggers the terminal's ability to re-report; The third condition includes at least one of the following: the time for data reporting has arrived, a capability reporting trigger event has occurred, or the capability reporting cycle has arrived.

7. The method according to any one of claims 1-6, characterized in that, The configuration information is also used to instruct the terminal to report cell information and / or network information for performing data collection.

8. The method according to claim 1 or 2, characterized in that, The capability information is also used to instruct the terminal to support autonomous data collection.

9. The method according to claim 1, 2 or 8, characterized in that, The configuration information is also used to allow the terminal to autonomously handle data collection anomalies, and / or the configuration information is also used to indicate the type of data collection anomaly that the terminal autonomously handles.

10. The method according to claim 1, 2, 8 or 9, characterized in that, The method further includes: Send an instruction message, which is used to indicate the reason for the data collection anomaly and / or the method for handling the data collection anomaly.

11. The method according to any one of claims 1, 2, or 8-10, characterized in that, The indication information is also used to indicate the time when the terminal expects to report data and / or the existence of data to be reported in the terminal.

12. The method according to claim 11, characterized in that, The method for handling data collection anomalies also includes at least one of the following: stopping data collection when the time for the terminal to report data arrives; overwriting the data in the third storage space when the third storage space used for storing data is full and the time for the terminal to report data arrives; or deleting the configuration information when the time for the terminal to report data arrives.

13. A communication method, characterized in that, include: Receive capability information, the capability information being used to indicate at least one of the following: application use cases for data collection supported by the terminal, functions for data collection supported by the terminal, number of condition identifiers, type of condition identifiers, available storage space of the terminal, or battery level of the terminal, wherein the condition identifiers are used to indicate network conditions applicable to the application use cases and / or functions for data collection supported by the terminal; Send configuration information, which is determined based on the capability information, and is used to perform data collection.

14. The method according to claim 13, characterized in that, The configuration information includes at least one of the following: a first condition identifier, a first duration, a first data volume, or a first storage space; Wherein, the network condition indicated by the first condition identifier is the network condition applicable to at least one application use case and / or at least one function, the first duration is the duration of data collection, the first data volume is the data volume of data collection, and the first storage space is used to store the data collected during data collection.

15. The method according to claim 13 or 14, characterized in that, The configuration information is also used to indicate at least one of the following: a first priority for performing data collection, whether the first storage space can be used to store data corresponding to the second priority, whether data collected subsequently can be stored in the second storage space when the first storage space is full, or a first condition for stopping data collection; Wherein, the second priority is the priority for performing data collection, the second priority is higher than the first priority, the first storage space is different from the second storage space, and the first condition includes the remaining battery power of the terminal being less than a first threshold and / or the remaining storage space of the first storage space being less than a second threshold.

16. The method according to any one of claims 13-15, characterized in that, The configuration information is also used to indicate a second condition for triggering data reporting, the second condition including at least one of the following: the amount of data collected is greater than a third threshold, the duration of data collection is greater than a fourth threshold, or the remaining battery power of the terminal is less than a fifth threshold.

17. The method according to any one of claims 13-16, characterized in that, The configuration information is also used to indicate whether to delete or retain the configuration information if the remaining battery power of the terminal is less than a sixth threshold.

18. The method according to any one of claims 13-17, characterized in that, The configuration information is also used to indicate a third condition that triggers the terminal's ability to re-report; The third condition includes at least one of the following: the time for data reporting has arrived, a capability reporting trigger event has occurred, or the capability reporting cycle has arrived.

19. The method according to any one of claims 13-18, characterized in that, The configuration information is also used to instruct the terminal to report cell information and / or network information for performing data collection.

20. The method according to claim 13 or 14, characterized in that, The capability information is also used to instruct the terminal to support autonomous data collection.

21. The method according to claim 13, 14 or 20, characterized in that, The configuration information is also used to allow the terminal to autonomously handle data collection anomalies, and / or the configuration information is also used to indicate the type of data collection anomaly that the terminal autonomously handles.

22. The method according to claim 13, 14, 20 or 21, characterized in that, The method further includes: Receive instruction information, which is used to indicate the reason for the data collection anomaly and / or the method for handling the data collection anomaly.

23. The method according to any one of claims 1, 2, or 20-22, characterized in that, The indication information is also used to indicate the time when the terminal expects to report data and / or the existence of data to be reported in the terminal.

24. The method according to claim 11, characterized in that, The method for handling data collection anomalies also includes at least one of the following: stopping data collection when the time for the terminal to report data arrives; overwriting the data in the third storage space when the third storage space used for storing data is full and the time for the terminal to report data arrives; or deleting the configuration information when the time for the terminal to report data arrives.

25. A communication device, characterized in that, It includes units or modules for implementing the method as described in any one of claims 1-12, or includes units or modules for implementing the method as described in any one of claims 13-24.

26. A communication device, characterized in that, The communication device includes at least one processor; wherein the at least one processor is configured to cause the communication device to perform the method of any one of claims 1-12, or the at least one processor is configured to cause the communication device to perform the method of any one of claims 13-24.

27. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions or programs that, when executed, cause the computer to perform the method as described in any one of claims 1-12, or cause the computer to perform the method as described in any one of claims 13-24.

28. A chip, characterized in that, The chip includes at least one processor, the processor being configured to execute computer instructions or programs that, when the computer instructions or programs are executed, cause the chip to perform the method as described in any one of claims 1-12, or cause the chip to perform the method as described in any one of claims 13-24.

Images