Communication method and device

Abstract

Embodiments of this application provide a communication method and apparatus that enable AS data collection of a terminal device to be performed by an EVEX data collection mechanism. The method includes the steps of a network device detecting the data collection capabilities supported by the terminal device's AS, selecting a first configuration to be used by the terminal device to collect AS data delivered by and expected by an application providing entity, and excluding data collection configurations not supported by the terminal device from the first configuration, so that the data collection capabilities supported by the terminal device's AS are matched to the selected configuration and AS data collection is performed.

Description

Technical Field

[0001] This application claims the priority of Chinese Patent Application No. 202311010644.4, titled "Communication Method and Apparatus", filed with the China National Intellectual Property Administration on August 10, 2023, and the entire content of the Chinese patent application is incorporated herein by reference.

[0002] Embodiments of this application relate to the field of communications, and in particular, to communication methods and apparatuses.

Background Art

[0003] In an event exposure (EVEX) data collection mechanism, a data collection application function (DCAF) can obtain application layer data of a user equipment (UE) directly through a direct data collection client (DDCC), or can obtain application layer data of the UE indirectly through an indirect data collection client (IDCC). In the EVEX data collection mechanism, only a specific mechanism for collecting application layer data of the UE is defined, and there is no appropriate method for collecting access stratum (AS) data of the UE.

Summary of the Invention

Means for Solving the Problems

[0004] Embodiments of this application provide a communication method and apparatus so that AS data collection of the UE can be implemented in the EVEX data collection mechanism.

[0005] To achieve the above object, the following technical solutions are used in embodiments of this application.

[0006] According to the first embodiment, a communication method is provided. This method may be performed by a network device, or by a part of a network device, for example, by a processor, chip, or chip system of the network device, or by a logic module or software capable of performing all or part of the functions of the network device. Hereinafter, an example of this method being performed by a network device will be used for illustrative purposes. This method includes the step of the network device receiving first capability information from a terminal device, the first capability information indicating the data collection capabilities supported by the terminal device's access stratum AS. The network device receives a first configuration from an application-providing entity, the first configuration being used by the terminal device to collect AS data expected by the application-providing entity. Based on the first capability information, the network device determines from the first configuration which configuration is supported by the terminal device and used for AS data collection.

[0007] According to this communication method, the network device detects the data collection capabilities supported by the terminal device's AS, selects a first configuration to be used by the terminal device to collect AS data delivered by and expected by the application provider entity, and excludes data collection configurations not supported by the terminal device from the first configuration. As a result, the data collection capabilities supported by the terminal device's AS are matched to the selected configuration, improving the network device's management and control of collected AS data and associated configurations, and enabling AS data collection. In this way, the collected AS data can be disclosed to the application provider entity or another network entity, enabling the application provider entity or another network entity to complete relevant event processing based on the disclosed AS data, thus achieving effective AS data utilization.

[0008] In one possible design solution, the network device is an access network device or an access and mobility management network element, and the network device receiving a first configuration from an application-providing entity may include the network device receiving the first configuration from the application-providing entity through a data-collecting application entity. According to this design solution, the first configuration delivered by the application-providing entity may be forwarded to the network device by the data-collecting application entity, and as a result, the network device selects a configuration from the first configuration that is supported by the terminal device and used for AS data collection.

[0009] In one possible design solution, the method provided in this embodiment of the present application may further include the step of a network device determining which data collection capabilities supported by the terminal device's AS can be transmitted to a data collection application entity or application provider entity. According to this design solution, to enhance the reliability of communications, the network device can manage and control the AS data collection capabilities disclosed to a third party (e.g., a data collection application entity or application provider entity) by the terminal device when the terminal device's AS data collection capabilities are disclosed to a third party.

[0010] In one possible design solution, the method provided in this embodiment of the present application may further include the step of a network device transmitting first feedback information to a data collection application entity. According to this design solution, after selecting a first configuration, the network device can notify the data collection application entity of the selection result by the first feedback information. In this way, the data collection application entity further notifies the application provider entity of the selection result, and in addition, the data collection application entity updates the first configuration based on the selection result to obtain an AS data collection configuration suitable for the terminal device.

[0011] In one possible design solution, the method provided in this embodiment of the present application may further include the step of a network device transmitting first feedback information to an application providing entity through a data collection application entity. According to this design solution, after selecting the first configuration, the network device can notify the application providing entity of the selection results through the data collection application entity, and as a result the application providing entity can determine which of the first configurations can be performed by terminal devices and which cannot be performed by terminal devices.

[0012] In one possible design solution, the network device is a data acquisition application entity, and the method provided in this embodiment of the present application may further include the step of the network device transmitting first feedback information to the application provider entity. According to this design solution, the data acquisition application entity detects the data acquisition capabilities supported by the AS of the terminal device, selects a first configuration to be used by the terminal device to collect AS data that is delivered by and expected by the application provider entity, and notifies the application provider entity of the selection result.

[0013] In one possible design solution, the first feedback information indicates some or all of the first configurations supported by the terminal device.

[0014] In one possible design solution, the first feedback information may include at least one of the following reasons: a configuration supported by the terminal device and used for AS data collection, a configuration not supported by the terminal device and used for AS data collection, or a configuration not supported by the terminal device and used for AS data.

[0015] In one possible design solution, the method provided in this embodiment of the present application may further include the step of a network device transmitting a second configuration to a terminal device, the second configuration being obtained by updating the first configuration based on a configuration supported by the terminal device and used for AS data collection. According to this design solution, a data collection application entity can update the first configuration based on the selection results to obtain an AS data collection configuration suitable for the terminal device and deliver that configuration to the terminal device for collecting AS data.

[0016] In one possible design solution, the network device sending a second configuration to a terminal device may include the network device sending the second configuration to the terminal device through an application-providing entity.

[0017] In one possible design solution, the data collection capability supported by the AS of the terminal device includes supporting or not supporting the transmission of AS data to the application layer of the terminal device.

[0018] In one possible design solution, the data collection capability supported by the AS of a terminal device includes supporting the transmission of AS data to the application layer of the terminal device, and the data collection capability supported by the AS of a terminal device may further include at least one of the following: the type of AS data that is supported for transmission to the application layer of the terminal device, the supported AS data format, or the supported object for obtaining the AS data.

[0019] According to a second aspect, a communication method is provided. This method may be performed by a data acquisition application entity, or by a part of the data acquisition application entity, for example, by a processor, chip, or chip system of the data acquisition application entity, or by a logic module or software capable of performing all or part of the functions of the data acquisition application entity. An example of this method being performed by a data acquisition application entity is used for illustrative purposes. This method includes the step of the data acquisition application entity receiving a first configuration from an application provider entity, the first configuration being used by a terminal device to collect AS data expected by the application provider entity. The data acquisition application entity receives first feedback information from a network device, the first feedback information indicating some or all of the first configurations supported by the terminal device. The data acquisition application entity sends a second configuration to the terminal device, the second configuration being obtained by updating the first configuration based on the first feedback information.

[0020] According to this communication method, a data collection application entity can update the first configuration based on some or all of the configurations supported by the terminal device and fed back by the network device, so that the delivered configuration conforms to the data collection capabilities supported by the terminal device's AS.

[0021] In one possible design solution, the first feedback information may include at least one of the following reasons: a configuration supported by the terminal device and used for AS data collection, a configuration not supported by the terminal device and used for AS data collection, or a configuration not supported by the terminal device and used for AS data.

[0022] In one possible design solution, the data collection application entity sending a second configuration to the terminal device may include the data collection application entity sending the second configuration to the terminal device through the application provider entity.

[0023] According to a third aspect, a communication method is provided. This method may be performed by a network device, or by a part of a network device, for example, by a processor, chip, or chip system of the network device, or by a logic module or software capable of performing all or part of the functions of the network device. Hereinafter, an example of this method being performed by a network device will be used for illustrative purposes. This method includes the step of a network device receiving first capability information from a first terminal device, the first capability information indicating data collection capabilities supported by an access stratum AS of the first terminal device. The network device receives one or more configuration groups from an application providing entity, each of which is used by the terminal device to collect AS data expected by the application providing entity. The network device determines a second configuration from the one or more configuration groups based on the first capability information, the second configuration being a configuration supported by the first terminal device and used for AS data collection. The network device transmits the second configuration to the first terminal device.

[0024] According to this communication method, in order to complete AS data collection, the network device matches a configuration that can be executed based on the capabilities of the terminal device from one or more configuration groups distributed by the application providing entity, based on the AS data collection capability reported by the terminal device, and transmits the configuration to the terminal device.

[0025] In one possible design solution, a network device receiving one or more configurations from an application-providing entity may include a network device receiving one or more configuration groups from the application-providing entity through a data-collecting application entity.

[0026] In one possible design solution, the network device transmitting the second configuration to the first terminal device may include the network device transmitting the second configuration to the first terminal device through a data collection application entity.

[0027] In one possible design solution, the method provided in this embodiment of the present application may further include the step of the network device transmitting second feedback information to a data collection application entity, where the second feedback information indicates an AS data collection situation corresponding to a configuration executed by a terminal device among one or more configuration groups.

[0028] In one possible design solution, the second feedback information may include at least one of the following: collected AS data, uncollected AS data, or the reason for uncollected AS data.

[0029] In one possible design solution, the network device may be an access network device or an access and mobility management network element.

[0030] In one possible design solution, the data collection capability supported by the AS of the first terminal device includes whether the transmission of AS data to the application layer of the first terminal device is supported.

[0031] In one possible design solution, the data collection capability supported by the AS of the first terminal device includes that the transmission of AS data to the application layer of the first terminal device is supported, and the data collection capability supported by the AS of the first terminal device further includes at least one of the following: the type of AS data whose transmission to the application layer of the first terminal device is supported, the supported AS data format, or the supported object for obtaining AS data.

[0032] In one possible design solution, the method provided in this embodiment of the present application may further include the step of a network device determining which data collection capabilities supported by the AS of a first terminal device can be transmitted to a data collection application entity or an application providing entity.

[0033] According to a fourth aspect, a communication method is provided. This method may be performed by an application-providing entity, or by a part of the application-providing entity, for example, by a processor, chip, or chip system of the application-providing entity, or by a logic module or software capable of performing all or part of the functions of the application-providing entity. An example of this method being performed by an application-providing entity is used for illustrative purposes. This method includes the step of an application-providing entity receiving first capability information from a terminal device, the first capability information indicating a data acquisition capability supported by the terminal device's access stratum AS. The application-providing entity determines a second configuration based on the first capability information, the second configuration being a configuration supported by the terminal device and used for AS data acquisition. The application-providing entity transmits the second configuration to the terminal device.

[0034] According to this communication method, in order to perform AS data collection, the application providing entity can directly configure an appropriate AS data collection configuration for the terminal device by detecting the terminal device's AS data collection capability.

[0035] In one possible design solution, the application-providing entity sending a second configuration to the terminal device may include the application-providing entity sending the second configuration to the terminal device through a data-collecting application entity.

[0036] In one possible design solution, the data collection capability supported by the AS of the terminal device includes supporting or not supporting the transmission of AS data to the application layer of the terminal device.

[0037] In one possible design solution, the data collection capability supported by the AS of a terminal device includes supporting the transmission of AS data to the application layer of the terminal device, and the data collection capability supported by the AS of a terminal device may further include at least one of the following: the type of AS data that is supported for transmission to the application layer of the terminal device, the supported AS data format, or the supported object for obtaining the AS data.

[0038] According to a fifth aspect, a communication method is provided. This method may be performed by a terminal device, or by a part of a terminal device, for example, by a processor, chip, or chip system of the terminal device, or by a logic module or software capable of performing all or part of the functions of the terminal device. Hereinafter, an example of this method being performed by a terminal device will be used for explanation. This method includes the steps of: transmitting first capability information, wherein the first capability information indicates a data acquisition capability supported by an access stratum AS of the terminal device; and receiving a second configuration, wherein the second configuration is a configuration supported by the terminal device and used for AS data acquisition, and the second configuration is determined based on the first capability information.

[0039] In one possible design solution, the step of transmitting the first capability information may include the step of transmitting the first capability information to an access network device or an access and mobility management network element.

