Verification method and apparatus for data collection

Abstract

The present application provides a verification method and apparatus for data collection. The method comprises: a network device sends first indication information to a DCAF, wherein the first indication information is used for indicating that a first access stratum data set of the terminal device can only be provided for other network elements when authorized; the network device receives first request information from an ECAF or a non-access stratum of the terminal device, wherein the first request information is used for requesting authorization for a second access stratum data set; the network device sends first information to the ECAF or the non-access stratum of the terminal device, wherein the first information is used for indicating a first key, the first key is used for authorization for a third access stratum data set, and the third access stratum data set comprises all or some of data in the second access stratum data set; the network device receives first information from the DCAF or an access stratum of the terminal device; and the network device sends second information to the DCAF or the access stratum of the terminal device, wherein the second information is used for indicating a verification result of the first key.

Description

A data collection verification method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on August 10, 2023, with application number 202311014019.7 and application name “A method and device for verifying data collection”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular, to a method and device for verifying data collection. Background Art

[0003] With the advancement of data storage and computing capabilities, artificial intelligence (AI) technology is increasingly being used. AI can be applied to communications systems such as new radio (NR) systems, improving network performance and user experience through intelligent data collection and analysis.

[0004] The 3rd Generation Partnership Project (3GPP) has introduced multiple AI application scenarios, such as using AI for channel state information (CSI) feedback enhancement, beam management (BM), and positioning accuracy enhancements.

[0005] AI models need to collect data from terminal devices. In the permission management process of event consumers subscribing to the data collection function of the Data Collection AF (DCAF), an authorization application server (AAS) is introduced. By verifying the key (token) provided by the AAS to the event consumer application function (ECAF) network element, it confirms whether the DCAF can send data to the corresponding ECAF.

[0006] However, in the above-mentioned AI application scenarios, the input of the AI ​​model is the access stratum (AS) data of the user equipment (UE). Since AS layer data is usually collected by operators and they have the authority to process it, the existing AAS authorization mechanism cannot be directly used. There is no relevant authorization mechanism for AS layer data, which may lead to the improper exposure of AS data to third-party ECAF nodes due to lack of authorization when collecting AS layer data.

[0007] Summary of the Invention

[0008] The present application provides a data collection verification method and device, which is used to verify how to complete the collection authorization of AS data through the authority management of network devices when collecting AS layer data.

[0009] In a first aspect, a data collection verification method is provided. The method can be executed by a network device, or can be executed by a chip or circuit configured in the network device, and this application does not limit this.

[0010] The method includes: a network device sends first indication information to a data collection application function network element, the first indication information is used to indicate that access layer data in a first access layer data set of a terminal device needs to be authorized before being provided to other network elements; the network device receives first request information from a non-access layer of an event user application function network element or a terminal device, the first request information is used to request authorization of a second access layer data set, and the second access layer data set includes all or part of the data in the first access layer data set; the network device sends first information to the non-access layer of the event user application function network element or the terminal device, the first information is used to indicate a first key, and the first key is used to authorize a third access layer data set, and the third access layer data set includes all or part of the data in the second access layer data set; the network device receives first information from the access layer of the data collection application function network element or the terminal device; the network device sends second information to the access layer of the data collection application function network element or the terminal device, and the second information is used to indicate a verification result of the first key.

[0011] Through the above solution, the event user application function network element needs to be authorized by the network device before it can obtain the collected access layer measurement data from the data collection application function network element, ensuring the network device's authority management of access layer data collection and avoiding the direct exposure of access layer data to other network nodes in the non-access layer.

[0012] In combination with the first aspect, in some implementations of the first aspect, the network device sends second indication information to the access layer of the terminal device, and the second indication information is used to indicate that the access layer data in the fourth access layer data set can be sent to the non-access layer of the terminal device.

[0013] Through the above solution, the network device can configure additional measurements for the access layer of the UE, thereby expanding the scope of data collection.

[0014] In one possible implementation, the network device sends a third indication message to the non-access layer of the event user application function network element or the terminal device, where the third indication message is used to indicate that the request for part of the access layer data in the second access layer data set is not authorized, and the third indication message includes reason information, where the reason information is used to indicate the reason why the request for the access layer data is not authorized.

[0015] In a possible implementation, the second access layer data set also includes all or part of the data in the fifth access layer data set, where the fifth access layer data set is the access layer data requested by the event user application function network element to the data collection application function network element.

[0016] On the second aspect, a data collection verification method is provided. The method can be executed by a data collection application function network element, or it can also be executed by a chip or circuit configured in the data collection application function network element. This application does not limit this.

[0017] The method includes: a data collection application function network element receives first indication information from a network device, the first indication information is used to indicate that access layer data in a first access layer data set of a terminal device needs to be authorized before being provided to other network elements; the data collection application function network element receives second request information from an event user application function network element, the second request information is used to request a third access layer data set of the terminal device, the second request information includes first information, the first information is used to indicate a first key, and the first key is used to authorize the third access layer data set; the data collection application function network element sends the first information to the network device; the data collection application function network element receives second information from the network device, and the second information is used to indicate a verification result of the first key.

[0018] Through the above solution, the event user application function network element needs to be authorized by the network device before it can obtain the collected access layer measurement data from the data collection application function network element, ensuring the network device's authority management of access layer data collection and avoiding the direct exposure of access layer data to other network nodes in the non-access layer.

[0019] In one possible implementation, the data collection application function network element receives a third request message from the event user application function network element, and the third request message is used to request the fifth access layer data set of the terminal device; the data collection application function network element sends a third message to the event user application function network element, and the third message is used to indicate that the second access layer data set needs to be authorized at the network device, and the second access layer data set includes all or part of the data in the fifth access layer data set, and the third information includes first identification information, and the first identification information includes the identification of the network device.

[0020] In a possible implementation manner, the data collection application function network element sends first confirmation information to the event user application function network element, where the first confirmation information is used to indicate a request result of the third request information.

[0021] On the third aspect, a data collection verification method is provided, which can be executed by an event user application function network element, or can also be executed by a chip or circuit configured in the event user application function network element, and this application does not limit this.

[0022] The method includes: an event user application function network element sends a first request message to a network device, the first request message is used to request authorization of a second access layer data set of a terminal device; the event user application function network element receives a first message from the network device, the first message is used to indicate a first key, the first key is used to authorize a third access layer data set, the third access layer data set includes all or part of the data in the second access layer data set; the event user application function network element sends a second request message to a data collection application function network element, the second request message is used to request a third access layer data set, and the second request message includes the first information.

[0023] Through the above solution, the event user application function network element needs to be authorized by the network device before it can obtain the collected access layer measurement data from the data collection application function network element, ensuring the network device's authority management of access layer data collection and avoiding the direct exposure of access layer data to other network nodes in the non-access layer.

[0024] In one possible implementation, the event user application function network element sends a third request message to the data collection application function network element, and the third request message is used to request the fifth access layer data set of the terminal device; the event user application function network element receives the third information from the data collection application function network element, and the third information is used to indicate that the second access layer data set needs to be authorized at the network device, and the second access layer data set includes all or part of the data in the fifth access layer data set, and the third information includes first identification information, and the first identification information includes the identification of the network device.

[0025] In a possible implementation, the event user application function network element receives first confirmation information from the data collection application function network element, where the first confirmation information is used to indicate a request result of the third request information.

[0026] In a fourth aspect, a data collection verification method is provided. The method can be executed by a terminal device, or can be executed by a chip or circuit configured in the terminal device. This application does not limit this.

[0027] The method includes: a non-access layer of a terminal device receives first request information from a data collection application function network element, the first request information is used to request authorization of a second access layer data set of the terminal device; the non-access layer of the terminal device sends the first request information to a network device; the non-access layer of the terminal device receives first information from the network device, the first information includes a first key, the first key is used to authorize a third access layer data set, the third access layer data set includes all or part of the data in the second access layer data set; the non-access layer of the terminal device sends the first information to the access layer of the terminal device; the access layer of the terminal device sends the first information to the network device; the access layer of the terminal device receives second information from the network device, the second information is used to indicate whether the first key is correct.

[0028] Through the above scheme, the authorization application of the event user application function network element is forwarded to the network device via the non-access layer of the terminal device, and the authorization verification is completed between the terminal device and the network device, and the authorization result and data collection result are sent to the event user application function network element via the data collection application function network element, ensuring that the access layer data is collected with authorization.

[0029] In a possible implementation, the non-access layer of the terminal device sends authorization result information to the data collection application function network element, where the authorization result information is used to indicate which data in the second access layer data set is authorized and which data is not authorized.

[0030] In the fifth aspect, a data collection verification method is provided. The method can be executed by an event user application function network element, or it can be executed by a chip or circuit configured in the event user application function network element. This application does not limit this.

