Verification method and device for data collection

Abstract

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

Description

Technical Field

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

[0002] With the improvement of data storage and computing power, artificial intelligence (AI) technology has been increasingly used. AI technology can be applied to communication systems such as new radio (NR) systems to improve network performance and user experience by intelligently collecting and analyzing data.

[0003] 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), positioning accuracy enhancements, etc.

[0004] The AI ​​model needs to collect data from terminal devices. In the permission management process of the event consumer (Event Consumer) subscribing to the data collection application function (Data Collection AF, DCAF), the Authorization Application Server (AAS) is introduced. The token provided by AAS to the event consumer application function (ECAF) network element is verified to confirm whether DCAF can send data to the corresponding ECAF.

[0005] However, in the above AI application scenarios, the input of the AI ​​model is the access stratum (AS) data of the user equipment (UE). Since the AS layer data is usually collected by the operator and has 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. Summary of the invention

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

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

[0008] 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, 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, 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 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, the second information is used to indicate a verification result of the first key.

[0009] 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 over access layer data collection and avoiding direct exposure of access layer data to other network nodes in the non-access layer.

[0010] In combination with the first aspect, in certain 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.

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

[0012] 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 a request for some access layer data in a 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.

[0013] 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, 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.

[0014] 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 can also be executed by a chip or circuit configured in the data collection application function network element, and the present application does not limit this.

[0015] 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 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 the network device, and the second information is used to indicate a verification result of the first key.

[0016] 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 over access layer data collection and avoiding direct exposure of access layer data to other network nodes in the non-access layer.

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

[0018] In a possible implementation, 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.

[0019] 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 the present application does not limit this.

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

[0021] 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 over access layer data collection and avoiding direct exposure of access layer data to other network nodes in the non-access layer.

[0022] 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 the first identification information, and the first identification information includes the identification of the network device.

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

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

[0025] The method comprises: 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.

[0026] 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 the 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.

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

[0028] In the fifth 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 the present application does not limit this.

[0029] 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 the 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 the authorization of the second access layer data set, and the first request message includes the identification information of the ECAF.

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

[0031] 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 can also be executed by a chip or circuit configured in the data collection application function network element. This application does not limit this.

[0032] The method includes: the data collection application function network element receives third request information from the event user application function network element, the third request information is used to request the 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, 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 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 ECAF identification information; the data collection application function network element sends the first request information to the non-access layer of the terminal device.

[0033] In a possible implementation, 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.

[0034] 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 a non-access layer of an event user application function network element or a terminal device, the first request message is used to request authorization of a second access layer data set, 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, 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 receiving unit is also used to receive a first message 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, the second information is used to indicate a verification result of the first key.

[0035] In a possible implementation, the sending unit is further used to send 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.

[0036] In a 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.

[0037] 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, 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.

[0038] In an eighth aspect, a data collection verification device is provided, comprising: a receiving unit, for receiving first indication information from a network device, the first indication information being 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 receiving unit is also used to receive second request information from an event user application function network element, the second request information being used to request a third access layer data set of the terminal device, the second request information comprising first information, the first information being used to indicate a first key, and the first key being used for authorization of the third access layer data set; a sending unit, for sending the first information to the network device; the receiving unit is also used to receive second information from the network device, the second information being used to indicate a verification result of the first key.

[0039] In a possible implementation, the receiving unit is also used to receive a third request information from an event user application function network element, and the third request information is used to request a fifth access layer data set of a 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 an identification of the network device.

[0040] In a possible implementation manner, the sending unit is further used 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.

[0041] In the ninth aspect, a data collection verification device is provided, including: a sending unit, used to send 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, used to receive 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.

[0042] In a 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.

[0043] In a possible implementation, the receiving unit is further used 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.

[0044] 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 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; 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 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 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.

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

[0046] In the eleventh aspect, a data collection verification device is provided, including: a sending unit, used to send a third request message to a data collection application function network element, the third request message is used to request a fifth access layer data set of a 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 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 a fifth access layer data set; the sending unit is also used to send a first request message to the data collection application function network element, the first request message is used to request authorization of a second access layer data set, and the first request message includes ECAF identification information.