[0040] In one possible design solution, the step of transmitting the first capability information may include the step of transmitting the first capability information to a data collection application entity.

[0041] In one possible design solution, the step of transmitting the first capability information may include the step of transmitting the first capability information to the application-providing entity.

[0042] In one possible design solution, the step of receiving the second configuration may include the step of receiving the second configuration from the application-providing entity.

[0043] In one possible design solution, the step of receiving the second configuration may include the step of receiving the second configuration from the data collection application entity.

[0044] In one possible design solution, the data collection capability supported by the AS of the terminal device includes supporting or not supporting the transmission of AS data to the application layer of the terminal device.

[0045] In one possible design solution, the data collection capability supported by the AS of a terminal device includes supporting the transmission of AS data to the application layer of the terminal device, and the data collection capability supported by the AS of a terminal device may further include at least one of the following: the type of AS data that is supported for transmission to the application layer of the terminal device, the supported AS data format, or the supported object for obtaining the AS data.

[0046] For the technical effects of the method according to the fifth embodiment, please refer to the technical effects of the method according to any one of the first to fourth embodiments. Further details will not be explained here.

[0047] According to the sixth aspect, a communication device is provided for carrying out the method described above. The communication device may be a network device according to the first aspect, a device including a network device, or a device included within a network device, such as a chip. The communication device includes corresponding modules, units, or means for carrying out the method according to the first aspect. The modules, units, or means may be implemented by hardware, software, or hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0048] In some possible designs, the communication device includes a processing module and a transceiver module. The transceiver module is configured to receive first capability information from a terminal device, which indicates the data collection capabilities supported by the terminal device's access stratum AS. The transceiver module is further configured to receive first configuration from an application-providing entity, which is used by the terminal device to collect AS data expected by the application-providing entity. The processing module is configured to determine, based on the first capability information, which configuration from the first configuration is supported by the terminal device and used for AS data collection.

[0049] In one possible design solution, the communication device is an access network device or an access and mobility management network element, and the transceiver module is configured to receive a first configuration from an application-providing entity, which may include the transceiver module being configured to receive a first configuration from an application-providing entity through a data-collecting application entity.

[0050] In one possible design solution, the processing module is further configured to determine which of the data collection capabilities supported by the terminal device's AS can be sent to a data collection application entity or application provider entity.

[0051] In one possible design solution, the transceiver module is further configured to send primary feedback information to the data acquisition application entity.

[0052] In one possible design solution, the transceiver module is further configured to transmit primary feedback information to the application-providing entity through the data-collecting application entity.

[0053] In one possible design solution, the communication device is a data acquisition application entity, and the transceiver module is further configured to transmit first feedback information to the application providing entity.

[0054] In one possible design solution, the first feedback information indicates some or all of the first configurations supported by the terminal device.

[0055] In one possible design solution, the first feedback information may include at least one of the following reasons: a configuration supported by the terminal device and used for AS data collection, a configuration not supported by the terminal device and used for AS data collection, or a configuration not supported by the terminal device and used for AS data.

[0056] In one possible design solution, the transceiver module is further configured to send a second configuration to a terminal device, which is obtained by updating the first configuration based on a configuration supported by the terminal device and used for AS data acquisition.

[0057] In one possible design solution, further configuration of the transceiver module to transmit a second configuration to a terminal device may include further configuration of the transceiver module to transmit a second configuration to a terminal device through an application-providing entity.

[0058] In one possible design solution, the data collection capability supported by the AS of the terminal device includes supporting or not supporting the transmission of AS data to the application layer of the terminal device.

[0059] In one possible design solution, the data collection capability supported by the AS of a terminal device includes supporting the transmission of AS data to the application layer of the terminal device, and the data collection capability supported by the AS of a terminal device may further include at least one of the following: the type of AS data that is supported for transmission to the application layer of the terminal device, the supported AS data format, or the supported object for obtaining the AS data.

[0060] For the technical effects of the communication device according to the sixth embodiment, please refer to the technical effects of the method according to the first embodiment. Further details will not be explained here.

[0061] According to the seventh aspect, a communication device is provided for carrying out the method described above. The communication device may be a data acquisition application entity according to the second aspect, a device including a data acquisition application entity, or a device contained within a data acquisition application entity, such as a chip. The communication device includes corresponding modules, units, or means for carrying out the method according to the second aspect. The modules, units, or means may be implemented by hardware, software, or hardware running the corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0062] In some possible designs, the communication device includes a processing module and a transceiver module. The processing module controls the transceiver module to receive a first configuration from an application-providing entity, the first configuration being used by a terminal device to collect AS data expected by the application-providing entity. The processing module further controls the transceiver module to receive first feedback information from a network device, the first feedback information indicating some or all of the first configurations supported by the terminal device. The processing module further controls the transceiver module to transmit a second configuration to a terminal device, the second configuration being obtained by updating the first configuration based on the first feedback information.

[0063] In one possible design solution, the first feedback information may include at least one of the following reasons: a configuration supported by the terminal device and used for AS data collection, a configuration not supported by the terminal device and used for AS data collection, or a configuration not supported by the terminal device and used for AS data.

[0064] In one possible design solution, the processing module may be further configured to control the transceiver module to transmit a second configuration to a terminal device, which may include the processing module being further configured to control the transceiver module to transmit a second configuration to a terminal device through an application-providing entity.

[0065] For the technical effects of the communication device according to the seventh embodiment, please refer to the technical effects of the method according to the second embodiment. Further details will not be explained here.

[0066] According to the eighth aspect, a communication device is provided for carrying out the method described above. The communication device may be a network device according to the third aspect, a device including a network device, or a device included within a network device, such as a chip. The communication device includes corresponding modules, units, or means for carrying out the method according to the third aspect. The modules, units, or means may be implemented by hardware, software, or hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0067] In some possible designs, the communication device includes a processing module and a transceiver module. The transceiver module is configured to receive first capability information from a first terminal device, the first capability information indicating the data collection capabilities supported by the access stratum AS of the first terminal device. The transceiver module is further configured to receive one or more configuration groups from an application providing entity, each of the one or more configuration groups being used by the terminal device to collect AS data expected by the application providing entity. The processing module is configured to determine a second configuration from one or more configuration groups based on the first capability information, the second configuration being a configuration supported by the first terminal device and used for AS data collection. The transceiver module is further configured to transmit the second configuration to the first terminal device.

[0068] In one possible design solution, the transceiver module may be further configured to receive one or more configurations from the application-providing entity, which may include the transceiver module being further configured to receive one or more configuration groups from the application-providing entity through the data-collecting application entity.

[0069] In one possible design solution, further configuration of the transceiver module to transmit a second configuration to a first terminal device may include further configuration of the transceiver module to transmit a second configuration to the first terminal device through a data acquisition application entity.

[0070] In one possible design solution, the transceiver module is further configured to send second feedback information to a data acquisition application entity, which in turn indicates the AS data acquisition status corresponding to a configuration performed by a terminal device in one or more configuration groups.

[0071] In one possible design solution, the second feedback information may include at least one of the following: collected AS data, not collected AS data, or reasons for not collecting AS data.

[0072] In one possible design solution, the network device could be an access network device or an access and mobility management network element.

[0073] In one possible design solution, the data collection capability supported by the AS of the first terminal device includes whether the transmission of AS data to the application layer of the first terminal device is supported.

[0074] In one possible design solution, the data collection capability supported by the AS of the first terminal device includes supporting the transmission of AS data to the application layer of the first terminal device, and the data collection capability supported by the AS of the first terminal device further includes at least one of the following: the type of AS data that is supported for transmission to the application layer of the first terminal device, the supported AS data format, or the supported object for obtaining the AS data.

[0075] In one possible design solution, the processing module is further configured to determine which of the data collection capabilities supported by the AS of the first terminal device can be sent to a data collection application entity or application provider entity.

[0076] For the technical effects of the communication device according to the eighth aspect, please refer to the technical effects of the method according to the third aspect. Further details will not be explained here.

[0077] According to the ninth aspect, a communication device is provided for carrying out the method described above. This communication device may be an application-providing entity according to the fourth aspect, a device including an application-providing entity, or a device contained within an application-providing entity, such as a chip. This communication device includes corresponding modules, units, or means for carrying out the method according to the fourth aspect. The modules, units, or means may be implemented by hardware, software, or hardware running the corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0078] In some possible designs, the communication device includes a processing module and a transceiver module. The transceiver module is configured to receive first capability information from a terminal device, the first capability information indicating the data acquisition capability supported by the terminal device's access stratum AS. The processing module is configured to determine a second configuration based on the first capability information, the second configuration being one supported by the terminal device and used for AS data acquisition. The transceiver module is further configured to transmit the second configuration to the terminal device.

[0079] In one possible design solution, further configuration of the transceiver module to transmit a second configuration to a terminal device may include further configuration of the transceiver module to transmit a second configuration to a terminal device through a data acquisition application entity.

[0080] In one possible design solution, the data collection capability supported by the AS of the terminal device includes supporting or not supporting the transmission of AS data to the application layer of the terminal device.

[0081] In one possible design solution, the data collection capability supported by the AS of a terminal device includes supporting the transmission of AS data to the application layer of the terminal device, and the data collection capability supported by the AS of a terminal device may further include at least one of the following: the type of AS data that is supported for transmission to the application layer of the terminal device, the supported AS data format, or the supported object for obtaining the AS data.

[0082] For the technical effects of the communication device according to the ninth aspect, please refer to the technical effects of the method according to the fourth aspect. Further details will not be explained here.

[0083] According to the tenth aspect, a communication device is provided for carrying out the method described above. The communication device may be a terminal device according to the fifth aspect, a device including a terminal device, or a device contained within a terminal device, such as a chip. The communication device includes corresponding modules, units, or means for carrying out the method according to the fifth aspect. The modules, units, or means may be implemented by hardware, software, or hardware running corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0084] In some possible designs, the communication device includes a processing module and a transceiver module. The processing module is configured to control the transceiver module to transmit a first capability information, which indicates the data acquisition capability supported by the access stratum AS of the terminal device. The processing module is further configured to control the transceiver module to receive a second configuration, which is a configuration supported by the terminal device and used for AS data acquisition, and which is determined based on the first capability information.

[0085] In one possible design solution, the processing module may be configured to control the transceiver module to transmit first capability information, which may include the processing module being configured to control the transceiver module to transmit first capability information to an access network device or an access and mobility management network element.

[0086] In one possible design solution, configuring the processing module to control the transceiver module to transmit first capability information may include configuring the processing module to control the transceiver module to transmit first capability information to a data acquisition application entity.

[0087] In one possible design solution, the processing module may be further configured to control the transceiver module to transmit first capability information, which may include the processing module being further configured to control the transceiver module to transmit first capability information to the application-providing entity.

[0088] In one possible design solution, the processing module may be further configured to control the transceiver module to receive a second configuration, which may include the processing module being further configured to control the transceiver module to receive a second configuration from the application-providing entity.

[0089] In one possible design solution, the processing module may be further configured to control the transceiver module to receive a second configuration, which may include the processing module being further configured to control the transceiver module to receive a second configuration from a data acquisition application entity.

[0090] In one possible design solution, the data collection capability supported by the AS of the terminal device includes supporting or not supporting the transmission of AS data to the application layer of the terminal device.

[0091] In one possible design solution, the data collection capability supported by the AS of a terminal device includes supporting the transmission of AS data to the application layer of the terminal device, and the data collection capability supported by the AS of a terminal device may further include at least one of the following: the type of AS data that is supported for transmission to the application layer of the terminal device, the supported AS data format, or the supported object for obtaining the AS data.

[0092] Furthermore, for the technical effects of the communication device according to the tenth embodiment, please refer to the technical effects of the method according to the fifth embodiment. Details will not be explained again here.

[0093] Referring to any one of the sixth to tenth embodiments, in a possible design solution, the transceiver module may include a receiving module and a transmitting module. The transmitting module is configured to perform the transmitting function of the communication device according to any one of the sixth to tenth embodiments, and the receiving module is configured to perform the receiving function of the communication device according to any one of the sixth to tenth embodiments.