[0031] The method includes: the event user application function network element sends a third request message to the data collection application function network element, the third request message is used to request the fifth access layer data set of the terminal device; the event user application function network element receives a fourth message from the data collection application function network element, the fourth message is used to indicate that the second access layer data set needs to be authorized at the non-access layer of the terminal device, and the second access layer data set includes all or part of the data in the fifth access layer data set; the event user application function network element sends a first request message to the data collection application function network element, the first request message is used to request authorization of the second access layer data set, and the first request message includes ECAF identification information.

[0032] In a possible implementation, the event user application function network element receives first confirmation information from the data collection application function network element, where the first confirmation information is used to indicate a request result of the third request information.

[0033] In the sixth aspect, a data collection verification method is provided. The method can be executed by a data collection application function network element, or it can be executed by a chip or circuit configured in the data collection application function network element. This application does not limit this.

[0034] The method includes: a data collection application function network element receives third request information from an event user application function network element, the third request information is used to request a fifth access layer data set of a terminal device; the data collection application function network element sends fourth information to the event user application function network element, the fourth information is used to indicate that a second access layer data set needs to be authorized at a non-access layer of the terminal device, the second access layer data set includes all or part of the data in the fifth access layer data set; the data collection application function network element receives first request information from the event user application function network element, the first request information is used to request authorization of the second access layer data set, the first request information includes identification information of ECAF; the data collection application function network element sends the first request information to the non-access layer of the terminal device.

[0035] In a possible implementation manner, the data collection application function network element sends first confirmation information to the event user application function network element, where the first confirmation information is used to indicate a request result of the third request information.

[0036] In the seventh aspect, a data collection verification device is provided, including: a sending unit, used to send a first indication message to a data collection application function network element, the first indication message is used to indicate that the access layer data in the first access layer data set of the terminal device needs to be authorized before it can be provided to other network elements; a receiving unit, used to receive a first request message from the non-access layer of the event user application function network element or the terminal device, the first request message is used to request authorization of the second access layer data set, and the second access layer data set includes all or part of the data in the first access layer data set; the sending unit is also used to send a first message to the non-access layer of the event user application function network element or the terminal device, the first information is used to indicate a first key, and the first key is used to authorize a third access layer data set, and the third access layer data set includes all or part of the data in the second access layer data set; the receiving unit is also used to receive the first information from the access layer of the data collection application function network element or the terminal device; the sending unit is also used to send a second message to the access layer of the data collection application function network element or the terminal device, and the second information is used to indicate the verification result of the first key.

[0037] In a possible implementation, the sending unit is further configured to send second indication information to the access layer of the terminal device, where the second indication information is configured to indicate that the access layer data in the fourth access layer data set can be sent to the non-access layer of the terminal device.

[0038] In one possible implementation, the sending unit is also used to send a third indication message to the non-access layer of the event user application function network element or terminal device, and the third indication message is used to indicate that the request for part of the access layer data in the second access layer data set is not authorized, and the third indication message includes reason information, and the reason information is used to indicate the reason why the request for the access layer data is not authorized.

[0039] In a possible implementation, the second access layer data set also includes all or part of the data in the fifth access layer data set, where the fifth access layer data set is the access layer data requested by the event user application function network element to the data collection application function network element.

[0040] In the eighth aspect, a data collection verification device is provided, including: a receiving unit for receiving first indication information from a network device, the first indication information is used to indicate that the access layer data in the first access layer data set of the terminal device needs to be authorized before it can be provided to other network elements; the receiving unit is also used to receive second request information from an event user application function network element, the second request information is used to request a third access layer data set of the terminal device, the second request information includes first information, the first information is used to indicate a first key, and the first key is used for authorization of the third access layer data set; a sending unit is used to send the first information to the network device; the receiving unit is also used to receive second information from the network device, the second information is used to indicate the verification result of the first key.

[0041] In one possible implementation, the receiving unit is also used to receive a third request information from the event user application function network element, and the third request information is used to request the fifth access layer data set of the terminal device; the sending unit is also used to send a third information to the event user application function network element, and the third information is used to indicate that the second access layer data set needs to be authorized at the network device, and the second access layer data set includes all or part of the data in the fifth access layer data set, and the third information includes first identification information, and the first identification information includes the identification of the network device.

[0042] In a possible implementation manner, the sending unit is further configured to send first confirmation information to the event user application function network element, where the first confirmation information is used to indicate a request result of the third request information.

[0043] In the ninth aspect, a data collection verification device is provided, including: a sending unit for sending a first request message to a network device, the first request message is used to request authorization of a second access layer data set of a terminal device; a receiving unit for receiving first information from the network device, the first information is used to indicate a first key, the first key is used to authorize a third access layer data set, the third access layer data set includes all or part of the data in the second access layer data set; the sending unit is also used to send a second request message to a data collection application function network element, the second request message is used to request a third access layer data set, and the second request message includes the first information.

[0044] In one possible implementation, the sending unit is also used to send a third request message to the data collection application function network element, and the third request message is used to request the fifth access layer data set of the terminal device; the receiving unit is also used to receive a third information from the data collection application function network element, and the third information is used to indicate that the second access layer data set needs to be authorized at the network device, and the second access layer data set includes all or part of the data in the fifth access layer data set, and the third information includes first identification information, and the first identification information includes the identification of the network device.

[0045] In a possible implementation, the receiving unit is further configured to receive first confirmation information from the data collection application function network element, where the first confirmation information is used to indicate a request result of the third request information.

[0046] In the tenth aspect, a data collection verification device is provided, including: a receiving unit, used for the non-access layer of the terminal device to receive a first request information from the data collection application function network element, the first request information is used to request authorization of the second access layer data set of the terminal device; a sending unit, used for the non-access layer of the terminal device to send the first request information to the network device; the receiving unit is also used for the non-access layer of the terminal device to receive the first information from the network device, the first information includes a first key, the first key is used for authorization of a third access layer data set, the third access layer data set includes all or part of the data in the second access layer data set; the sending unit is also used for the non-access layer of the terminal device to send the first information to the access layer of the terminal device; the sending unit is also used for the access layer of the terminal device to send the first information to the network device; the receiving unit is also used for the access layer of the terminal device to receive the second information from the network device, the second information is used to indicate whether the first key is correct.

[0047] In a possible implementation, the sending unit is also used for the non-access layer of the terminal device to send authorization result information to the data collection application function network element, and the authorization result information is used to indicate which data in the second access layer data set is authorized and which data is not authorized.

[0048] In the eleventh aspect, a data collection verification device is provided, including: a sending unit, used to send a third request information to the data collection application function network element, the third request information is used to request the fifth access layer data set of the terminal device; a receiving unit, used to receive fourth information from the data collection application function network element, the fourth information is used to indicate that the second access layer data set needs to be authorized at the non-access layer of the terminal device, and the second access layer data set includes all or part of the data in the fifth access layer data set; the sending unit is also used to send a first request information to the data collection application function network element, the first request information is used to request authorization of the second access layer data set, and the first request information includes ECAF identification information.

[0049] In a possible implementation, the receiving unit is further configured to receive first confirmation information from the data collection application function network element, where the first confirmation information is used to indicate a request result of the third request information.

[0050] In the twelfth aspect, a data collection verification device is provided, including: a receiving unit, used to receive a third request information from an event user application function network element, the third request information is used to request a fifth access layer data set of a terminal device; a sending unit, used to send a fourth information to the event user application function network element, the fourth information is used to indicate that the second access layer data set needs to be authorized at the non-access layer of the terminal device, and the second access layer data set includes all or part of the data in the fifth access layer data set; the receiving unit is also used to receive a first request information from the event user application function network element, the first request information is used to request authorization of the second access layer data set, and the first request information includes identification information of ECAF; the sending unit is also used to send the first request information to the non-access layer of the terminal device.

[0051] In a possible implementation manner, the sending unit is further configured to send first confirmation information to the event user application function network element, where the first confirmation information is used to indicate a request result of the third request information.

[0052] In a thirteenth aspect, a wireless communication device is provided, comprising modules or units for executing the method in the first aspect or any possible implementation of the first aspect.

[0053] In a fourteenth aspect, a wireless communication device is provided, comprising modules or units for executing the method in the second aspect or any possible implementation of the second aspect.

[0054] In a fifteenth aspect, a wireless communication device is provided, comprising modules or units for executing the method in the third aspect or any possible implementation of the third aspect.

[0055] In the sixteenth aspect, a wireless communication device is provided, comprising modules or units for executing the method in the fourth aspect or any possible implementation of the fourth aspect.

[0056] In the seventeenth aspect, a wireless communication device is provided, comprising modules or units for executing the method in the fifth aspect or any possible implementation of the fifth aspect.

[0057] In the eighteenth aspect, a wireless communication device is provided, comprising modules or units for executing the method in the sixth aspect or any possible implementation of the sixth aspect.