[0047] In a possible implementation, the receiving unit is further used 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.

[0048] 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 ECAF identification information; the sending unit is also used to send the first request information to the non-access layer of the terminal device.

[0049] In a possible implementation manner, the sending unit is further used 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.

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

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

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

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

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

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

[0056] In a nineteenth aspect, a communication device is provided, including a processor, the processor is coupled to a memory, and can be used to perform any one of the first to sixth aspects, and the method in any possible implementation of the above aspects. In a possible implementation, the communication device also includes a memory. In a possible implementation, the communication device also includes a communication interface, the processor is coupled to the communication interface. In a possible implementation, the communication device also includes a communication interface, the processor is coupled to the communication interface.

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

[0058] 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 a possible implementation, the transceiver may be a transceiver circuit. In a possible implementation, the input / output interface may be an input / output circuit.

[0059] 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 a possible implementation, the transceiver may be a transceiver circuit. In a possible implementation, the input / output interface may be an input / output circuit.

[0060] 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 a possible implementation, the transceiver may be a transceiver circuit. In a possible implementation, the input / output interface may be an input / output circuit.

[0061] 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 may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or the chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0062] In a twentieth aspect, a communication device is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive a signal through the input circuit and transmit a signal through the output circuit, so that any aspect of the first to sixth aspects, and any possible implementation of the above aspects are implemented.

[0063] In the specific implementation process, the above-mentioned communication device can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a trigger, and various logic circuits. The input signal received by the input circuit can be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter, and the input circuit and the output circuit can be different circuits or the same circuit. In this case, the circuit is used as an input circuit and an output circuit at different times. The embodiment of the present application does not limit the specific implementation method of the processor and various circuits.

[0064] In a twenty-first aspect, a processing device is provided, comprising a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute any one of the first to sixth aspects, and any possible implementation of the above aspects.

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

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

[0067] 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 respectively. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0068] It should be understood that the relevant data interaction process, such as sending indication information, can be a process of outputting indication information from a processor, and receiving capability information can be a process of receiving input capability information from a processor. Specifically, the processed output data can be output to a transmitter, and the input data received by the processor can come from a receiver. Among them, the transmitter and the receiver can be collectively referred to as a transceiver.

[0069] The processor in the above aspects can be a chip, which can be implemented by hardware or by 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 software codes stored in a memory. The memory can be integrated in the processor or can be located outside the processor and exist independently.

[0070] In the twenty-second aspect, a computer program product is provided, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables a computer to execute any one of the first to sixth aspects, as well as a method in any possible implementation of the above aspects.

[0071] 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 executed on a computer, enables the computer to execute any one of the first to sixth aspects above, as well as a method in any possible implementation of the above aspects.

[0072] 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 aspect of the above-mentioned first to sixth aspects and their possible implementation methods.

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

[0074] 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

[0075] Figure 1 This is a schematic diagram of an example of a communication system to which the present application is applicable.

[0076] Figure 2 It is a schematic diagram of the architecture of an access network device provided in an embodiment of the present application.

[0077] Figure 3 It is a schematic diagram of an AI application framework provided in an embodiment of the present application.

[0078] Figure 4 It is a schematic diagram of another AI application framework provided in an embodiment of the present application.

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

[0080] Figure 6 It is a schematic flow chart of a data collection verification method provided in an embodiment of the present application.

[0081] Figure 7 A schematic flowchart of another data collection verification method provided in an embodiment of the present application.

[0082] Figure 8 A schematic flowchart of another data collection verification method provided in an embodiment of the present application.

[0083] Fig. 9 A schematic block diagram of a communication device provided in an embodiment of the present application.

[0084] Fig.10 A schematic block diagram of a communication device provided in an embodiment of the present application.

[0085] Fig.11 A schematic block diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0086] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0087] 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), 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, the 5th Generation (5G) system, the 6th generation (6G) system or new wireless (NR) system or future wireless communication system.

[0088] Figure 1 1 is a schematic diagram of a communication system 100 provided in an embodiment of the present application. Figure 1As shown, 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.