[0094] Referencing any one of the sixth to tenth embodiments, in a possible design solution, a communication device according to any one of the sixth to tenth embodiments may further include a storage module, the storage module storing a program or instruction. When a processing module executes a program or instruction, the communication device according to any one of the sixth to tenth embodiments can perform a method according to any one of the first to fifth embodiments.

[0095] For the technical effects of the communication device according to any one of the sixth to tenth embodiments, please refer to the technical effects of the method according to any one of the first to fifth embodiments. Further details will not be explained here.

[0096] According to the eleventh aspect, a communication device is provided. The device includes a processor and a communication interface. The communication interface is configured to communicate with a module other than the communication device. In order to cause the communication device to perform a method according to any one of the first to fifth aspects, the processor is configured to execute a computer program or instructions.

[0097] According to the twelfth aspect, a communication device is provided (for example, the communication device may be a chip or a chip system). The communication device includes a processor configured to perform the functions according to any one of the first to fifth aspects.

[0098] In some possible designs, the communication device includes memory. The memory is configured to store the necessary program instructions and / or data.

[0099] In one possible design solution, the processor may be integrated with the memory.

[0100] In some possible designs, if the communication device is a chip system, the communication device may include a chip, or it may include a chip and other discrete devices.

[0101] According to the thirteenth aspect, a communication device is provided. The device includes a transceiver and a processor. The transceiver is configured to exchange information between the communication device and another communication device, and the processor executes program instructions to perform a method according to any one of the first to fifth aspects.

[0102] In one possible design solution, the communication device according to the 13th aspect may further include memory. The memory and processor may be integrated or located separately. The memory may be configured to store computer programs and / or data in any way according to one of the first to fifth aspects.

[0103] It should be understood that the 11th to 13th aspects include corresponding modules, units, or means for carrying out the method according to any one of the first to fifth aspects. The modules, units, or means may be implemented by hardware, software, or hardware running the corresponding software. The hardware or software includes one or more modules or units configured to perform the function in the manner described above.

[0104] It will be understood that when a communication device according to any one of the 11th to 13th embodiments is a chip, the transmission operation / function may be understood as an output and the reception operation / function may be understood as an input.

[0105] According to the fourteenth aspect, a computer-readable storage medium is provided. This computer-readable storage medium stores a computer program or instruction. When the computer program or instruction is executed on a communication device, the communication device is made to perform a method according to any one of the first to fifth aspects.

[0106] According to the 15th aspect, a computer program product including instructions is provided. When this computer program product is executed on a communication device, the communication device is made to perform a method according to any one of the first to fifth aspects.

[0107] According to the sixteenth aspect, a communication system is provided. The system includes a network device configured to perform the method according to the first aspect and a terminal device configured to perform the method according to the fifth aspect; a network device configured to perform the method according to the first aspect, a data collection application entity configured to perform the method according to the second aspect and a terminal device configured to perform the method according to the fifth aspect; a network device configured to perform the method according to the third aspect and a terminal device configured to perform the method according to the fifth aspect; or an application providing entity configured to perform the method according to the fourth aspect and a terminal device configured to perform the method according to the fifth aspect. [Brief explanation of the drawing]

[0108] [Figure 1] This is a diagram of the architecture of an EVEX data acquisition architecture according to one embodiment of this application. [Figure 2] This is a diagram of the architecture of an AI application mechanism in NR according to one embodiment of this application. [Figure 3] This is a diagram of the architecture of another AI application mechanism according to one embodiment of this application. [Figure 4] This is a schematic flowchart of the overall signaling procedure of the LCM of an AI model according to one embodiment of this application. [Figure 5] This is a diagram showing the architecture of a communication system according to one embodiment of this application. [Figure 6] This is a diagram showing the architecture of an AI model distribution according to one embodiment of this application. [Figure 7]This is a diagram showing the architecture of a 5G system according to one embodiment of this application. [Figure 8] This is a schematic flowchart of a communication method according to one embodiment of this application. [Figure 9] This is a schematic flowchart of another communication method according to one embodiment of this application. [Figure 10] This is a schematic flowchart of yet another communication method according to one embodiment of this application. [Figure 11] This is a schematic flowchart of yet another communication method according to one embodiment of this application. [Figure 12] This is a diagram showing the structure of a communication device according to one embodiment of this application. [Figure 13] This is a diagram showing the structure of another communication device according to one embodiment of this application. [Modes for carrying out the invention]

[0109] To better understand the embodiments of this application, the system architecture in the embodiments of this application will be described below.

[0110] In the embodiments of this application, all aspects, embodiments, or features are presented by describing a system that may include multiple devices, components, modules, etc. It should be recognized and understood that each system may include other devices, components, and modules, etc., and / or may not include all of the devices, components, and modules, etc., discussed with reference to the accompanying drawings. In addition, combinations of these solutions may be used.

[0111] The technical solutions in the embodiments of this application can be applied to various communication systems, such as fourth-generation (4G) mobile communication systems like wireless fidelity (Wi-Fi) systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, Internet of Vehicles communication systems, long-term evolution (LTE) systems, and worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) mobile communication systems like new radio (NR) systems, and future communication systems like sixth-generation (6G) mobile communication systems.

[0112] The following describes the technologies related to the embodiments of this application.

[0113] 1. EVEX Data Collection Architecture The EVEX data acquisition architecture is used to collect application (APP) layer data or non-accessible stratum data from a UE, such as some media streaming data and quality of experience (QoE) metrics for media streaming data. As shown in Figure 1, the EVEX data acquisition architecture mainly consists of the UE, DCAF, and application service provider (ASP). The UE includes a DDCC module and an application layer module. The DDCC module and the application layer module communicate with each other through the R7 interface, and the DDCC module and DCAF communicate with each other through the R2 interface.

[0114] The ASP includes a provisioning application function (PAF) module, an IDCC module, and an event consumer application function (ECAF) module. The PAF module and DCAF communicate with each other via the R1 interface, the IDCC module and DCAF communicate with each other via the R3 interface, and the ECAF module and DCAF communicate with each other via the R6 interface.

[0115] The PAF module transmits data acquisition / processing and event exposure configurations to the DCAF via the R1 interface. The DACF can transmit data acquisition and reporting configurations to the corresponding entity, which then reports the collected data based on the configuration. For example, the DACF may transmit data acquisition and reporting configurations to the DDCC module via the R2 interface, and as a result, the UE's application layer module may be configured to report the collected application layer data. The application layer data collected by the UE's application layer module may be transmitted directly to the DCAF (e.g., from R7 through R2) or indirectly (e.g., from R8 through R3). The DCAF processes the collected data based on event identification (ID) requests and discloses the collected data based on the event ID to subscribers. For example, the ASP or network data analytics function (NWDAF) instructs the DCAF with an event ID corresponding to the data that needs to be collected, the DCAF sends the corresponding data to be collected to the ASP or NWDAF based on the event ID, and the NWDAF and DCAF communicate with each other through the R5 interface.

[0116] 2.Artificial intelligence (AI) Applying AI to NR enables intelligent data collection and analysis, resulting in improved network performance and user experience. As shown in Figure 2, the AI ​​application mechanism in NR may include the following modules. A data collection module configured to collect and store data from next generation Node-B (gNB), gNB central unit (CU), gNB distributed unit (DU), UE, or another managed entity as a database for AI model training, data analysis, and inference; a model training module that analyzes the training data provided by the data collection module to provide the optimal AI model; a model inference module that provides AI-based rational predictions to a network operating with the AI ​​model based on inference data provided by the data collection module, or guides the network to make policy adjustments; and a decision / actor module that adjusts the relevant policies output by the model inference module and feeds back specific performance characteristics of the network after the relevant policies have been applied (such as various performance parameters) to the data collection module for storage.

[0117] Figure 3 is a diagram of another AI-applied communication. The difference from Figure 2 is that, in addition to the data acquisition module, model training module, and model inference module, the AI-applied communication mechanism shown in Figure 3 further includes a model management module and a model storage module configured to perform AI model management and storage, respectively. In addition, in the AI-applied communication mechanism shown in Figure 3, the data collected by the data acquisition module can be used by the model training module, model inference module, and model management module.

[0118] Currently, RAN1 is primarily researching the following three application scenarios (use cases) for AI technology: (1) Channel state information (CSI) feedback enhancement, (2) Beam management (BM), and (3) Positioning accuracy enhancement.

[0119] In addition, AI model lifecycle management (LCM) is the management of the entire process from the start to the end of an AI model. For example, in a communication system, the overall signaling procedure for AI model LCM between the UE, RAN, and core network (CN) or operation, administration and maintenance (OAM) (which is sometimes called the network management system) is shown in Figure 4, and includes processing procedures such as AI-related capability interactions, data collection for AI model training, AI model training, AI model operation, data collection for AI model inference, AI model inference, AI model performance feedback / monitoring, and AI model switching / update / deactivation / fallback.

[0120] In the aforementioned AI application scenarios, the input data for the AI ​​model is AS data. For example, in the CSI compression scenario, the model input is the channel state information reference signal (CSI-RS) measurement result, which is related to access stratum CSI reporting. When it is necessary to collect AS data from the UE based on the EVEX data collection architecture, the ASP needs to transmit configuration information for AS data collection based on the UE's AS capabilities. However, the UE's capabilities, such as AS data collection capability, are usually reported only to the RAN or access and mobility management function (AMF), and the ASP cannot detect the UE's AS data collection capability. Therefore, how to collect AS data from the UE based on the EVEX data collection architecture becomes an urgent issue to be resolved.

[0121] To better understand the embodiments of this application, the following description is provided before describing the embodiments of this application.

[0122] Firstly, in the embodiments of this application, “to indicate” may include “to indicate directly” and “to indicate indirectly.” If “indication information” is described as indicating A, the indication information may indicate A directly or indirectly, but this does not indicate that the indication information will definitely carry A.

[0123] Information referred to by referencing information is called referred information. In a specific implementation process, referred information may be referred to in several ways, including, but not limited to, ways that directly refer to the referred information. For example, referred information or an index of referred information may be referred to. Alternatively, referred information may be referred to indirectly by referring to other information, and there may be a correlation between the other information and the referred information. Alternatively, only a part of the referred information may be referred to, with the other parts of the referred information being known or pre-agreed. For example, to reduce referencing overhead to some extent, specific information may instead be referred to by using a pre-agreed (e.g., specified in a protocol) arrangement of multiple pieces of information. In addition, to reduce the referencing overhead that would arise from referring to the same information separately, common parts of each piece of information may be identified and referred to in a unified manner.

[0124] Furthermore, a particular instruction method may instead be, but is not limited to, various existing instruction methods, such as the instruction methods described above or various combinations thereof. For details of various instruction methods, please refer to the prior art, which will not be described in detail herein. For example, it can be seen from the above description that different information may be indicated in different ways when it is necessary to indicate multiple pieces of information of the same type. In a specific implementation, the instruction method required may be selected based on the specific requirements. The instruction method to be selected is not limited to the embodiments of this application. Thus, the instruction methods in the embodiments of this application should be understood to encompass a variety of ways in which the indicated party may be able to know the indicated information.

[0125] The information to be indicated may be transmitted as a whole, or it may be divided into multiple sub-informations for separate transmission. In addition, the transmission cycle and / or transmission opportunities of these sub-informations may be the same or different. The specific transmission method is not limited in this application. The transmission cycle and / or transmission opportunities of these sub-informations may be predetermined, for example, according to a protocol, or may be configured by the transmitting device by transmitting configuration information to the receiving device. The configuration information may include, but is not limited to, one or at least two of the following: radio resource control (RRC) signaling, medium access control (MAC) layer signaling, and physical layer signaling. MAC layer signaling may include, for example, a MAC-control element (CE), and physical (PHY) layer signaling may include, for example, DCI.

[0126] Secondly, the numbers such as "first" and "second" in the embodiments of this application are merely for illustrative purposes and are not intended to limit the scope of the embodiments of this application, for example, to distinguish different instructional information. As another example, the first instructional information and the second instructional information are simply to distinguish different areas, and the order of the first instructional information and the second instructional information is not limited. Those skilled in the art will understand that terms such as "first" and "second" do not limit the quantity or execution order, and that terms such as "first" and "second" do not indicate a clear difference.