[0058] In a nineteenth aspect, a communication device is provided, comprising a processor coupled to a memory, and configured to perform the method of any one of aspects one through six, as well as any possible implementation of each of the aforementioned aspects. In one possible implementation, the communication device further comprises a memory. In one possible implementation, the communication device further comprises a communication interface, the processor coupled to the communication interface. In another possible implementation, the communication device further comprises a communication interface, the processor coupled to the communication interface.

[0059] In one implementation, the communication device is a terminal device. When the communication device is a terminal device, the communication interface may be a transceiver or an input / output interface. In one possible implementation, the transceiver may be a transceiver circuit. In one possible implementation, the input / output interface may be an input / output circuit.

[0060] In another implementation, the communication device is a network device. When the communication device is a network device, the communication interface may be a transceiver or an input / output interface. In one possible implementation, the transceiver may be a transceiver circuit. In another possible implementation, the input / output interface may be an input / output circuit.

[0061] In another implementation, the communication device is a data collection application function network element. When the communication device is a data collection application function network element, the communication interface may be a transceiver or an input / output interface. In one possible implementation, the transceiver may be a transceiver circuit. In another possible implementation, the input / output interface may be an input / output circuit.

[0062] In another implementation, the communication device is an event user application function network element. When the communication device is a data collection application function network element, the communication interface may be a transceiver or an input / output interface. In one possible implementation, the transceiver may be a transceiver circuit. In another possible implementation, the input / output interface may be an input / output circuit.

[0063] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be embodied as a processing circuit or a logic circuit.

[0064] In a twentieth aspect, a communication device is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal via the input circuit and transmit a signal via the output circuit, so that the method of any one of aspects 1 to 6, and any possible implementation of any of the above aspects, is implemented.

[0065] In a specific implementation, the communication device may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to a transmitter and transmitted by the transmitter. The input circuit and the output circuit may be different circuits or the same circuit, in which case the circuit functions as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation of the processor and various circuits.

[0066] In a twenty-first aspect, a processing device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory and receive signals via a receiver and transmit signals via a transmitter to execute the method of any one of aspects 1 to 6, and any possible implementation of any of the above aspects.

[0067] In a possible implementation, there are one or more processors and one or more memories.

[0068] In a possible implementation, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0069] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0070] It should be understood that related data interaction processes, such as sending indication information, can be the process of outputting indication information from the processor, and receiving capability information can be the process of receiving input capability information from the processor. Specifically, the output data of the processing can be output to the transmitter, and the input data received by the processor can come from the receiver. The transmitter and receiver can be collectively referred to as a transceiver.

[0071] The processor in the above aspects can be a chip, which can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated in the processor or located outside the processor and exist independently.

[0072] In aspect 22, a computer program product is provided, which includes: a computer program (also referred to as code, or instructions), which, when the computer program is run, enables the computer to execute any aspect from aspect 1 to aspect 6, as well as any possible implementation method of the above aspects.

[0073] In the twenty-third aspect, a computer-readable medium is provided, which stores a computer program (also referred to as code, or instructions) which, when run on a computer, enables the computer to execute any one of the above-mentioned aspects from the first to the sixth aspect, as well as any possible implementation method of the above-mentioned aspects.

[0074] In the twenty-fourth aspect, a chip system is provided, comprising a memory and a processor, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a communication device equipped with the chip system executes the methods in any of the above-mentioned first to sixth aspects and their possible implementation methods.

[0075] Among them, the chip system may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

[0076] In the twenty-fifth aspect, a communication system is provided, comprising the aforementioned data collection application function network element, event user application function network element, at least one of a network device and a terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] FIG1 is a schematic diagram of an example of a communication system to which the present application is applied.

[0078] FIG2 is a schematic diagram of the architecture of an access network device provided in an embodiment of the present application.

[0079] FIG3 is a schematic diagram of an AI application framework provided in an embodiment of the present application.

[0080] FIG4 is a schematic diagram of another AI application framework provided in an embodiment of the present application.

[0081] Figure 5 is a schematic flowchart of AI model lifecycle management provided in an embodiment of the present application.

[0082] FIG6 is a schematic flowchart of a data collection verification method provided in an embodiment of the present application.

[0083] FIG7 is a schematic flowchart of another data collection verification method provided in an embodiment of the present application.

[0084] FIG8 is a schematic flowchart of another data collection verification method provided in an embodiment of the present application.

[0085] FIG9 is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0086] FIG10 is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0087] FIG11 is a schematic block diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0088] The technical solution in this application will be described below with reference to the accompanying drawings.

[0089] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Wireless Fidelity (WIFI), Device to Device (D2D) communication system, Vehicle-to-Everything (V2X) communication system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, Machine to Machine (M2M) system, Machine Type Communication (MTC) system, Internet of Things (IoT) system. things, IoT) communication system, non-terrestrial network (NTN) system, fifth generation mobile communication system (5G) system, sixth generation mobile communication system (6G) or new radio (NR) or future wireless communication system.

[0090] FIG1 is a schematic diagram of a communication system 100 provided in an embodiment of the present application. As shown in FIG1 , the communication system 100 includes a network device 10, a terminal device 20, and an application layer network element 30. In this communication system, the terminal device 20 can send uplink data / signals / information to the network device 10, and the network device 10 can send downlink data / signals / information to the terminal device 20. Optionally, data / signals / information can be transmitted between the network device 10 and the application layer network element 30. Optionally, data / signals / information can be transmitted between the terminal device 20 and the application layer network element 30.

[0091] The communication method provided in the embodiment of the present application may also involve devices or transmission nodes not shown in Figure 1, and the embodiment of the present application is not limited to this.

[0092] The above-mentioned communication system applied to the embodiment of the present application is only an example. The communication system applicable to the embodiment of the present application is not limited to this. Any communication system that can realize the functions of the above-mentioned devices is applicable to the embodiment of the present application.

[0093] The terminal device in the embodiments of the present application may refer to a user device, an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved Public Land Mobile Network (PLMN), etc., and the embodiments of the present application are not limited thereto.

[0094] Wearable devices, also known as wearable smart devices, are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve full or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0095] Furthermore, the terminal device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network that interconnects people, machines, and things.

[0096] It should be understood that this application does not limit the specific form of the terminal device.

[0097] A network device may be a device in a wireless network, and in this application, may also be referred to as an operator device. For example, a network device may be a device deployed in a wireless network to provide wireless communication functions for a terminal device. For example, a network device may be a radio access network (RAN) node that connects a terminal device to a wireless network. The RAN may be connected to a core network (e.g., a long term evolution (LTE) core network or a 5G core network).

[0098] The network device in the embodiments of the present application may be an access network device, including but not limited to: various base stations, such as the next generation Node B (gNodeB, gNB), evolved Node B (eNB) or base station equipment in future evolved communication systems, or a server, a wearable device, an in-vehicle device, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), etc. It may also be one or a group (including multiple antenna panels) of antenna panels of a base station, or it may also be a network node constituting a base station, such as a baseband unit (BBU) or a distributed unit (DU), etc. Among them, the base station may be a macro base station, a micro base station, a pico base station, a small station, a relay station or a balloon station, etc.

[0099] The network device in the embodiment of the present application may also be a core network device, including but not limited to: access and mobility management function (AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, policy control function (PCF) network element, or unified data management function UDM network element, etc.

[0100] Application layer network elements refer to network devices in computer networks that are responsible for processing application layer protocols, including but not limited to: Data Collection Application Function (DCAF) network elements, Provisioning Application Function (PAF) network elements, Event Consumer Application Function (ECAF) network elements, etc.

[0101] It can be understood that all or part of the functions of the network device or terminal device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0102] Figure 2 is a schematic diagram of the architecture of an access network device provided in an embodiment of the present application. As shown in Figure 2, the network device involved in the embodiment of the present application may be a centralized unit (CU) and a distributed unit (DU) separated architecture. CU and DU can be understood as a division of network devices from a logical functional perspective. CU and DU can be physically separated or deployed together. Multiple DUs can share one CU. A DU can also be connected to multiple CUs (not shown in Figure 2). The CU and DU can be connected through an interface, such as an F1 interface. The CU and DU can be divided according to the protocol layer of the wireless network. One possible division method is: the CU is used to perform the functions of the radio resource control (RRC) layer, the service data adaptation protocol (SDAP) layer, and the packet data convergence protocol (PDCP) layer, and the DU is used to perform the functions of the radio link control (RLC) layer, the media access control (MAC) layer, the physical layer, etc.

[0103] It is understood that the division of the processing functions of the CU and DU according to the protocol layer is only an example, and the CU and DU may also be divided in other ways. For example, the CU or DU may be divided into functions of more protocol layers than the above division method. For example, the CU or DU may also be divided into some processing functions of the protocol layer in the above division method.

[0104] In one design, part of the functions of the RLC layer and the functions of the protocol layers above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer are set in the DU.