[0089] The communication method provided in the embodiment of the present application may also involve Figure 1 The devices or transmission nodes not shown in the figure are not limited in the embodiments of the present application.

[0090] The above-mentioned communication system applied to the embodiment of the present application is only an example, and 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.

[0091] The terminal device in the embodiments of the present application may refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. 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 function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a future Public Land Mobile Network (PLMN), etc., and the embodiments of the present application are not limited to this.

[0092] Among them, wearable devices can also be called wearable smart devices, which are a general term for the intelligent design and development of wearable devices for daily wear using wearable technology, 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 clothes or accessories. Wearable devices are not only hardware devices, but also realize powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, 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.

[0093] In addition, the terminal device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part 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 and machines and things.

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

[0095] The 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, the network device may be a device deployed in a wireless network to provide wireless communication functions for terminal devices. For example, the network device may be a radio access network (RAN) node that connects the terminal device to the wireless network. Among them, the RAN may be connected to a core network (for example, a core network of long term evolution (LTE), a core network of 5G, etc.).

[0096] The network device in the embodiment 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 (evolved Node B, eNB) or base station equipment in the future evolved communication system, or a server, a wearable device, a vehicle-mounted device, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), etc., or one or a group of antenna panels (including multiple antenna panels) of a base station, or 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 micro-micro base station, a small station, a relay station or a balloon station, etc.

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

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

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