[0127] Thirdly, in the embodiments of this application, phrases such as "when," "in the case of," "if," and "assume" mean that a device (e.g., a terminal device or a network device) performs the corresponding processing under objective circumstances, and are not intended to limit time, nor do they imply that the device (e.g., a terminal device or a network device) is required to perform a decision operation during implementation, nor do they imply any other limitation.

[0128] In addition, in embodiments of this application, terms such as “example” or “for example” are used to indicate that an example, illustration, or explanation is being given. No embodiment or design described as “example” or “for example” in embodiments of this application should be described as preferable to or having more advantages than another embodiment or design. Strictly speaking, the use of terms such as “example” or “for example” is intended to present relevant concepts in a particular manner for ease of understanding.

[0129] Finally, the network architectures and service scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application and do not constitute any limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will know that as network architectures evolve and new service scenarios emerge, the technical solutions provided in the embodiments of this application will also be applicable to similar technical challenges.

[0130] For example, Figure 5 is a diagram of the architecture of a communication system to which a communication method according to one embodiment of the present application can be applied. As shown in Figure 5, the communication system includes terminal devices, network devices, and application-providing entities, two of each of the three of which can communicate with each other. In the embodiments of the present application, the network devices may be access network devices, core network devices (e.g., access and mobility management network elements), or data collection application entities.

[0131] 1. Terminal device There may be one or more terminal devices, for example, a first terminal device, a second terminal device, and a third terminal device. A terminal device may be a terminal device having transceiver functionality, or it may be a chip or chip system located within the terminal device. A terminal device may also be called a UE, access terminal, subscriber unit, subscriber station, mobile station (MS), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment. The terminal devices in the embodiments of this application include mobile phones, cellular phones, smartphones, tablet computers (Pads), wireless data cards, personal digital assistant (PDA) computers, wireless modems, handheld devices (handsets), laptop computers, machine type communication (MTC) terminals, computers with wireless transceiver functionality, virtual reality (VR) terminals, augmented reality (AR) terminals, smart home devices (e.g., refrigerators, televisions, air conditioners, meters), intelligent robots, robotic arms, workshop equipment, wireless terminals for autonomous driving, wireless terminals for industrial control, wireless terminals for autonomous driving, wireless terminals for remote medical care, wireless terminals for smart grids, wireless terminals for transportation safety, wireless terminals for smart cities, and smart homes. This may include wireless terminals (home), in-vehicle terminals, roadside units (RSUs) with terminal functions, and flying devices (e.g., intelligent robots, hot air balloons, unmanned aerial vehicles, or airplanes).The terminal device in this application may instead be an in-vehicle module, in-vehicle assembly, in-vehicle part, in-vehicle chip, or in-vehicle unit incorporated into a vehicle as one or more parts or units. The terminal device may instead be another device having terminal functionality. For example, the terminal device may instead be a device that functions as a terminal in D2D communication.

[0132] The device form of the terminal is not limited in the embodiments of this application. The device configured to perform the functions of the terminal device may be the terminal device itself, or it may be a device capable of supporting the terminal device in performing those functions, such as a chip system. The device may be mounted on the terminal device or used together with the terminal device. In the embodiments of this application, the chip system may include a chip, or it may include a chip and other discrete devices.

[0133] 2. Access Network Devices There may be multiple access network devices, for example, a first access network device, a second access network device, and a third access network device. Access network devices are sometimes called access network nodes, RAN nodes, RAN entities, or access nodes, and are located on the network side of the aforementioned communication system, configured to assist terminal devices in performing radio access, and are devices having radio transceiver functionality, or may be located on the chip or within the chip system of the device. Access network devices include, but are not limited to, base stations, evolved NodeB (eNodeB), access points (AP), TRP or transmission points (TP), gNB, next-generation base stations for 6G mobile communication systems, base stations for future mobile communication systems, and access nodes for Wi-Fi systems. Access network devices may be macro base stations, micro base stations, indoor base stations, relay nodes, donor nodes, or radio controllers in centralized radio access network (CRAN) scenarios. Alternatively, the access network device may be one or a group of antenna panels (including multiple antenna panels) of a 5G base station, or a network node forming a gNB, TRP, TP, or transmission measurement function (TMF), such as a central unit (CU), DU, CU-control plane (CP), CU-user plane (UP), or radio unit (RU), or a roadside unit (RSU) with base station functionality. Optionally, the access network device may instead be a server, wearable device, vehicle, or in-vehicle device. For example, the access network device in V2X technology may be an RSU.All or part of the functions of the network device in this application may instead be implemented by software functions running on hardware, or by virtualization functions in which instances are created on a platform (e.g., a cloud platform). The access network device in this application may instead be a logical node, logical module, or software capable of implementing all or part of the functions of the access network device.

[0134] CUs and DUs may be located separately or may be contained within the same network element, for example, within a baseband unit (BBU). RUs may be contained within radio frequency devices or radio frequency units, for example, within a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). It will be understood that an access network device may be a CU node, a DU node, or a device containing both CU and DU nodes. In addition, a CU may be classified as a network device within an access network RAN, or a CU may be classified as a network device within a CN. This is not limited here.

[0135] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open-RAN (O-RAN) system, CU may be called O-CU (open CU), DU may be called O-DU, CU-CP may be called O-CU-CP, CU-UP may be called O-CU-UP, and RU may be called O-RU. For ease of explanation, CU, CU-CP, CU-UP, DU, and RU will be used as examples in the description of this application. In this application, any one of CU (or CU-CP or CU-UP), DU, and RU may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0136] In embodiments of this application, the form of the access network device is not limited. The device configured to perform the functions of the access network device may be the access network device itself, or it may be a device capable of supporting the access network device when performing its functions, such as a chip system. The device may be mounted on the access network device or used in conjunction with the access network device.

[0137] 3. Core network devices A core network device is a device deployed within a core network and configured to serve terminal devices. In systems using different radio access technologies, core network devices with similar radio communication capabilities may have different names. In embodiments of this application, a core network device may be an access and mobility management network element. For example, when the method of the embodiments of this application is applied to a 5G system, the access and mobility management network element may be an AMF. When the method of the embodiments of this application is applied to an LTE system, the access and mobility management network element may be a mobility management entity (MME). For simplicity of explanation, in embodiments of this application, the aforementioned devices that can serve terminal devices are collectively referred to as core network devices.

[0138] 4. Application Provider Entity An application provider entity is deployed in the application layer and configured to provide application services to terminal devices. The application provider entity may include a configuration provisioning application module, an indirect data collection module, and an event usage module. The configuration provisioning application module is configured to deliver data collection configuration information to terminal devices, the indirect data collection module is configured to transfer the collected data from terminal devices, and the event usage module uses the collected data to complete event processing. In embodiments of this application, the application provider entity may be an ASP. Accordingly, the configuration provisioning application module may be a PAF, the indirect data collection module may be an IDCC, and the event usage module may be an ECAF.

[0139] 5. Data Collection Application Entity The data collection application entity is deployed in the application layer and is configured to collect data from the application layer and access stratum of terminal devices, and to disclose the collected data to access network devices, application provider entities, etc. In embodiments of this application, the data collection application entity may be a DCAF.

[0140] In embodiments of this application, an AI module may also be deployed in a terminal device, network device, or application-providing entity, the AI ​​module being a module with machine learning computing capabilities. When the AI ​​module is deployed in a communication device or communication equipment, the communication device or communication equipment can perform processes such as model training and model inference, as shown in Figure 2 or 3, based on the AI ​​model. When the method of embodiments of this application is applied to a 5G system, the AI ​​module may be located in the OAM, in a RAN device (or in a CU / DU if the RAN device is of a segmented architecture), in several terminal devices, or independently in a network element entity RAN intelligent controller (RIC) module, as shown in Figure 6. The main function of the AI ​​module in a wireless communication system is to perform a series of AI computing tasks, such as model establishment, training approximation, and reinforcement learning based on input data (input data in a wireless communication system is typically network operational data, e.g., network load and channel quality, provided by the RAN side or monitored by the OAM). The trained models provided by the AI ​​module have predictive capabilities for network changes on the RAN side and can typically be used for load prediction, UE path prediction, CSI prediction, optimal beam prediction, and positioning prediction. In addition, the AI ​​module can perform further policy inference from the perspective of network energy saving and mobility optimization, based on the prediction results of RAN network performance by the trained models, in order to obtain rational and efficient energy saving policies and mobility optimization policies. If the AI ​​module is located in the OAM, the current northbound interface can be reused for communication between the AI ​​module and the gNB on the RAN side. If the AI ​​module is located in the gNB or CU, the current interface such as F1, Xn, or Uu can be reused.If the AI ​​module is an independent network entity, it will be necessary to re-establish communication links to the OAM or RAN side, such as wired or wireless links.

[0141] Furthermore, Figure 7 is a diagram of the architecture of a 5G system usable in the aforementioned communication system according to one embodiment of the present application. As shown in Figure 7, the 5G system includes terminal devices, an access network (AN), and a CN.

[0142] The aforementioned AN is configured to perform access-related functions, providing network access to authorized users within a specific area, and determining transmission links of varying quality based on user level, service requirements, etc., for transmitting user data. The AN transfers control signals and user data between terminal devices and CN. The AN may include access network devices, or may be called RAN devices.

[0143] The Network Network (CN) is primarily responsible for maintaining mobile network subscription data and provides functions such as session management, mobility management, policy management, and security authentication for terminal devices. The CN mainly includes the following network elements: User Plane Function (UPF), Authentication Server Function (AUSF), AMF, Session Management Function (SMF), Network Slice Selection Function (NSSF), Network Exposure Function (NEF), Network Repository Function (NRF), Policy Control Function (PCF), Unified Data Management (UDM), Unified Data Repository (UDR), and Application Function (AF).

[0144] As shown in Figure 7, terminal devices access the 5G network through RAN devices, terminal devices communicate with AMF through the N1 interface (abbreviated as N1), RAN devices communicate with AMF through the N2 interface (abbreviated as N2), RAN devices communicate with UPF through the N3 interface (abbreviated as N3), SMF communicates with UPF through the N4 interface (abbreviated as N4), and UPF accesses the data network (DN) through the N6 interface (abbreviated as N6).

[0145] In embodiments of this application, names of nodes, modules, devices, or network elements in different scenarios, architectures, or systems, and names of communication interfaces between any two of these nodes, modules, devices, or network elements are provided as examples, and it should be understood that the possibility of name changes in future communication systems, scenarios, or architectures is not ruled out.

[0146] The communication method provided in the embodiments of this application will be described in detail below with reference to Figures 8 to 11.

[0147] For example, Figure 8 is a schematic flowchart of a communication method according to one embodiment of this application. This communication method may be for communication between a terminal device and a network device.

[0148] In embodiments of this application, the terminal device that implements an embodiment of the method may be the terminal device itself, or a part of the terminal device, for example, the processor, chip, or chip system of the terminal device, or implemented by a logic module or software that implements all or some of the functions related to the terminal device. The following embodiments of the method will use for illustrative purposes an example in which an embodiment of the method is implemented by a terminal device. In embodiments of this application, the network device that implements an embodiment of the method may be the network device itself, or a part of the network device, for example, the processor, chip, or chip system of the network device, or implemented by a logic module or software that implements all or some of the functions related to the network device. The following embodiments of the method will use for illustrative purposes an example in which an embodiment of the method is implemented by a network device. As shown in Figure 8, the communication method includes the following steps.

[0149] S801: The terminal device transmits first capability information to the network device. Accordingly, the network device receives first capability information from the terminal device.

[0150] The first capability information indicates the data collection capabilities (sometimes abbreviated as AS data collection capabilities) supported by the terminal device's AS. In embodiments of this application, the first capability information reported by the terminal device may include all of the data collection capabilities owned or supported by the terminal device's AS, or it may include some of the data collection capabilities owned or supported by the terminal device's AS. The specific data collection capabilities to be reported are related to application scenarios, objects for obtaining data collection capabilities, etc.

[0151] AS data collection capability includes supporting or not supporting the transmission of AS data to the application layer of the terminal device. In other words, it is whether the terminal device's AS supports the transmission of AS data to the terminal device's application layer (APP layer). Typically, the terminal device's AS and APP can negotiate to determine whether the terminal device's AS can transmit data to the terminal device's APP, or whether AS data can be transmitted between the terminal device's AS and APP by default.