[0105] In another design, the functions of the CU or DU can be divided according to service type or other system requirements. For example, by latency, functions whose processing time meets the latency requirement are implemented in the DU, while functions that do not meet the latency requirement are implemented in the CU.

[0106] In another design, a CU can also have one or more core network functions. One or more CUs can be centrally located or separately located. For example, a CU can be located on the network side for centralized management. A DU can have multiple radio frequency functions, or the radio frequency functions can be remotely located.

[0107] The functions of a CU can be implemented by a single entity or by different entities. For example, the functions of a CU can be further divided, such as separating the control plane (CP) and the user plane (UP), namely the CU control plane (CU-CP) and the CU user plane (CU-UP). The CU control plane CU-CP also includes a further divided architecture, that is, the CU-CP is further divided into CU-CP1 and CU-CP2. CU-CP1 includes various radio resource management functions, while CU-CP2 only includes RRC functions and PDCP-C functions (i.e., the basic functions of control plane signaling at the PDCP layer).

[0108] In different systems, CU (including CU-CP or CU-UP) or DU may have different names, but those skilled in the art can understand their meanings. For example, in an open radio access network (O-RAN) system, CU may also be referred to as O-CU (open CU), DU may also be referred to as O-DU, CU-CP may also be referred to as O-CU-CP, and CU-UP may also be referred to as O-CU-UP. This application does not limit this.

[0109] The AI ​​module is a module with machine learning computing capabilities. As shown in Figure 2, in a wireless communication system, the AI ​​module can be located in the operations, administration, and maintenance (OAM) unit, the gNB (for example, if the gNB is a split architecture, it can be located in the CU / DU), the terminal device, or a separate network element entity, the RAN Intelligent Control (RIC). The AI ​​module's primary function in a wireless communication system is to perform a series of AI computations, including model building, training approximation, and reinforcement learning, based on input data (in wireless communication systems, input data generally refers to network operation data provided by access network equipment or monitored by OAM, such as network load, channel quality, or user plane data transmission provided by the core network). The trained model provided by the AI ​​module has predictive capabilities for RAN network changes and can be used for load prediction, terminal device path prediction, CSI prediction, optimal beam prediction, and positioning prediction. Furthermore, the AI ​​module can use the trained model's predicted RAN network performance to perform policy inference from the perspectives of network energy conservation and mobility optimization, thereby developing reasonable and efficient energy conservation and mobility optimization strategies. When the AI ​​model is located in the CU and the CU's CP and UP are separated, the CP can be responsible for receiving the AI ​​model and subsequent AI reasoning and policy generation functions. When the CU-CP is further divided into CU-CP1 and CU-CP2, CU-CP1 can be responsible for receiving the AI ​​model and subsequent AI model reasoning functions, and generating specific interaction signaling, which is then sent by CU-CP2. When the AI ​​module is located in the OAM, its communication with the gNB on the RAN side can reuse the current northbound interface. When the AI ​​module is located in the gNB or CU, it can reuse the current F1, Xn, Uu, and other interfaces. When the AI ​​module becomes an independent network entity, it needs to re-establish communication links with the OAM and RAN sides, such as based on wired links or wireless links.

[0110] Figure 3 is a schematic diagram of an AI application framework provided by an embodiment of the present application. As shown in Figure 3, the AI ​​application framework includes a data acquisition module, a model training module, a model reasoning module, and an execution entity (Actor).

[0111] The model training module and model inference module are examples of AI modules. For example, the network devices and terminal devices shown in Figure 1, or the CU, DU, or other management entities of the gNB shown in Figure 2, can input data into the data acquisition module, which can serve as a database for AI model training and data analysis and inference. The model training module analyzes the training data output by the data acquisition module and generates a usable AI model, which is then deployed to the model inference module. Based on the inference data output by the data acquisition module, the model inference module generates reasonable predictions about network operation based on the AI ​​model (trained by the model training module) and feeds the AI ​​model's performance data back to the model training module. The model training module then continues to train the model based on the fed-back performance data and informs the model inference module of the updated AI model. Alternatively, the model inference module guides network policy adjustments based on the inference data and the AI ​​model output by the data acquisition module. These policy adjustments are centrally planned by the execution entity and sent to multiple network entities for execution. Furthermore, the specific network performance after the relevant policies are applied is fed back to the data acquisition module for storage.

[0112] Figure 4 is a schematic diagram of another AI application framework provided by an embodiment of the present application. As shown in Figure 4, the framework includes a data acquisition module, a model training module, a model management module, a model reasoning module, and a model storage module.

[0113] Among them, the model management module interacts with and manages the other modules, and the model storage module is used to store and manage AI models.

[0114] Figure 5 is a schematic flowchart of AI model lifecycle management (LCM) provided in an embodiment of the present application.

[0115] For different use cases, there may be different LCM overall signaling processes. The process shown in Figure 5 is only an example, and this application does not limit the specific LCM process.

[0116] The 3rd Generation Partnership Project (3GPP) has introduced multiple AI application scenarios for the RAN. These include, but are not limited to, energy saving, load balancing, mobility optimization, enhanced channel state information-reference signal (CSI-RS) feedback, beam management enhancement (BME), and positioning enhancement. These scenarios are also referred to as AI use cases.

[0117] For example, AI can be used to enhance CSI feedback. CSI is the channel property of the communication link. The UE reports downlink channel quality information to the gNB, allowing the base station to select a more appropriate modulation and coding scheme (MCS) for the UE. According to the latest progress of the RAN1 meeting, two sub-use cases, AI-based CSI compression and CSI prediction (low priority), were approved. CSI compression is based on a bilateral model (an encoder (and quantizer) on the UE side for compressing CSI, and a decoder (and dequantizer) on the gNB side for decompression). AI-based codecs can be implemented using AI models such as convolutional neural networks (CNNs) and Transformers that use attention mechanisms to speed up model training).

[0118] For example, AI can also be used for beam management (BM), which primarily aims to find the strongest transmit / receive beam pair. AI / ML-based sparse beam prediction aims to improve the accuracy of optimal beam prediction. During the training phase, the network scans all possible beams, and then the network needs to inform the UE of the transmit beam pattern. When model training is complete, the network only needs to scan a small number of beams, and the UE then feeds back the inferred top-K narrow beams (e.g., the K beams with the best receiving power) to the network.

[0119] For example, AI can also be used for positioning accuracy enhancements. R17 already supports LOS / NLOS indication reporting, with the aim of improving positioning accuracy. For AI / ML-based LOS / NLOS recognition, it can improve positioning accuracy with a smaller number of transmission reception point (TRP) antennas. For indoor scenarios (heavy NLOS scenarios), there may not be a sufficient number of line-of-sight paths, and traditional methods cannot work well. Therefore, AI-based positioning can improve positioning accuracy in indoor scenarios.

[0120] The input to the AI ​​models in these AI application scenarios is access layer data. For example, in the CSI compression scenario, the input to the model is CSI-RS measurement results, which involves access layer CSI reporting. When collecting UE data, permission management is required.

[0121] However, in the above-mentioned AI application scenarios, the input of the AI ​​model is the UE's AS data. Since AS-layer data is usually collected by operators and they have the authority to process it, the existing AAS authorization mechanism cannot be directly used. There is no relevant authorization mechanism for AS-layer data, which may lead to the improper exposure of AS data to third-party ECAF nodes due to lack of authorization when collecting AS-layer data.

[0122] This application provides a variety of verification methods for AS data collection, targeting the scenario of collecting UE AS data. By introducing an authorization mechanism for the collected AS data, it ensures that AS layer data can be reasonably collected under permission control.

[0123] It should be understood that the description of the specific scenarios in the embodiments of the present application is only an example. In addition to being applicable to the application scenarios described above, the methods provided in the embodiments of the present application are also applicable to application scenarios with similar problems.

[0124] In the description of the embodiments of the present application, unless otherwise specified, "a plurality of" or "a plurality of" means two or more. In addition, "at least one" can be replaced by "one or more".

[0125] The ordinal numbers "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, the first indication information and the second indication information can be the same information or different information, and such names do not indicate differences in the content, size, application scenario, sender / receiver, priority, or importance of the two messages. In addition, the numbering of the steps in the various embodiments introduced in this application is only for distinguishing different steps and is not used to limit the order of the steps.

[0126] In this application, the terms "comprises" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or elements is not necessarily limited to those steps or elements explicitly listed, but may include other steps or elements not explicitly listed or inherent to such process, method, product or apparatus.

[0127] The technical solutions provided in the embodiments of this application can be applied to wireless communications between communication devices. Wireless communications between communication devices may include: wireless communications between network devices and terminals, wireless communications between network devices, and wireless communications between terminals. In the embodiments of this application, the term "wireless communications" may also be referred to as "communication," which may also be described as "data transmission," "information transmission," or "transmission."