[0100] Figure 2 Schematic diagram of the architecture of an access network device provided in an embodiment of the present application. Figure 2 As shown, the network device involved in the embodiment of the present application can be a centralized unit (CU) and a distributed unit (DU) separation architecture. CU and DU can be understood as the division of network devices from the perspective of logical functions. CU and DU can be physically separated or deployed together. Multiple DUs can share one CU. One DU can also be connected to multiple CUs ( Figure 2 CU and DU may be connected via an interface, such as an F1 interface. CU and DU may be divided according to the protocol layer of the wireless network. One possible division method is that 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 DU is used to perform the functions of the radio link control (RLC) layer, the media access control (MAC) layer, the physical layer, etc.

[0101] It is understandable 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 part of the processing functions of the protocol layer of the above division method.

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

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

[0104] In another design, the CU may also have one or more functions of the core network. One or more CUs may be centrally set or separately set. For example, the CU may be set on the network side for centralized management. The DU may have multiple radio frequency functions or the radio frequency functions may be remotely set.

[0105] The functions of CU can be implemented by one entity or by different entities. For example, the functions of CU can be further divided, for example, the control plane (CP) and the user plane (UP) are separated, that is, the control plane (CU-CP) of CU and the user plane (CU-UP) of CU. The control plane CU-CP of CU also includes a further divided architecture, that is, the CU-CP is further divided into CU-CP1 and CU-CP2. Among them, CU-CP1 includes various radio resource management functions, and CU-CP2 only includes RRC functions and PDCP-C functions (that is, the basic functions of control plane signaling at the PDCP layer).

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

[0107] The AI ​​module is a module with machine learning computing capabilities. Figure 2As shown, in a wireless communication system, the AI ​​module can be located in operations, administration and maintenance (OAM), in a gNB (for example, if the gNB is a separated architecture, it can be located in the CU / DU), in a terminal device, or as a separate network element entity RAN Intelligent Control Module (RAN Intelligent Controller, RIC). The main function of the AI ​​module in the wireless communication system is to perform a series of AI calculations such as model establishment, training approximation, and reinforcement learning based on input data (in a wireless communication system, input data generally refers to network operation data provided by access network equipment or monitored by OAM, such as network load, channel quality, etc., or user plane data transmission provided by the core network). The trained model provided by the AI ​​module has the function of predicting changes in the RAN side network, and can be used for load prediction, terminal device path prediction, CSI prediction, optimal beam prediction, positioning prediction, etc. In addition, the AI ​​module can also perform policy reasoning from the perspectives of network energy saving and mobility optimization based on the prediction results of the trained model on the RAN network performance, so as to obtain reasonable and efficient energy saving strategies, mobility optimization strategies, etc. When the AI ​​model is located in the CU and the CP and UP of the CU are separated, the CP can be responsible for receiving the AI ​​model and the 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 the subsequent AI model reasoning functions, and generating specific interactive signaling, which will be sent by CU-CP2. When the AI ​​module is located in 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, the current F1, Xn, Uu and other interfaces can be reused; when the AI ​​module becomes an independent network entity, it is necessary to re-establish the communication link to the OAM and RAN side, such as based on a wired link or a wireless link.

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

[0109] Among them, the model training module and the model reasoning module are examples of AI modules. For example, Figure 1 The network devices and terminal devices shown in the figure are Figure 2The CU, DU or other management entities of the gNB shown can input data into the data acquisition module, and the data acquisition module can be used as a database for AI model training and data analysis and reasoning. The model training module analyzes the training data output by the data acquisition module, and gives an available AI model, and deploys the obtained AI model to the model reasoning module. Based on the reasoning data output by the data acquisition module, the model reasoning module gives a reasonable prediction of the network operation based on the AI ​​model (trained by the model training module), and feeds back the performance data of the AI ​​model to the model training module. The subsequent model training module continues to train the model according to the feedback performance data, and informs the model reasoning module of the updated AI model; or, the model reasoning module guides the network to make policy adjustments based on the reasoning data and AI model output by the data acquisition module. The relevant policy adjustments are uniformly planned by the execution entity and sent to multiple network entities for operation. At the same time, the specific performance of the network after the application of the relevant policies will be fed back to the data acquisition module for storage.

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

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

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

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

[0114] The 3rd Generation Partnership Project (3GPP) has introduced multiple AI application scenarios on the RAN side. The applications of AI on the RAN side include but are not limited to the following application scenarios: energy saving, load balancing, mobility optimization, channel state information-reference signal (CSI-RS) feedback enhancement, beam management enhancement (BME), and positioning enhancement. These application scenarios can also be called AI use cases.

[0115] For example, AI can be used for CSI feedback enhancement. CSI is the channel attribute of the communication link. The UE reports the downlink channel quality information to the gNB so that the base station can 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 based on AI, CSI compression and CSI prediction (low priority), were adopted. CSI compression is based on a bilateral model (there is 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 through AI models such as Convolutional Neural Network (CNN) and AI models (Transformer) that use attention mechanisms to increase the speed of model training).

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

[0117] Exemplarily, AI can also be used for positioning accuracy enhancements. LOS / NLOS indication reporting is already supported in R17, 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 means cannot work well. Therefore, AI-based positioning can improve positioning accuracy in indoor scenarios.

[0118] The input of the AI ​​model in the above AI application scenarios is access layer data. For example, the input of the model in the CSI compression scenario is the CSI-RS measurement result, which involves access layer CSI reporting. When collecting UE data, permission management is required.

[0119] However, in the above AI application scenarios, the input of the AI ​​model is the AS data of the UE. Since the AS layer data is usually collected by the operator and has 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.

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

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

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

[0123] The ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority or importance of multiple objects. For example, the first indication information and the second indication information can be the same information or different information, and such a name does not indicate the difference 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 the present application is only for distinguishing different steps, and is not used to limit the order of the steps.

[0124] In the present 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 comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products or apparatuses.

[0125] The technical solution provided in the embodiment of the present application can be applied to wireless communication between communication devices. Wireless communication between communication devices may include: wireless communication between network devices and terminals, wireless communication between network devices and network devices, and wireless communication between terminals. In the embodiment of the present application, the term "wireless communication" may also be referred to as "communication", and the term "communication" may also be described as "data transmission", "information transmission" or "transmission".

[0126] 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 to limit the names of various nodes and messages. On the contrary, any name that has the same or similar function as the node or message used in this application is regarded as the method of this application or an equivalent replacement, and is within the scope of protection of this application, and will not be repeated below.

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

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

[0129] Figure 6 A data collection verification method 600 provided by the present application is shown, through which the authority management of collecting AS data of UE is performed. Figure 6 The method includes at least part of the following contents.

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

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

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

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

[0134] S650, DCAF obtains access layer data.

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

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

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

[0138] S690, the network device and DCAF verify the first key.

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

[0140] Through the above solution, ECAF needs to be authorized by the operator's equipment before it can obtain the collected AS measurement data from DCAF, ensuring the operator's authority management over AS data collection and avoiding direct exposure of AS data to other network nodes in the non-AS layer.

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

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

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

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

[0145] 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 sends it to the corresponding subscribers (or event users).

[0146] In one implementation, the collected data information may include one or more of the following: artificial intelligence AI function information indicating 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 region, cell, cell configuration, etc., and information on the maximum number of beams reported (for example, indicating measurement results of 4 / 6 / several Beams).

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

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

[0149] 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 (ie, measurement and reporting configuration information of access layer data).

[0150] After receiving the measurement and reporting configuration information of the access layer data, the network device determines whether the Event related to the AS data needs to be granted permission before it can be provided to other ECAFs based on the Event information in the measurement and reporting configuration information.

[0151] The operator equipment 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 needs to be authorized before being provided to other network elements.

[0152] Method 1

[0153] Instructions are given according to different Events.

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

[0155] 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 each Event ID needs to obtain authorization.

[0156] Method 2

[0157] Overall instructions

[0158] That is, the network device sends the first indication information 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 all access layer data corresponding to events containing AS data.

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

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

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

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

[0163] 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.).