[0152] Based on this, AS data acquisition capability may further include at least one of the following: the type of AS data supported for transmission to the application layer of the terminal device, the supported AS data format, or the supported object for obtaining AS data. The type of AS data supported for transmission to the application layer of the terminal device may be AS data that can be transmitted to the application layer of the terminal device by the terminal device's AS in one or more application scenarios (e.g., AI application scenarios such as CSI feedback enhancement, beam management, or positioning accuracy improvement), or the type of AS data that can be transmitted to the application layer of the terminal device by the terminal device's AS. The supported object for obtaining AS data may be a supported object on which AS data is disclosed, or a supported object for receiving AS data. For example, a direct data acquisition module of the terminal device (e.g., DDCC in Figure 1) is supported for AS data transmission and reception, an indirect data acquisition module of an application providing entity (e.g., IDCC in Figure 1) is supported for AS data transmission and reception, and a data acquisition application entity or application providing entity is supported for AS data acquisition. It should be understood that the above provides some examples of data acquisition capability supported by the AS of a terminal device. This is not limited to embodiments of this application.

[0153] In embodiments of this application, AS data may include, but is not limited to, the following types: channel measurement data, layer (L)1-reference signal received power (RSRP), positioning reference signal (PRS) measurement data, sounding reference signal (SRS) measurement data, channel impulse response (CIR) / channel frequency domain response (CFR) data, power delay profile (PDP), model performance monitoring indicator data, or tag data. For example, channel measurement data includes at least one of several original channel measurement data, or data obtained by processing the original channel measurement data, e.g., the original channel matrix measured based on CSI-RS, or eigenvector data obtained by decomposing the original channel matrix. For example, model performance monitoring indicator data includes one or more of the channel prediction accuracy rate, Top-k beam prediction accuracy rate, positioning accuracy rate, and line of sight (LOS) / non-line of sight (NLOS) identification accuracy rate. For example, the label data includes one or more of the following: channel truth value, optimal beam truth value, terminal device position truth value, and LOS / NOLS state truth value.

[0154] In one possible design solution, the network device may be an access network device or an access and mobility management network element. For example, the access network device may be the RAN device in Figure 7, and the access and mobility management network element may be the AMF in Figure 7. When the network device is an access and mobility management network element, the terminal device may transmit first capability information to the access and mobility management network element through the access network device, or it may transmit first capability information directly to the access and mobility management network element. This is not limited to the above.

[0155] In one possible design solution, the network device may be a data collection application entity. For example, the data collection application entity is the DCAF in Figure 1. In this design solution, first capability information is authenticated based on an access network device or an access and mobility management network element. Specifically, when a terminal device transmits data collection capability information to a data collection application entity, the access network device or access and mobility management network element can manage and control the data collection capability information that the terminal device discloses or exposes to the data collection application entity, for example, whether the terminal device's AS data collection capability may be disclosed to the data collection application entity, and which specific AS data collection capabilities may be disclosed to the data collection application entity.

[0156] In one possible implementation, an access network device or access and mobility management network element may determine which data collection capabilities supported by the AS of a terminal device can be sent to a data collection application entity or application provider entity. For example, when forwarding AS data collection capabilities reported by a terminal device to a data collection application entity, the access network device or access and mobility management network element filters the AS data collection capabilities according to a pre-configured policy and then sends the selected AS data collection capabilities to the data collection application entity. In this case, the first capability information received by the data collection application entity is first capability information obtained by screening by the access network device or access and mobility management network element; in other words, the first capability information received may differ from the first capability information sent by the terminal device. Alternatively, the access network device or access and mobility management network element may negotiate with the terminal device to determine which specific AS data collection capabilities may be disclosed to the data collection application entity. This is not limited to the above.

[0157] S802: An application-providing entity sends a first configuration to a network device. The network device receives the first configuration from the application-providing entity.

[0158] The first configuration is used by a terminal device to collect AS data expected by an application-providing entity. In this embodiment of the application, the application-providing entity distributes the first configuration to configure a terminal device to collect AS data expected by the application-providing entity. In one possible design solution, the first configuration may include an event associated with the expected AS data, event identifiers (event ID), and the type of expected AS data. The event associated with the expected AS data indicates the use or purpose of the expected AS data. For example, the expected AS data may be used for CSI feedback enhancement or beam management. The event identifiers identify the event associated with the expected AS data. The above provides some exemplary parameters that constitute the first configuration. In addition, other AS data collection-related parameters, such as the data processing method for the expected AS data, the objects to which the expected AS data may be disclosed / exposed, and the AS data collection cycle, may be further configured in the first configuration. This is not limited herein.

[0159] For example, the first configuration is as follows: Event: xxx, for example, Event 1 Event ID: xxx, for example, ID1 External / Internal Application Identifier: xxx Data access configuration file: >Data processing instruction: xxx, for example, an instruction to perform singular value decomposition (SVD) on the original channel matrix measured based on CSI-RS. >Data disclosure restrictions: xxx, where, for example, AS data may only be disclosed to the application providing entity. Parameters to be collected (AS data expected to be collected): xx, e.g., eigenvectors obtained by decomposing the original channel matrix, L1-RSRP, reference signal received quality (RSRQ), and signal-to-interference plus noise ratio (SINR). ...

[0160] The data access configuration file includes data processing instructions and data disclosure restrictions. The data processing instructions specify the concrete processing required to obtain the expected AS data. For example, the expected AS data includes eigenvectors obtained by decomposing the original channel matrix, and these eigenvectors are configured to be obtained based on singular value decomposition (SVD) processing according to the data processing instructions. Data disclosure restrictions are used to define the objects to which the collected expected AS data may be disclosed. For example, expected AS data collected by a terminal device may only be disclosed to the application provider entity.

[0161] If the network device is an access network device or an access and mobility management network element, the network device can receive a first configuration from an application-providing entity through a data-collecting application entity. In other words, the first configuration sent by the application-providing entity is forwarded to the network device by the data-collecting application entity.

[0162] It should be understood that the order in which S801 and S802 are executed is not limited in this embodiment of the present application. S801 and S802 may be executed simultaneously, or S801 may be executed first, or S802 may be executed first. This is not limited here.

[0163] S803: The network device determines, based on the first capability information, the configuration supported by the terminal device and used for AS data collection from the first configuration.

[0164] In this embodiment of the present application, after obtaining first capability information and a first configuration, the network device selects or filters the first configuration based on the first capability information to determine a specific configuration within the first configuration that is supported / executable / acceptable by the terminal device and used for AS data collection.

[0165] For example, the AS data acquisition capability of a terminal device includes supporting the transmission of RSRP, SINR, and PRS / SRS measurement data to the application layer of the terminal device, and supporting the disclosure of AS data to application-providing entities and network analysis network elements (e.g., NWDAF in Figure 7). For a first configuration, see the example in S802. Based on the first capability information, the network device can determine that the terminal device does not support the acquisition of eigenvectors obtained by decomposing the original channel matrix and RSRQ acquisition, but supports L1-RSRP acquisition and SINR acquisition.

[0166] If the network device is an access network device or an access and mobility management network element, the network device may send first feedback information to a data collection application entity after determining the configurations in the first configuration that are supported by the terminal device and used for AS data collection. Accordingly, the data collection application entity receives first feedback information from the network device. The first feedback information is used to provide feedback on the configuration status supported by the terminal device in the first configuration, for example, certain configurations that can be performed by the terminal device and certain configurations that cannot be performed by the terminal device in the first configuration.

[0167] In one possible case, the first feedback information indicates some or all of the configurations of the first configuration that the terminal device supports. In other words, the network device can use the first feedback information to tell the terminal device whether it supports all of the configurations of the first configuration or some of them. For example, the first feedback information is indicated using one bit. If the value of that bit is 1, it indicates that the terminal device supports all of the configurations of the first configuration. If the value of that bit is 0, it indicates that the terminal device supports some of the configurations of the first configuration.

[0168] In another possible case, the network device may, through first feedback information, provide feedback to the data acquisition application entity on specific configurations supported by the terminal device and specific configurations not supported by the terminal device within the first configuration. The first feedback information may include at least one of the following reasons: a configuration supported by the terminal device and used for AS data acquisition, a configuration not supported by the terminal device and used for AS data acquisition, or a configuration not supported by the terminal device and used for AS data. See the example above for further details. The first feedback information may include that the terminal device does not support the acquisition of eigenvectors obtained by decomposing the original channel matrix and RSRQ acquisition. The reason why the acquisition of eigenvectors obtained by decomposing the original channel matrix is ​​not supported is that the AI ​​model on the terminal device side only accepts the original channel data as input data for model training / inference and does not support eigenvectors obtained by SVD decomposition as input data for model training / inference. The reason why RSRQ acquisition is not supported is that the terminal device does not have the capability to measure RSRQ. L1-RSRP acquisition and SINR acquisition are supported.

[0169] Therefore, based on the first feedback information received, the data acquisition application entity can determine which configurations in the first configuration are supported by the terminal device and update the first configuration based on the first feedback information, for example, by removing configurations not supported by the terminal device from the first configuration or by adding configurations supported by the terminal device to obtain a second configuration. Each configuration in the second configuration is supported by the terminal device. Furthermore, the data acquisition application entity can send the second configuration to the terminal device, and accordingly, the terminal device receives the second configuration from the data acquisition application entity, and as a result, the terminal device can complete the corresponding AS data acquisition based on the second configuration. For example, the second configuration includes the following configurations: configuring the terminal device to obtain L1-RSRP and SINR collected based on CSI-RS measurements, and configuring the period for the terminal device to collect L1-RSRP and SINR to 100 milliseconds (ms). Event: Event 1 Event ID: ID1 External / Internal Application Identifier: xxx Parameters to be collected (AS data expected to be collected): L1-RSRP and SINR Reference signal: CSI-RS Data collection cycle: 100 ms ...

[0170] In this case, one possible design solution is that after the data collection application entity receives the first feedback information, it can further transmit the first feedback information to the application provider entity. Accordingly, the application provider entity receives the first feedback information from the data collection application entity and, as a result, determines a specific configuration from the configurations distributed by the application provider entity that can be executed by the terminal device. Specifically, the data collection application entity can transmit the first feedback information directly to the application provider entity's event usage module (e.g., ECAF in Figure 1). In this case, the network device forwards the first feedback information to the application provider entity through the data collection application entity.

[0171] In one possible scenario, a network device can directly send the first feedback information to the application-providing entity. Specifically, the network device directly sends the first feedback information to the event-using module of the application-providing entity.

[0172] If the network device is a data collection application entity, the network device directly updates the first configuration to obtain a second configuration based on the configuration supported by the terminal device and used for AS data collection, and then transmits the second configuration to the terminal device. It will also be understood that the network device obtains a configuration (i.e., the second configuration) that matches the capabilities of the terminal device by updating the first configuration based on the data collection capabilities supported by the terminal device's AS.

[0173] According to the solution described above, the first configuration update is performed by the data collection application entity, and the data collection application entity then delivers the second configuration (the updated first configuration) to the terminal device.

[0174] In one possible design solution, a data collection application entity can directly send a second configuration to a terminal device, and the terminal device accordingly receives the second configuration from the data collection application entity. Specifically, the data collection application entity sends the second configuration to the terminal device's direct data collection module. After receiving the second configuration, the direct data collection module sends the second configuration to the terminal device's application layer, which then sends the second configuration to the terminal device's AS, thereby allowing the terminal device's AS to collect the AS data expected by the application provider entity based on the second configuration. Accordingly, after collecting the AS data expected by the application provider entity, the terminal device's AS can send the AS data to the data collection application entity through the terminal device's application layer and the direct data collection module, and the data collection application entity then discloses the collected AS data to the application provider entity or another entity (e.g., a network analysis network element).