[0128] It should be understood that the names of all nodes and messages in this application are merely names set for the convenience of description in this application. The names in the actual network may be different. This application should not be understood as limiting the names of various nodes and messages. On the contrary, any name with the same or similar function as the node or message used in this application is regarded as a method or equivalent replacement of this application, and is within the scope of protection of this application. No further details will be given below.

[0129] The various methods provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0130] It should be understood that the step numbers in the embodiments of the present application are for illustration only and do not limit the order in which the steps occur.

[0131] FIG6 shows a data collection verification method 600 provided in the present application, through which permission management of collecting AS data of UE is performed. The method in FIG6 includes at least part of the following contents.

[0132] S610: The PAF sends access layer data measurement and reporting configuration information to the DCAF.

[0133] S620, DCAF exchanges authorization information with the network device.

[0134] S630, ECAF sends third request information to DCAF, where the third request information is used to request a fifth access layer data set.

[0135] S640, DCAF sends third information to ECAF, where the third information is used to indicate that the second access layer data set needs to be authorized at the network device.

[0136] S650: DCAF obtains access layer data.

[0137] S660, ECAF sends a first request message to the network device, where the first request message is used to request authorization of the second access layer data set.

[0138] S670: The network device sends first information to ECAF, where the first information is used to indicate a first key.

[0139] S680: ECAF sends a second request message to DCAF, where the second request message is used to request a third access layer data set, and the second request message includes the first information.

[0140] S690: The network device and DCAF verify the first key.

[0141] S691, DCAF sends subscription confirmation information (ie, an example of first confirmation information) to ECAF.

[0142] Through the above solution, ECAF needs to obtain authorization from the operator's equipment before it can obtain the collected AS measurement data from DCAF. This ensures the operator's authority management over AS data collection and prevents AS data from being directly exposed to other network nodes in the non-AS layer.

[0143] The following is a detailed introduction to S610 to S690.

[0144] First, DCAF needs to register with NRF (Network Repository Function). DCAF initiates registration with NRF. The registration information includes a series of event IDs. The data collection results of the events corresponding to these IDs can be provided to ECAF after authorization.

[0145] It should be noted that, unless otherwise specified, in this application, the access layer refers to the access layer of the terminal device, the access layer data refers to the measurement results of the access layer data of the terminal device, and the non-access layer refers to the non-access layer of the terminal device.

[0146] In S610 , the PAF sends measurement and reporting configuration information of access layer data to the DCAF.

[0147] Specifically, the measurement and reporting configuration information may include: what data needs to be collected, the configuration of data collection (such as the sampling frequency of collection, geographical restrictions, etc.), the reporting frequency and format of the collected data, how DCAF processes this data and how it is sent to the corresponding subscribers (or called event users).

[0148] In one implementation, the collected data information may include one or more of the following: artificial intelligence AI function information indicating the access layer data corresponding to the access layer data (the AI ​​function may indicate one or more functions including but not limited to CSI compression, CSI prediction, BM, and positioning), target frequency information measured by the UE, reference signal type information measured by the UE (for example, indicating SSB and / or CSI), channel quality type information measured by the UE (for example, RSRP / RSRQ / SINR, etc.), indication information collected and reported via the UE's physical layer L1 and / or network layer L3, scenario information requiring collection of access layer data (for example, a specific area, cell, cell configuration, etc.), and information on the maximum number of beams reported (for example, indicating measurement results of 4 / 6 / several Beams).

[0149] It should be noted that this application does not limit the relationship between the AS layer data collection requirements and the Event ID. That is to say, an Event ID may include non-AS layer data collection requirements and AS layer data collection requirements; or, an Event ID may only include AS layer data collection requirements.

[0150] In S620 , the DCAF exchanges authorization information with the network device.

[0151] First, DCAF needs to send a data collection request to the network device. The data collection request includes event information containing AS data collection and related data collection configuration (i.e., measurement and reporting configuration information of access layer data).

[0152] After receiving the measurement and reporting configuration information of the access layer data, the network device determines whether the events related to the AS data need to be granted permission before they can be provided to other ECAFs based on the event information in the measurement and reporting configuration information.

[0153] The operator device may indicate authorization information (ie, an example of first indication information) to the DCAF in any of the following ways, where the first indication information is used to indicate that the access layer data in the first access layer data set requires authorization before being provided to other network elements.

[0154] Method 1

[0155] Instructions are given according to different Events.

[0156] That is, the first indication information sent by the network device to the DCAF indicates whether the access layer data corresponding to each Event in the first access layer data set needs to be authorized before being provided to other ECAFs.

[0157] Optionally, when there are multiple device entities in the network device, the authorization information may further indicate the identifier of the target network device entity for which authorization is required for each Event ID.

[0158] Method 2

[0159] Overall instructions

[0160] That is, the network device sends a first indication to the DCAF, indicating that any access layer data corresponding to an event containing AS data must be authorized by the network device before it can be provided to other ECAFs. In this case, the first access layer data set includes the access layer data corresponding to all events containing AS data.

[0161] Optionally, when there are multiple device entities in the network device, the authorization information may further indicate an identifier of a target network device entity for which authorization needs to be obtained.

[0162] Mode 3: Authorization is required by default. That is, DCAF defaults to instructing ECAF to obtain authorization from the network device for any subsequent subscription information containing AS data received from ECAF. In this case, the first access layer data set includes all AS data.

[0163] Optionally, when there are multiple device entities in the operator equipment, the authorization information may further indicate the target operator equipment entity identifier for which authorization needs to be obtained.

[0164] In S630 , the ECAF sends a third request message to the DCAF, where the third request message is used to request a fifth access layer data set.

[0165] In one implementation, the third request information includes the target UE information corresponding to the measurement (such as UE ID, UE IP address, or UE cluster ID, and any identification information that can point to a specific UE), measurement event ID (which can be one or a group of event IDs), and measurement result reporting configuration (event / periodic reporting, reporting duration, maximum number of reports, etc.).

[0166] It should be understood that in this third request message, ECAF may further send model-related subscription information to DCAF to request the measurement results required for local training of the model with the event user application function network element. For example, it may indicate that a local model is to be trained and include functional information corresponding to the trained model (e.g., measurement information corresponding to the CSI compression function).

[0167] In S640, the DCAF sends third information to the ECAF, where the third information is used to indicate that the second access layer data set needs to be authorized at the network device.

[0168] After receiving the third request information sent by ECAF, DCAF can determine, based on the first indication information, that there is some access layer data in the fifth access layer data set that needs to be authorized, and this partial data is the second access layer data set.

[0169] It should be understood that the second access-stratum data set includes all or part of the data in the fifth access-stratum data set, or in other words, the second access-stratum data set is a subset of the fifth access-stratum data set.

[0170] It should be understood that, since the second access layer data set includes all or part of the data in the first access layer data set, the DCAF determines that the second access layer data set needs to apply for authorization at the network device.

[0171] Optionally, the third information includes first identification information, and the first identification information includes an identification of the network device.

[0172] In S650 , the DCAF obtains access layer data.

[0173] In this step, DCAF needs to obtain the AS data of the UE. Specifically, DCAF can send an AS data collection request to the network device, and the network device will send the AS data collection configuration to the UE; alternatively, DCAF can send an AS data collection request to the non-AS layer of the UE, and the non-AS layer of the UE will perform data collection. The specific process is not described here.

[0174] In S660, the ECAF sends a first request message to the network device, where the first request message is used to request authorization of the second access layer data set.

[0175] In step S640, the ECAF learns through the third information that it needs to obtain authorization from a specific network device, and obtains the identification of the network device through the first identification information.

[0176] Thus, ECAF can send the first request information to the network device according to the identifier of the network device.

[0177] The first request information may include one or more of the following information: ECAF identification information, ECAF requirement indication information for collecting AS data, Event ID information for which ECAF requests authorization and contains AS data collection requirements, specific data collection requirements related to AS in Event data collection, estimated collection time or deadline for Event data, purpose / scope of Event data collection (such as PLMN, NID / PNI-NPN, etc.), etc.

[0178] In S670, the network device sends first information to the ECAF, where the first information is used to indicate a first key, and the first key is used to authorize a third access layer data set, where the third access layer data set includes all or part of the data in the second access layer data set.

[0179] It should be understood that when ECAF applies to the network device for authorization of the second access layer data set, not all data may be authorized. Therefore, optionally, the third access layer data set is a subset of the second access layer data set.

[0180] In one implementation, in addition to the first key, the first information also includes description (claim) information corresponding to the first key. The claim information includes one or more of the following: ECAF identification information, Event ID information corresponding to the first key, specific AS data collection requirements corresponding to the first key, validity period or expiration time corresponding to the first key, and the scope of use of the first key (e.g., PLMN, NID / PNI-NPN, etc.). In addition, if the operator device can also feedback multiple first keys to ECAF, the operator device can distinguish the first keys to indicate the above information.