[0164] It should be understood that in this third request information, ECAF can further send subscription information related to the model to DCAF to request the measurement results required for the local training model of the event user application function network element. For example, it can indicate that there is a model to be trained locally, and include the functional information corresponding to the training model (such as the measurement information corresponding to the CSI compression function).

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

[0166] 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 the partial data is the second access layer data set.

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

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

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

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

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

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

[0173] In step S640, 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.

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

[0175] 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 duration or deadline for Event data, purpose / scope of Event data collection (such as PLMN, NID / PNI-NPN, etc.), etc.

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

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

[0178] 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 period corresponding to the first key, and 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, and distinguish the first keys to indicate the above information.

[0179] 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 some access layer data in the second access layer data set are 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.

[0180] In 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 first information, where the first information is used to indicate a first key.

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

[0182] In S690, the network device and the DCAF verify the first key.

[0183] 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 (i.e., an example of the second information, the second information is used to indicate the verification result of the first key).

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

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

[0186] Figure 7 A communication method 700 provided by the present application is shown, through which the authority management of collecting AS data of UE is performed. Figure 7 The method includes at least part of the following contents.

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

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

[0189] S730, the network device sends second indication information to the AS layer of the UE.

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

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

[0192] S760, DCAF obtains access layer data.

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

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

[0195] 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;.

[0196] S791, the network device and DCAF verify the first key.

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

[0198] Through the above solution, the network device can configure additional measurements for the UE's AS layer according to the data collection request from the non-AS layer sent by the UE's AS layer, thereby expanding the scope of data collection. In addition, the network device and the UE's AS layer interact with each other through authorization information, ensuring that the UE's AS data exposure scope is controllable.

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

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

[0201] 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 layer data in the fourth access layer data set can be sent to the non-access layer of the UE.

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

[0203] Specifically, the non-AS layer of the UE sends an AS data collection request to the AS layer of the UE, so that the AS layer can send access layer data to the non-AS layer. The AS layer of the UE performs measurements, which have no strict order relationship with the remaining steps, that is, the measurements performed by the UE are performed independently and are not affected by the data collection request received by the non-AS layer of the UE.

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

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

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

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

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

[0209] Figure 8 A data collection method 800 provided by the present application is shown, through which the authority management of collecting AS data of UE is performed. Figure 8 The method includes at least part of the following contents.

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

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

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

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

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

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

[0216] S870, the non-AS layer of the UE sends first request information to the network device.

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

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

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

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

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

[0222] Through the above solution, the authorization application of ECAF is forwarded to the operator equipment via the non-AS layer of the UE, 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.

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

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

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

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

[0227] In 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.

[0228] 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 duration or deadline for Event data, purpose / scope of Event data collection (such as PLMN, NID / PNI-NPN, etc.), etc.

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

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