[0175] In another possible design solution, the data collection application entity can send a second configuration to the terminal device through the application provider entity. In other words, the second configuration can be transferred to the terminal device through the application provider entity. Specifically, the data collection application entity sends the second configuration to the application provider entity's indirect data collection module, which then sends the second configuration to the terminal device's AS, thereby causing the terminal device's AS to collect the AS data expected by the application provider entity based on the second configuration. Accordingly, after sending the collected AS data to the application layer, the terminal device's AS can send the AS data to the data collection application entity or another entity through the application provider entity's indirect data collection module. For specific implementation steps, please refer to the embodiments of the following method shown in Figure 9. Details are not provided here.

[0176] In this embodiment of the present application, after obtaining AS data reported by a terminal device, the data collection application entity discloses the collected AS data to another entity based on an event exposure subscription procedure. For example, a network analysis network element or application provider entity initiates an event exposure subscription request to the data collection application entity, which carries event identification information associated with the AS data to be obtained. After obtaining the AS data associated with the corresponding event, the data collection application entity transmits the AS data associated with the event to the network analysis network element or application provider entity.

[0177] According to the communication method shown in Figure 8, the network device detects the data collection capabilities supported by the terminal device's AS, selects an AS data collection configuration (e.g., a first configuration) to be delivered to the terminal device by the application provider entity, and excludes data collection configurations not supported by the terminal device from the first configuration. As a result, the data collection capabilities supported by the terminal device's AS are adapted to the delivered configuration, improving the network device's management and control of the collected AS data and associated configurations, and enabling AS data collection. In this way, the collected AS data can be disclosed to the application provider entity or another network entity, enabling the application provider entity or another network entity to complete relevant event processing based on the disclosed AS data, resulting in effective use of AS data.

[0178] In this embodiment of the present application, it should be understood that the collection of AS data by a terminal device may include, but is not limited to, operations such as measuring the AS data and performing related processing on the measured AS data.

[0179] To facilitate understanding, the specific implementation steps of the communication method shown in Figure 8 will be described in detail below, with reference to the EVEX architecture shown in Figure 1 and the 5G system shown in Figure 7. For example, the communication method provided in the embodiments of this application will be described in detail using an example where the terminal device is the UE, the network device is the RAN device, the application providing entity is the ASP, and the data collection application entity is the DCAF. As shown in Figure 9, the communication method includes the following steps.

[0180] S900: APP and AS negotiate AS data collection.

[0181] For example, the APP and AS within the UE negotiate to determine that the AS can send data to the APP, and the APP decides that it can package the data collected by the AS and send it to the DCAF via the EVEX mechanism.

[0182] S901: The AS transmits the first capability information to the RAN device. The RAN device receives the first capability information from the AS accordingly.

[0183] For a specific description of the first capability information, please refer to the relevant explanation in S801. Details will not be explained again here. For example, the first capability information includes that the AS supports the transmission of AS data to the APP, and that the supported AS data types include L1-RSRP and SINR.

[0184] Before S902 is executed, in this embodiment of the present application, further steps such as application function registration (AF registration) and DCAF discovery (discover DCAF) may be performed. Application function registration mainly concerns the interaction between network elements, functions, or modules such as NRF, DCAF, and NWDAF. DCAF discovery mainly concerns the interaction between network elements, functions, or modules such as NRF and PAF. For specific implementation processes, please refer to relevant descriptions of existing implementations. Details will not be described again here. Steps such as application function registration and DCAF discovery may be performed before or after S901, or simultaneously with S901. This is not limited herein.

[0185] S902: PAF transmits the first configuration to DCAF. Accordingly, DCAF receives the first configuration from PAF.

[0186] The first configuration is used by the UE to collect AS data expected by the ASP, and may be carried in a Data Reporting Provisioning (Ndcad_DataReportingProvisioning) message and sent to the DCAF via the R1 interface. For a specific description of the first configuration, see the relevant description in S802, which will not be described in detail again here. For example, the first configuration includes expecting the UE to collect L1-RSRP and RSRQ from the ASP, that the event associated with L1-RSRP and RSRQ is Event 1, and that the event identifier for Event 1 is ID 1.

[0187] It should be understood that PAF can deliver a configuration to DCAF via the R1 interface that assumes DCAF / ASP is in a trusted domain. If DCAF / ASP is outside a trusted domain, authentication and authorization must be performed by NEF.

[0188] S903: DCAF transmits a first configuration to the RAN device. The RAN device receives the first configuration from DCAF.

[0189] S904: The RAN device determines, based on the first capability information, the configuration supported by the UE and used for AS data acquisition from the first configuration.

[0190] For example, based on first capability information, a RAN device can determine that the AS supports sending AS data to the APP and that the supported AS data types include L1-RSRP and SINR. However, in the first configuration, the ASP expects the UE to collect L1-RSRP and RSRQ. Therefore, the RAN device can determine that the UE does not support RSRQ collection, and thus can determine that the configuration in the first configuration that is supported by the UE and used for AS data collection supports L1-RSRP collection.

[0191] S905: The RAN device transmits the first feedback information to the DCAF. Accordingly, the DCAF receives the first feedback information from the RAN device.

[0192] For example, after S904 is executed, the RAN device provides feedback via first feedback information regarding certain configurations of the first configuration that can be performed by the UE and certain configurations that cannot be performed by the UE. For example, the first feedback information includes configurations in which the UE supports L1-RSRP collection and configurations in which the UE does not support RSRQ collection.

[0193] S906: DCAF transmits the second configuration to DDCC. Accordingly, DDCC receives the second configuration from DCAF.

[0194] The second configuration is obtained by updating based on the first feedback information. For example, after receiving the first feedback information, DCAF updates the first configuration based on the first feedback information, for example, by removing AS data configurations not supported by the UE from the first configuration to obtain the second configuration. The second configuration is the configuration supported by the UE and used for AS data collection. For example, the second configuration includes the ASP expecting the UE to collect L1-RSRP, the event associated with L1-RSRP being event 1, and the event identifier for event 1 being ID 1.

[0195] S907: DDCC sends a second configuration to the APP. Accordingly, the APP receives the second configuration from DDCC.

[0196] S908: The APP sends a second configuration to the AS. The AS receives the second configuration from the APP.

[0197] Based on S907 and S908, the AS within the UE obtains a second configuration from the DCAF via DDCC and APP, and collects AS data (e.g., L1-RSRP) based on the second configuration. Furthermore, after collecting the AS data, the AS can transmit the collected AS data to the DCAF via APP and DDCC.

[0198] In one possible design solution, the DDCC can further transmit the collected AS data to the RAN device by calling the Data Reporting Service (Ndcaf_DataReporting service), and the RAN device then transmits the collected AS data to the DCAF. Alternatively, after receiving the AS data transmitted by the AS, the APP transmits the AS data to the IDCC in the ASP via the R8 interface, and the IDCC then transmits the AS data to the DCAF via the R3 interface.

[0199] In this way, DCAF can obtain AS data associated with each event based on the procedure described above, and can disclose the collected AS data for each event to another entity, function, or module, such as ECAF, NEF, or NWDAF within ASP, based on the event exposure subscription procedure. For example, if ECAF subscribes to AS data associated with event 1 from DCAF, DCAF sends the AS data associated with event 1 to ECAF based on the identification information of event 1, and as a result ECAF completes event 1 based on the AS data associated with event 1.

[0200] According to the communication method shown in Figure 9, the RAN device detects the UE's AS data collection capability and selects an AS data collection configuration to be delivered by the ASP based on the UE's AS data collection capability in order to provide the UE with an appropriate configuration for reporting AS data.

[0201] In addition, one embodiment of this application further provides a communication method. The network device does not select the AS data collection configuration distributed by the application-providing entity, but performs a matching process based on the AS data collection capabilities of each terminal device and the AS data collection configuration distributed by the application-providing entity, and distributes an AS data collection configuration suitable for each terminal device to the terminal device in order to collect AS data. For example, one example is shown in Figure 10, where the network device is an access network device (e.g., a RAN device) or an access and mobility management network element (e.g., an AMF). The communication method includes the following steps.

[0202] S1001: The first terminal device transmits first capability information to the network device. Accordingly, the network device receives first capability information from the first terminal device.

[0203] The first capability information indicates the data acquisition capabilities supported by the AS of the first terminal device. For a relevant explanation of the first capability information, please refer to the relevant explanation in S801. Details will not be explained again here. For example, the first capability information of the first terminal device indicates that the AS of the first terminal device supports only L1-RSRP acquisition. Different terminal devices correspond to different first capability information. For example, the first capability information of the second terminal device indicates that the AS of the second terminal device supports only channel impulse response acquisition.

[0204] S1002: An application-providing entity sends one or more configuration groups to a network device. Accordingly, the network device receives one or more configuration groups from the application-providing entity.

[0205] Each of one or more configuration groups may be used by a terminal device to collect AS data expected by an application-providing entity, and the AS data expected to be collected by one or more configuration groups may differ from one another. For example, an application-providing entity distributes three configuration groups to a network device, where configuration 1 is used to configure the terminal device to collect L1-RSRP, configuration 2 is used to configure the terminal device to collect channel impulse responses, and configuration 3 is used to configure the terminal device to collect LOS / NLOS label data. In this embodiment of the present application, in addition to the AS data expected to be collected, each configuration group may further include event information associated with the AS data expected to be collected. For a specific explanation, see the relevant description of the first configuration in S802, which will not be explained in detail again here. For example, the application-providing entity is the ASP in Figure 1, and one or more configuration groups may be distributed by the PAF within the ASP.

[0206] It should be understood that at least two of the multiple configuration groups may contain some of the same configurations. For example, Configuration 1 is used to configure a terminal device to collect L1-RSRP and RSRQ, and Configuration 2 is used to configure a terminal device to collect L1-RSRP and SINR, and the configurations related to L1-RSRP collection in Configuration 1 and Configuration 2 are the same.

[0207] In one possible design solution, an application-providing entity sends one or more configuration groups to network devices through a data-collecting application entity. In other words, configurations delivered by the application-providing entity are transferred to network devices through the data-collecting application entity. For example, the data-collecting application entity is DCAF in Figure 1.

[0208] S1003: The network device determines a second configuration from one or more configuration groups based on the first capability information.

[0209] The second configuration is one supported by the first terminal device and used for AS data collection. For example, a network device determines, based on the first capability information, that the first terminal device supports only L1-RSRP collection. Referring to the example in S1002, the network device may determine that configuration 1 matches the AS data collection capability of the first terminal device and then designate configuration 1 as the second configuration. It should be understood that the AS data collection capability of the first terminal device may match one or more configuration groups.

[0210] S1004: The network device sends the second configuration to the first terminal device. The first terminal device receives the second configuration from the network device.

[0211] In one possible design solution, a network device transmits a second configuration to a first terminal device through a data collection application entity.

[0212] In this embodiment of the present application, the first terminal device, after receiving the second configuration, collects AS data based on the second configuration and transmits the collected AS data to the data collection application entity. For example, the first terminal device collects the L1-RSRP and then reports the L1-RSRP to the data collection application entity. For the process of the first terminal device reporting the AS data and the process by which the data collection application entity discloses the AS data to another entity after obtaining it, please refer to the relevant descriptions in S803 or S908. Details will not be described again here.

[0213] Furthermore, the communication method provided in this embodiment of the present application may further include the following steps:

[0214] S1005: The network device sends second feedback information to the data collection application entity. Accordingly, the data collection application entity receives second feedback information from the network device.

[0215] The second feedback information indicates the AS data collection status corresponding to the configuration performed by the terminal device in one or more configuration groups. In other words, the network device uses the second feedback information to provide feedback on a specific configuration performed by the terminal device in one or more configuration groups, i.e., the specific configuration on which the terminal device collects specific AS data.

[0216] In this embodiment of the present application, the second feedback information may include at least one of the following: collected AS data, uncollected AS data, or the reason for uncollected AS data. For example, in three configuration groups (Configurations 1 to 3) distributed by an application providing entity, the first terminal device completes L1-RSRP collection based on Configuration 1, the second terminal device completes channel impulse response collection based on Configuration 2, and there are no terminal devices with satisfactory capability to match Configuration 3. Thus, the network device can determine that the collected AS data includes L1-RSRP and channel impulse responses, and the uncollected AS data includes LOS / NLOS label data, and the reason why LOS / NLOS label data collection is not completed is that among the terminal devices reporting AS data collection capability, there are no terminal devices that support LOS / NLOS label data collection, and therefore the data collection application entity is notified in the second feedback information.