[0181] In one implementation, for data that cannot be authorized in the second access layer data set, a third indication message may also be sent to ECAF. The third indication message is used to indicate that part of the access layer data in the second access layer data set is not authorized. The third indication message includes reason information, which is used to feedback the reason why authorization cannot be obtained, such as protecting the privacy of AS data.

[0182] In S680 , the ECAF sends a second request message to the DCAF, where the second request message is used to request a third access layer data set. The second request message includes the first information, where the first information is used to indicate the first key.

[0183] Based on the authorization information obtained from the operator's equipment, ECAF initiates a subscription request to DCAF containing AS data collection, which includes the first key obtained in step S670.

[0184] In S690, the network device verifies the first key with the DCAF.

[0185] Specifically, DCAF needs to first send the obtained first key (by sending the first information) to the network device, and then determine whether the third access layer data set corresponding to the first key can be sent to ECAF based on the verification information sent by the network device (that is, an example of the second information, the second information is used to indicate the verification result of the first key).

[0186] In S691, DCAF sends a subscription confirmation message to ECAF.

[0187] It should be understood that after the verification of the first key is passed, DCAF sends a subscription confirmation message to ECAF to inform ECAF that the verification is successful, so that DCAF sends the AS layer data (i.e., the third access layer data set) authorized in the subscription request to ECAF. After ECAF receives the AS layer data, it can send a cancellation indication message to DCAF to end the collection of AS data.

[0188] FIG7 shows a communication method 700 provided in the present application, through which permission management of collecting AS data of UE is performed. The method in FIG7 includes at least part of the following contents.

[0189] S710, the PAF sends access layer data measurement and reporting configuration information to the DCAF.

[0190] S720, DCAF exchanges authorization information with the network device.

[0191] S730: The network device sends second indication information to the AS layer of the UE.

[0192] S740, ECAF sends third request information to DCAF, where the third request information is used to request a fifth access layer data set.

[0193] S750, DCAF sends third information to ECAF, where the third information is used to indicate that the second access layer data set needs to be authorized at the network device.

[0194] S760: DCAF obtains access layer data.

[0195] S770, ECAF sends a first request message to the network device, where the first request message is used to request authorization of the second access layer data set.

[0196] S780. The network device sends first information to ECAF, where the first information is used to indicate a first key.

[0197] S790, ECAF sends a second request message to DCAF, where the second request message is used to request a third access layer data set, the first key is used to authorize the third access layer data set, and the third access layer data set includes all or part of the data in the second access layer data set;

[0198] S791: The network device and DCAF verify the first key.

[0199] S792, DCAF sends subscription confirmation information to ECAF

[0200] With this solution, network devices can configure additional measurements for the UE's AS layer based on data collection requests from non-AS layers sent by the UE's AS layer, thereby expanding the scope of data collection. Furthermore, by exchanging authorization information between the network device and the UE's AS layer, the scope of the UE's AS data exposure can be controlled.

[0201] The following is a detailed introduction to S710 to S790.

[0202] Steps S710 to S720 may refer to steps S610 to S620 .

[0203] In S730 , the network device sends second indication information to the AS layer of the UE, where the second indication information is used to indicate that the access stratum data in the fourth access stratum data set can be sent to the non-access stratum of the UE.

[0204] It should be understood that this solution is applied to the scenario of collecting AS data through the non-AS layer of the UE.

[0205] Specifically, the UE's non-AS layer sends an AS data collection request to the UE's AS layer, which in turn enables the AS layer to send access stratum data to the non-AS layer. The UE's AS layer performs measurements, which are not strictly sequential with the remaining steps. That is, the UE's measurements are independent and unaffected by data collection requests received by the UE's non-AS layer.

[0206] Since the network device and the AS layer of the UE have exchanged authorization information, that is, the AS layer of the UE has received the second indication information sent by the network device, it can determine which measurement data of the AS layer can be sent to the non-AS layer of the UE. For example, the network device indicates to the AS layer of the UE which data (such as the fourth access layer data set) can be sent to the non-AS layer of the UE. The indication method can be a specific measurement or a corresponding Event ID.

[0207] Optionally, the second indication signal may further include the forwarding effective time and effective area (constrained by PLMN, etc.) of the measurement quantity that can be forwarded.

[0208] Optionally, the AS layer of the UE sends a data collection request received from the non-AS layer to the network device, thereby obtaining the second indication information.

[0209] Optionally, the network device may issue additional measurement configurations to the AS layer of the UE according to the data collection request received from the non-AS layer and reported by the UE, so as to expand the non-AS layer data collection scope of the UE.

[0210] Steps S740 to S792 may refer to steps S630 to S691 .

[0211] FIG8 shows a data collection method 800 provided in the present application, through which permission management of collecting AS data of UE is performed. The method in FIG8 includes at least part of the following contents.

[0212] S810, the PAF sends access layer data measurement and reporting configuration information to the DCAF.

[0213] S820, DCAF exchanges authorization information with the network device.

[0214] S830, ECAF sends a third request message to DCAF, where the third request message is used to request a fifth access layer data set.

[0215] S840, DCAF sends fourth information to ECAF, where the fourth information is used to indicate that the second access layer data set needs to be authorized at the non-AS layer of the UE.

[0216] S850. ECAF sends first request information to DCAF, where the first request information is used to request authorization of the second access layer data set.

[0217] S860: DCAF sends first request information to the non-AS layer of the UE.

[0218] S870: The non-AS layer of the UE sends first request information to the network device.

[0219] S880, the network device sends first information to the non-AS layer of the UE, where the first information is used to indicate a first key, and the first key is used to authorize a third access layer data set, where the third access layer data set includes all or part of the data in the second access layer data set.

[0220] S890. The non-AS layer of the UE sends first information to the AS layer of the UE.

[0221] S891: The network device and the AS layer of the UE verify the first key.

[0222] S892: DCAF obtains the access layer data and authorization result information forwarded by the non-access layer of the UE.

[0223] S893, DCAF sends subscription confirmation information to ECAF.

[0224] Through the above solution, the ECAF authorization application is forwarded to the operator equipment via the UE's non-AS layer, and the authorization verification is completed between the UE and the operator equipment. The authorization result and data collection result are sent to ECAF via DCAF, ensuring that AS data is collected with authorization.

[0225] The following is a detailed introduction to S810 to S891.

[0226] Steps S810 to S830 may refer to steps S610 to S630 .

[0227] In S840 , the DCAF sends fourth information to the ECAF, where the fourth information is used to indicate that the second access layer data set needs to be authorized at the non-AS layer of the UE.

[0228] Optionally, the fourth information includes second identification information, and the second identification information includes the identification of the UE.

[0229] In S850 , the ECAF sends first request information to the DCAF, where the first request information is used to request authorization of the second access layer data set.

[0230] The first request information may include one or more of the following information: ECAF identification information, ECAF requirement indication information for collecting AS data, Event ID information for which ECAF requests authorization and contains AS data collection requirements, specific data collection requirements related to AS in Event data collection, estimated collection time or deadline for Event data, purpose / scope of Event data collection (such as PLMN, NID / PNI-NPN, etc.), etc.

[0231] In S860, the DCAF sends the first request information to the non-AS layer of the UE. In S870, the non-AS layer of the UE sends the first request information to the network device.

[0232] Optionally, the DCAF may send an authorization request to the target UE according to the corresponding relationship based on the target UE indicated by the third request information in S830.

[0233] Optionally, the network device may indicate to the AS layer of the UE which measurement data can be sent to the non-AS layer of the UE. For example, the network device may send second indication information to the AS layer of the UE, where the second indication information is used to indicate that access stratum data in the fourth access stratum data set can be sent to the non-access stratum of the UE. For details, see step S730.

[0234] In S880, the network device sends first information to the non-AS layer of the UE, where the first information is used to indicate a first key, where the first key is used to authorize a third access layer data set, where the third access layer data set includes all or part of the data in the second access layer data set.

[0235] It should be understood that when the non-AS layer of the UE applies to the network device for authorization of the second access layer data set, not all data may be authorized. Therefore, optionally, the third access layer data set is a subset of the second access layer data set.

[0236] In one implementation, in addition to the first key, the first information also includes description (claim) information corresponding to the first key. The claim information includes one or more of the following: ECAF identification information, Event ID information corresponding to the first key, specific AS data collection requirements corresponding to the first key, validity period or expiration time corresponding to the first key, and the scope of use of the first key (e.g., PLMN, NID / PNI-NPN, etc.). In addition, if the operator device can also feedback multiple first keys to ECAF, the operator device can distinguish the first keys to indicate the above information.