[0231] 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 sends second indication information to the AS layer of the UE, 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 UE. For details, please refer to step S730.

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

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

[0234] 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 period corresponding to the first key, and 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, and distinguish the first keys to indicate the above information.

[0235] In one implementation, for data that cannot be authorized in the second access layer data set, a third indication information may 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.

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

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

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

[0239] 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 (i.e., an example of the second information, the second information is used to indicate the verification result of the first key).

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

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

[0242] Optionally, the non-AS layer of the UE sends authorization result information to the DCAF, 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. For example, which data in the second access layer data set is successfully authorized to the network device through the non-AS layer, specifically, it can indicate which ECAF, which Event, or which measurement requirements are authorized, and the reason why the authorization is not provided.

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

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

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

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

[0247] Fig. 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, and the processing unit 920 is used for data processing. The transceiver unit 910 can also be called a communication interface or a communication unit.

[0248] In a possible implementation, the device 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.

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

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

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

[0252] 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 (e.g., 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 may 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, and to avoid repetition, it will not be repeated here.

[0253] The device 900 of each of the above schemes has the function of implementing the corresponding steps performed by the network device, terminal device or application layer network element in the above method. The function can be implemented by hardware, or by hardware executing the corresponding software. The hardware or software includes one or more modules corresponding to the above 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.

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

[0255] It should be pointed out that Fig. 9 The device in the embodiment may be a network element or device in the foregoing embodiment, or may be a chip or a 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 or a microprocessor or an integrated circuit integrated on the chip. This is not limited here.

[0256] like Fig.10 As shown, the embodiment of the present application further provides a communication device 1000. The communication device 1000 includes a processor 1010, the processor 1010 is coupled to a memory 1020, the memory 1020 is used to store computer programs or instructions or and / or data, and 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.

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

[0258] In one possible implementation, Figure 8 As shown, the communication device 1000 may further include a memory 1020 .

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

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

[0261] In one possible implementation, Figure 8As shown, the wireless communication device 1000 may further include a transceiver 1030, and the transceiver 1030 is used for receiving and / or sending signals. For example, the processor 1010 is used to control the transceiver 1030 to receive and / or send signals.

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

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

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

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

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

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

[0268] like Fig.11 The 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.

[0269] Among them, the logic circuit 1110 can be a processing circuit in the chip system 1100. The logic circuit 1110 can be coupled to the storage unit and call the instructions in the storage unit so that the chip system 1100 can implement the methods and functions of each embodiment of the present application. The input / output interface 1120 can be an input / output circuit in the chip system 1100, outputting information processed by the chip system 1100, or inputting data or signaling information to be processed into the chip system 1100 for processing.

[0270] 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 method embodiments.

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

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

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

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

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

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

[0277] In an embodiment of the present application, a terminal device or a 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. Among them, the hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also called 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 Linux operating system, Unix operating system, Android operating system, iOS operating system, or Windows operating system. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0278] The embodiments of the present application do not specifically limit the specific structure of the execution subject of the method provided in the embodiments of the present application, as long as it is possible to communicate 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. 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 the satellite that can call and execute the program.

[0279] Various aspects or features of the embodiments of the present application may be implemented as methods, devices, or products using standard programming and / or engineering techniques. The term "product" as used herein may cover a computer program accessible from any computer-readable device, carrier, or medium. For example, a computer-readable medium may include, but is not limited to: a magnetic storage device (e.g., a hard disk, a floppy disk, or a magnetic tape, etc.), an optical disk (e.g., a compact disc (CD), a digital versatile disc (DVD), etc.), a smart card, and a flash memory device (e.g., an erasable programmable read-only memory (EPROM), a card, a stick, or a key drive, etc.).

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

[0281] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or 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. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0282] 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).

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

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

[0285] Those of ordinary skill 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 the present application.

[0286] Those skilled in the art can 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.

[0287] 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 only 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.

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

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

[0290] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially 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, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.

[0291] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope 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, where the first request message is used to request authorization of a second access layer data set of the terminal device; 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, 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; 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