[0217] S1006: The data collection application entity sends second feedback information to the application provider entity. Accordingly, the application provider entity receives second feedback information from the data collection application entity.

[0218] Specifically, the data collection application entity notifies the application provider entity of the execution status of the AS data collection configuration delivered by the application provider entity through the second feedback information.

[0219] According to the communication method shown in Figure 10, in order to complete AS data collection, the network device matches a configuration that can be executed based on the capabilities of the terminal device from one or more configuration groups distributed by the application providing entity, based on the AS data collection capability reported by the terminal device, and transmits the configuration to the terminal device.

[0220] In the communication methods shown in Figures 8 to 10, an access network device (e.g., a RAN device), an access and mobility management network element (e.g., an AMF), or a data collection application entity (e.g., a DCAF) can detect the AS data collection capability of a terminal device and match or select an appropriate AS data collection configuration for the terminal device in order to perform AS data collection. In addition, an application provider entity may instead obtain or detect the AS data collection capability of a terminal device and deliver a matched configuration directly to the terminal device based on the terminal device's AS data collection capability.

[0221] For example, Figure 11 is a schematic flowchart of yet another communication method according to one embodiment of the present application. As shown in Figure 11, the communication method includes the following steps:

[0222] S1101: The terminal device transmits first capability information to the application provider entity. Accordingly, the application provider entity receives first capability information from the terminal device.

[0223] The first capability information indicates the data collection capabilities of the terminal device supported by the AS. In this case, the data collection capabilities supported by the AS and reported by the terminal device may be all or part of the data collection capabilities supported by the AS of the terminal device.

[0224] In one possible design solution, the AS data collection capabilities reported by the terminal device must be authenticated by a network device (e.g., an access network device or an access and mobility management network element) before S1101 is executed. In other words, the network device can manage and control the data collection capability information disclosed or exposed by the terminal device to the application-providing entity, for example, whether the terminal device's AS data collection capabilities may be disclosed to the application-providing entity, and which specific AS data collection capabilities may be disclosed to the application-providing entity.

[0225] In one possible implementation, a network device can negotiate with a terminal device to determine which AS data collection capabilities may be disclosed to the application provider entity. In this case, the first capability information reported by the terminal device is authenticated. Alternatively, in the process of transferring the first capability information to the application provider entity, the network device filters the AS data collection capabilities according to a pre-configured policy and then sends the selected AS data collection capabilities to the application provider entity. In this case, the first capability information received by the application provider entity is the first capability information obtained through screening by the network device, and in other words, the received first capability information may differ from the first capability information sent by the terminal device.

[0226] In one possible design solution, a terminal device can sequentially transmit first capability information to an application-providing entity through a network device and a data-collecting application entity.

[0227] Optionally, the terminal device may further transmit capability information related to the terminal device's application layer to the application provider entity, for example, its ability to support the application layer when encapsulating data collected by the AS.

[0228] S1102: The application-providing entity determines the second configuration based on the first capability information.

[0229] The second configuration is one supported by the terminal device and used for AS data collection. For example, after receiving the first capability information, the application providing entity can directly customize the configuration information for the terminal device, i.e., the second configuration, based on the AS data collection capabilities supported by the terminal device, so that the delivered configuration matches the data collection capabilities of the terminal device. For example, if the terminal device supports L1-RSRP and RSRQ collection but does not support channel impulse response collection, the second configuration may be used to configure the terminal device to collect L1-RSRP and / or RSRQ. For example, the application providing entity is the ASP in Figure 1, and the second configuration may be configured and delivered by the PAF within the ASP.

[0230] S1103: The application provider entity sends a second configuration to the terminal device. The terminal device receives the second configuration from the application provider entity.

[0231] For example, an application-providing entity can transfer a second configuration to a terminal device through a data-collecting application entity. In this way, the terminal device can complete the collection of corresponding AS data based on the second configuration. For details on the process of distributing the second configuration and reporting the AS data, please refer to the relevant explanations in S803 or S906-S908. Details will not be explained again here.

[0232] According to the communication method shown in Figure 11, in order to perform AS data collection, the application providing entity can directly configure an appropriate AS data collection configuration for the terminal device by detecting the terminal device's AS data collection capability.

[0233] It will be understood that in the embodiments described above, methods and / or steps performed by a network device may instead be performed by parts that can be used within the network device (e.g., processors, chips, chip systems, circuits, logic modules, or software); methods and / or steps performed by a data acquisition application entity may instead be performed by parts that can be used within the data acquisition application entity (e.g., processors, chips, chip systems, circuits, logic modules, or software); methods and / or steps performed by an application provider entity may instead be performed by parts that can be used within the application provider entity (e.g., processors, chips, chip systems, circuits, logic modules, or software); and methods and / or steps performed by a terminal device may instead be performed by parts that can be used within the terminal device (e.g., processors, chips, chip systems, circuits, logic modules, or software).

[0234] The above primarily describes the solutions provided in this application. Accordingly, this application further provides communication devices. The communication devices are configured to implement various methods of embodiments of the methods described above. The communication devices may be network devices, devices including network devices, or parts that can be used within network devices, such as chips or chip systems, in embodiments of the methods described above. Alternatively, the communication devices may be data acquisition application entities, devices including data acquisition application entities, or parts that can be used within data acquisition application entities, such as chips or chip systems, in embodiments of the methods described above. Alternatively, the communication devices may be application providing entities, devices including application providing entities, or parts that can be used within application providing entities, such as chips or chip systems, in embodiments of the methods described above. Alternatively, the communication devices may be terminal devices, devices including terminal devices, or parts that can be used within terminal devices, such as chips or chip systems, in embodiments of the methods described above.

[0235] It will be understood that, in order to implement the functions described herein, the communication device will include hardware structures and / or software modules for performing the corresponding functions. Those skilled in the art will readily realize, in combination with the example units and algorithmic steps described in the embodiments disclosed herein, that this application may be implemented in hardware, or in combination with hardware and computer software. Whether the functions are performed by hardware or by hardware driven by computer software will depend on the specific application and design constraints of the technical solution. Those skilled in the art may implement the functions described using various methods for specific applications, but such implementation should not be considered to exceed the scope of this application.

[0236] In embodiments of this application, a communication device may be divided into functional modules based on embodiments of the method described above. For example, each functional module may be obtained by division based on corresponding functions, or two or more functions may be integrated into a single processing module. The integrated module may be implemented in hardware form or in the form of a software functional module. Note that in embodiments of this application, the module division is merely an example and represents only a logical functional division. In actual implementation, other division methods may be used.

[0237] For example, the communication device is a network device, data collection application entity, application provider entity, or terminal device in the embodiments of the method described above. Figure 12 is a diagram of the structure of a communication device according to one embodiment of the present application. As shown in Figure 12, the communication device 1200 includes a processing module 1201 and a transceiver module 1202. The processing module 1201 is configured to perform the processing functions of a network device, data collection application entity, application provider entity, or terminal device in the embodiments of the method described above. The transceiver module 1202 is configured to perform the transceiver functions of a network device, data collection application entity, application provider entity, or terminal device in the embodiments of the method described above.

[0238] Any relevant details of the steps in the embodiments of the method described above can be referenced in the description of the functions of the corresponding functional modules. Further details will not be provided here.

[0239] The communication device 1200 provided in this embodiment can perform the computation task scheduling method described above. Therefore, for the technical effects that can be achieved by the communication device 1200, please refer to the embodiments of the method described above. Details will not be explained again here.

[0240] In one possible design solution, in this embodiment of the present application, the transceiver module 1202 may include a receiving module and a transmitting module (not shown in Figure 12). The transceiver module is configured to perform the transmitting and receiving functions of the communication device 1200.

[0241] In one possible design solution, the communication device 1200 may further include a storage module (not shown in Figure 12) that stores a program or instruction. When the processing module 1201 executes the program or instruction, the communication device 1200 is made to perform the functions of a network device, a data acquisition application entity, an application providing entity, or a terminal device in the manner shown in any of Figures 8 to 11.

[0242] It should be understood that the processing module 1201 within the communication device 1200 may be implemented by a processor or processor-related circuit components, and may be a processor or processing unit. The transceiver module 1202 may be implemented by a transceiver or transceiver-related circuit components, and may be a transceiver or transceiver unit.

[0243] For example, Figure 13 shows the structure of another communication device according to one embodiment of the present application. This communication device may be a network device, a data acquisition application entity, an application providing entity, or a terminal device, or a chip (system) or another component or part that may be located within a network device, a data acquisition application entity, an application providing entity, or a terminal device. As shown in Figure 13, the communication device 1300 may include a processor 1301. In one possible design solution, the communication device 1300 may further include a memory 1302 and / or a transceiver 1303. The processor 1301 may be coupled to the memory 1302 and the transceiver 1303 and connected to the memory 1302 and the transceiver 1303, for example, via a communication bus.

[0244] In the following sections, each part of the communication device 1300 will be described in detail with reference to Figure 13.

[0245] The processor 1301 is the control center of the communication device 1300 and may be a single processor or a collective term for multiple processing elements. For example, the processor 1301 may be one or more central processing units (CPUs), or application-specific integrated circuits (ASICs), or one or more integrated circuits for carrying out embodiments of this application, such as one or more digital signal processors (DSPs) or one or more field programmable gate arrays (FPGAs).

[0246] In one possible design solution, the processor 1301 can perform various functions of the communication device 1300 by running or executing software programs stored in memory 1302, and by retrieving data stored in memory 1302.

[0247] In a specific implementation, in one embodiment, the processor 1301 may include one or more CPUs, such as CPU0 and CPU1 shown in Figure 13.

[0248] In a specific implementation, in one embodiment, the communication device 1300 may instead include multiple processors, for example, processors 1301 and 1304 shown in Figure 13. Each of the processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A processor here may be one or more devices, circuits, and / or processing cores configured to process data (e.g., computer program instructions).

[0249] Memory 1302 is configured to store a software program for executing the solution of this application, and processor 1301 controls the execution. For specific implementations, please refer to the embodiments of the method described above. Details will not be described again here.

[0250] In one possible design solution, memory 1302 may be read-only memory (ROM) or another type of static storage device capable of storing static information and instructions, or random access memory (RAM) or another type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or another compact disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital multipurpose discs, Blu-ray discs, etc.), magnetic disk storage medium or another magnetic storage device, or any other medium that can be used to carry or store program code expected in the form of instructions or data structures and can be accessed by a computer. However, it is not limited to these. Memory 1302 may be integrated with processor 1301 or exist independently, and may be coupled to processor 1301 through an interface circuit of communication device 1300 (not shown in Figure 13). This is not specifically limited to this embodiment of the present application.

[0251] The transceiver 1303 is configured to communicate with other communication devices. For example, if the communication device 1300 is a terminal device, the transceiver 1303 may be configured to communicate with a network device or with other terminal devices. Alternatively, if the communication device 1300 is a network device, the transceiver 1303 may be configured to communicate with a terminal device or with another network device.

[0252] In one possible design solution, the transceiver 1303 may include a receiver and a transmitter (not shown separately in Figure 13). The receiver is configured to perform the receiving function, and the transmitter is configured to perform the transmitting function.

[0253] In one possible design solution, the transceiver 1303 may be integrated with the processor 1301 or may exist independently, and is coupled to the processor 1301 through an interface circuit of the communication device 1300 (not shown in Figure 13). This is not specifically limited to this embodiment of the present application.

[0254] Please note that the configuration of the communication device 1300 shown in Figure 13 is not limiting to other communication devices. Actual communication devices may include more or fewer parts than those shown in the figure, or some parts may be combined, or different part arrangements may be used.

[0255] Furthermore, for the technical effects of the communication device 1300, please refer to the technical effects of the computation task scheduling method in the embodiment of the method described above. Details will not be explained again here.

[0256] One embodiment of this application further provides a computer-readable storage medium for storing computer programs or instructions. When the computer programs or instructions are executed by a computer, the functions of the embodiments of the method described above are performed.

[0257] One embodiment of this application further provides a computer program product. When this computer program product is executed by a computer, the functions of the embodiment of the method described above are performed.