[0237] In one implementation, for data that cannot be authorized in the second access layer data set, a third indication information can also be sent to the non-AS layer of the UE. The third indication information is used to indicate that some access layer data in the second access layer data set is not authorized. The third indication information includes reason information, which is used to feedback the reason why authorization cannot be obtained, such as protecting the privacy of AS data.

[0238] In S890 , the non-AS layer of the UE sends first information to the AS layer of the UE.

[0239] The non-AS layer of the UE initiates a subscription request containing AS data collection to the DCAF based on the first information obtained from the network device, wherein the subscription request contains the first information obtained in step S880.

[0240] In S891 , the network device and the AS layer of the UE verify the first key.

[0241] Specifically, the AS layer of the UE needs to first send the obtained first key (by sending the first information) to the network device, and then determine whether the third access layer data set corresponding to the first key can be sent to the non-AS layer of the UE based on the verification information sent by the network device (that is, an example of the second information, the second information is used to indicate the verification result of the first key).

[0242] In S892, the DCAF obtains the access stratum data and authorization result information forwarded by the non-access stratum of the UE.

[0243] Specifically, after the verification is passed, the AS layer of the UE sends the measurement result of the access layer (the third access layer data set) to the non-AS layer of the UE, and the non-AS layer of the UE forwards it to the DCAF.

[0244] Optionally, the non-AS layer of the UE sends authorization result information to the DCAF, where the authorization result information is used to indicate which data in the second access layer data set is authorized and which data is not authorized. For example, which data in the second access layer data set is successfully authorized to the network device through the non-AS layer, specifically, which ECAF, which Events, or which measurement requirements are authorized, and the reason why authorization is not provided.

[0245] S893, DCAF sends subscription confirmation information to ECAF.

[0246] It should be understood that after the verification is successful, DCAF sends a subscription confirmation message to ECAF to inform ECAF that the verification is successful.

[0247] Optionally, the DCAF may send the authorized access layer data to the corresponding ECAF based on the authorization result information, and may further forward the reasons why some data are not authorized.

[0248] After receiving the AS layer data, ECAF can send a subscription cancellation instruction message to DCAF to end the collection of AS data.

[0249] Figure 9 is a schematic block diagram of a communication device 900 provided in an embodiment of the present application. The device 900 includes a transceiver unit 910 and a processing unit 920. The transceiver unit 910 can communicate with the outside world, and the processing unit 920 is used to process data. The transceiver unit 910 can also be referred to as a communication interface or a communication unit.

[0250] In a possible implementation, the apparatus 900 may further include a storage unit, which may be used to store instructions and / or data, and the processing unit 920 may read the instructions and / or data in the storage unit.

[0251] The device 900 can be used to execute the actions performed by the network device in the above method embodiment. In this case, the device 900 can be a network device, or a component that can be configured in a network device. The transceiver unit 910 is used to execute the transceiver-related operations of the network device in the above method embodiment, and the processing unit 920 is used to execute the processing-related operations of the network device in the above method embodiment.

[0252] Alternatively, the device 900 can be used to execute the actions performed by the terminal device in the above method embodiment. In this case, the device 900 can be a terminal device or a component that can be configured on the terminal device. The transceiver unit 910 is used to execute the transceiver-related operations on the terminal device side in the above method embodiment, and the processing unit 920 is used to execute the processing-related operations on the terminal device side in the above method embodiment.

[0253] Alternatively, the device 900 can be used to execute the actions performed by the application layer network element in the above method embodiment. In this case, the device 900 can be an application layer network element or a component that can be configured on an application layer network element. The transceiver unit 910 is used to execute the transceiver-related operations on the application layer network element side in the above method embodiment, and the processing unit 920 is used to execute the processing-related operations on the application layer network element side in the above method embodiment.

[0254] It should also be understood that the device 900 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 900 may be specifically a network device, a terminal device or an application layer network element in the above-mentioned embodiment, which may be used to execute the various processes and / or steps corresponding to the network device, the terminal device or the application layer network element in the above-mentioned method embodiments, or the device 900 may be specifically a network device, a terminal device or an application layer network element in the above-mentioned embodiment, which may be used to execute the various processes and / or steps corresponding to the network device, the terminal device or the application layer network element in the above-mentioned method embodiments. To avoid repetition, it will not be described here.

[0255] The apparatus 900 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the network device, terminal device or application layer network element in the above-mentioned method. The functions can be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

[0256] In addition, the transceiver unit 910 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit.

[0257] It should be noted that the apparatus in FIG9 may be a network element or device in the aforementioned embodiment, or may be a chip or chip system, such as a system on chip (SoC). The transceiver unit may be an input / output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.

[0258] As shown in Figure 10, an embodiment of the present application further provides a communication device 1000. The communication device 1000 includes a processor 1010, which is coupled to a memory 1020. The memory 1020 is used to store computer programs or instructions and / or data. The processor 1010 is used to execute the computer programs or instructions and / or data stored in the memory 1020, so that the method in the above method embodiment is executed.

[0259] In a possible implementation, the communication device 1000 includes one or more processors 1010 .

[0260] In a possible implementation, as shown in FIG8 , the communication device 1000 may further include a memory 1020 .

[0261] In a possible implementation, the communication device 1000 may include one or more memories 1020 .

[0262] In a possible implementation, the memory 1020 may be integrated with the processor 1010 or separately provided, or the processor 1020 may be outside the communication device 1000 .

[0263] In one possible implementation, as shown in Figure 8, the wireless communication device 1000 may further include a transceiver 1030, which is configured to receive and / or transmit signals. For example, the processor 1010 is configured to control the transceiver 1030 to receive and / or transmit signals.

[0264] As a solution, the communication device 1000 is used to implement the operations performed by the network device in the above method embodiment.

[0265] For example, the processor 1010 is used to implement the processing-related operations performed by the network device in the above method embodiment, and the transceiver 1030 is used to implement the sending and receiving-related operations performed by the network device in the above method embodiment.

[0266] As another solution, the communication device 1000 is used to implement the operations performed by the terminal device in the above method embodiment.

[0267] For example, the processor 1010 is used to implement the processing-related operations performed by the terminal device in the above method embodiment, and the transceiver 1030 is used to implement the sending and receiving-related operations performed by the terminal device in the above method embodiment.

[0268] As another solution, the communication device 1000 is used to implement the operations performed by the application layer network element in the above method embodiment.

[0269] For example, the processor 1010 is used to implement the processing-related operations performed by the application layer network element in the above method embodiment, and the transceiver 1030 is used to implement the sending and receiving-related operations performed by the application layer network element in the above method embodiment.

[0270] As shown in FIG11 , an embodiment of the present application provides a chip system 1100 . The chip system 1100 (or also referred to as a processing system) includes a logic circuit 1110 and an input / output interface 1120 .

[0271] Logic circuit 1110 may be a processing circuit within chip system 1100. Logic circuit 1110 may be coupled to a storage unit and invoke instructions within the storage unit, enabling chip system 1100 to implement the methods and functions of various embodiments of the present application. Input / output interface 1120 may be an input / output circuit within chip system 1100, outputting information processed by chip system 1100 or inputting data or signaling information to be processed into chip system 1100 for processing.

[0272] As a solution, the chip system 1100 is used to implement the operations performed by the network device, terminal device or application layer network element in the above various method embodiments.

[0273] For example, the logic circuit 1110 is used to implement the processing-related operations of the network device in the above method embodiment; the input / output interface 1120 is used to implement the sending and / or receiving-related operations of the network device in the above method embodiment.

[0274] An embodiment of the present application further provides a computer-readable storage medium on which computer instructions are stored for implementing the method executed by a terminal device or a method executed by a satellite in the above method embodiment.

[0275] For example, when the computer program is executed by a computer, the computer can implement the method executed by the terminal device, or the method executed by the network device, or the method executed by the application layer network element in the above method embodiment.

[0276] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to implement the method executed by a network device, or the method executed by a terminal device, or the method executed by an application layer network element in the above method embodiment.

[0277] An embodiment of the present application also provides a communication system, which includes one or more of the network devices, terminal devices or application layer network elements in the above embodiments.

[0278] The explanation and beneficial effects of the relevant contents in any of the wireless communication devices provided above may refer to the corresponding method embodiments provided above, and will not be repeated here.

[0279] In an embodiment of the present application, a terminal device or network device may include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also known as main memory). The operating system of the operating system layer may be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0280] The embodiments of the present application do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of the present application; as long as it is capable of communicating according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application, it is sufficient. For example, the execution subject of the method provided in the embodiments of the present application may be a terminal device or a satellite, or a functional module in the terminal device or satellite that is capable of calling and executing the program.

[0281] Various aspects or features of the embodiments of the present application can be implemented as methods, devices, or articles of manufacture using standard programming and / or engineering techniques. As used herein, the term "article of manufacture" can encompass a computer program accessible from any computer-readable device, carrier, or medium. For example, a computer-readable medium can include, but is not limited to, magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.).