[0258] All or part of the embodiments described above may be implemented by software, hardware, firmware, or any combination thereof. If a software program is used to implement an embodiment, the embodiment may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the procedures or functions according to the embodiments of this application are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired means (e.g., coaxial cable, optical fiber, or digital subscriber line (DSL)) or wireless means (e.g., infrared, radio waves, or microwaves). Computer-readable storage media may be any available medium accessible by a computer, or a data storage device, such as a server or data center integrating one or more available media. Available media may be magnetic media (e.g., floppy disks, hard disks, or magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0259] Those skilled in the art will notice, in combination with the examples described in the embodiments disclosed herein, that the units and algorithmic steps may be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software will depend on the specific application and design constraints of the technical solution. Those skilled in the art may implement the functions described using various methods for specific applications, but such implementation should not be considered to exceed the scope of this application.

[0260] For the sake of brevity, it will be readily apparent to those skilled in the art that detailed working procedures for the aforementioned systems, apparatus, and units should be referred to in the corresponding procedures in the embodiments of the methods described above. Further details will not be provided here.

[0261] It should be understood that in some embodiments provided in this application, the disclosed systems, devices, and methods may be implemented in other ways. For example, the embodiments of the devices described above are merely examples. For example, the division into units is merely a logical functional division. In actual implementation, other division methods may be used. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the mutual coupling, direct coupling, or communication connection shown or discussed may be implemented through some interfaces. Indirect coupling or communication connection between devices or units may be implemented in electronic, mechanical, or other forms.

[0262] Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, may be located in one place, or may be distributed across multiple network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the embodiment's solution.

[0263] In addition, the functional units in the embodiments of this application may be integrated into a single processing unit, each unit may exist physically independently, or two or more units may be integrated into a single unit.

[0264] When a function is implemented in the form of a software function unit and sold or used as an independent product, the function may be stored on a computer-readable storage medium. Based on such understanding, the technical solutions of this application, or the portion that contributes to the prior art, or some of the technical solutions, may be implemented in the form of a software product. That computer software product includes several instructions that are stored on a storage medium and instruct a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method described in the embodiments of this application. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0265] Although this application is described with reference to embodiments, a person skilled in the art can understand and implement other variations of the disclosed embodiments by examining the accompanying drawings, the disclosed content and the accompanying claims in the process of implementing this application for which protection is claimed. In the claims, “comprising” does not exclude another component or another step, and “a” or “one” does not exclude multiple cases. A single processor or another unit may perform some of the functions enumerated in the claims. Although several approaches are recorded in different dependent claims, this does not mean that these approaches cannot be combined to produce a better effect. [Explanation of Symbols]

[0266] 1200 Communication equipment 1201 Processing Module 1202 Transceiver Module 1300 Communication equipment 1301 Processor 1302 memory 1303 Transceiver 1304 Processor

Claims

1. A communication method, wherein the method is A step of receiving first capability information from a terminal device via a network device, wherein the first capability information indicates the data collection capability supported by the access stratum AS of the terminal device; The steps include: receiving a first configuration from an application providing entity via the network device, wherein the first configuration is used by the terminal device to collect AS data expected by the application providing entity; The network device, based on the first capability information, determines a configuration from the first configuration that is supported by the terminal device and used for AS data collection. A method that includes [a certain feature].

2. The network device is an access network device or an access and mobility management network element, and the step of receiving the first configuration from the application providing entity by the network device is: The network device receives the first configuration from the application providing entity through the data collection application entity. The method according to claim 1, comprising:

3. The aforementioned method, The step of determining, by the network device, the data collection capabilities that are included in the data collection capabilities supported by the AS of the terminal device and that can be transmitted to the data collection application entity or the application provider entity. The method according to claim 1 or 2, further comprising:

4. The aforementioned method, The network device transmits first feedback information to the data collection application entity. The method according to any one of claims 1 to 3, further comprising:

5. The aforementioned method, The network device transmits the first feedback information to the application providing entity through the data collection application entity. The method according to claim 4, further comprising:

6. The network device is a data collection application entity, and the method is The network device transmits first feedback information to the application providing entity. The method according to claim 1, further comprising:

7. The method according to any one of claims 4 to 6, wherein the first feedback information indicates, in the first configuration, some or all of the configurations supported by the terminal device.

8. The method according to any one of claims 4 to 7, wherein the first feedback information comprises at least one of the following reasons: the configuration supported by the terminal device and used for AS data collection, the configuration not supported by the terminal device and used for AS data collection, or the reason for the configuration not supported by the terminal device and used for AS data.

9. The aforementioned method, A step of transmitting a second configuration to a terminal device by the network device, wherein the second configuration is obtained by updating the first configuration based on the configuration supported by the terminal device and used for AS data collection. The method according to any one of claims 6 to 8, further comprising:

10. The step of transmitting the second configuration to the terminal device by the network device is: The step of transmitting the second configuration to the terminal device through the application providing entity using the network device. The method according to claim 9, comprising:

11. The method according to any one of claims 1 to 10, wherein the data collection capability of the terminal device supported by the AS supports or does not support the transmission of AS data to the application layer of the terminal device.

12. The method according to any one of claims 1 to 10, wherein the data collection capability of the terminal device supported by the AS supports the transmission of AS data to the application layer of the terminal device, and the data collection capability of the terminal device supported by the AS further comprises at least one of the following: a type of AS data that is supported for transmission to the application layer of the terminal device, a supported AS data format, or a supported object for obtaining AS data.

13. A communication method, wherein the method is A data collection application entity receives a first configuration from an application provider entity, the first configuration being used by a terminal device to collect AS data expected by the application provider entity; The data collection application entity receives first feedback information from a network device, wherein the first feedback information indicates some or all of the configurations supported by the terminal device in the first configuration. A step of transmitting a second configuration to the terminal device by the data collection application entity, wherein the second configuration is obtained by updating the first configuration based on the first feedback information. A method that includes [a certain feature].

14. The method according to claim 13, wherein the first feedback information comprises at least one of the following: a configuration supported by the terminal device and used for AS data collection, a configuration not supported by the terminal device and used for AS data collection, or a reason for the configuration not supported by the terminal device and used for AS data.

15. The step of transmitting the second configuration to the terminal device by the data collection application entity is: The data collection application entity transmits the second configuration to the terminal device through the application providing entity. The method according to claim 13 or 14, comprising:

16. A communication method, wherein the method is A step of receiving first capability information from a first terminal device via a network device, wherein the first capability information indicates the data collection capability supported by the access stratum AS of the first terminal device. The steps include: receiving one or more configuration groups from an application providing entity via the network device, wherein each of the one or more configuration groups is used by a terminal device to collect AS data expected by the application providing entity; A step of determining a second configuration from one or more configuration groups based on the first capability information by the network device, wherein the second configuration is a configuration supported by the first terminal device and used for AS data collection. The network device transmits the second configuration to the first terminal device. A method that includes [a certain feature].

17. The step of receiving one or more configurations from the application providing entity by the network device is: The network device receives one or more configuration groups from the application providing entity through the data collection application entity. The method according to claim 16, comprising:

18. The step of transmitting the second configuration to the first terminal device by the network device is: The network device transmits the second configuration to the first terminal device through the data collection application entity. The method according to claim 16 or 17, comprising:

19. The aforementioned method, A step of transmitting second feedback information to the data collection application entity by the network device, wherein the second feedback information indicates the AS data collection status corresponding to a configuration performed by the terminal device in one or more configuration groups. The method according to any one of claims 16 to 18, further comprising:

20. The method according to claim 19, wherein the second feedback information comprises at least one of the following: collected AS data, not collected AS data, or the reason for the not collected AS data.

21. The method according to any one of claims 16 to 20, wherein the network device is an access network device or an access and mobility management network element.

22. The method according to any one of claims 16 to 21, wherein the data collection capability of the first terminal device supported by the AS is supported by the transmission of AS data to the application layer of the first terminal device.

23. The method according to any one of claims 16 to 21, wherein the data acquisition capability of the first terminal device supported by the AS is supported for transmission of AS data to the application layer of the first terminal device, and the data acquisition capability of the first terminal device supported by the AS is further supported for transmission to the application layer of the first terminal device, namely, at least one of the following: the type of AS data supported for transmission to the application layer of the first terminal device, the supported AS data format, or the supported object for obtaining the AS data.

24. The aforementioned method, The step of determining, by the network device, the data collection capabilities that are included in the data collection capabilities supported by the AS of the first terminal device and that can be transmitted to the data collection application entity or the application provider entity. The method according to any one of claims 16 to 23, further comprising:

25. A communication method, wherein the method is A step of receiving first capability information from a terminal device by an application providing entity, wherein the first capability information indicates the data collection capability supported by the access stratum AS of the terminal device. A step in which the application providing entity determines a second configuration based on the first capability information, wherein the second configuration is a configuration supported by the terminal device and used for AS data collection. The application providing entity transmits the second configuration to the terminal device. A method that includes [a certain feature].

26. The step of transmitting the second configuration to the terminal device by the application providing entity is: The application providing entity transmits the second configuration to the terminal device through the data collection application entity. The method according to claim 25, comprising:

27. The method according to claim 25 or 26, wherein the data collection capability of the terminal device supported by the AS supports or does not support the transmission of AS data to the application layer of the terminal device.

28. The method according to claim 25 or 26, wherein the data collection capability of the terminal device supported by the AS comprises supporting the transmission of AS data to the application layer of the terminal device, and the data collection capability of the terminal device supported by the AS further comprises at least one of the following: a type of AS data that is supported for transmission to the application layer of the terminal device, a supported AS data format, or a supported object for obtaining AS data.

29. A communication method, wherein the method is A step of transmitting first capability information, wherein the first capability information indicates the data collection capability supported by the access stratum AS of the terminal device, A step of receiving a second configuration, wherein the second configuration is a configuration supported by the terminal device and used for AS data collection, and the second configuration is determined based on the first capability information. A method that includes [a certain feature].

30. The step of transmitting the first capability information is: Step 1: Transmitting the first capability information to an access network device or an access and mobility management network element. The method according to claim 29, comprising:

31. The step of transmitting the first capability information is: Step of transmitting the first capability information to the data collection application entity. The method according to claim 29, comprising:

32. The step of transmitting the first capability information is: Step of transmitting the first capability information to the application providing entity. The method according to claim 29, comprising:

33. The step of receiving the second configuration is: Steps to receive the second configuration from the application providing entity. The method according to claim 32, comprising:

34. The step of receiving the second configuration is: step of receiving the second configuration from the data collection application entity. The method according to any one of claims 29 to 32, comprising:

35. The method according to any one of claims 29 to 34, wherein the data collection capability of the terminal device supported by the AS supports or does not support the transmission of AS data to the application layer of the terminal device.

36. The method according to any one of claims 29 to 34, wherein the data collection capability of the terminal device supported by the AS supports the transmission of AS data to the application layer of the terminal device, and the data collection capability of the terminal device supported by the AS further comprises at least one of the following: a type of AS data that is supported for transmission to the application layer of the terminal device, a supported AS data format, or a supported object for obtaining AS data.

37. A communication device comprising a processing module and a transceiver module, The processing module is configured to perform a processing function in the manner described in any one of claims 1 to 36, The transceiver module is configured to perform a transceiver function in the manner described in any one of claims 1 to 36. Communication device.

38. A communication device comprising a processor and an interface circuit, wherein the interface circuit is configured to receive a signal from another communication device different from the communication device and transmit the signal to the processor, or to transmit a signal from the processor to another communication device different from the communication device, and the processor is configured to carry out the method according to any one of claims 1 to 36 through a logic circuit or by executing code instructions.

39. A communication device comprising a processor, wherein the processor is configured to execute a computer program in order to cause the communication device to perform the method according to any one of claims 1 to 36.

40. A communication chip, wherein the communication chip stores instructions, and when the chip operates on a communication device, the method according to any one of claims 1 to 36 is performed.

41. A computer-readable storage medium, wherein the storage medium stores a computer program or instruction, and when the computer program or instruction is executed by a communication device, the method according to any one of claims 1 to 36 is performed.

42. A computer program product comprising computer program code, wherein when the computer program code is executed on a communication device, the communication device carries out the method according to any one of claims 1 to 36.

Images