[0282] The various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0283] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0284] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM may include the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0285] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0286] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0287] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of this application.

[0288] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0289] In the several embodiments provided in the embodiments of the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0291] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0292] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0293] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the embodiments of the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A data collection verification method, characterized in that: include: The network device sends first indication information to the data collection application function network element, where the first indication information is used to indicate that access layer data in the first access layer data set of the terminal device needs to be authorized before being provided to other network elements; The network device receives a first request message from an event user application function network element or a non-access layer of the terminal device, where the first request message is used to request authorization of a second access layer data set, where the second access layer data set includes all or part of the data in the first access layer data set; The network device sends first information to the event user application function network element or the non-access layer of the terminal device, where the first information is used to indicate a first key, where the first key is used to authorize a third access layer data set, where the third access layer data set includes all or part of the data in the second access layer data set; The network device receives the first information from the data collection application function network element or the access layer of the terminal device; The network device sends second information to the data collection application function network element or the access layer of the terminal device, where the second information is used to indicate the verification result of the first key.

2. The method according to claim 1, characterized in that The method further comprises: The network device sends the second indication information to the access layer of the terminal device, where the second indication information is used to indicate that the access layer data in the fourth access layer data set can be sent to the non-access layer of the terminal device.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: The network device sends a third indication message to the event user application function network element or the non-access layer of the terminal device, wherein the third indication message is used to indicate that part of the access layer data in the second access layer data set is not authorized, and the third indication message includes reason information, and the reason information is used to indicate the reason why the request for the part of the access layer data is not authorized.

4. The method according to any one of claims 1 to 3, characterized in that The second access layer data set also includes all or part of the data in the fifth access layer data set, and the fifth access layer data set is the access layer data requested by the event user application function network element to the data collection application function network element.

5. A data collection verification method, characterized in that: include: The data collection application function network element receives first indication information from the network device, where the first indication information is used to indicate that access layer data in the first access layer data set of the terminal device needs to be authorized before being provided to other network elements; The data collection application function network element receives second request information from the event user application function network element, the second request information is used to request a third access layer data set of the terminal device, the third access layer data set includes all or part of the data in the first access layer data set, the second request information includes first information, the first information is used to indicate a first key, and the first key is used for authorization of the third access layer data set; The data collection application function network element sends the first information to the network device; The data collection application function network element receives second information from a network device, where the second information is used to indicate a verification result of the first key.

6. The method according to claim 5, characterized in that The method further comprises: The data collection application function network element receives a third request message from the event user application function network element, wherein the third request message is used to request a fifth access layer data set of the terminal device, wherein the fifth access layer data set includes all or part of the data in the first access layer data set; The data collection application function network element sends third information to the event user application function network element, and the third information is used to indicate that the second access layer data set needs to be authorized at the network device, and the second access layer data set includes all or part of the data in the fifth access layer data set. The third information includes first identification information, and the first identification information includes the identification of the network device.

7. The method according to claim 6, characterized in that The method further comprises: The data collection application function network element sends a first confirmation message to the event user application function network element, where the first confirmation message is used to indicate a request result of the third request information.

8. A data collection verification method, characterized in that: include: The event user application function network element sends a first request message to the network device, wherein the first request message is used to request the terminal device to Second, authorization of access layer data collection; The event user application function network element receives first information from a network device, where the first information is used to indicate a first key, where the first key is used to authorize a third access layer data set, where the third access layer data set includes all or part of the data in the second access layer data set; The event user application function network element sends a second request message to the data collection application function network element, where the second request message is used to request a third access layer data set, and the second request message includes the first information.

9. The method according to claim 8, characterized in that The method further comprises: The event user application function network element sends a third request message to the data collection application function network element, where the third request message is used to request a fifth access layer data set of the terminal device; The event user application function network element receives third information from the data collection application function network element, and the third information is used to indicate that the second access layer data set needs to be authorized at the network device, and the second access layer data set includes all or part of the data in the fifth access layer data set. The third information includes first identification information, and the first identification information includes the identification of the network device.

10. The method according to claim 8 or 9, characterized in that: The method further comprises: The event user application function network element receives first confirmation information from the data collection application function network element, where the first confirmation information is used to indicate a request result of the third request information.

11. A data collection verification method, characterized in that: include: The non-access layer of the terminal device receives first request information from the data collection application function network element, where the first request information is used to request authorization of the second access layer data set of the terminal device; The non-access layer of the terminal device sends the first request information to the network device; The non-access layer of the terminal device receives first information from the network device, where the first information includes a first key, where the first key is used for authorization of a third access layer data set, where the third access layer data set includes all or part of the data in the second access layer data set; The non-access layer of the terminal device sends the first information to the access layer of the terminal device; The access layer of the terminal device sends the first information to the network device; The access layer of the terminal device receives second information from a network device, where the second information is used to indicate a verification result of the first key.

12. The method according to claim 11, characterized in that The method further comprises: The non-access layer of the terminal device sends authorization result information to the data collection application function network element, and the authorization result information is used to indicate which data in the second access layer data set is authorized and which data is not authorized.

13. A data collection verification method, characterized in that: include: The event user application function network element sends a third request message to the data collection application function network element, where the third request message is used to request a fifth access layer data set of the terminal device; The event user application function network element receives fourth information from the data collection application function network element, wherein the fourth information is used to indicate that the second access layer data set needs to be authorized at the non-access layer of the terminal device, and the second access layer data set includes all or part of the data in the fifth access layer data set; The event user application function network element sends a first request message to the data collection application function network element, where the first request message is used to request authorization of a second access layer data set, and the first request message includes identification information of the ECAF.

14. The method according to claim 13, characterized in that The method further comprises: The event user application function network element receives first confirmation information from the data collection application function network element, where the first confirmation information is used to indicate a request result of the third request information.

15. A data collection verification method, characterized in that: include: The data collection application function network element receives a third request message from the event user application function network element, wherein the third request message is used to request a fifth access layer data set of the terminal device; The data collection application function network element sends fourth information to the event user application function network element, where the fourth information is used to indicate that the second access layer data set needs to be authorized at the non-access layer of the terminal device, and the second access layer data set includes all or part of the data in the fifth access layer data set; The data collection application function network element receives a first request message from the event user application function network element. The first request The information is used to request authorization of the second access layer data set, and the first request information includes identification information of the ECAF; The data collection application function network element sends the first request information to the non-access layer of the terminal device.

16. The method according to claim 15, characterized in that The method further comprises: The data collection application function network element sends a first confirmation message to the event user application function network element, where the first confirmation message is used to indicate a request result of the third request information.

17. A communication device, characterized in that: include: A unit for implementing the method of any one of claims 1 to 4; or, a unit for implementing the method of any one of claims 5 to 7; or, a unit for implementing the method of any one of claims 8 to 10; or, a unit for implementing the method of claim 11 or 12; or, a unit for implementing the method of claim 13 or 14; or, a unit for implementing the method of claim 15 or 16.

18. A computer program product, characterized in that The computer program product comprises: a computer program code, when the computer program code is executed, causes the device to perform Execute the method according to any one of claims 1 to 4, or Execute the method according to any one of claims 5 to 7, or Execute the method according to any one of claims 8 to 10, or Execute the method of claim 11 or 12, or Execute the method of claim 13 or 14, or Execute the method of claim 15 or 16.

19. A computer-readable storage medium, characterized in that: The computer readable storage medium stores a computer program. When the computer program is executed, The device performs the method according to any one of claims 1 to 4, or The device performs the method according to any one of claims 5 to 7, or The device performs the method according to any one of claims 8 to 10, or The device performs the method according to claim 11 or 12, or causing the device to perform the method according to claim 13 or 14, or The device is caused to perform the method as claimed in claim 15 or 16.

20. A chip system, characterized in that: comprising: a processor for calling and running a computer program from a memory, Enable a communication device equipped with the chip system to perform the method according to any one of claims 1 to 4; or Enable a communication device equipped with the chip system to perform the method as claimed in any one of claims 5 to 7; or Enable a communication device equipped with the chip system to perform the method as claimed in any one of claims 8 to 10; or Enable a communication device equipped with the chip system to perform the method according to claim 11 or 12; or Enable a communication device equipped with the chip system to perform the method according to claim 13 or 14; or The communication device equipped with the chip system executes the method as claimed in claim 15 or 16.

21. A communication system, characterized in that: It includes a terminal device, a network device, a data collection application function network element and an event user application function network element, the terminal device is used to execute the method as claimed in claim 11 or 12, the network device is used to execute the method as claimed in any one of claims 1 to 4, the data collection application function network element is used to execute the method as claimed in any one of claims 5 to 7, or used to execute the method as claimed in claim 15 or 16, and the event user application function network element is used to execute the method as claimed in any one of claims 8 to 10, or used to execute the method as claimed in claim 13 or 14.

Images