Communication method and apparatus

Abstract

Embodiments of the present application provide a communication method and device, relating to the field of communication, to improve the security of the process of the AF obtaining data of the terminal device. In the method, a first network element can receive a first request message from a first application function for requesting to obtain data associated with a terminal device, the first request message comprising a first identifier, which can be used to indicate a first chip manufacturer and / or a first terminal manufacturer associated with the data. In the case where the first application function belongs to a data consumer list allowed by the first chip manufacturer and / or the first terminal manufacturer, the first network element further exposes first data of a first terminal device associated with the first identifier to the first application function through a first response message. In this way, the application function (such as the first application function) can be prevented from obtaining data of the terminal device without authorization, so as to avoid the data of the terminal device being leaked, thereby improving the security of the process of the application function (such as the first application function) obtaining data of the terminal device.

Description

Technical Field

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

[0002] When training the terminal device-side model, it is necessary to collect (measurement) data from the terminal device. Currently, the main body for training the terminal device-side model may be a third-party application function (AF). In this case, the AF can obtain data from the terminal device through the core network (CN) or other devices, such as operation administration and maintenance (OAM), for subsequent training of the terminal device-side model.

[0003] However, based on the existing implementation, there are risks in the process of AF acquiring data from terminal devices. How to improve the security of the AF acquisition process of terminal devices is an urgent problem to be solved. Summary of the Invention

[0004] This application provides a communication method and apparatus to improve the security of the process by which an AF acquires data from a terminal device.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] In a first aspect, a communication method is provided. This method can be executed by a first network element, by a module applied to the first network element (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the first network element. The method includes: receiving a first request message from a first application function, and, if the first application function belongs to a data consumer list permitted by a first chip manufacturer and / or a first terminal manufacturer, sending a first response message to the first application function. The first request message requests data associated with a terminal device, and includes a first identifier indicating the first chip manufacturer and / or the first terminal manufacturer associated with the data; the first response message includes first data associated with the first terminal device, and the first terminal device is associated with the first identifier.

[0007] As described in the first aspect, the first network element can receive a first request message from a first application function requesting data associated with a terminal device. This first request message includes a first identifier, which can be used to indicate the first chip manufacturer and / or the first terminal manufacturer associated with the data. If the first application function belongs to the data consumer list permitted by the first chip manufacturer and / or the first terminal manufacturer (i.e., the first application function is authorized), meaning the first application function has the permission to obtain the requested data, the first network element can further expose the first data of the first terminal device associated with the first identifier to the first application function through a first response message. This prevents unauthorized application functions from obtaining terminal data, thus avoiding data leakage from the terminal device and improving the security of the process by which an application function (such as the first application function) obtains data (such as measurement data) from the terminal device.

[0008] In one possible implementation, the first identifier includes at least one of the following: an identifier of a first chip manufacturer, an identifier of a first terminal manufacturer, an identifier of a first chip, a first type allocation code, or an identifier of a terminal device. Wherein, the first chip is the chip of the terminal device, and the first type allocation code is the type allocation code of the terminal device. That is, the first identifier can be represented by different granularities to meet the needs of different scenarios.

[0009] In one possible implementation, the first request message further includes at least one of the following: an identifier of a first application function, a data type, or a first condition. The first condition is used to determine the first terminal device. For example, when the first request message includes an identifier of a first application function, the first network element can directly determine that the first request message originates from the first application function based on the identifier, for use in subsequently providing the requested data (such as first data) of the terminal device to the first application function; when the first request message includes a data type, the first network element can directly determine the data type requested by the first application function based on the data type, for use in subsequently providing data (such as first data) that satisfies the data type requested by the first application function; when the first request message includes a first condition, the first network element or (hereinafter) the second network element can determine the first terminal device that satisfies the first condition, for use in the first network element subsequently providing the first data of the first terminal device to the first application function.

[0010] In one possible implementation, the terminal device corresponds to at least one type allocation code. The first condition indicates at least one of the following: the number of at least one type allocation codes, the number of terminal devices for each type allocation code, or information about the region to which the terminal device belongs. The first terminal device is located within the region to which it belongs. That is, the first condition can be used to filter the first terminal device to ensure that the first network element can open the first data of the first terminal device that meets the first condition to the first application function, so that the first application function can obtain the required first data for performing subsequent steps, such as training the model on the first terminal device side, etc., without limitation.

[0011] The embodiments of this application are described below through various possible implementations when the first network element stores a list of data consumers allowed by at least one chip manufacturer (including the first chip manufacturer) and / or at least one terminal manufacturer (including the first terminal manufacturer), and stores a PEI of at least one terminal device (including the first terminal device).

[0012] In one possible implementation, the method described in the first aspect further includes: obtaining a list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer according to the first request message, and determining that the first application function has the permission to obtain data if it belongs to the list of permitted data consumers. Specifically, the first network element can determine the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer from the list of data consumers permitted by at least one chip manufacturer and / or at least one terminal manufacturer according to the first identifier in the first request message. The first network element can verify or determine whether the first application function belongs to the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer to determine whether the first application function has the permission to obtain the data, thereby improving the security of the process by which the first application function obtains data from the terminal device (such as the first data of the first terminal device); at the same time, the first network element can directly verify whether the first application function has the permission to obtain the data without querying other network elements (such as the second network element) or devices, thereby reducing the signaling interaction of the first network element and reducing resource overhead.

[0013] In one possible implementation, the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer is pre-configured or predefined, simplifying implementation. Alternatively, the method described in the first aspect further includes: receiving the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer. For example, at least one chip manufacturer and / or at least one terminal manufacturer, or a network element or device storing the list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer, can dynamically send the list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer to the first network element in real time. This list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer may include the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer, providing flexibility. It is understood that the first network element can also obtain the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer through any other possible means, and this application embodiment does not limit this.

[0014] In one possible implementation, the method in the first aspect further includes: obtaining first information based on the PEI of at least one terminal device, and determining a first terminal device based on the PEI of at least one terminal device, the first information, and a first request message. The first information indicates at least one of the following: information about the chip manufacturer of each of the at least one terminal device, information about the terminal manufacturer of each of the at least one terminal device, or information about the chip of each of the at least one terminal device; the at least one terminal device includes the first terminal device, and the first terminal device satisfies at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device, the first terminal manufacturer includes the terminal manufacturer of the first terminal device, or the first chip includes the chip of the first terminal device. In this case, the first network element can determine the first information based on the PEI of at least one terminal device, and filter out the first terminal device from the at least one terminal device based on the PEI of at least one terminal device, the first information, and the first request message, so that the first data of the first terminal device is the data requested by the first application function; furthermore, the first network element can determine the first terminal device itself without querying other network elements (such as a second network element) or devices, thereby reducing signaling interaction of the first network element and reducing resource overhead.

[0015] In one possible implementation, the identifier of the terminal device is the Universal Public User Identifier (GPSI) of the terminal device. The method described in the first aspect further includes: determining the Subscription Permanent Identifier (SUPI) corresponding to the GPSI based on the GPSI of the terminal device, and determining the first type allocation code corresponding to the SUPI based on the SUPI; and determining the first chip manufacturer and / or the first terminal manufacturer based on the first type allocation code. That is, when the first identifier includes the GPSI of the terminal device, the first network element can first determine the SUPI corresponding to the GPSI based on the correspondence between GPSI and SUPI, and determine the PEI corresponding to the SUPI based on the SUPI. The first network element can determine the first type allocation code corresponding to the PEI based on the PEI corresponding to the SUPI, and determine the first chip manufacturer and / or the first terminal manufacturer associated with the first type allocation code based on the first type allocation code, so as to use the first network element to subsequently determine the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer from the list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer, and to verify the permission for the first application function (data acquisition).

[0016] The embodiments of this application are described below through various possible implementations when the second network element stores a list of data consumers allowed by at least one chip manufacturer (including the first chip manufacturer) and / or at least one terminal manufacturer (including the first terminal manufacturer), and stores a PEI of at least one terminal device (including the first terminal device).

[0017] In one possible implementation, the method in the first aspect further includes: sending a second request message to a second network element based on a first request message, and receiving a second response message from the second network element; determining the first terminal device based on the SUPI of the first terminal device. The second request message is used to request the acquisition of a terminal device associated with a first identifier, and the second request message includes the first identifier; the second response message includes the SUPI of the first terminal device. That is, the first network element can send a second request message to the second network element to query the second network element for a terminal device associated with the first identifier. The second network element can then send the SUPI of the first terminal device associated with the first identifier obtained from the query to the first network element via a second response message, so that the first network element can determine the first terminal device. In this case, the first network element does not need to determine the first terminal device itself, thereby reducing the capability requirements of the first network element.

[0018] In one possible implementation, the second request message further includes a first condition and information about the service area of ​​the first network element, wherein the first terminal device is within the service area of ​​the first network element. That is, the first network element can send the first condition and information about its service area to the second network element, so that the second network element can select a first terminal device that meets the first condition and is within its service area, so that the first data from the first terminal device can meet the requirements of the first application function.

[0019] In one possible implementation, the second network element can be any of the following: a unified data management network element, a unified data storage network element, or an access and mobility management network element, or any other possible network element, to meet the needs of different scenarios, without limitation.

[0020] Based on the above description, in one possible implementation, the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer includes at least one of the following: an identifier for an application function, an identifier for the application function of the chip manufacturer, an identifier for the chip manufacturer, an identifier for the application function of the terminal manufacturer, or an identifier for the terminal manufacturer. Wherein, the application function includes the first application function, the chip manufacturer includes the first chip manufacturer, and the terminal manufacturer includes the first terminal manufacturer. That is, the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer can be represented at different granularities to meet the needs of different scenarios.

[0021] In one possible implementation, the method in the first aspect further includes: collecting first data from the first terminal device. Sending a first response message to a first application function includes: sending the first response message to the first application function based on the first data. The first response message further includes a type allocation code of the first terminal device and / or an identifier of the chip of the first terminal device. That is, the first network element can collect the first data from the first terminal device and de-identify or anonymize the first data, such as converting the SUPI of the first terminal device into an identifier that the first application function can recognize, such as the type allocation code of the first terminal device and / or the identifier of the chip of the first terminal device, so that the first application function can determine the type allocation code and / or chip corresponding to the first data.

[0022] In one possible implementation, the first network element can be any of the following: a network open function network element, a network data analysis function network element, or a data collection and coordination function network element, or any other possible network element, to meet the needs of different scenarios, without limitation.

[0023] Secondly, a communication method is provided. This method can be executed by a second network element, by a module applied to the second network element (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the second network element. The method includes: receiving a second request message from a first network element, and sending a second response message to the first network element according to the second request message. The second request message is used to request access to a terminal device associated with a first identifier. The second request message includes the first identifier, which indicates a first chip manufacturer and / or a first terminal manufacturer associated with the data. The first identifier originates from a first application function. The second response message includes a permanent subscription identifier (SUPI) of the first terminal device, the first terminal device is associated with the first identifier, and the first application function belongs to the data consumer list allowed by the first chip manufacturer and / or the first terminal manufacturer.

[0024] In one possible implementation, the first identifier includes at least one of the following: an identifier of a first chip manufacturer, an identifier of a first terminal manufacturer, an identifier of a first chip, a first type allocation code, or an identifier of a terminal device. Wherein, the first chip is the chip of the terminal device, and the first type allocation code is the type allocation code of the terminal device.

[0025] In one possible implementation, the method in the second aspect further includes: obtaining a list of allowed data consumers based on the second request message, and determining that the first application function has permission to access data if it belongs to the list of allowed data consumers of the first chip manufacturer and / or the first terminal manufacturer. That is, the second network element can determine the list of allowed data consumers of the first chip manufacturer and / or the first terminal manufacturer based on the first identifier in the second request message, according to a stored list of allowed data consumers of at least one chip manufacturer (including the first chip manufacturer) and / or at least one terminal manufacturer (including the first terminal manufacturer). The first network element can verify or determine whether the first application function belongs to the list of allowed data consumers of the first chip manufacturer and / or the first terminal manufacturer to determine whether the first application function has permission to access the data. If it is determined that the first application function has permission to access the data, the second network element can then perform subsequent steps, such as identifying the first terminal device and sending a second response message to the first network element, thereby improving the security of the process by which the first application function accesses data from the terminal device.

[0026] In one possible implementation, the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer is pre-configured or predefined, simplifying implementation. Alternatively, the method described in the second aspect further includes: receiving a list of allowed data consumers, for example, from at least one chip manufacturer and / or at least one terminal manufacturer, or a network element or device storing a list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer, which can dynamically send the list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer to a second network element in real time. This list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer may include the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer, providing flexibility. It is understood that the second network element can also obtain the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer through any other possible means, and this application embodiment does not limit this.

[0027] In one possible implementation, the method in the second aspect further includes: obtaining second information based on the Permanent Device Identifier (PEI) of at least one terminal device, and determining a first terminal device based on the PEI of the at least one terminal device, the second information, and a second request message. The second information indicates at least one of the following: information about the chip manufacturer of each of the at least one terminal device, information about the terminal manufacturer of each of the at least one terminal device, or information about the chip of each of the at least one terminal device; the at least one terminal device includes the first terminal device, and the first terminal device satisfies at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device, the first terminal manufacturer includes the terminal manufacturer of the first terminal device, or the first chip includes the chip of the first terminal device. In this case, the first network element can determine the second information based on the PEI of the at least one terminal device, and filter out the first terminal device from the at least one terminal device based on the PEI of the at least one terminal device, the second information, and the second request message, so that the first data of the first terminal device is the data requested by the first application function.

[0028] In one possible implementation, the second request message further includes a first condition and information about the service area of ​​the first network element. The first condition is used to determine the first terminal device, which is located within the service area of ​​the first network element.

[0029] In one possible implementation, the terminal device corresponds to at least one type allocation code, and the first condition indicates any of the following: the number of at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs. Wherein, the first terminal device is located within the region to which the terminal device belongs.

[0030] In one possible implementation, the identifier of the terminal device is the Universal Public User Identifier (GPSI) of the terminal device. The method described in the second aspect further includes: determining the SUPI corresponding to the GPSI based on the GPSI of the terminal device, and determining the first type allocation code corresponding to the SUPI based on the SUPI; and determining the first chip manufacturer and / or the first terminal manufacturer based on the first type allocation code. That is, when the first identifier includes the GPSI of the terminal device, the second network element can first determine the SUPI corresponding to the GPSI based on the correspondence between GPSI and SUPI, and determine the PEI corresponding to the SUPI based on the SUPI. The second network element can determine the first type allocation code corresponding to the PEI based on the PEI corresponding to the SUPI, and determine the first chip manufacturer and / or the first terminal manufacturer associated with the first type allocation code based on the first type allocation code, so as to use the second network element to subsequently determine the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer from the list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer, and to verify the permission of the first application function (data acquisition).

[0031] In one possible implementation, the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer includes at least one of the following: an identifier of an application function, an identifier of an application function of the chip manufacturer, an identifier of the chip manufacturer, an identifier of an application function of the terminal manufacturer, or an identifier of the terminal manufacturer. Wherein, the application function includes the first application function, the chip manufacturer includes the first chip manufacturer, and the terminal manufacturer includes the first terminal manufacturer.

[0032] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection coordination function network element; the second network element is any one of the following: a unified data management network element, a unified data storage network element, or an access and mobility management network element.

[0033] Furthermore, the technical effects of the method described in the second aspect can be referred to the technical effects of the method described in the first aspect above, and will not be repeated here.

[0034] Thirdly, a communication method is provided. This method can be executed by a first application function, by a module applied to the first application function (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the first application function. The method includes: sending a first request message to a first network element and receiving a first response message from the first network element. The first request message requests data associated with a terminal device and includes a first identifier indicating a first chip manufacturer and / or a first terminal manufacturer associated with the data. The first response message includes first data associated with the first terminal device, and the first terminal device is associated with the first identifier.

[0035] In one possible implementation, the first identifier includes at least one of the following: an identifier of a first chip manufacturer, an identifier of a first terminal manufacturer, an identifier of a first chip, a first type allocation code, or an identifier of a terminal device. Wherein, the first chip is the chip of the terminal device, and the first type allocation code is the type allocation code of the terminal device.

[0036] In one possible implementation, the first request message further includes at least one of the following: an identifier of a first application function, a data type, or a first condition. The first condition is used to identify the first terminal device.

[0037] In one possible implementation, the terminal device corresponds to at least one type allocation code, and the first condition indicates at least one of the following: the number of at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs. Wherein, the first terminal device is located within the region to which the terminal device belongs.

[0038] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection and coordination function network element.

[0039] Furthermore, the technical effects of the method described in the third aspect can be referred to the technical effects of the method described in the first aspect above, and will not be repeated here.

[0040] Fourthly, a communication method is provided. This method can be executed by a first network element, by a module applied to the first network element (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the first network element. The method includes: receiving a first request message from a first application function, and sending a second request message to a second network element based on the first request message; receiving a second response message from the second network element, and sending a first response message to the first application function based on the SUPI of a first terminal device. The first request message requests data associated with the terminal device and includes a first identifier indicating the identifier of a first chip associated with the data, or a first type allocation code, wherein the first chip is associated with the first type allocation code; the second request message requests the terminal device associated with the first identifier and includes information about the first identifier and the service area of ​​the first network element; the second response message includes the subscription permanent identifier (SUPI) of the first terminal device, the first type allocation code includes the type allocation code of the first terminal device, and the first terminal device is located within the service area of ​​the first network element; the first response message includes first data provided by the first terminal device.

[0041] Based on the method described in the fourth aspect, the first network element can receive a first request message from a first application function requesting data associated with a terminal device. The first request message includes an identifier for indicating a first chip associated with the data, or a first identifier for a first type allocation code. The first network element can send a second request message to a second network element based on the first request message. This second request message can include the first identifier and information about the service area of ​​the first network element, allowing the second network element to query a terminal device associated with the first identifier and located within the service area of ​​the first network element. The first network element receives a second response message from the second network element including the SUPI of the first terminal device. Based on the SUPI of the first terminal device, the first network element can open or provide the first data of the first terminal device to the first application function. This ensures that the first type allocation code includes the type allocation code of the first terminal device, and that the first terminal device is located within the service area of ​​the first network element. This guarantees that the first terminal device can provide the data required by the first application function (such as the first data), and that the first network element can collect the first data of the first terminal device, thereby meeting the needs of the first application function and improving the efficiency of the first application function in obtaining data from the terminal device.

[0042] In one possible implementation, the first request message further includes an identifier of a first application function and / or a first condition, wherein the first condition is used to determine the first terminal device. For example, when the first request message includes an identifier of a first application function, the first network element can directly determine that the first request message originates from the first application function based on the identifier, for use in subsequently opening the requested data of the terminal device (as described below, the first data) to the first application function; when the first request message includes the first condition, it can be used by the second network element to subsequently determine a terminal device that meets the first condition, for use by the first network element to subsequently open the first data of the first terminal device to the first application function.

[0043] In one possible implementation, the first type allocation code includes at least one type allocation code, and the first condition indicates at least one of the following: the number of first type allocation codes, the number of terminal devices for each type allocation code in the first type allocation codes, or information about the region to which the terminal devices belong. Wherein, the first terminal device is located within the region to which the terminal devices belong.

[0044] In one possible implementation, the second request message further includes an identifier of the first application function and / or a first condition. For example, when the second request message includes an identifier of the first application function, the second network element can directly determine that the first identifier originates from the first application function, or in other words, the terminal device associated with the first identifier queried by the first network element is associated with the first application function, for use by the second network element to subsequently verify the permissions of the first application function (data acquisition); when the second request message includes a first condition, it can be used by the second network element to subsequently determine a first terminal device that meets the first condition, for use by the first network element to subsequently open the first data of the first terminal device to the first application function.

[0045] In one possible implementation, the method in the fourth aspect further includes: acquiring first information, and determining, based on the first information, that the first chip belongs to a chip list, and / or the first type allocation code belongs to a type allocation code list. The first information is used to indicate the chip list and / or type allocation code list supported by the first application function. That is, the first network element stores the chip list and / or type allocation code list supported by the first application function, and the first network element can verify whether the first application function has permission to obtain data based on the chip list and / or type allocation code list supported by the first application function. If the first chip belongs to the chip list supported by the first application function, and / or the first type allocation code belongs to the type allocation code list supported by the first application function, then subsequent steps are performed, such as determining the first terminal device and opening the first data of the first terminal device to the first application function through the first response message. In this way, unauthorized application functions can be prevented from obtaining terminal data, thereby preventing the leakage of terminal device data and improving the security of the process by which application functions (such as the first application function) obtain terminal device data (such as measurement data). In addition, the first network element can directly verify whether the first application function has the right to obtain the data without querying other network elements (such as the second network element) or devices, thereby reducing the signaling interaction of the first network element and reducing resource overhead.

[0046] In one possible implementation, sending a first response message to a first application function based on the SUPI of the first terminal device includes: collecting first data based on the SUPI of the first terminal device, and sending the first response message to the first application function based on the first data. The first response message further includes the type allocation code of the first terminal device and / or the identifier of the chip of the first terminal device. That is, the first network element collects the first data of the first terminal device based on the SUPI of the first terminal device, and de-identifies or anonymizes the first data, such as converting the SUPI of the first terminal device into an identifier that the first application function can recognize, such as the type allocation code of the first terminal device and / or the identifier of the chip of the first terminal device, so that the first application function can determine the type allocation code and / or chip corresponding to the first data.

[0047] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection coordination function network element, or any other possible network element, to meet the needs of different scenarios without limitation; the second network element is any one of the following: a unified data management network element, a unified data storage network element, or an access and mobility management network element, or any other possible network element, to meet the needs of different scenarios without limitation.

[0048] Furthermore, the technical effects of the method described in the fourth aspect can be referred to the technical effects of the method described in the first aspect above, and will not be repeated here.

[0049] Fifthly, a communication method is provided. This method can be executed by a second network element, by a module applied to the second network element (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the second network element. The method includes: receiving a second request message from a first network element, and sending a second response message to the first network element according to the second request message. The second request message is used to request access to a terminal device associated with a first identifier. The second request message includes the first identifier and information about the service area of ​​the first network element. The first identifier indicates the identifier of a first chip or a first type allocation code, and the first chip is associated with the first type allocation code. The second response message includes a permanent subscription identifier (SUPI) of the first terminal device, the first type allocation code includes a type allocation code of the first terminal device, and the first terminal device is located within the service area of ​​the first network element.

[0050] In one possible implementation, the second request message further includes an identifier of the first application function and / or a first condition. The first type allocation code includes at least one type allocation code, and the first condition is used to indicate at least one of the following: the number of first type allocation codes, the number of terminal devices for each type allocation code in the first type allocation code, or information about the region to which the terminal device belongs; the first terminal device is located in the region to which the terminal device belongs.

[0051] In one possible implementation, the method in the fifth aspect further includes: determining candidate terminal devices based on a first identifier, and determining a first terminal device that meets a first condition. Wherein, the type allocation code of the candidate terminal device belongs to a first type allocation code, and the candidate terminal devices include the first terminal device. That is, the second network element can determine candidate terminal devices whose type allocation codes belong to the first type allocation code based on the first identifier, and filter out the first terminal devices that meet the first condition from among the candidate terminal devices, so that the first data of the first terminal device is the data requested by the first application function.

[0052] In one possible implementation, the method in the fifth aspect further includes: obtaining a permanent device identifier (PEI) of at least one terminal device; determining a candidate terminal device based on a first identifier, including: when the first identifier is used to indicate an identifier of a first chip, determining a first type allocation code based on the identifier of the first chip, and determining a candidate terminal device based on the first type allocation code and the PEI of at least one terminal device; or, when the first identifier is used to indicate a first type allocation code, determining a candidate terminal device based on the first type allocation code and the permanent device identifier (PEI) of at least one terminal device. Wherein, the permanent device identifier (PEI) of at least one terminal device is used to indicate the type allocation code of each of the at least one terminal device, and the at least one terminal device includes the candidate terminal device. That is, when the first identifier is used to indicate the identifier of the first chip, the second network element needs to first determine the first type allocation code corresponding to the first chip based on the identifier of the first chip, and then, based on the first type allocation code and the PEI of at least one terminal device, determine the terminal device whose type allocation code belongs to the first type allocation code among at least one terminal device, i.e., the candidate terminal device, so that the second network element can subsequently filter out the first terminal device from the candidate terminal devices; when the first identifier is used to indicate the first type allocation code, the second network element can directly determine the terminal device whose type allocation code belongs to the first type allocation code among at least one terminal device, i.e., the candidate terminal device, based on the first type allocation code and the PEI of at least one terminal device, which is simple to implement and can be used by the second network element to filter out the first terminal device from the candidate terminal devices. In this way, the needs of different scenarios can be met.

[0053] In one possible implementation, the method in the fifth aspect further includes: acquiring second information and determining, based on the second information, that the first chip belongs to a chip list and / or the first type allocation code belongs to a type allocation code list. The second information is used to indicate the chip list and / or type allocation code list supported by the first application function. That is, the second network element stores the chip list and / or type allocation code list supported by the first application function, and the second network element can verify whether the first application function has permission to obtain data based on the chip list and / or type allocation code list supported by the first application function. If the first chip belongs to the chip list and / or the first type allocation code belongs to the type allocation code list, then the first terminal device is determined, and the SUPI of the first terminal device is sent to the first network element. This prevents unauthorized application functions from obtaining terminal data, thus avoiding data leakage from the terminal device and improving the security of the process by which application functions (such as the first application function) obtain data (such as measurement data) from the terminal device.

[0054] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection coordination function network element; the second network element is any one of the following: a unified data management network element, a unified data storage network element, or an access and mobility management network element.

[0055] Furthermore, the technical effects of the method described in the fifth aspect can be referred to the technical effects of the method described in the fourth aspect above, and will not be repeated here.

[0056] Sixthly, a communication method is provided. This method can be executed by a first application function, by a module applied to the first application function (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the first application function. The method includes: sending a first request message to a first network element and receiving a first response message from the first network element. The first request message requests data associated with a terminal device and includes a first identifier indicating an identifier of a first chip associated with the data, or a first type allocation code, wherein the first chip is associated with the first type allocation code. The first response message includes first data provided by the first terminal device, and the first type allocation code includes a type allocation code of the first terminal device, wherein the first terminal device is located within the service area of ​​the first network element.

[0057] In one possible implementation, the first request message may further include an identifier of a first application function and / or a first condition, the first condition being used to determine the first terminal device.

[0058] In one possible implementation, the first type allocation code includes at least one type allocation code, and the first condition indicates at least one of the following: the number of first type allocation codes, the number of terminal devices for each type allocation code in the first type allocation codes, or information about the region to which the terminal devices belong. Wherein, the first terminal device is located within the region to which the terminal devices belong.

[0059] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection and coordination function network element.

[0060] Furthermore, the technical effects of the method described in the sixth aspect can be referred to the technical effects of the method described in the fourth aspect above, and will not be repeated here.

[0061] A seventh aspect provides a communication method, which can be executed by a first network element, by a module applied to the first network element (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the first network element. The method includes: receiving a first request message from a first application function, and, if the first application function belongs to a data consumer list permitted by a first type allocation code, sending a first response message to the first application function. The first request message is used to request data associated with a terminal device, and includes a first identifier, which includes a first type allocation code; the first response message includes first data associated with the first terminal device, and the first terminal device is associated with the first identifier.

[0062] Based on the method described in the seventh aspect, the first network element can receive a first request message from a first application function requesting data associated with a terminal device. This first request message includes a first identifier, which includes a first type allocation code. If the first application function belongs to the data consumer list permitted by the first type allocation code (i.e., the first application function is authorized), meaning it has the permission to obtain the requested data, the first network element can further expose the first data of the first terminal device associated with the first identifier to the first application function via a first response message. This prevents unauthorized application functions from obtaining terminal data, thus avoiding data leakage from the terminal device and improving the security of the process by which an application function (such as the first application function) obtains data (such as measurement data) from the terminal device.

[0063] In one possible implementation, the first type of allocation code is associated with a first chip manufacturer and / or a first terminal manufacturer associated with the data; the list of data consumers allowed by the first type of allocation code is determined based on the list of data consumers allowed by the first chip manufacturer and / or the list of data consumers allowed by the first terminal manufacturer.

[0064] In one possible implementation, the first request message further includes at least one of the following: an identifier of a first application function, a data type, or a first condition. The first condition is used to identify the first terminal device.

[0065] In one possible implementation, the terminal device corresponds to at least one type allocation code, and the first condition indicates at least one of the following: the number of at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs. Wherein, the first terminal device is located within the region to which the terminal device belongs.

[0066] The embodiments of this application are described below through various possible implementations when the first network element stores a list of data consumers allowed by at least one type allocation code (including the first type allocation code) and a PEI storing at least one terminal device (including the first terminal device).

[0067] In one possible implementation, the method in the seventh aspect further includes: obtaining a list of data consumers permitted by the first type of allocation code based on the first request message, and determining that the first application function has the permission to obtain data if the first application function belongs to the list of data consumers permitted by the first type of allocation code.

[0068] In one possible implementation, the list of data consumers allowed by the first type of allocation code is pre-configured or predefined, which is simple to implement; or, the method described in the seventh aspect further includes: receiving the list of data consumers allowed by the first type of allocation code.

[0069] In one possible implementation, the method in the seventh aspect further includes: obtaining first information based on the PEI of at least one terminal device, and determining a first terminal device based on the PEI of at least one terminal device, the first information, and a first request message. The first information indicates at least one of the following: information about the chip manufacturer of each of the at least one terminal device, information about the terminal manufacturer of each of the at least one terminal device, or information about the chip of each of the at least one terminal device; the at least one terminal device includes the first terminal device, and the first terminal device satisfies at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device, the first terminal manufacturer includes the terminal manufacturer of the first terminal device, or the first chip includes the chip of the first terminal device.

[0070] The embodiments of this application are described below through various possible implementations when the second network element stores a list of data consumers allowed by at least one type allocation code (including the first type allocation code) and a PEI storing at least one terminal device (including the first terminal device).

[0071] In one possible implementation, the method in the seventh aspect further includes: sending a second request message to a second network element according to a first request message, and receiving a second response message from the second network element; determining a first terminal device according to the SUPI of the first terminal device. The second request message is used to request the acquisition of a terminal device associated with a first identifier, and the second request message includes the first identifier; the second response message includes the SUPI of the first terminal device.

[0072] In one possible implementation, the second request message also includes a first condition and information about the service area of ​​the first network element, wherein the first terminal device is located within the service area of ​​the first network element.

[0073] In one possible implementation, the second network element is any of the following: a unified data management network element, a unified data storage network element, or an access and mobility management network element.

[0074] Based on the above description, in one possible implementation, the list of data consumers allowed by the first type of allocation code includes at least one of the following: an identifier for an application function, an identifier for an application function from a chip manufacturer, an identifier for a chip manufacturer, an identifier for an application function from a terminal manufacturer, or an identifier for a terminal manufacturer. Wherein, the application function includes a first application function, the chip manufacturer includes a first chip manufacturer, and the terminal manufacturer includes a first terminal manufacturer. That is, the list of data consumers allowed by the first type of allocation code can be represented at different granularities to meet the needs of different scenarios.

[0075] In one possible implementation, the method in the seventh aspect further includes: collecting first data from the first terminal device; and sending a first response message to a first application function, including: sending the first response message to the first application function based on the first data. The first response message further includes a type allocation code for the first terminal device and / or an identifier of the chip of the first terminal device.

[0076] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection and coordination function network element.

[0077] Furthermore, the technical effects of the method described in the seventh aspect can be referred to the technical effects of the method described in the first aspect above, and will not be repeated here.

[0078] Eighthly, a communication method is provided. This method can be executed by a second network element, by a module applied to the second network element (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the second network element. The method includes: receiving a second request message from a first network element, and sending a second response message to the first network element according to the second request message. The second request message is used to request access to a terminal device associated with a first identifier. The second request message includes the first identifier, which includes a first type allocation code, and the first identifier originates from a first application function. The second response message includes a permanent subscription identifier (SUPI) of the first terminal device, the first terminal device is associated with the first identifier, and the first application function belongs to the data consumer list allowed by the first type allocation code.

[0079] In one possible implementation, the first type of allocation code is associated with a first chip manufacturer and / or a first terminal manufacturer associated with the data; the list of data consumers allowed by the first type of allocation code is determined based on the list of data consumers allowed by the first chip manufacturer and / or the list of data consumers allowed by the first terminal manufacturer.

[0080] In one possible implementation, the method in the eighth aspect further includes: obtaining a list of data consumers permitted by the first type of allocation code based on the second request message, and determining that the first application function has the permission to obtain data if the first application function belongs to the list of data consumers permitted by the first type of allocation code.

[0081] In one possible implementation, the list of data consumers allowed by the first type of allocation code is pre-configured or predefined, which is simple to implement; or, the method described in the eighth aspect further includes: receiving the list of data consumers allowed by the first type of allocation code.

[0082] In one possible implementation, the method in the eighth aspect further includes: obtaining second information based on a permanent device identifier (PEI) of at least one terminal device, and determining a first terminal device based on the PEI of the at least one terminal device, the second information, and a second request message. The second information indicates at least one of the following: information about the chip manufacturer of each of the at least one terminal device, information about the terminal manufacturer of each of the at least one terminal device, or information about the chip of each of the at least one terminal device; the at least one terminal device includes the first terminal device, and the first terminal device satisfies at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device, the first terminal manufacturer includes the terminal manufacturer of the first terminal device, or the first chip includes the chip of the first terminal device.

[0083] In one possible implementation, the second request message further includes a first condition and information about the service area of ​​the first network element. The first condition is used to determine the first terminal device, which is located within the service area of ​​the first network element.

[0084] In one possible implementation, the terminal device corresponds to at least one type allocation code, and the first condition indicates any of the following: the number of at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs. Wherein, the first terminal device is located within the region to which the terminal device belongs.

[0085] In one possible implementation, the list of data consumers allowed by the first type of allocation code includes at least one of the following: an identifier of an application function, an identifier of an application function from a chip manufacturer, an identifier of a chip manufacturer, an identifier of an application function from a terminal manufacturer, or an identifier of a terminal manufacturer. Wherein, the application function includes a first application function, the chip manufacturer includes a first chip manufacturer, and the terminal manufacturer includes a first terminal manufacturer.

[0086] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection coordination function network element; the second network element is any one of the following: a unified data management network element, a unified data storage network element, or an access and mobility management network element.

[0087] Furthermore, the technical effects of the method described in the eighth aspect can be referred to the technical effects of the method described in the first or seventh aspect above, and will not be repeated here.

[0088] A ninth aspect provides a communication method, which can be executed by a first application function, by a module applied to the first application function (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the first application function. The method includes: sending a first request message to a first network element and receiving a first response message from the first network element. The first request message is used to request data associated with a terminal device, and includes a first identifier, which includes a first type allocation code; the first response message includes first data associated with the first terminal device, and the first terminal device is associated with the first identifier.

[0089] In one possible implementation, the first type of allocation code is associated with a first chip manufacturer and / or a first terminal manufacturer associated with the data; the list of data consumers allowed by the first type of allocation code is determined based on the list of data consumers allowed by the first chip manufacturer and / or the list of data consumers allowed by the first terminal manufacturer.

[0090] In one possible implementation, the first request message further includes at least one of the following: an identifier of a first application function, a data type, or a first condition. The first condition is used to identify the first terminal device.

[0091] In one possible implementation, the terminal device corresponds to at least one type allocation code, and the first condition indicates at least one of the following: the number of at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs. Wherein, the first terminal device is located within the region to which the terminal device belongs.

[0092] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection and coordination function network element.

[0093] Furthermore, the technical effects of the method described in the ninth aspect can be referred to the technical effects of the method described in the first or seventh aspect above, and will not be repeated here.

[0094] In a tenth aspect, a communication method is provided. This method can be executed by a first network element, by a module applied to the first network element (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the first network element. The method includes: receiving a first request message from a first application function and sending a first response message to the first application function. The first request message is used to request data associated with a terminal device, and includes a first identifier indicating a first chip manufacturer and / or a first terminal manufacturer associated with the data; the first response message includes first data associated with the first terminal device, and the first terminal device is associated with the first identifier.

[0095] In one possible implementation, the first identifier includes at least one of the following: an identifier of a first chip manufacturer, an identifier of a first terminal manufacturer, an identifier of a first chip, a first type allocation code, or an identifier of a terminal device. Wherein, the first chip is the chip of the terminal device, and the first type allocation code is the type allocation code of the terminal device.

[0096] In one possible implementation, the first request message further includes at least one of the following: an identifier of a first application function, a data type, or a first condition. The first condition is used to identify the first terminal device.

[0097] In one possible implementation, the terminal device corresponds to at least one type allocation code, and the first condition indicates at least one of the following: the number of at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs. Wherein, the first terminal device is located within the region to which the terminal device belongs.

[0098] In one possible implementation, the method in the tenth aspect further includes: obtaining first information based on the PEI of at least one terminal device, and determining a first terminal device based on the PEI of at least one terminal device, the first information, and a first request message. The first information is used to indicate at least one of the following: information about the chip manufacturer of each of the at least one terminal device, information about the terminal manufacturer of each of the at least one terminal device, or information about the chip of each of the at least one terminal device; the at least one terminal device includes the first terminal device, and the first terminal device satisfies at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device, the first terminal manufacturer includes the terminal manufacturer of the first terminal device, or the first chip includes the chip of the first terminal device.

[0099] In one possible implementation, the method in the tenth aspect further includes: sending a second request message to a second network element according to a first request message, and receiving a second response message from the second network element; determining a first terminal device according to the SUPI of the first terminal device. The second request message is used to request the acquisition of a terminal device associated with a first identifier, and the second request message includes the first identifier; the second response message includes the SUPI of the first terminal device.

[0100] In one possible implementation, the second request message also includes a first condition and information about the service area of ​​the first network element, wherein the first terminal device is located within the service area of ​​the first network element.

[0101] In one possible implementation, the second network element is any of the following: a unified data management network element, a unified data storage network element, or an access and mobility management network element.

[0102] In one possible implementation, the method in the tenth aspect further includes: collecting first data from the first terminal device; and sending a first response message to a first application function, including: sending the first response message to the first application function based on the first data. The first response message further includes a type allocation code for the first terminal device and / or an identifier of the chip of the first terminal device.

[0103] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection and coordination function network element.

[0104] Furthermore, the technical effects of the method described in the tenth aspect can be referred to the technical effects of the method described in the first aspect above, and will not be repeated here.

[0105] Eleventhly, a communication method is provided. This method can be executed by a second network element, by a module applied to the second network element (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the second network element. The method includes: receiving a second request message from a first network element, and sending a second response message to the first network element according to the second request message. The second request message is used to request access to a terminal device associated with a first identifier. The second request message includes the first identifier, which indicates a first chip manufacturer and / or a first terminal manufacturer associated with the data. The second response message includes a permanent subscription identifier (SUPI) of the first terminal device, and the first terminal device is associated with the first identifier.

[0106] In one possible implementation, the first identifier includes at least one of the following: an identifier of a first chip manufacturer, an identifier of a first terminal manufacturer, an identifier of a first chip, a first type allocation code, or an identifier of a terminal device. Wherein, the first chip is the chip of the terminal device, and the first type allocation code is the type allocation code of the terminal device.

[0107] In one possible implementation, the method in the eleventh aspect further includes: obtaining second information based on the permanent device identifier (PEI) of at least one terminal device, and determining the first terminal device based on the PEI of the at least one terminal device, the second information, and the second request message. The second information indicates at least one of the following: information about the chip manufacturer of each of the at least one terminal device, information about the terminal manufacturer of each of the at least one terminal device, or information about the chip of each of the at least one terminal device; the at least one terminal device includes the first terminal device, and the first terminal device satisfies at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device, the first terminal manufacturer includes the terminal manufacturer of the first terminal device, or the first chip includes the chip of the first terminal device.

[0108] In one possible implementation, the second request message further includes a first condition and information about the service area of ​​the first network element. The first condition is used to determine the first terminal device, which is located within the service area of ​​the first network element.

[0109] In one possible implementation, the terminal device corresponds to at least one type allocation code, and the first condition indicates any of the following: the number of at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs. Wherein, the first terminal device is located within the region to which the terminal device belongs.

[0110] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection coordination function network element; the second network element is any one of the following: a unified data management network element, a unified data storage network element, or an access and mobility management network element.

[0111] Furthermore, the technical effects of the method described in the eleventh aspect can be referred to the technical effects of the method described in the first aspect above, and will not be repeated here.

[0112] In a twelfth aspect, a communication method is provided. This method can be executed by a first application function, by a module applied to the first application function (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the first application function. The method includes: sending a first request message to a first network element and receiving a first response message from the first network element. The first request message requests data associated with a terminal device, and includes a first identifier indicating a first chip manufacturer and / or a first terminal manufacturer associated with the data. The first response message includes first data associated with the first terminal device, and the first terminal device is associated with the first identifier.

[0113] In one possible implementation, the first identifier includes at least one of the following: an identifier of a first chip manufacturer, an identifier of a first terminal manufacturer, an identifier of a first chip, a first type allocation code, or an identifier of a terminal device. Wherein, the first chip is the chip of the terminal device, and the first type allocation code is the type allocation code of the terminal device.

[0114] In one possible implementation, the first request message further includes at least one of the following: an identifier of a first application function, a data type, or a first condition. The first condition is used to identify the first terminal device.

[0115] In one possible implementation, the terminal device corresponds to at least one type allocation code, and the first condition indicates at least one of the following: the number of at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs. Wherein, the first terminal device is located within the region to which the terminal device belongs.

[0116] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection and coordination function network element.

[0117] Furthermore, the technical effects of the method described in the twelfth aspect can be referred to the technical effects of the method described in the first aspect above, and will not be repeated here.

[0118] In a thirteenth aspect, a communication method is provided. This method can be executed by a first network element, by a module applied to the first network element (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the first network element. The method includes: receiving a first request message from a first application function and sending a first response message to the first application function. The first request message is used to request data associated with a terminal device, and the first request message includes a first identifier, which includes a first type allocation code; the first response message includes first data associated with the first terminal device, and the first terminal device is associated with the first identifier.

[0119] In one possible implementation, the first request message further includes at least one of the following: an identifier of a first application function, a data type, or a first condition. The first condition is used to identify the first terminal device.

[0120] In one possible implementation, the terminal device corresponds to at least one type allocation code, and the first condition indicates at least one of the following: the number of at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs. Wherein, the first terminal device is located within the region to which the terminal device belongs.

[0121] In one possible implementation, the method of the thirteenth aspect further includes: obtaining first information based on the PEI of at least one terminal device, and determining a first terminal device based on the PEI of at least one terminal device, the first information, and a first request message. The first information is used to indicate at least one of the following: information about the chip manufacturer of each of the at least one terminal device, information about the terminal manufacturer of each of the at least one terminal device, or information about the chip of each of the at least one terminal device; the at least one terminal device includes the first terminal device, and the first terminal device satisfies at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device, the first terminal manufacturer includes the terminal manufacturer of the first terminal device, or the first chip includes the chip of the first terminal device.

[0122] In one possible implementation, the method in aspect thirteen further includes: sending a second request message to a second network element according to a first request message, and receiving a second response message from the second network element; determining a first terminal device according to the SUPI of the first terminal device. The second request message is used to request the acquisition of a terminal device associated with a first identifier, and the second request message includes the first identifier; the second response message includes the SUPI of the first terminal device.

[0123] In one possible implementation, the second request message also includes a first condition and information about the service area of ​​the first network element, wherein the first terminal device is located within the service area of ​​the first network element.

[0124] In one possible implementation, the second network element is any of the following: a unified data management network element, a unified data storage network element, or an access and mobility management network element.

[0125] In one possible implementation, the method in aspect thirteen further includes: collecting first data from the first terminal device; and sending a first response message to a first application function, including: sending the first response message to the first application function based on the first data. The first response message further includes a type allocation code for the first terminal device and / or an identifier of the chip of the first terminal device.

[0126] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection and coordination function network element.

[0127] Furthermore, the technical effects of the method described in aspect thirteen can be referred to the technical effects of the method described in aspect one or aspect seven above, and will not be repeated here.

[0128] In a fourteenth aspect, a communication method is provided. This method can be executed by a second network element, by a module applied to the second network element (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the second network element. The method includes: receiving a second request message from a first network element, and sending a second response message to the first network element according to the second request message. The second request message is used to request access to a terminal device associated with a first identifier. The second request message includes the first identifier, which includes a first type allocation code. The second response message includes a permanent subscription identifier (SUPI) of the first terminal device, and the first terminal device is associated with the first identifier.

[0129] In one possible implementation, the method of the fourteenth aspect further includes: obtaining second information based on a permanent device identifier (PEI) of at least one terminal device, and determining a first terminal device based on the PEI of the at least one terminal device, the second information, and a second request message. The second information indicates at least one of the following: information about the chip manufacturer of each of the at least one terminal device, information about the terminal manufacturer of each of the at least one terminal device, or information about the chip of each of the at least one terminal device; the at least one terminal device includes the first terminal device, and the first terminal device satisfies at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device, the first terminal manufacturer includes the terminal manufacturer of the first terminal device, or the first chip includes the chip of the first terminal device.

[0130] In one possible implementation, the second request message further includes a first condition and information about the service area of ​​the first network element. The first condition is used to determine the first terminal device, which is located within the service area of ​​the first network element.

[0131] In one possible implementation, the terminal device corresponds to at least one type allocation code, and the first condition indicates any of the following: the number of at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs. Wherein, the first terminal device is located within the region to which the terminal device belongs.

[0132] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection coordination function network element; the second network element is any one of the following: a unified data management network element, a unified data storage network element, or an access and mobility management network element.

[0133] Furthermore, the technical effects of the method described in the fourteenth aspect can be referred to the technical effects of the method described in the first or seventh aspect above, and will not be repeated here.

[0134] In a fifteenth aspect, a communication method is provided. This method can be executed by a first application function, by a module applied to the first application function (e.g., a processor, circuit, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the first application function. The method includes: sending a first request message to a first network element and receiving a first response message from the first network element. The first request message is used to request data associated with a terminal device, and the first request message includes a first identifier, which includes a first type allocation code; the first response message includes first data associated with the first terminal device, and the first terminal device is associated with the first identifier.

[0135] In one possible implementation, the first request message further includes at least one of the following: an identifier of a first application function, a data type, or a first condition. The first condition is used to identify the first terminal device.

[0136] In one possible implementation, the terminal device corresponds to at least one type allocation code, and the first condition indicates at least one of the following: the number of at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs. Wherein, the first terminal device is located within the region to which the terminal device belongs.

[0137] In one possible implementation, the first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection and coordination function network element.

[0138] Furthermore, the technical effects of the method described in aspect fifteen can be referred to the technical effects of the method described in aspect one or aspect seven above, and will not be repeated here.

[0139] In a sixteenth aspect, a communication device is provided. The communication device includes modules for performing the method as described in the first aspect, such as a transceiver module and a processing module. The transceiver module is used to instruct the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0140] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the sixteenth aspect, and the receiving module implements the receiving function of the communication device described in the sixteenth aspect.

[0141] Optionally, the communication device according to the sixteenth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to the first aspect.

[0142] It should be noted that the communication device described in the sixteenth aspect may be the first network element, or a chip (system) or other component or assembly in the first network element, or a device containing the first network element. This application does not limit this.

[0143] Furthermore, the technical effects of the communication device described in the sixteenth aspect can be referred to the technical effects of the communication method described in the first aspect, and will not be repeated here.

[0144] In a seventeenth aspect, a communication device is provided. The communication device includes: a module for performing the method described in the second aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0145] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the seventeenth aspect, and the receiving module implements the receiving function of the communication device described in the seventeenth aspect.

[0146] Optionally, the communication device according to the seventeenth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the second aspect.

[0147] It is understood that the communication device described in the seventeenth aspect may be a second network element, or a chip (system) or other component or assembly in the second network element, or a device containing a second network element. This application does not limit this.

[0148] Furthermore, the technical effects of the communication device described in the seventeenth aspect can be referred to the technical effects of the method described in the second aspect, and will not be repeated here.

[0149] Eighteenth aspect: A communication device is provided. The communication device includes: a module for performing the method described in the third aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0150] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the eighteenth aspect, and the receiving module implements the receiving function of the communication device described in the eighteenth aspect.

[0151] Optionally, the communication device according to the eighteenth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to the third aspect.

[0152] It should be noted that the communication device described in the eighteenth aspect may be the first application function, or a chip (system) or other component or part in the first application function, or a device containing the first application function. This application does not limit it in this regard.

[0153] Furthermore, the technical effects of the communication device described in the eighteenth aspect can be referred to the technical effects of the communication method described in the third aspect, and will not be repeated here.

[0154] In a nineteenth aspect, a communication device is provided. The communication device includes: a module for performing the method described in the fourth aspect, such as a transceiver module and a processing module. The transceiver module is used to instruct the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0155] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device according to the nineteenth aspect, and the receiving module implements the receiving function of the communication device according to the nineteenth aspect.

[0156] Optionally, the communication device according to the nineteenth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to the fourth aspect.

[0157] It should be noted that the communication device described in the nineteenth aspect may be the first network element, or a chip (system) or other component or assembly in the first network element, or a device containing the first network element. This application does not limit this.

[0158] Furthermore, the technical effects of the communication device described in the nineteenth aspect can be referred to the technical effects of the communication method described in the fourth aspect, and will not be repeated here.

[0159] In a twentieth aspect, a communication device is provided. The communication device includes: modules for performing the method described in the fifth aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0160] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the twentieth aspect, and the receiving module implements the receiving function of the communication device described in the twentieth aspect.

[0161] Optionally, the communication device according to the twentieth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to the fifth aspect.

[0162] It should be noted that the communication device described in aspect 20 can be a second network element, a chip (system) or other component or assembly in the second network element, or a device containing a second network element. This application does not limit this.

[0163] Furthermore, the technical effects of the communication device described in aspect 20 can be referred to the technical effects of the communication method described in aspect 5, and will not be repeated here.

[0164] In a twenty-first aspect, a communication device is provided. The communication device includes: a module for performing the method described in the sixth aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0165] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in aspect twenty-one, and the receiving module implements the receiving function of the communication device described in aspect twenty-one.

[0166] Optionally, the communication device according to aspect twenty-one may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to aspect six.

[0167] It should be noted that the communication device described in aspect 21 may be the first application function, or a chip (system) or other component or part in the first application function, or a device containing the first application function. This application does not limit it in this regard.

[0168] Furthermore, the technical effects of the communication device described in aspect 21 can be referred to the technical effects of the communication method described in aspect 6, and will not be repeated here.

[0169] In a twenty-second aspect, a communication device is provided. The communication device includes: modules for performing the method described in the seventh aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0170] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in aspect twenty-two, and the receiving module implements the receiving function of the communication device described in aspect twenty-two.

[0171] Optionally, the communication device according to the twenty-second aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to the seventh aspect.

[0172] It should be noted that the communication device described in aspect 22 may be a first network element, a chip (system) or other component or assembly in the first network element, or a device containing the first network element. This application does not limit this.

[0173] Furthermore, the technical effects of the communication device described in aspect 22 can be referred to the technical effects of the communication method described in aspect 7, and will not be repeated here.

[0174] In a twenty-third aspect, a communication device is provided. The communication device includes: modules for performing the method described in the eighth aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0175] Optionally, the transceiver module may include a sending module and a receiving module. The sending module implements the sending function of the communication device described in aspect twenty-three, and the receiving module implements the receiving function of the communication device described in aspect twenty-three.

[0176] Optionally, the communication device according to aspect twenty-three may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to aspect eight.

[0177] It should be noted that the communication device described in aspect 23 may be a second network element, or a chip (system) or other component or assembly in the second network element, or a device containing a second network element. This application does not limit this.

[0178] Furthermore, the technical effects of the communication device described in aspect 23 can be referred to the technical effects of the communication method described in aspect 8, and will not be repeated here.

[0179] In a twenty-fourth aspect, a communication device is provided. The communication device includes: modules for performing the method described in the ninth aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0180] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in aspect twenty-four, and the receiving module implements the receiving function of the communication device described in aspect twenty-four.

[0181] Optionally, the communication device according to the twenty-fourth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to the ninth aspect.

[0182] It should be noted that the communication device described in aspect 24 may be the first application function, or a chip (system) or other component or part in the first application function, or a device containing the first application function. This application does not limit it in this respect.

[0183] Furthermore, the technical effects of the communication device described in aspect 24 can be referred to the technical effects of the communication method described in aspect 9, and will not be repeated here.

[0184] In a twenty-fifth aspect, a communication device is provided. The communication device includes: a module for performing the method described in the tenth aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0185] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device according to aspect twenty-five, and the receiving module implements the receiving function of the communication device according to aspect twenty-five.

[0186] Optionally, the communication device according to aspect twenty-five may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to aspect ten.

[0187] It should be noted that the communication device described in aspect 25 may be a first network element, a chip (system) or other component or assembly in the first network element, or a device containing the first network element. This application does not limit this.

[0188] Furthermore, the technical effects of the communication device described in aspect 25 can be referred to the technical effects of the communication method described in aspect 10, and will not be repeated here.

[0189] A twenty-sixth aspect provides a communication device. The communication device includes: modules for performing the method described in the eleventh aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0190] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device according to aspect twenty-six, and the receiving module implements the receiving function of the communication device according to aspect twenty-six.

[0191] Optionally, the communication device according to the twenty-sixth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to the eleventh aspect.

[0192] It should be noted that the communication device described in aspect 26 may be a second network element, or a chip (system) or other component or assembly in the second network element, or a device containing a second network element. This application does not limit this.

[0193] Furthermore, the technical effects of the communication device described in aspect 26 can be referred to the technical effects of the communication method described in aspect 11, and will not be repeated here.

[0194] A twenty-seventh aspect provides a communication device. The communication device includes modules for performing the method described in the twelfth aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0195] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in aspect twenty-seven, and the receiving module implements the receiving function of the communication device described in aspect twenty-seven.

[0196] Optionally, the communication device according to the twenty-seventh aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to the twelfth aspect.

[0197] It should be noted that the communication device described in aspect 27 may be the first application function, or a chip (system) or other component or part in the first application function, or a device containing the first application function. This application does not limit it in this respect.

[0198] Furthermore, the technical effects of the communication device described in aspect 27 can be referred to the technical effects of the communication method described in aspect 12, and will not be repeated here.

[0199] A twenty-eighth aspect provides a communication device. The communication device includes modules for performing the method described in aspect thirteen, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0200] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in aspect twenty-eight, and the receiving module implements the receiving function of the communication device described in aspect twenty-eight.

[0201] Optionally, the communication device according to aspect twenty-eight may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to aspect thirteen.

[0202] It should be noted that the communication device described in aspect 28 may be a first network element, a chip (system) or other component or assembly in the first network element, or a device containing the first network element. This application does not limit this.

[0203] Furthermore, the technical effects of the communication device described in aspect 28 can be referred to the technical effects of the communication method described in aspect 13, and will not be repeated here.

[0204] A twenty-ninth aspect provides a communication device. The communication device includes modules for performing the method described in the fourteenth aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0205] Optionally, the transceiver module may include a sending module and a receiving module. The sending module implements the sending function of the communication device according to aspect 29, and the receiving module implements the receiving function of the communication device according to aspect 29.

[0206] Optionally, the communication device according to the twenty-ninth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to the fourteenth aspect.

[0207] It should be noted that the communication device described in aspect 29 may be a second network element, or a chip (system) or other component or assembly in the second network element, or a device containing a second network element. This application does not limit this.

[0208] Furthermore, the technical effects of the communication device described in aspect 29 can be referred to the technical effects of the communication method described in aspect 14, and will not be repeated here.

[0209] In a thirtieth aspect, a communication device is provided. The communication device includes modules for performing the method described in the fifteenth aspect, such as a transceiver module and a processing module. The transceiver module is used to indicate the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0210] Optionally, the transceiver module may include a sending module and a receiving module. The sending module implements the sending function of the communication device described in the thirtieth aspect, and the receiving module implements the receiving function of the communication device described in the thirtieth aspect.

[0211] Optionally, the communication device according to the thirtieth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method according to the fifteenth aspect.

[0212] It should be noted that the communication device described in aspect 30 may be the first application function, or a chip (system) or other component or part in the first application function, or a device containing the first application function. This application does not limit it in this respect.

[0213] Furthermore, the technical effects of the communication device described in aspect 30 can be referred to the technical effects of the communication method described in aspect 15, and will not be repeated here.

[0214] In a thirty-first aspect, a communication device is provided. The communication device includes a processor configured to perform the method described in any one of the first to fifteenth aspects.

[0215] In one possible implementation, the communication device described in aspect thirty-one may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in aspect thirty-one and other communication devices.

[0216] In one possible implementation, the communication device described in aspect thirty-one may further include a memory. The memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs and / or data relating to the methods described in any of aspects one through fifteen.

[0217] In the embodiments of this application, the communication device described in the thirty-first aspect may be a first network element as described in the first aspect, fourth aspect, seventh aspect, tenth aspect, or thirteenth aspect, or a chip (system) or other component or assembly disposed in the first network element, or a device containing the first network element; or, the communication device described in the thirty-first aspect may be a second network element as described in the second aspect, fifth aspect, eighth aspect, eleventh aspect, or fourteenth aspect, or a chip (system) or other component or assembly disposed in the second network element, or a device containing the second network element; or, the communication device described in the thirty-first aspect may be a first application function as described in the third aspect, sixth aspect, ninth aspect, twelfth aspect, or fifteenth aspect, or a chip (system) or other component or assembly disposed in the first application function, or a device containing the first application function.

[0218] Furthermore, the technical effects of the communication device described in aspect 31 can be referred to the technical effects of the method described in any one of aspects 1 to 15, and will not be repeated here.

[0219] In a thirty-second aspect, a communication device is provided. The communication device includes a processor coupled to a memory, the processor being configured to execute a computer program stored in the memory, such that the communication device performs the method described in any one of the first to fifteenth aspects.

[0220] In one possible implementation, the communication device described in aspect thirty-two may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in aspect thirty-two and other communication devices.

[0221] In the embodiments of this application, the communication device described in the thirty-second aspect may be a first network element as described in the first aspect, fourth aspect, seventh aspect, tenth aspect, or thirteenth aspect, or a chip (system) or other component or assembly disposed in the first network element, or a device containing the first network element; or, the communication device described in the thirty-second aspect may be a second network element as described in the second aspect, fifth aspect, eighth aspect, eleventh aspect, or fourteenth aspect, or a chip (system) or other component or assembly disposed in the second network element, or a device containing the second network element; or, the communication device described in the thirty-second aspect may be a first application function as described in the third aspect, sixth aspect, ninth aspect, twelfth aspect, or fifteenth aspect, or a chip (system) or other component or assembly disposed in the first application function, or a device containing the first application function.

[0222] Furthermore, the technical effects of the communication device described in aspect thirty-two can be referred to the technical effects of the method described in any one of aspects one through fifteen, and will not be repeated here.

[0223] In a thirty-third aspect, a communication device is provided, comprising: a processor and a memory; the memory being configured to store a computer program, which, when executed by the processor, causes the communication device to perform the method described in any one of the first to fifteenth aspects.

[0224] In one possible implementation, the communication device described in aspect thirty-three may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in aspect thirty-three and other communication devices.

[0225] In the embodiments of this application, the communication device described in aspect 33 may be a first network element as described in aspect 1, aspect 4, aspect 7, aspect 10, or aspect 13, or a chip (system) or other component or assembly disposed in the first network element, or a device containing the first network element; or, the communication device described in aspect 33 may be a second network element as described in aspect 2, aspect 5, aspect 8, aspect 11, or aspect 14, or a chip (system) or other component or assembly disposed in the second network element, or a device containing the second network element; or, the communication device described in aspect 33 may be a first application function as described in aspect 3, aspect 6, aspect 9, aspect 12, or aspect 15, or a chip (system) or other component or assembly disposed in the first application function, or a device containing the first application function.

[0226] Furthermore, the technical effects of the communication device described in aspect 33 can be referred to the technical effects of the method described in any one of aspects 1 to 15, and will not be repeated here.

[0227] In a thirty-fourth aspect, a communication device is provided, comprising: a processor; the processor being configured to be coupled to a memory, and after reading a computer program from the memory, to execute, according to the computer program, the method described in any one of the first to fifteenth aspects.

[0228] In one possible implementation, the communication device described in aspect thirty-four may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in aspect thirty-four and other communication devices.

[0229] In the embodiments of this application, the communication device described in the thirty-fourth aspect may be a first network element as described in the first aspect, fourth aspect, seventh aspect, tenth aspect, or thirteenth aspect, or a chip (system) or other component or assembly disposed in the first network element, or a device containing the first network element; or, the communication device described in the thirty-fourth aspect may be a second network element as described in the second aspect, fifth aspect, eighth aspect, eleventh aspect, or fourteenth aspect, or a chip (system) or other component or assembly disposed in the second network element, or a device containing the second network element; or, the communication device described in the thirty-fourth aspect may be a first application function as described in the third aspect, sixth aspect, ninth aspect, twelfth aspect, or fifteenth aspect, or a chip (system) or other component or assembly disposed in the first application function, or a device containing the first application function.

[0230] Furthermore, the technical effects of the communication device described in aspect 34 can be referred to the technical effects of the method described in any one of aspects 1 to 15, and will not be repeated here.

[0231] In a thirty-fifth aspect, a communication system is provided. The communication system includes: the first network element described in the first aspect and the first application function described in the third aspect. Optionally, the communication system may further include the second network element described in the second aspect.

[0232] In a thirty-sixth aspect, a communication system is provided. The communication system includes: the first network element described in the fourth aspect, the second network element described in the fifth aspect, and the first application function described in the sixth aspect.

[0233] In a thirty-seventh aspect, a communication system is provided. The communication system includes: the first network element described in the seventh aspect and the first application function described in the ninth aspect. Optionally, the communication system may further include the second network element described in the eighth aspect.

[0234] In a thirty-eighth aspect, a communication system is provided. The communication system includes: the first network element described in the tenth aspect and the first application function described in the twelfth aspect. Optionally, the communication system may further include the second network element described in the eleventh aspect.

[0235] In a thirty-ninth aspect, a communication system is provided. The communication system includes: the first network element described in the thirteenth aspect and the first application function described in the fifteenth aspect. Optionally, the communication system may further include the second network element described in the fourteenth aspect.

[0236] In a fortieth aspect, a communication chip is provided, wherein instructions are stored that, when the communication chip is operated on a communication device, cause the method described in any one of the first to fifteenth aspects to be implemented.

[0237] In a forty-first aspect, a computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are executed on a computer, the computer causes the computer to perform the method described in any one of the first to fifteenth aspects.

[0238] In a forty-second aspect, a computer program product is provided, comprising a computer program or instructions that, when executed on a computer, cause the computer to perform the method described in any one of the first to fifteenth aspects. Attached Figure Description

[0239] Figure 1 This is a schematic diagram of a 5GS architecture;

[0240] Figure 2 This is a schematic diagram of a method for obtaining NWDAF from AF analysis.

[0241] Figure 3 A schematic diagram of the architecture of a communication system provided in this application embodiment. Figure 1 ;

[0242] Figure 4 A schematic diagram of the architecture of a communication system provided in this application embodiment. Figure 2 ;

[0243] Figure 5 A flowchart illustrating a communication method provided in an embodiment of this application. Figure 1 ;

[0244] Figure 6 A flowchart illustrating a communication method provided in an embodiment of this application. Figure 2 ;

[0245] Figure 7 A flowchart illustrating a communication method provided in an embodiment of this application. Figure 3 ;

[0246] Figure 8 A flowchart illustrating a communication method provided in an embodiment of this application. Figure 4 ;

[0247] Figure 9 A flowchart illustrating a communication method provided in an embodiment of this application. Figure 5 ;

[0248] Figure 10 A flowchart illustrating a communication method provided in an embodiment of this application. Figure 6 ;

[0249] Figure 11 A schematic diagram of the structure of a communication device provided in this application embodiment. Figure 1 ;

[0250] Figure 12 A schematic diagram of the structure of a communication device provided in this application embodiment. Figure 2 . Detailed Implementation

[0251] For ease of understanding, the technical terms involved in the embodiments of this application will be introduced below.

[0252] 1. Fifth generation (5G) mobile communication system (5G system, 5GS):

[0253] Figure 1 This is a schematic diagram of a 5GS architecture. (For example...) Figure 1As shown, 5GS includes: access network (AN) and core network (CN), and may also include: terminal equipment.

[0254] The aforementioned terminal equipment can be a terminal device with transceiver functions, or it can be a chip or chip system installed in the terminal device. This terminal equipment can also be referred to as user equipment (UE), access terminal equipment, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal equipment, mobile device, user terminal equipment, terminal equipment, wireless communication equipment, user agent, or user apparatus. The terminal devices in the embodiments of this application may be mobile phones, cellular phones, smartphones, tablets (such as tablets), wireless data cards, personal digital assistants (PDAs), wireless modems, handsets, laptop computers, machine-type communication (MTC) terminal devices, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminal devices in autonomous driving, wireless terminal devices in industrial control, wireless terminal devices in self-driving, wireless terminal devices in telemedicine, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, and smart homes. The terminal equipment in this application can be a wireless terminal device (e.g., a home-based device), an in-vehicle terminal device, a roadside unit (RSU) with terminal device functionality, or an aerial device (e.g., an intelligent robot, a hot air balloon, a drone, or an airplane). The terminal equipment in this application can also be an in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit built into a vehicle as one or more components or units, a transportation vehicle with wireless communication functionality, or a communication module. The terminal equipment can also be other devices with terminal device functionality; for example, it can be a device that functions as a terminal device in device-to-device (D2D) communication.

[0255] This application does not limit the form of the terminal device. The device used to implement the functions of the terminal device can be the terminal device itself, or it can be a device that supports the terminal device in implementing the functions, such as a chip system. This device can be installed in the terminal device or used in conjunction with the terminal device. In this application, the chip system can be composed of chips, or it can include chips and other discrete devices. The terminal device typically contains a communication module, circuit, or chip that performs the corresponding communication functions. The terminal device can also be configured with program instructions for performing the corresponding communication functions.

[0256] The aforementioned AN is used to implement access-related functions, providing network access capabilities to authorized users in specific areas, and determining transmission links of different quality levels to transmit user data based on user level, service requirements, etc. The AN forwards control signals and user data between the terminal device and the CN. The AN may include access network equipment, also known as radio access network (RAN) equipment. The CN is primarily responsible for maintaining the mobile network's subscription data, providing terminal devices with functions such as session management, mobility management, policy management, and security authentication.

[0257] A CN may include, but is not limited to, the following network functions (NFs): userplane function (UPF), authentication server function (AUSF), access and mobility management function (AMF), session management function (SMF), network slice selection function (NSSF), network exposure function (NEF), network repository function (NRF), policy control function (PCF), unified data management (UDM), unified data repository (UDR), network data analytics function (NWDAF), and application function (AF).

[0258] like Figure 1As shown, the UE accesses the 5G network through the RAN device. The UE communicates with the AMF through the N1 interface (N1 for short); the RAN communicates with the AMF through the N2 interface (N2 for short); the RAN communicates with the UPF through the N3 interface (N3 for short); the SMF communicates with the UPF through the N4 interface (N4 for short); and the UPF accesses the data network (DN) through the N6 interface (N6 for short). Furthermore, Figure 1 The control plane functions shown, such as AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, UDR, NWDAF, or AF, interact using service-oriented interfaces. For example, the service-oriented interface provided by AUSF is Nausf; AMF is Namf; SMF is Nsmf; NSSF is Nnssf; NEF is Nnef; NRF is Nnrf; PCF is Npcf; UDM is Nudm; UDR is Nudr; NWDAF is Nnwdaf; and AF is Naf.

[0259] RAN equipment can be a device with wireless transceiver capabilities, or it can be a chip or chip system installed in the device to provide access services for terminal devices. For example, RAN equipment may include: access network equipment of future mobile communication systems, or in future communication systems, the network equipment may have other naming methods, all of which are covered within the protection scope of the embodiments of this application, and this application does not impose any limitations on them. Alternatively, RAN equipment can also include 5G, such as next-generation NodeBs (gNBs) in new radio (NR) systems, or one or a group of antenna panels (including multiple antenna panels) of a 5G base station. It can also be network nodes constituting a gNB, transmission and reception point (TRP), transmission point (TP), or transmission measurement function (TMF), such as a central unit (CU), distributed unit (DU), CU-control plane (CP), CU-user plane (UP), or radio unit (RU), RSU with base station functionality, or wired access gateway, or 5G core network elements, etc. Alternatively, network equipment can also include: access points (APs) in wireless fidelity (WiFi) systems, wireless relay nodes, wireless backhaul nodes, various forms of macro base stations, micro base stations (also known as small cells), relay stations, access points, wearable devices, vehicle-mounted equipment, etc.

[0260] CU and DU can be configured separately or included in the same network element, such as a baseband unit (BBU). RU can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). It is understood that network equipment can be CU nodes, DU nodes, or a combination of both. Furthermore, CUs can be classified as network equipment in the access network (RAN) or the core network (CN); there are no restrictions on this classification.

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

[0262] This application does not limit the form of the RAN device. The device used to implement the function of the network device can be the network device itself, or it can be a device that supports the network device in implementing the function, such as a chip system. The device can be installed in the network device or used in conjunction with the network device.

[0263] The User-Defined Processing (UPP) is primarily responsible for user data processing (forwarding, receiving, billing, etc.). For example, a UPF can receive user data from a data network (DN) and forward it to the terminal device through access network equipment. A UPF can also receive user data from the terminal device through access network equipment and forward it to the DN. A DN refers to the operator's network that provides data transmission services to users. Examples include Internet Protocol (IP) multimedia services (IMS) and the Internet. A DN can be an external network of the operator or a network controlled by the operator, used to provide services to terminal devices. In a Protocol Data Unit (PDU) session, the UPF directly connected to the DN via N6 is also called the Protocol Data Unit Session Anchor (PSA).

[0264] AUSF is primarily used to perform security authentication for terminal devices.

[0265] AMF is primarily used for mobility management in mobile networks. Examples include user location updates, user network registration, and user handover.

[0266] SMF is primarily used for session management in mobile networks. This includes session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting a UPF (User-Defined Provider) to handle packet forwarding.

[0267] The PCF primarily supports providing a unified policy framework to control network behavior, delivering policy rules to control-layer network functions, and acquiring user subscription information related to policy decisions. The PCF can provide policies to the AMF and SMF, such as Quality of Service (QoS) policies and slice selection policies.

[0268] NSSF is primarily used to select network slices for terminal devices.

[0269] NEF is primarily used to support the opening of capabilities and events.

[0270] UDM is primarily used to store user data, such as contract data and authentication / authorization data.

[0271] UDR is primarily used to store structured data, including contract data, policy data, externally exposed structured data, and application-related data.

[0272] NWDAF is primarily used to collect data (including data from terminal devices, access network devices, core network elements, and third-party devices, or a combination thereof). This data can be data from the terminal device, access network device, core network element, or third-party application device itself, or data from the terminal device on that access network device, core network element, or third-party application device. The collected data is then analyzed, and the analysis results are output for use by the network, network management equipment, and applications in policy decisions. In other words, NWDAF provides data analysis capabilities to 5G core network (5G core, 5GC) NFs or other devices, such as Operation Administration and Maintenance (OAM). 5GC NFs or OAMs can request network data analysis results from NWDAFs. Upon receiving a request, NWDAF can collect data from relevant network elements and train an Artificial Intelligence (AI) model. NWDAFs can then use the AI ​​model to perform data inference and feed the inference results back to the corresponding 5GC NF or OAM. Depending on their functions, NWDAFs can be divided into training-supporting NWDAFs (such as model training logical function (MTLF)) and inference-supporting NWDAFs (such as analytics logical function (AnLF)). AnLF can request AI model information from MTLF for data inference. In this embodiment, an NWDAF can be a separate network element or co-located with other network elements, such as within a PCF or AMF; this embodiment does not limit this. The AF primarily supports interaction with the CN to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.

[0273] It is understood that the CN may also include other possible network elements, such as the data collection coordination function (DCCF), without limitation. The DCCF can be used to coordinate the collection and distribution of data requested by NF consumers, and also has the function of preprocessing the collected data according to the parameters specified by the consumer.

[0274] The functions mentioned in the embodiments of this application can also refer to functional network elements or functional entities. For example, UPF can be described as UPF network element, AMF can be described as AMF network element, SMF can be described as SMF network element, PCF can be described as PCF network element, and so on, without limitation.

[0275] 2. User Identifier

[0276] A user identifier is an identifier associated with a terminal device (or user). For example, user identifiers may include subscription permanent identifiers (SUPI), permanent equipment identifiers (PEI), and generic public subscription identifiers (GPSI), without limitation. The following is a detailed description of each of these identifiers.

[0277] SUPI is a permanent and unique identifier for 5G users, used by the core network to identify the user's subscription identity.

[0278] PEI stands for International Mobile Equipment Identity (IMEI) or International Mobile Station Equipment Identity and Software Version Number (IMEI). PEI may include a Type Allocation Code (TAC), which consists of the first 8 digits of the IMEI. The TAC can be used to identify the manufacturer (or vendor), model, and hardware version (such as chip identity, ID) of a terminal device (e.g., a mobile phone), and can be used to distinguish mobile phone brands and models.

[0279] It should be understood that during the registration process of a terminal device (such as registering to a new AMF), if the PEI is not actively provided by the terminal device and cannot be obtained from the old AMF, the new AMF can request the PEI of the terminal device by sending an identity request. Unless the terminal device is performing emergency registration and authentication is impossible, the PEI should be transmitted in encrypted form.

[0280] GPSI is a user-disclosed identifier used by third-party services to identify users, while avoiding the exposure of sensitive information such as SUPI.

[0281] It is understandable that the 3rd generation partnership project (3GPP) system stores the association between GPSI and the corresponding SUPI in the user data, that is, there is a relationship between GPSI and SUPI.

[0282] For a detailed introduction to SUPI, PEI, TAC, and GPSI, please refer to existing technologies; further details will not be provided here.

[0283] 3. Manufacturer or supplier information

[0284] Vendor information may include information about the terminal equipment vendor (denoted as UE vendor) and / or the chip vendor. The UE vendor refers to the manufacturer that produces the user terminal equipment, and the chip vendor is the manufacturer that designs and produces the chips inside these devices. For a detailed introduction, please refer to existing technologies, which will not be elaborated here.

[0285] 4. AF acquires data from terminal devices

[0286] When training a terminal device-side model (such as an AI model), it is necessary to collect measurement information from the terminal device, such as data from the terminal device (e.g., measurement data). Currently, the main entity training the terminal device-side model may be a third-party AF, such as an over-the-top (OTT) server, which can be simply referred to as OTT. In this scenario, for example, taking a third-party AF as the OTT server, the data transmission method of the UE can include the following three implementation options:

[0287] Option 1: UE->OTT server.

[0288] In option 1, the UE can directly expose (or provide) data to the OTT server via 3GPP or non-3GPP methods.

[0289] option 2: UE->CN->OTT server.

[0290] In option 2, the CN (such as NWDAF) is responsible for collecting data from the UE and then making the collected data available to the OTT server.

[0291] option 3: UE->gNB->TT server.

[0292] In option 3, OAM can collect data from the UE via gNB and then make the collected data available to the OTT server.

[0293] It is understood that options 1-3 above are merely examples, and the data transmission method of the UE can also be any other possible transmission method, without limitation.

[0294] The following section uses the transmission method shown in option 2 above as an example to specifically introduce the implementation of AF obtaining NWDAF analysis (i.e., obtaining UE data collected by NWDAF) through NEF.

[0295] For example, such as Figure 2 As shown, the method for obtaining NWDAF analysis by AF may include the following steps:

[0296] S200, NEF control analytics exposure mapping.

[0297] In other words, NEF can transform the network's internal analytical capabilities into standardized services that can be securely invoked by third parties through policy control, data mapping, and security mechanisms.

[0298] S201, AF sends Analysis Subscription Request #1 to NEF. Correspondingly, NEF receives Analysis Subscription Request #1 from AF.

[0299] When the AF needs to obtain measurement data from the UE (such as for training a model on the terminal device side), the AF can send an analysis subscription request #1 to the NEF through the Nnef interface to request the required measurement data from the UE. For example, the analysis subscription request #1 may include the analysis ID (i.e., the identifier of the analysis that the AF needs to obtain), etc., without limitation.

[0300] S202, NEF sends analytics subscription request #2 to NWDAF. Correspondingly, NWDAF receives analytics subscription request #2 from NEF.

[0301] Based on analysis subscription request #1, NEF can send analysis subscription request #2 to NWDAF through the Nnwdaf interface. Analysis subscription request #2 may include the aforementioned analysis ID, etc., without limitation. It is understood that analysis subscription request #1 and analysis subscription request #2 can be the same (e.g., NEF transmits them transparently) or different (e.g., NEF does not transmit them transparently, such as encapsulating subscription request #1 and other parameters together in subscription request #2, etc.). This application embodiment does not limit this.

[0302] Optionally, before sending the analysis subscription request #2 to the NWDAF, the NEF can determine or verify whether the AF has the permission to obtain the analysis based on the analysis subscription request #1. If the verification is successful, the NEF can then trigger the sending of the analysis subscription request #2 to the NWDAF to improve the security of the UE's measurement data acquisition.

[0303] S203, NWDAF sends analytics subscription response #2 to NEF. Correspondingly, NEF receives analytics subscription response #2 from NWDAF.

[0304] The NWDAF can obtain or generate the analysis corresponding to the analysis ID in the analysis subscription request #2, such as analysis #1 (which can also be understood as the measurement data of the UE requested by the AF), and send analysis #1 to the NEF through analysis subscription response #2 (the response to analysis subscription request #2). The NEF can send analysis subscription response #2 to the NEF through the Nnwdaf interface.

[0305] S204, NEF sends Analysis Subscription Response #1 to AF. Correspondingly, AF receives Analysis Subscription Response #1 from NEF.

[0306] The NEF can anonymize or transform the acquired analytics based on Analytics Subscription Request #2. For example, if Analytics #1 includes the UE's ID, such as SUPI, the NEF can convert SUPI into a corresponding identifier that the AF can recognize, such as GPSI. The NEF can then send the anonymized or transformed Analytics #1 to the AF via Analytics Subscription Response #1 (the response to Analytics Subscription Request #1). The NEF can also send Analytics Subscription Response #2 to the NEF via the Nnef interface.

[0307] It is understood that the specific implementation of steps S200-S204 above can refer to the prior art, and this application embodiment will not elaborate on them. Steps S200-S204 above are only examples, and AF can also obtain NWDAF analysis through any other possible methods, without limitation.

[0308] Based on the above introduction, when training the terminal device-side model, it is necessary to collect (measurement) data from the terminal device. Currently, the main method for training the terminal device-side model is likely a third-party auto-analyzer (AF). In this case, the AF can acquire data from the terminal device through a network object (CN) (such as NWDAF) or other devices, such as OAM, for subsequent training of the terminal device-side model. However, based on the existing implementation, the following problems may exist:

[0309] Question A: Based on the existing implementation, there are risks in the process of AF acquiring data from terminal devices. How to improve the security of the AF acquiring data from terminal devices is an urgent problem to be solved.

[0310] Question B: Based on the above description, the AF can obtain data from terminal devices through the CN, such as the NWDAF. For example, the AF can send a data request message to the NWDAF to request the required data. The NWDAF can send terminal device retrieval request messages to other network elements (or devices), such as UDM and UDR, to query the terminal devices that provide data to the AF. Other network elements (such as UDM and UDR) can send information about at least one terminal device, such as the SUPI of at least one terminal device, to the NWDAF, so that the NWDAF can determine at least one terminal device that provides data to the AF based on the SUPI of at least one terminal device and collect its corresponding data.

[0311] However, based on the above implementation, NWDAF may not be able to collect data from each terminal device in at least one terminal device, which would cause AF to be unable to obtain the required data and affect the efficiency of AF in obtaining data from terminal devices.

[0312] In summary, in view of the above-mentioned technical problems, the embodiments of this application propose the following technical solutions to improve the security of the process of AF acquiring measurement data from terminal devices.

[0313] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0314] The technical solutions of this application embodiment can be applied to various communication systems, such as Bluetooth systems, WiFi systems, long-range radio (LoRa), vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, machine-to-machine (M2M) communication systems, machine-type communication (MTC), Internet of Things (IoT) communication systems, fourth-generation (4G) communication systems such as long-term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, worldwide interoperability for microwave access (WiMAX) communication systems, 5G communication systems such as NR systems, non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication, and future communication systems.

[0315] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The term "device" can also be replaced with entities, network entities, communication equipment, communication modules, nodes, communication nodes, etc.

[0316] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0317] In addition, to better understand the embodiments of this application, the following points are made before introducing the embodiments of this application.

[0318] In the embodiments of this application, the words "exemplary," "for example," etc., are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or design options. Specifically, the use of the term "exemplary" is intended to present the concept in a concrete manner.

[0319] In the embodiments of this application, the terms "information," "signal," "message," "channel," and "signaling" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, their intended meanings are consistent. Similarly, "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, their intended meanings are consistent. Furthermore, the " / " mentioned in this application can be used to indicate an "or" relationship. It is understood that in this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing an instruction information used to indicate A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A.

[0320] In this embodiment, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index; or indirectly indicating the information to be instructed by indicating other information, wherein there is an association between the other information and the information to be instructed. Alternatively, only a part of the information to be instructed may be indicated, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent.

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

[0322] The information to be instructed can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device.

[0323] The terms "first," "second," and various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, they distinguish different instruction information. Similarly, "first network region" and "second network region" are simply used to distinguish different regions and do not limit their order. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that "first," "second," etc., are not necessarily different.

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

[0325] The “protocol” mentioned in the embodiments of this application may refer to standard protocols in the field of communication, such as LTE protocol, NR protocol and related protocols applied to future communication systems. The embodiments of this application do not limit this.

[0326] In the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the fact that the device (e.g., a terminal device or a network device) will make corresponding processing under certain objective circumstances. They are not time limits, nor do they require the device (e.g., a terminal device or a network device) to have a judgment action when implementing it, nor do they imply any other limitations.

[0327] In the embodiments of this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY by other units or modules via the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0328] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0329] To facilitate understanding of the embodiments of this application, let's first take... Figure 3 and Figure 4 The communication system illustrated herein is used as an example to illustrate a communication system applicable to embodiments of this application. For example, Figure 3 A schematic diagram of the architecture of a communication system to which the communication method provided in the embodiments of this application is applicable. Figure 1 .

[0330] like Figure 3 As shown, the communication system mainly includes: a first application function and a first network element. Optionally, the communication system may also include a second network element.

[0331] The first application function can be a third-party application function used to request and obtain (measurement) data from the terminal device, which is then used to perform subsequent steps based on the obtained terminal device data, such as training a model on the terminal device side. For example, the first application function can be the AF in the aforementioned 5GS, and its specific description can be found in the relevant description in the aforementioned 5GS, which will not be repeated here; or, the first application function can be a network element that implements the corresponding function in other or future communication systems (such as other network elements used to request and obtain data from the terminal device), which is not limited in this respect.

[0332] It is understood that the application functions (including the first application function) in the embodiments of this application can be the aforementioned OTT. For example, OTT can be divided into chip OTT and / or terminal OTT. Among them, chip OTT can be hardware support provided by chip manufacturers to optimize the service performance of OTT or chip; terminal OTT can be OTT applications and services running on terminal devices. For a detailed description, please refer to the prior art, which will not be elaborated here.

[0333] The first network element can be used to collect data from terminal devices and to make the collected data available or provided to the first application function. For example, the first network element can be any of the following: a network open function network element (such as NEF in the above 5GS), a network data analysis function network element (such as NWDAF in the above 5GS), or a data collection coordination function network element (such as DCCF), etc. For a detailed description, please refer to the relevant description in the above 5GS, which will not be repeated here; or, the first network element can be a network element that implements the corresponding function in other or future communication systems, which is not limited in this application embodiment.

[0334] The second network element may store at least one of the following: a list (or set, including a list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer) permitted by at least one vendor (such as a chip manufacturer or a terminal (equipment) manufacturer); a list of consumers permitted by at least one type allocation code (including a list of data consumers permitted by the first type allocation code); or the PEI (information) of at least one terminal device (such as the at least one terminal device registered to the second network element, or the second network element used to manage the at least one terminal device). For example, the second network element may be any of the following: a unified data management network element (such as UDM in the above 5GS), a unified data storage network element (such as UDR in the above 5GS), or an access and mobility management network element (such as AMF in the above 5GS), etc. For details, please refer to the relevant descriptions in the above 5GS, which will not be repeated here; or, the second network element may be a network element that implements the corresponding function in other or future communication systems, which is not limited in this application embodiment.

[0335] It is understood that when the first network element can obtain at least one of the following: a consumer list allowed by at least one vendor, a consumer list allowed by at least one type allocation code, or the PEI (information) of each of the at least one terminal devices, the communication system may not include the second network element in order to reduce signaling interaction between network elements (such as the first network element and the second network element) and thus reduce resource overhead. This application embodiment does not limit this.

[0336] In this communication system, a first network element can receive a first request message from a first application function requesting access to data associated with a terminal device. This first request message includes a first identifier, which can be used to indicate the first chip manufacturer and / or the first terminal manufacturer associated with the data. If the first application function is on the data consumer list authorized by the first chip manufacturer and / or the first terminal manufacturer (i.e., the first application function is authorized), meaning the first application function has the permission to access the requested data, the first network element can then grant access to the first data of the first terminal device associated with the first identifier through a first response message. This prevents unauthorized application functions from obtaining terminal data, thus avoiding data leakage and improving the security of the process by which application functions (such as the first application function) acquire data (such as measurement data) from the terminal device.

[0337] For example, Figure 4 A schematic diagram of the architecture of a communication system to which the communication method provided in the embodiments of this application is applicable. Figure 2 .

[0338] like Figure 4 As shown, the communication system mainly includes: a first application function, a first network element, and a second network element.

[0339] The first application function is the same as the above. Figure 3 The first application function is similar and can be used for reference and understanding, so I will not go into details.

[0340] The first network element can be used to collect data from terminal devices and to open or provide the collected data to the first application function. For example, the first network element can be any of the following: a network opening function network element (such as NEF in the aforementioned 5GS), a network data analysis function network element (such as NWDAF in the aforementioned 5GS), or a data collection coordination function network element (such as DCCF), etc. For a detailed description, please refer to the relevant description in the aforementioned 5GS, which will not be repeated here. Alternatively, the first network element can be a network element that implements the corresponding function in other or future communication systems, which is not limited in this application embodiment. It is understood that if the first network element stores a list of consumers allowed by the first application function, the first network element can also verify whether the first application function has the permission to obtain the data it requests, etc., which is not limited.

[0341] The second network element may store at least one of the following: PEI (information) of at least one terminal device (such as the at least one terminal device registered to the second network element, or the second network element used to manage the at least one terminal device), or the association relationship between chip identifier and type allocation code, etc., to determine the terminal device that provides the data requested by the first application function. For example, the second network element may be any of the following: a unified data management network element (such as UDM in the above 5GS), a unified data storage network element (such as UDR in the above 5GS), or an access and mobility management network element (such as AMF in the above 5GS), etc., the specific descriptions of which can be found in the relevant descriptions in the above 5GS, and will not be repeated here; or, the second network element may be a network element that implements the corresponding function in other or future communication systems, and this application embodiment does not limit this. It is understood that if the second network element stores a list of consumers allowed by the first application function, the second network element may also verify whether the first application function has the permission to obtain the data it requests, etc., without limitation.

[0342] In this communication system, a first network element can receive a first request message from a first application function requesting data associated with a terminal device. The first request message includes an identifier indicating a first chip associated with the data, or a first identifier of a first type allocation code. Based on the first request message, the first network element can send a second request message to a second network element. This second request message may include the first identifier and information about the first network element's service area, allowing the second network element to query terminal devices associated with the first identifier and located within the first network element's service area. The first network element receives a second response message from the second network element including the SUPI of the first terminal device. Based on the SUPI of the first terminal device, the first network element can open or provide the first data of the first terminal device to the first application function. This ensures that the first type allocation code includes the type allocation code of the first terminal device, and that the first terminal device is located within the first network element's service area. This guarantees that the first terminal device can provide the data required by the first application function (such as the first data), and that the first network element can collect the first data from the first terminal device, thereby meeting the needs of the first application function and improving the efficiency of the first application function in obtaining data from the terminal device.

[0343] It is understandable that the above Figure 3 and Figure 4 In the communication system shown, the naming of the first application function, the first network element, and the second network element is merely an example and can be replaced with any other possible names without limitation. The term "network element" mentioned in the embodiments of this application is only an exemplary representation and can be replaced with any possible representation, such as "network function," "entity," or "device," without limitation.

[0344] It should be noted that the solutions in the embodiments of this application can also be applied to other communication systems, and the corresponding names can be replaced by the names of the corresponding functions in other communication systems.

[0345] It should be understood that Figures 3-4 This is a simplified diagram for ease of understanding only. The communication system may also include other devices (such as the first terminal device) and / or other network elements. Figures 3-4 It was not drawn in the middle.

[0346] For ease of understanding, the following will combine... Figures 5-9 This paper details the interaction process between various network elements / devices in the aforementioned communication system through specific method embodiments. The communication method provided in this application can be applied to the aforementioned communication system and specifically to various scenarios mentioned in the aforementioned communication system, which will be described in detail below.

[0347] For example, corresponding to question A above, Figure 5 A flowchart illustrating a communication method provided in an embodiment of this application. Figure 1 This communication method is applicable to the above. Figure 3 The communication system shown mainly involves the interaction between a first application function, a first network element, and a second network element (optionally). For example... Figure 5 As shown, the flow of this communication method is as follows:

[0348] S501, the first application function sends a first request message to the first network element. Correspondingly, the first network element receives the first request message from the first application function.

[0349] The first request message can be used to request data associated with the terminal device. That is, the first application function can send a first request message to the first network element to request the required data, such as measurement data from the terminal device. For example, when the first application function needs to obtain data from the terminal device, such as when training a model on the terminal device side, it can send a first request message to the first network element. The first request message will be described in detail below.

[0350] The first request message may include a first identifier, which may be used to indicate a first chip manufacturer and / or a first terminal manufacturer associated with the data. That is, the chip manufacturer of the terminal device providing the data belongs to the first chip manufacturer, and / or the terminal manufacturer of the terminal device providing the data belongs to the first terminal manufacturer. It is understood that the first chip manufacturer may include at least one chip manufacturer, and the first terminal manufacturer may include at least one terminal manufacturer; this application embodiment does not limit this.

[0351] The first identifier will be described in detail below.

[0352] In one possible implementation, the first identifier may include at least one of the following: an identifier of a first chip manufacturer, an identifier of a first terminal manufacturer, an identifier of a first chip, a first type allocation code, or an identifier of a terminal device. That is, the first identifier can be represented by different granularities to meet the needs of different scenarios. These will be described in detail below.

[0353] The identifier of the first chip manufacturer can be used to indicate or identify the first chip manufacturer. For example, the identifier of the first chip manufacturer can be the first chip manufacturer ID, or any other possible identifier, without limitation. In this case, the data requested by the first application function can be data of a terminal device whose chip manufacturer belongs to the first chip manufacturer. That is, the chip manufacturer of the terminal device providing the data requested by the first application function can belong to the first chip manufacturer.

[0354] The identifier of the first terminal manufacturer can be used to indicate or identify the first terminal manufacturer. For example, the identifier of the first terminal manufacturer can be the first terminal manufacturer ID, or any other possible identifier, without limitation. In this case, the data requested by the first application function can be data of a terminal device belonging to the first terminal manufacturer. That is, the terminal manufacturer of the terminal device providing the data requested by the first application function can belong to the first terminal manufacturer.

[0355] The identifier of the first chip can be used to indicate or identify the first chip. For example, the identifier of the first chip can be a first chip ID, or any other possible identifier, without limitation. The first chip can be the chip of the terminal device providing the data. In this case, the data requested by the first application function can be the data of the terminal device whose chip is the first chip. It is understood that the first chip can include at least one chip, and this application embodiment does not limit this. The chip manufacturer of the terminal device whose chip is the first chip can belong to some or all of the aforementioned first chip manufacturers (i.e., the terminal device providing the data requested by the first application function uses the first chip manufacturer's first chip), and / or the terminal manufacturer of the terminal device whose chip is the first chip can belong to some or all of the aforementioned first terminal manufacturers.

[0356] The first type allocation code can be used to identify the manufacturer (or vendor), model, and hardware version (such as chip identifier) ​​of a terminal device (such as a mobile phone), and can be denoted as the first TAC. In this case, the data requested by the first application function can be data from the terminal device with the type allocation code of the first TAC. It is understood that the first type allocation code may include at least one type allocation code, and this application embodiment does not limit this. The chip manufacturer of the terminal device corresponding to the first TAC may belong to the aforementioned first chip manufacturer, and / or the terminal manufacturer of the terminal device corresponding to the first TAC may belong to the aforementioned first terminal manufacturer.

[0357] The identifier of the terminal device can be used to indicate at least one terminal device for which the first application function requests data (i.e., the identifier of the terminal device is used to indicate a list of terminal devices, which may include the at least one terminal device). For example, the identifier of the terminal device can be GPSI, SUPI, or any other possible identifier, without limitation. It is understood that the chip manufacturer of the at least one terminal device may belong to the aforementioned first chip manufacturer, and / or the terminal manufacturer of at least one terminal device may belong to the aforementioned first terminal manufacturer. It is understood that the first network element determines the first chip manufacturer and / or the first terminal manufacturer based on the identifier of the terminal device; the specific implementation of this can be referred to the relevant content in Situations 1 and 2 below, and will not be elaborated further.

[0358] It is understood that, based on the above description of the first chip manufacturer's identifier, the first terminal manufacturer's identifier, the first chip's identifier, the first type allocation code, and the first identifier, the first network element can determine at least one of the following based on one or more of the above: the first chip manufacturer and / or the first terminal manufacturer associated with the data requested by the first application function, the terminal device associated with the data requested by the first application function (as described below as the first terminal device), or the list of allowed consumers corresponding to the data requested by the first application function (such as the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer), etc.

[0359] It should be understood that the above descriptions of the identifier of the first chip manufacturer, the identifier of the first terminal manufacturer, the identifier of the first chip, the first type allocation code, and the first identifier are provided respectively. The identifier of the first chip manufacturer, the identifier of the first terminal manufacturer, the identifier of the first chip, the first type allocation code, or the identifier of the terminal device may be combined or coupled with each other to indicate the relevant information of the terminal device associated with the data requested by the first application function. The implementation principle is similar and can be understood by reference. This application embodiment does not limit this aspect.

[0360] It is understood that the first identifier shown above is only an example, and the first identifier may also be or include any other possible identifiers, which are not limited in this application embodiment.

[0361] Based on the above description, in one possible implementation, the first request message may include any of the following: the identifier of the first application function, the data type, or the first condition.

[0362] The identifier of the first application function can be used to indicate or identify the first application function. For example, the identifier of the first application function may include or specifically include one or more of the following: the ID of the first application function, the vendor ID to which the first application function belongs (such as the chip vendor ID to which the first application function belongs, the terminal vendor ID to which the first application function belongs, etc.), or any other possible identifier, without limitation. For example, the identifier of the first application function may include or specifically include the ID of the first application function, or the identifier of the first application function may include or specifically include the vendor ID to which the first application function belongs, or the identifier of the first application function may include or specifically include the ID of the first application function and the vendor ID to which the first application function belongs.

[0363] Based on the above description, that is, the first request message may include the ID of the first application function, or the first request message may include the vendor ID to which the first application function belongs, or the first request message may include both the ID of the first application function and the vendor ID to which the first application function belongs. This application embodiment does not limit this.

[0364] When the first request message includes the identifier of the first application function, the first network element can directly determine that the first request message comes from the first application function based on the identifier of the first application function, so as to subsequently open the requested data (such as the first data below) to the first application function.

[0365] The data type can be used to indicate or characterize the data type requested by the first application function. For example, the data type may include at least one of the following: channel power delay profile (PDP), channel energy response (CER), channel impulse response (CIR), sounding reference signal (SRS), sensing data, AI data, network data, IoT data, application data, on-network computing data, etc., without limitation. When the first request message includes the data type, the first network element can directly determine the data type of the data requested by the first application function (such as the first data described below satisfying or belonging to that data type) based on the data type, so that subsequent data (such as the first data described below) opened to the first application function satisfies or belongs to that data type.

[0366] The first condition can be used by a first network element or a second network element (named network element #a, where network element #a is the network element used to determine the first terminal device described below) to determine the first terminal device. That is, the first condition can be a filtering or screening condition. The first network element or the second network element (the second request message below includes the first condition) can determine the terminal device that meets the first condition based on the first condition, so that the first network element can subsequently open the first data of the first terminal device to the first application function. The first condition will be described in detail below.

[0367] In one possible implementation, the terminal device corresponds to at least one type allocation code; that is, the terminal device associated with the data requested by the first application function corresponds to at least one type allocation code.

[0368] In this case, the first condition may be used to indicate at least one of the following: a first chip ID, a first chip manufacturer ID, a first terminal manufacturer ID, a terminal device ID, the number of at least one type allocation code, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs.

[0369] The first chip ID can be used to indicate or identify the first chip. The first condition includes that the first chip ID can characterize that the chip of the terminal device associated with the data requested by the first application function is the first chip, or that the first application function is used to request the collection of data from the terminal device whose chip is the first chip.

[0370] The first chip manufacturer ID can be used to indicate or identify the first chip manufacturer. The first condition includes that the first chip manufacturer ID can characterize that the chip manufacturer of the terminal device associated with the data requested by the first application function is the first chip manufacturer, or that the first application function is used to request the collection of data from a terminal device whose chip is the first chip manufacturer.

[0371] The first terminal manufacturer ID can be used to indicate or identify the first terminal manufacturer. The first condition includes that the first terminal manufacturer ID can characterize the terminal manufacturer of the terminal device associated with the data requested by the first application function as the first terminal manufacturer, or that the first application function is used to request the collection of data from the terminal device of the first terminal manufacturer.

[0372] A terminal device ID (such as GPSI, SUPI, etc.) can be used to indicate at least one terminal device for which a first application function requests to obtain its data, or in other words, the first application function is used to request to collect data from at least one terminal device indicated by the terminal device ID.

[0373] The number of at least one type allocation code can indicate the number of TACs. Network element #a (the first network element or the second network element) can determine the number of TACs associated with the data requested by the first application function based on the number of TACs. The number of terminal devices corresponding to each type allocation code in at least one type allocation code can indicate the TAC (data) distribution. Network element #a (the first network element or the second network element) can determine the specific number of terminal devices for each type allocation code in at least one type allocation code based on the TAC distribution. For example, the number of TACs and the TAC (data) distribution can be: the number of TACs corresponding to the first chip ID, the number of TACs corresponding to the first chip manufacturer ID, the number of TACs corresponding to the first terminal manufacturer ID, or the number of TACs corresponding to the terminal device ID, etc., without limitation.

[0374] It is understood that the at least one type allocation code may include a first type allocation code. For example, taking the case where the at least one type allocation code corresponding to a terminal device is the same as the first type allocation code, assume that the first TAC includes TAC#a, TAC#b, and TAC#c. The number of the at least one type allocation code can be 3; the number of terminal devices for each type allocation code in the at least one type allocation code can be characterized as follows: the number of terminal devices with TAC#a is A1, the number of terminal devices with TAC#b is A2, and the number of terminal devices with TAC#c is A3, so that subsequent network element #a can determine the corresponding number of terminal devices for each TAC (such as TAC#a-TAC#c). It is understood that A1, A2, and A3 are positive integers, and the specific values ​​of A1, A2, and A3 are not limited in this application embodiment.

[0375] Information about the region to which the terminal device belongs can be used to indicate that the first application function needs to obtain data from terminal devices within the region to which the terminal device belongs. It is understood that the information about the region to which the terminal device belongs can be represented by latitude and longitude coordinates, cell location, geographic location information, etc., and this application embodiment does not limit this. Network element #a (first network element or second network element) can select a terminal device within the region to which the terminal device belongs based on the information about the region to which the terminal device belongs, such as the first terminal device being located within the region to which the terminal device belongs.

[0376] It is understood that the above is only an example, and the first condition may also include any other possible parameters or information. For example, the first condition may also include the total number of terminal devices corresponding to the at least one type allocation code, the proportion of terminal devices for each type allocation code in the total number of terminal devices for the at least one type allocation code, the capability requirements (such as processing power) of the first application function on the terminal devices, etc. This application embodiment does not limit this.

[0377] Based on the above description, the first request message may also include any other possible parameters or information, such as data reporting methods, etc., and this application embodiment does not limit this.

[0378] Based on the above introduction, in one possible implementation, the first request message may include at least one of the following: a first identifier, an identifier of a first application function, a data type, a first condition, etc., without limitation.

[0379] It is understood that the first application function can directly send the first request message to the first network element (without going through other network elements). In this case, the first network element can be NEF or NWDAF. Alternatively, the first application function can send the first request message to the first network element through other network elements (such as NEF). In this case, the first network element can be NWDAF. The first application function can send the first request message to NWDAF through NEF. For example, the first application function can send the first request message to NEF, and NEF can send a third request message to NWDAF (determined according to the first request message) based on the first request message. This third request message can be used to request data associated with the terminal device. The third request message can include at least one of the following: a first identifier, an identifier of the first application function, the data type, a first condition, etc., without limitation. It is understood that this third request message is similar to the first request message mentioned above and can be understood by reference without limitation.

[0380] It is understood that the naming of the first request message, the first identifier, the first chip manufacturer, the first terminal manufacturer, the first chip, the first type allocation code, the first condition, and the third request message is merely an example and can be replaced with any other possible naming without limitation.

[0381] S502, if the first application function belongs to the data consumer list permitted by the first chip manufacturer and / or the first terminal manufacturer, the first network element sends a first response message to the first application function. Correspondingly, the first application function receives the first response message from the first network element.

[0382] The first response message may include first data associated with the first terminal device, which may be associated with a first identifier. It is understood that when the first application function belongs to the data consumer list permitted by the first chip manufacturer and / or the first terminal manufacturer, the first application function may have the permission to obtain data associated with the first identifier. In this case, the first network element can send the first data of the first terminal device associated with the first identifier to the first application function through the first response message. The following uses cases 1 and 2 as examples to specifically describe step S502.

[0383] Scenario 1: The first network element determines the first terminal device itself.

[0384] In one possible implementation, the above method embodiment may further include:

[0385] The first network element obtains a list (or set) of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer based on the first request message.

[0386] If the first application function belongs to the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer, the first network element determines that the first application function has the right to obtain data.

[0387] That is, in case 1, the first network element stores a list of data consumers permitted by at least one chip manufacturer (including the first chip manufacturer) and / or at least one terminal manufacturer (including the first terminal manufacturer).

[0388] In one possible implementation, the list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer can be pre-configured or predefined. The list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer can include the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer, which is simple to implement.

[0389] Alternatively, the above method embodiments may further include:

[0390] The first network element receives a list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer.

[0391] Specifically, the first network element can receive a list of data consumers permitted by at least one chip manufacturer and / or at least one terminal manufacturer. For example, at least one chip manufacturer and / or at least one terminal manufacturer can send their list of permitted data consumers to the first network element via a registration (request) message. Alternatively, other network elements or devices that store a list of data consumers permitted by at least one chip manufacturer and / or at least one terminal manufacturer can send such a list to the first network element. This list of data consumers permitted by at least one chip manufacturer and / or at least one terminal manufacturer may include the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer, thus enabling flexibility.

[0392] For ease of understanding, the following explanation will use an example of an allowed data consumer list that applies to both chip manufacturers and terminal manufacturers.

[0393] For example, taking the example of at least one chip manufacturer and at least one terminal manufacturer sending their list of allowed data consumers to the first network element via a registration message, based on the above, OTT (i.e., AF) can be divided into chip OTT and / or terminal OTT. Taking chip OTT as an example, at least one chip OTT (associated with at least one chip manufacturer, such as the chip manufacturer corresponding to at least one chip OTT being at least one chip manufacturer) can send a registration message to the first network element. Taking one of the at least one chip OTTs, such as chip OTT#1, as an example, chip OTT#1 can send registration message #1 to the first network element. This registration message #1 may include: the chip manufacturer ID of chip OTT#1, the chip ID of chip OTT#1, the list of data consumers supported (allowed) by chip OTT#1, etc.

[0394] It is understandable that the above description, using the example of chip OTT #1 sending registration message #1 to the first network element, illustrates the principle behind other chip OTTs within at least one chip OTT sending registration messages to the first network element. This is similar to the process of chip OTT #1 sending registration message #1 to the first network element and will not be elaborated upon further. In this way, the first network element can obtain a list of data consumers permitted by at least one chip manufacturer. It should be understood that at least one chip OTT can provide services to chip OTTs managed by the first network element, or the first network element can provide services to them.

[0395] Taking terminal OTT as an example, at least one terminal OTT (associated with at least one terminal manufacturer, such as the terminal manufacturer corresponding to at least one terminal OTT being at least one terminal manufacturer) can send a registration message to the first network element, and at least one chip OTT (associated with at least one terminal manufacturer) can send a registration message to the first network element. Taking one of the at least one terminal OTTs, such as terminal OTT#1, as an example, terminal OTT#1 can send a registration message #2 to the first network element. The registration message #2 may include: the terminal manufacturer ID of terminal OTT#1, the type allocation code of terminal OTT#1, the device information of terminal OTT#1 (i.e., hardware or software information, such as chip ID, etc.), and the list of data consumers supported (allowed) by terminal OTT#1 #2, etc.

[0396] As can be understood, the above example of terminal OTT #1 sending registration message #2 to the first network element is used as an example. The implementation principle of other terminal OTTs in at least one terminal OTT sending registration messages to the first network element is similar to that of terminal OTT #1 sending registration message #2 to the first network element. This can be understood by referring to the example and will not be elaborated further. In this way, the first network element can obtain a list of data consumers allowed by at least one terminal manufacturer. It should be understood that at least one terminal OTT can be a terminal OTT managed by or providing services to the first network element.

[0397] Based on this, the first network element can obtain at least one list of data consumers allowed by chip OTT and / or at least one list of data consumers allowed by terminal OTT. The first network element can integrate or merge the list of data consumers allowed by at least one chip OTT and / or at least one list of data consumers allowed by terminal OTT, and the integrated or merged list of data consumers is called list #1. For example, if the chip ID of chip OTT #1 in registration message #1 is the same as the chip ID in registration message #2, then the first network element can integrate or merge consumer list #1 and consumer list #2 (e.g., take the intersection) to obtain consumer list #a (belonging to list #1). This consumer list #a can be an allowed consumer list applicable to both terminal OTT #1 and chip OTT #1.

[0398] It is understood that list #1 may include at least one consumer list, such as consumer list #a. Each consumer list in list #1 can be at the chip manufacturer granularity, terminal manufacturer granularity, chip granularity, type allocation code granularity, or terminal device granularity, etc., without limitation.

[0399] It is understood that the above is merely an example, and the first network element may obtain a list of data consumers allowed by at least one chip OTT and / or at least one terminal OTT through any other possible means, without limitation.

[0400] Based on the above description, after the first network element obtains the list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer, the first network element can determine the data consumer list associated with the first identifier from the list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer, i.e., the aforementioned list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer, according to the first request message, such as the first identifier in the first request message. As can be seen from the above description, each consumer list in list #1 can be at the chip manufacturer granularity, terminal manufacturer granularity, chip granularity, type allocation code granularity, or terminal device granularity. Therefore, the granularity of each consumer list in list #1 can be associated with the parameters carried by the first identifier.

[0401] For example, the first identifier includes a first type allocation code, so each consumer list in list #1 can be at the type allocation code granularity, and each type allocation code can correspond to an allowed data consumer list. Taking list #1 as including consumer list #a, consumer list #b, and consumer list #c as an example, assuming consumer list #a is associated with TAC#a1, consumer list #b is associated with TAC#b1, and consumer list #c is associated with TAC#c1. Assuming the first type allocation code is TAC#a1, the first network element can determine the consumer list #a associated with TAC#a1 in list #1 based on TAC#a1. Consumer list #a is the data consumer list allowed by the first chip manufacturer and / or the first terminal manufacturer.

[0402] After the first network element obtains the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer, the first network element can determine whether the first application function belongs to the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer. If the first application function belongs to the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer, the first network element can determine that the first application function has the permission to obtain the data it requests; otherwise, the first network element can determine that the first application function does not have the permission to obtain the data it requests.

[0403] It is understood that the above is merely an example. For instance, the data consumer list permitted by the first chip manufacturer and / or the first terminal manufacturer can also be replaced with a data consumer list not permitted by the first chip manufacturer and / or the first terminal manufacturer. In this case, if the first application function belongs to the data consumer list not permitted by the first chip manufacturer and / or the first terminal manufacturer, the first network element can determine that the first application function does not have permission to obtain the data it requests; if the first application function does not belong to the data consumer list not permitted by the first chip manufacturer and / or the first terminal manufacturer, the first network element can determine that the first application function has permission to obtain the data it requests. This application embodiment does not limit this.

[0404] Based on the above description, in one possible design scheme, the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer may include at least one of the following: an application function identifier, a chip identifier, an application function identifier of the chip manufacturer, an application function identifier of the chip manufacturer, or an application function identifier of the terminal manufacturer, or an identifier of the terminal manufacturer. Wherein, the application function may include a first application function, the chip identifier may include the identifier of the first chip, the chip manufacturer may include the first chip manufacturer, and the terminal manufacturer may include the first terminal manufacturer. That is, the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer can be represented by different granularities to meet the needs of different scenarios.

[0405] For example, suppose the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer includes the identifier of the application function, and the first request message includes the identifier of the first application function. If the identifier of the application function includes the identifier of the first application function, then the first network element can determine that the first application function has the permission to obtain the data it requests.

[0406] For example, suppose the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer includes the chip manufacturer's identifier, and the first request message includes the identifier of the first application function. In this case, if the chip manufacturer corresponding to the first application function belongs to the list of chip manufacturers indicated or identified by the chip manufacturer's identifier, then the first network element can determine that the first application function has the permission to obtain the data it requests.

[0407] For example, suppose the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer includes the identifier of the terminal manufacturer, and the first request message includes the identifier of the first application function. In this case, if the terminal manufacturer corresponding to the first application function belongs to the list of terminal manufacturers indicated or identified by the identifier of the terminal manufacturer, then the first network element can determine that the first application function has the permission to obtain the data it requests.

[0408] For example, suppose the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer includes chip identifiers, and the first request message includes an identifier for a first application function. In this case, if the chip corresponding to the first application function belongs to the list of chips indicated or identified by the chip identifier, the first network element can determine that the first application function has the permission to obtain the data it requests.

[0409] It is understood that the above is only an example. When the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer includes the other parameters mentioned above (such as the application function identifier of the chip manufacturer and the application function identifier of the terminal manufacturer), the implementation principle of the first network element verifying whether the first application function has the permission to obtain the requested data is similar to the example above. It can be referred to for understanding and will not be elaborated further.

[0410] Based on the above description, when the first network element determines that the first application function has the permission to obtain the requested data, it can determine the terminal device that provides the requested data to the first application function, as described below. The specific implementation of the first network element determining the first terminal device is described below.

[0411] In one possible implementation, the above method embodiment further includes:

[0412] The first network element obtains the first information based on the PEI (information) of at least one terminal device (each).

[0413] The first network element determines the first terminal device based on the PEI of at least one terminal device, the first information, and the first request message.

[0414] The first network element may store the PEI of the at least one terminal device (including the first terminal device). For example, the at least one terminal device may be a terminal device registered to the first network element, or the first network element may be used to manage the at least one terminal device, without limitation.

[0415] The PEI of at least one terminal device can be pre-configured or pre-defined; or, the PEI of at least one terminal device can be sent to the first network element by at least one terminal device. For example, at least one terminal device can send its own PEI to the first network element, or, if the first network element does not receive the PEI of at least one terminal device, the first network element can send PEI request messages to at least one terminal device to request to obtain the PEI of at least one terminal device; or, the PEI of at least one terminal device can be sent to the first network element by other network elements or devices that store the PEI of the at least one terminal device.

[0416] It is understood that the above is merely an example, and the first network element may also obtain the PEI of the at least one terminal device (each) in any other possible way, without limitation.

[0417] Based on the above description of technical terminology, the PEI may include a TAC (Technical Identifier), used to identify the manufacturer (or vendor), model, and hardware version (such as chip ID) of the terminal device. Therefore, the first network element can determine the TAC of at least one terminal device based on its respective PEI. The first network element can determine the first information based on the TAC of at least one terminal device, such as by querying the Equipment Identity Register (EIR) or the UDM (User Device Manager). The first information can be used to indicate at least one of the following: information about the chip manufacturer of at least one terminal device (including the first terminal device) (such as the identifier of the chip manufacturer of at least one terminal device), information about the terminal manufacturer of at least one terminal device (such as the identifier of the terminal manufacturer of at least one terminal device), or information about the chip of at least one terminal device (such as the identifier of the chip of at least one terminal device), etc. It is understood that the above is only an example, and the first network element can obtain the first information in any other possible way. This application embodiment does not limit this.

[0418] After the first network element obtains the first information, it can filter at least one terminal device based on the PEI of at least one terminal device, the first information, and the first request message to obtain the first terminal device. That is, at least one terminal device may include the first terminal device. The first terminal device may satisfy at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device, the first terminal manufacturer includes the terminal manufacturer of the first terminal device, or the first chip includes the chip of the first terminal device.

[0419] It is understood that, based on the fact that the first chip manufacturer includes at least one chip manufacturer, the first terminal manufacturer includes at least one terminal manufacturer, and the first chip may include at least one chip, the chip manufacturer of the first terminal device can be a subset or the entire set of the first chip manufacturers, the terminal manufacturer of the first terminal device can be a subset or the entire set of the first terminal manufacturers, and the chip of the first terminal device can be a subset or the entire set of the first chips.

[0420] For example, the first network element can select a terminal device (denoted as a candidate terminal device) from at least one terminal device that meets the following conditions: the chip manufacturer belongs to the first chip manufacturer, the terminal manufacturer belongs to the first terminal manufacturer, or the chip belongs to the first chip manufacturer. After the first network element determines the candidate terminal devices, it can further filter or select a terminal device that meets the first condition from the candidate terminal devices, i.e., the first terminal device.

[0421] Optionally, the first network element can further filter or select terminal devices from the candidate terminal devices that meet the first condition and are located within the service area of ​​the first network element, i.e., the first terminal device, by combining the first condition and its own service area information, to ensure that the first network element can collect data from the first terminal device. It can be understood that if the first condition includes information about the region to which the terminal device belongs, the service area of ​​the first network element and the region to which the terminal device belongs can be the same or overlap. In this case, the first terminal device is located both within the service area of ​​the first network element and within the region to which it belongs; in other words, the first terminal device is located in the overlapping portion of the service area of ​​the first network element and the region to which the terminal device belongs.

[0422] Based on the above introduction, in one possible design scheme, if the first identifier includes the identifier of the terminal device, such as the identifier of the terminal device being the GPSI of the terminal device, the above method embodiment may further include:

[0423] The first network element determines the SUPI corresponding to the GPSI based on the GPSI of the terminal device;

[0424] The first network element determines the first type allocation code corresponding to the SUPI based on the SUPI;

[0425] The first network element determines the first chip manufacturer and / or the first terminal manufacturer based on the first type of allocation code.

[0426] It is understood that there is a correlation between GPSI and SUPI, and between SUPI and PEI. The first network element can determine the SUPI corresponding to the GPSI based on the correlation between GPSI and SUPI, and determine the PEI corresponding to the SUPI based on the correlation between SUPI and PEI. The first network element can then determine the corresponding type allocation code, i.e., the aforementioned first type allocation code, based on the obtained PEI. After obtaining the first type allocation code, the first network element can determine the first chip manufacturer and / or the first terminal manufacturer corresponding to the first type allocation code.

[0427] It should be understood that if the identifier of the terminal device included in the first identifier is the SUPI of the terminal device, then the first network element can directly determine the PEI corresponding to the SUPI based on the association between the SUPI and PEI. The first network element can determine the corresponding type allocation code, i.e., the aforementioned first type allocation code, based on the obtained PEI. After obtaining the first type allocation code, the first network element can determine the first chip manufacturer and / or the first terminal manufacturer corresponding to the first type allocation code based on the first type allocation code.

[0428] Based on the above description, in scenario 1, the first network element can directly verify whether the first application function has the permission to obtain the requested data without querying other network elements (such as the second network element) or devices, thereby reducing signaling interaction of the first network element and reducing resource overhead. In addition, the first network element can determine the first terminal device itself without querying other network elements (such as the second network element) or devices, thereby reducing signaling interaction of the first network element and reducing resource overhead.

[0429] Scenario 2: The first network element queries the second network element to obtain the first terminal device.

[0430] In scenario 2, one possible implementation of the above method embodiment may further include:

[0431] S502a, the first network element sends a second request message to the second network element based on the first request message. Correspondingly, the second network element receives the second request message from the first network element.

[0432] In S502b, the second network element sends a second response message to the first network element based on the second request message. Correspondingly, the first network element receives the second response message from the second network element.

[0433] That is, in scenario 2, the first network element can send a second request message to the second network element based on the received first request message (e.g., if the first network element does not store the PEI of at least one terminal device (including the first terminal device)). This second request message can be used to request the acquisition of the terminal device associated with the first identifier. The second request message is determined based on the first request message. This second request message may include the aforementioned first identifier; that is, the first network element can send the first identifier from the first request message to the second network element via the second request message. In other words, the first identifier in the second request message may originate from the first application function.

[0434] Based on the above introduction, the specific implementation of the second network element determining the first terminal device will be described below.

[0435] In one possible implementation, the above method embodiment may further include:

[0436] The second network element obtains the second information based on the PEI of at least one terminal device (each).

[0437] The second network element determines the first terminal device based on the PEI of at least one terminal device, the second information, and the second request message.

[0438] The second network element stores the PEI of at least one terminal device (each). For example, the second network element can be used to manage the at least one terminal device (e.g., the second network element can be a UDM or UDR), or the at least one terminal device can be a terminal device registered to the second network element (e.g., the second network element can be an AMF). The second information can be used to indicate at least one of the following: information about the chip manufacturer of each of the at least one terminal device, information about the terminal manufacturer of each of the at least one terminal device, or information about the chip of each of the at least one terminal device.

[0439] It is understandable that the second information is similar to the first information in Case 1 above, and can be understood by reference without further explanation. The implementation principle of the second network element obtaining the second information based on the PEI of at least one terminal device (each) is similar to the implementation principle of the first network element obtaining the first information based on the PEI of at least one terminal device (each) in Case 1 above, and can be understood by reference without further explanation.

[0440] At least one terminal device may include a first terminal device, which may satisfy at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device; the first terminal manufacturer includes the terminal manufacturer of the first terminal device; or the first chip includes the chip of the first terminal device. It is understood that the second network element determines the implementation principle of the first terminal device based on the PEI, second information, and second request message of at least one terminal device. This is similar to the first network element determining the implementation principle of the first terminal device based on the PEI, first information, and first request message of at least one terminal device in Case 1 above, and can be understood by reference only; further details are omitted.

[0441] In conjunction with the above description, in one possible implementation, the second request message may further include a first condition and information about the service area of ​​the first network element. The first condition can be used to determine the first terminal device, which is located within the service area of ​​the first network element.

[0442] That is, the first network element can send the first condition in the first request message and its own service area information to the second network element through the second request message, so that the second network element can determine the first terminal device that meets the first condition and is located in the service area of ​​the first network element. The specific implementation can be referred to the relevant content in Case 1 above, and will not be repeated here.

[0443] It is understood that the second request message may also include any other possible parameters or information, such as the identifier of the first application function, the data type of the data requested by the first application function, and the capability requirements of the first application function on the terminal device (such as processing power), without limitation.

[0444] It should be understood that the first network element can pass the first request message through to the second network element, in which case the first request message and the second request message are the same; or, the first network element can process the first request message and then send it to the second network element through the second request message, in which case the first request message and the second request message are different.

[0445] Based on the above introduction, in one possible design scheme, if the first identifier includes the identifier of the terminal device, such as the identifier of the terminal device being the GPSI of the terminal device, the above method embodiment may further include:

[0446] The second network element determines the SUPI corresponding to the GPSI based on the GPSI of the terminal device;

[0447] The second network element determines the first type allocation code corresponding to the SUPI based on the SUPI.

[0448] The second network element determines the first chip manufacturer and / or the first terminal manufacturer based on the first type of allocation code.

[0449] It is understandable that the implementation principle of this process is similar to that of the first network element in situation 1 above, which determines the first chip manufacturer and / or the first terminal manufacturer based on the GPSI of the terminal device. This can be understood by reference and will not be elaborated further.

[0450] Based on the above introduction, the second network element can also verify whether the first application function has the permission to obtain the data it requests, which will be described in detail below.

[0451] In one possible implementation, the above method embodiment may further include:

[0452] The second network element obtains the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer based on the second request message.

[0453] If the first application function belongs to the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer, the second network element determines that the first application function has the right to obtain data.

[0454] It is understood that in scenario 2, the second network element can store a list of data consumers permitted by at least one chip manufacturer (including the first chip manufacturer) and / or at least one terminal manufacturer (including the first terminal manufacturer). The second network element can determine the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer from the list of data consumers permitted by at least one chip manufacturer and / or at least one terminal manufacturer, based on a second request message, such as a first identifier in the second request message (the first identifier comes from the first application function). If the first application function belongs to the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer, it can determine that the first application function has the permission to obtain the requested data. It is understood that the second network element can trigger subsequent steps, such as identifying the first terminal device and sending a second response message to the first network element, only after determining that the first application function has the permission to obtain the requested data. Conversely, the second network element can avoid performing steps such as identifying the first terminal device and sending a second response message to the first network element. This improves communication efficiency, reduces the resource overhead of the second network element, and enhances the security of the process by which the first application function obtains data from the terminal device.

[0455] Based on the above description, in one possible implementation, the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer can be pre-configured or predefined, which is simple to implement; or, the above method embodiments may further include:

[0456] The second network element receives a list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer.

[0457] It is understood that the second network element can receive a list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer. This list of data consumers allowed by at least one chip manufacturer and / or at least one terminal manufacturer may include a list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer. The implementation principle is similar to that of the second network element receiving the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer in case 1 above. It can be understood by reference and will not be elaborated further.

[0458] In one possible implementation, the list of data consumers permitted by the first chip manufacturer and / or the first terminal manufacturer includes at least one of the following: an identifier of an application function, an identifier of an application function of the chip manufacturer, an identifier of the chip manufacturer, an identifier of an application function of the terminal manufacturer, or an identifier of the terminal manufacturer.

[0459] The application function may include the first application function, the chip manufacturer may include the first chip manufacturer, and the terminal manufacturer may include the first terminal manufacturer. For details, please refer to the relevant content in Case 1 above, which will not be repeated here.

[0460] Based on the above description, after the second network element determines the first terminal device associated with the first identifier, it can send the identifier of the first terminal device, such as the SUPI or GPSI of the first terminal device, to the first network element through a second response message. That is, the second response message can include the SUPI, GPSI, or any other possible identifier of the first terminal device, without limitation. The second response message can be a response message to the second request message. For ease of understanding, the following description will use the example of the second response message including the SUPI of the first terminal device. The first network element can determine that the first terminal device is the terminal device used to provide the requested data for the first application function based on the SUPI of the first terminal device in the second response message. That is, in case 2, the first terminal device can be determined based on the SUPI of the first terminal device in the second response message.

[0461] It is understood that the second response message may also include any other possible parameters or information. For example, when the second request message is also used to request data associated with the terminal device, and the second network element has the ability to collect data from the terminal device, the second network element may also collect data from the first terminal device (e.g., by establishing a user plane connection with the first terminal device), such as first data, and send the collected first data from the first terminal device to the first network element through the second response message. In this case, the second response message may also include the first data from the first terminal device, etc. This application embodiment does not limit this.

[0462] Combining Situations 1 and 2 above, if the first application function belongs to the data consumer list permitted by the first chip manufacturer and / or the first terminal manufacturer, and the first network element determines that the first terminal device is the terminal device used to provide the data requested by the first application function, and if the second response message does not include the first data, in one possible implementation, the above method embodiment may further include:

[0463] The first network element collects the first data from the first terminal device.

[0464] The first network element sends a first response message to the first application function, including:

[0465] The first network element sends a first response message to the first application function based on the first data.

[0466] For example, the first network element can establish a user plane connection with the first terminal device to collect first data from the first terminal device. The specific implementation of this can be found in existing technology and will not be elaborated further. It is understood that the first terminal device may include at least one terminal device. The first network element can aggregate the data collected from at least one terminal device and send it to the first application function via a first response message. That is, the first response message may include the first data associated with the first terminal device. The first response message can be a response to a first request message.

[0467] Optionally, the first response message may also include a type assignment code for the first terminal device and / or an identifier for the chip of the first terminal device.

[0468] For example, the first network element can de-identify or anonymize the first data, such as converting the SUPI of the first terminal device into an identifier that can be recognized by the first application function, such as the type allocation code of the first terminal device and / or the chip identifier of the first terminal device, and sending it to the first application function through a first response message, so that the first application function can determine the type allocation code and / or the chip identifier corresponding to the first data.

[0469] In conjunction with scenario 2 above, if the second network element sends the first data collected from the first terminal device to the first network element via a second response message, the first network element can directly send the first data from the first terminal device to the first application function via a first response message based on the second response message. In this case, the first network element does not need to perform the step of collecting the first data, thereby reducing the capability requirements and resource overhead of the first network element. It is understood that the above steps S502a-S502b are optional steps, and this application embodiment does not limit them.

[0470] It is understandable that the first response message may include any other possible parameters or information, without limitation.

[0471] The first application function can obtain the required first data based on the received first response message, and use the data to perform subsequent steps, such as training the model on the first terminal device side. For its specific implementation, please refer to the existing technology, which will not be elaborated here.

[0472] It is understood that the naming of the first response message, the first terminal device, the first data, the consumer list, the first information, the second information, the second request message, and the second response message is merely an example and can be replaced with any other possible names without limitation.

[0473] In summary, the first network element can receive a first request message from a first application function requesting access to data associated with a terminal device. This first request message includes a first identifier, which can be used to indicate the first chip manufacturer and / or the first terminal manufacturer associated with the data. If the first application function is on the data consumer list permitted by the first chip manufacturer and / or the first terminal manufacturer (i.e., the first application function is authorized), meaning the first application function has the permission to access the requested data, the first network element can then grant access to the first data of the first terminal device associated with the first identifier through a first response message. This prevents unauthorized application functions from obtaining terminal data, thus avoiding data leakage and improving the security of the process by which application functions (such as the first application function) acquire data (such as measurement data) from the terminal device.

[0474] It is understood that the above steps S501-S502 use the first identifier to indicate the first chip manufacturer and / or the first terminal manufacturer associated with the data as an example. In other words, when verifying the permissions of the first application function, the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer associated with the data requested by the first application function is used as an example of the list of data consumers allowed for the requested data (i.e., the granularity of the chip manufacturer and / or the terminal manufacturer). The following steps will be used as an example to specifically describe the list of data consumers allowed for the data requested by the first application function as the TAC granularity.

[0475] For example, the method may include:

[0476] Step 1: The first application function sends a first request message to the first network element. Correspondingly, the first network element receives the first request message from the first application function.

[0477] The first request message can be used to request data associated with a terminal device. The first request message may include a first identifier, which may include a first type allocation code. The first type allocation code can be used to identify the manufacturer (or vendor), model, and hardware version (such as a chip identifier) ​​of the terminal device (e.g., a mobile phone), and can be denoted as a first TAC. In this case, the data requested by the first application function can be data from the terminal device with the type allocation code of the first TAC. It is understood that the first type allocation code may include at least one type allocation code, and this embodiment does not limit this.

[0478] In one possible implementation, the first request message may include at least one of the following: an identifier of the first application function, information about the manufacturer to which the first application function belongs (such as the chip manufacturer ID and / or the terminal manufacturer ID to which the first application function belongs), information about the chip corresponding to the first application function (such as the chip ID corresponding to the first application function), the data type, or a first condition. The first condition can be used to determine the first terminal device. It is understood that the information about the manufacturer to which the first application function belongs and the information about the chip corresponding to the first application function in the first request message can be used in subsequent steps (step 2 below) to determine whether the first application function has permission to obtain the requested data. For a detailed description, please refer to the relevant content in step 2 below; it will not be repeated here.

[0479] It is understood that the identifier of the first application function may include or specifically include one or more of the following: the ID of the first application function, the vendor ID to which the first application function belongs (such as the chip vendor ID to which the first application function belongs, the terminal vendor ID to which the first application function belongs, etc.), or any other possible identifier, without limitation.

[0480] For example, the identifier of the first application function may include or specifically be the ID of the first application function, or the identifier of the first application function may include or specifically be the vendor ID to which the first application function belongs, or the identifier of the first application function may include or specifically be the ID of the first application function and the vendor ID to which the first application function belongs. It is understood that when the identifier of the first application function includes the vendor ID to which the first application function belongs, the first request message may not include the vendor information to which the first application function belongs, and this application embodiment does not limit this.

[0481] Based on the above description, that is, the first request message may include the ID of the first application function, or the first request message may include the vendor ID to which the first application function belongs, or the first request message may include both the ID of the first application function and the vendor ID to which the first application function belongs. This application embodiment does not limit this.

[0482] In one possible implementation, the terminal device corresponds to at least one type allocation code. The first condition can be used to indicate at least one of the following: a first chip ID, a first chip manufacturer ID, a first terminal manufacturer ID, a terminal device ID, the number of at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs. Wherein, the first terminal device is located within the region to which the terminal device belongs; its specific description can be found in the relevant content of step S501 above, and will not be repeated here.

[0483] It is understood that the first application function can directly send the first request message to the first network element (without going through other network elements). In this case, the first network element can be NEF or NWDAF. Alternatively, the first application function can send the first request message to the first network element through other network elements (such as NEF). In this case, the first network element can be NWDAF. The first application function can send the first request message to NWDAF through NEF. For example, the first application function can send the first request message to NEF, and NEF can send a third request message to NWDAF (determined according to the first request message) based on the first request message. This third request message can be used to request data associated with the terminal device. The third request message can include at least one of the following: a first identifier, an identifier of the first application function, the data type, a first condition, etc., without limitation. It is understood that this third request message is similar to the first request message mentioned above and can be understood by reference without limitation.

[0484] It should be understood that step 1 is similar to step S501 above, and can be understood by reference, without further explanation.

[0485] It is understood that the naming of the first request message, the first identifier, the first chip manufacturer, the first terminal manufacturer, the first chip, the first type allocation code, and the first condition is merely an example, and can be replaced with any other possible naming without limitation.

[0486] Step 2: If the first application function belongs to the list of data consumers allowed by the first type of allocation code, a first response message is sent to the first application function. Correspondingly, the first application function receives the first response message from the first network element.

[0487] The first response message may include first data associated with the first terminal device, which is associated with a first identifier (i.e., the first TAC mentioned above).

[0488] It is understandable that when the first application function belongs to the data consumer list allowed by the first type of allocation code, the first application function has the permission to obtain data associated with the first identifier. At this time, the first network element can send the first data of the first terminal device associated with the first identifier to the first application function through the first response message. The following uses cases 3 and 4 as examples to specifically introduce step 2.

[0489] Scenario 3: The first network element determines the first terminal device itself.

[0490] In one possible implementation, the above method embodiment may further include:

[0491] The first network element obtains the list of data consumers allowed by the first type of allocation code based on the first request message.

[0492] If the first application function belongs to the list of data consumers allowed by the first type of allocation code, the first network element determines that the first application function has the right to obtain data.

[0493] That is, in case 3, the first network element stores a list of data consumers allowed by at least one type allocation code (including the first type allocation code).

[0494] In one possible implementation, the list of data consumers allowed by at least one type allocation code can be pre-configured or predefined, and the list of data consumers allowed by at least one type allocation code can include the list of data consumers allowed by the first type allocation code, which is simple to implement.

[0495] Alternatively, the above method example may also include: the first network element receiving a list of data consumers allowed by the first type of allocation code.

[0496] Specifically, the first network element can receive at least one list of data consumers allowed by a type allocation code. For example, other network elements or devices that store at least one list of data consumers allowed by a type allocation code can send the list of data consumers allowed by the at least one type allocation code to the first network element. The list of data consumers allowed by the at least one type allocation code may include the list of data consumers allowed by the first type allocation code, thus achieving flexibility.

[0497] Based on the above introduction, in one possible design scheme, the first type of allocation code is associated with the first chip manufacturer and / or the first terminal manufacturer associated with the data; the list of data consumers allowed by the first type of allocation code is determined according to the list of data consumers allowed by the first chip manufacturer and / or the list of data consumers allowed by the first terminal manufacturer.

[0498] That is, the chip manufacturer of the terminal device corresponding to the first type of allocation code can belong to the aforementioned first chip manufacturer, and / or the terminal manufacturer of the terminal device corresponding to the first TAC can belong to the aforementioned first terminal manufacturer. The following section provides a detailed description of the data consumer list allowed by the first type of allocation code, determined based on the data consumer list allowed by the first chip manufacturer, and / or the data consumer list allowed by the first terminal manufacturer.

[0499] For example, taking the data consumer list allowed by the first type of allocation code as determined based on the data consumer list allowed by the first chip manufacturer and the data consumer list allowed by the first terminal manufacturer, assume that the consumer list allowed by the first chip manufacturer includes list #a1, list #a2, and list #a3, wherein list #a1 is associated with TAC#1 (i.e., list #a1 is the consumer list allowed by TAC#1), list #a2 is associated with TAC#2 (i.e., list #a2 is the consumer list allowed by TAC#2), and list #a3 is associated with TAC#3 (i.e., list #a3 is the consumer list allowed by TAC#3); assume that the consumer list allowed by the first terminal manufacturer includes list #b1, list #b2, and list #b3, wherein list #b1 is associated with TAC#1 (i.e., list #b1 is the consumer list allowed by TAC#1), list #b2 is associated with TAC#2 (i.e., list #b2 is the consumer list allowed by TAC#2), and list #b3 is associated with TAC#4 (i.e., list #b3 is the consumer list allowed by TAC#4).

[0500] The first network element can integrate or merge the consumer lists permitted by the first chip manufacturer and the consumer lists permitted by the first terminal manufacturer, and the integrated or merged data consumer list is called list #2. For example, the first network element can take the intersection of consumer lists permitted by the same TAC, such as taking the intersection of list #a1 and list #b1 to obtain list #c1, which can be the consumer list permitted by TAC#1; similarly, the first network element can take the intersection of list #a2 and list #b2 to obtain list #c2, which can be the consumer list permitted by TAC#2; the first network element can determine list #a3 as the consumer list permitted by TAC#3, and combine list #b3 with the consumer list permitted by TAC#4. The above lists #c1, #c2, #a3, and #b3 can form list #2 (such as the data consumer list permitted by at least one type allocation code mentioned above).

[0501] It is understandable that list #2 can also be sent directly to the first network element from other network elements. In this case, the first network element does not need to perform the steps described above, such as taking the intersection of list #a1 and list #b1, to reduce the resource overhead of the first network element, and there is no limitation. List #2 can include at least one consumer list, such as list #c1, list #c2, list #a3, and list #a3 mentioned above. Each consumer list in list #2 can be at the chip manufacturer granularity, terminal manufacturer granularity, chip granularity, type allocation code granularity, or terminal device granularity, etc., and there is no limitation.

[0502] It is understood that the above is only an example, and the first network element can also obtain the list of data consumers allowed by the first type of allocation code in any other possible way, without limitation.

[0503] Based on the above description, after the first network element obtains a list of data consumers allowed by at least one type allocation code, the first network element can determine the list of data consumers associated with the first identifier, i.e., the list of consumers allowed by the aforementioned first type allocation code, from the list of data consumers allowed by at least one type allocation code, according to a first request message, such as the first TAC in the first request message. For example, assuming the first TAC is TAC#1, the first network element can determine, based on TAC#1, that the list of consumers allowed by TAC#1 can be list #c1 in list #2.

[0504] After the first network element obtains the list of data consumers allowed by the first type of allocation code, the first network element can determine whether the first application function belongs to the list of data consumers allowed by the first type of allocation code. If the first application function belongs to the list of data consumers allowed by the first type of allocation code, the first network element can determine that the first application function has the permission to obtain the data it requests; otherwise, the first network element can determine that the first application function does not have the permission to obtain the data it requests.

[0505] It is understood that the above is merely an example. For instance, the list of data consumers allowed by the first type of allocation code can also be replaced with a list of data consumers not allowed by the first type of allocation code. In this case, if the first application function belongs to the list of data consumers not allowed by the first type of allocation code, the first network element can determine that the first application function does not have permission to obtain the data it requests; if the first application function does not belong to the list of data consumers not allowed by the first type of allocation code, the first network element can determine that the first application function has permission to obtain the data it requests. This application embodiment does not limit this aspect.

[0506] Based on the above description, in one possible design scheme, the list of data consumers allowed by the first type of allocation code may include at least one of the following: an application function identifier, a chip identifier, an application function identifier from a chip manufacturer, an identifier from a chip manufacturer, an application function identifier from a terminal manufacturer, or an identifier from a terminal manufacturer. Specifically, the application function may include a first application function, the chip identifier may include an identifier from a first chip, the chip manufacturer may include a first chip manufacturer, and the terminal manufacturer may include a first terminal manufacturer. That is, the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer can be represented at different granularities to meet the needs of different scenarios.

[0507] For example, if the list of data consumers allowed by the first type of allocation code includes chip manufacturer identifiers, then the first network element needs to determine whether the chip manufacturer to which the first application function belongs is included in the list of chip manufacturers indicated by the chip manufacturer identifier (included in the list of data consumers allowed by the first type of allocation code) based on the chip manufacturer ID of the first application function in the first request message. If the chip manufacturer to which the first application function belongs belongs to the list of chip manufacturers, then the first network element can determine that the first application function has the permission to obtain the data it requests.

[0508] For example, if the list of data consumers allowed by the first type of allocation code includes the identifier of the terminal manufacturer, then the first network element needs to determine whether the terminal manufacturer to which the first application function belongs is included in the list of terminal manufacturers indicated by the identifier of the terminal manufacturer (included in the list of data consumers allowed by the first type of allocation code) based on the terminal manufacturer ID of the first application function in the first request message. If the terminal manufacturer to which the first application function belongs belongs to the list of terminal manufacturers, then the first network element can determine that the first application function has the permission to obtain the data it requests.

[0509] It is understood that the above is only an example. When the list of data consumers allowed by the first type of allocation code includes the other parameters mentioned above (such as the identifier of the application function, the identifier of the chip, the identifier of the application function of the chip manufacturer, and the identifier of the application function of the terminal manufacturer), the implementation principle of the first network element verifying whether the first application function has the permission to obtain the requested data is similar to the example above. It can be referred to for understanding and will not be elaborated further.

[0510] Based on the above description, when the first network element determines that the first application function has the permission to obtain the requested data, it can determine the terminal device that provides the requested data to the first application function, as described below. The specific implementation of the first network element determining the first terminal device is described below.

[0511] In one possible implementation, the above method embodiment further includes:

[0512] The first network element obtains the first information based on the PEI (information) of at least one terminal device (each).

[0513] The first network element determines the first terminal device based on the PEI of at least one terminal device, the first information, and the first request message.

[0514] The first information can be used to indicate at least one of the following: information about the chip manufacturer of each of the at least one terminal device, information about the terminal manufacturer of each of the at least one terminal device, or information about the chip of each of the at least one terminal device; the at least one terminal device includes a first terminal device, and the first terminal device satisfies at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device, the first terminal manufacturer includes the terminal manufacturer of the first terminal device, or the first chip includes the chip of the first terminal device. It is understood that the specific implementation of this process can be referred to the relevant content in Case 1 above, and will not be elaborated upon further.

[0515] Scenario 4: The first network element queries the second network element to obtain the first terminal device.

[0516] In scenario 4, one possible implementation of the above method embodiment may further include:

[0517] The first network element sends a second request message to the second network element based on the first request message. Correspondingly, the second network element receives the second request message from the first network element.

[0518] The second network element sends a second response message to the first network element based on the second request message. Correspondingly, the first network element receives the second response message from the second network element.

[0519] The second request message can be used to request the terminal device associated with the first identifier. The second request message includes the first identifier, which may include a first type allocation code. The first identifier originates from the first application function. The second response message may include the identifier of the first terminal device, such as SUPI, GPSI, etc., without limitation. The first application function may belong to the data consumer list allowed by the first type allocation code. It is understood that the specific implementation of this process can be referred to the relevant content in scenario 2 above, and will not be elaborated further.

[0520] Based on the above introduction, the specific implementation of the second network element determining the first terminal device will be described below.

[0521] In one possible implementation, the above method embodiment may further include:

[0522] The second network element obtains the second information based on the PEI of at least one terminal device.

[0523] The second network element determines the first terminal device based on the PEI of at least one terminal device, the second information, and the second request message.

[0524] The second information can be used to indicate at least one of the following: information about the chip manufacturer of each of the at least one terminal device, information about the terminal manufacturer of each of the at least one terminal device, or information about the chip of each of the at least one terminal device; at least one terminal device includes a first terminal device, and the first terminal device satisfies at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device, the first terminal manufacturer includes the terminal manufacturer of the first terminal device, or the first chip includes the chip of the first terminal device. For specific implementation, please refer to the relevant content in Case 2 above, which will not be repeated here.

[0525] In one possible implementation, the second request message may include a first condition and information about the service area of ​​the first network element. The first condition is used to determine the first terminal device. The first terminal device is located within the service area of ​​the first network element. For a detailed description of this, please refer to the relevant content in Case 2 above, which will not be repeated here.

[0526] Based on the above introduction, the second network element can also verify whether the first application function has the permission to obtain the data it requests, which will be described in detail below.

[0527] In one possible implementation, the above method embodiment may further include:

[0528] The second network element obtains the list of data consumers allowed by the first type of allocation code based on the second request message.

[0529] If the first application function belongs to the list of data consumers allowed by the first type of allocation code, the second network element determines that the first application function has the right to obtain data.

[0530] The list of data consumers allowed by the first type of allocation code can be pre-configured or predefined, making implementation simple; alternatively, the above method embodiment may further include: the second network element receiving the list of data consumers allowed by the first type of allocation code. It is understood that this implementation process can be referred to the relevant content in cases 2 and 3 above, and will not be elaborated upon further.

[0531] In one possible implementation, the first type of allocation code is associated with the first chip manufacturer and / or the first terminal manufacturer associated with the data; the list of data consumers allowed by the first type of allocation code is determined based on the list of data consumers allowed by the first chip manufacturer and / or the list of data consumers allowed by the first terminal manufacturer. For example, the second network element can determine the list of data consumers allowed by the first type of allocation code based on the list of data consumers allowed by the first chip manufacturer and / or the list of data consumers allowed by the first terminal manufacturer. For details, please refer to the relevant content in scenario 3 above, which will not be repeated here.

[0532] Based on the above description, in one possible implementation, the list of data consumers allowed by the first type of allocation code may include at least one of the following: an application function identifier, a chip identifier, an application function identifier from a chip manufacturer, an identifier from a chip manufacturer, an application function identifier from a terminal manufacturer, or an identifier from a terminal manufacturer. Specifically, the application function may include a first application function, the chip identifier may include an identifier from a first chip, the chip manufacturer may include a first chip manufacturer, and the terminal manufacturer may include a first terminal manufacturer. That is, the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer can be represented at different granularities to meet the needs of different scenarios. For a detailed description, please refer to the relevant content in Situations 1-3 above, which will not be repeated here.

[0533] Based on the above description, after the second network element determines the first terminal device associated with the first identifier, it can send the identifier of the first terminal device, such as the SUPI or GPSI of the first terminal device, to the first network element through a second response message. That is, the second response message can include the SUPI, GPSI, or any other possible identifier of the first terminal device, without limitation. For ease of understanding, the following description will use the example of the second response message including the SUPI of the first terminal device. The second response message can be a response message to the second request message. The first network element can determine that the first terminal device is the terminal device used to provide the requested data for the first application function based on the SUPI of the first terminal device in the second response message. That is, in case 4, the first terminal device can be determined based on the SUPI of the first terminal device in the second response message.

[0534] Combining situations 3 and 4 above, if the first application function belongs to the data consumer list allowed by the first type of allocation code, and the first network element determines that the first terminal device is a terminal device used to provide the data requested by the first application function, and if the second response message does not include the first data, in one possible implementation, the above method embodiment may further include:

[0535] The first network element collects the first data from the first terminal device.

[0536] The first network element sends a first response message to the first application function, including: the first network element sends a first response message to the first application function based on the first data.

[0537] It is understandable that the implementation process can be referred to the relevant content in step S502 above, and will not be repeated here.

[0538] Optionally, the first response message may also include the type allocation code of the first terminal device and / or the identifier of the chip of the first terminal device. For details, please refer to the relevant content in step S502 above, which will not be repeated here.

[0539] It is understandable that the first response message may include any other possible parameters or information, without limitation.

[0540] The first application function can obtain the required first data based on the received first response message, and use the data to perform subsequent steps, such as training the model on the first terminal device side. For its specific implementation, please refer to the existing technology, which will not be elaborated here.

[0541] It is understood that the naming of the first response message, the first terminal device, the first data, the consumer list, the first information, the second information, the second request message, and the second response message is merely an example and can be replaced with any other possible names without limitation.

[0542] In summary, the first network element can receive a first request message from a first application function requesting access to data associated with a terminal device. This first request message includes a first identifier, which in turn includes a first type allocation code. If the first application function belongs to the data consumer list permitted by the first type allocation code (i.e., the first application function is authorized), meaning it has the permission to access the requested data, the first network element can then grant access to the first terminal device's first data associated with the first identifier through a first response message. This prevents unauthorized application functions from obtaining terminal data, thus avoiding data leakage and improving the security of the process by which application functions (such as the first application function) acquire data (such as measurement data) from the terminal device.

[0543] It is understood that the above description, which combines or integrates the verification of whether the first application function has the permission to obtain the requested data with the first network element opening the first data collected from the first terminal device to the first application function, is not limited to the verification of whether the first application function has the permission to obtain the requested data by the first network element or the second network element and the opening of the first data collected from the first terminal device to the first application function by the first network element. For example, the first network element or the second network element may only verify whether the first application function has the permission to obtain the requested data, and the first network element may not need to open the first data of the first terminal device to the first application function; or, the first network element may only open the first data of the first terminal device to the first application function, and the first network element or the second network element may not need to verify whether the first application function has the permission to obtain the requested data (such as the methods described in aspects 10-12 of the above invention, or the methods described in aspects 13-15 of the above invention, etc.), to meet the needs of different scenarios. The embodiments of this application do not limit this.

[0544] For example, corresponding to question B above, Figure 6 A flowchart illustrating a communication method provided in an embodiment of this application. Figure 2 This communication method is applicable to the above. Figure 4 The communication system shown mainly involves the first application function and the interaction between the first network element and the second network element. For example... Figure 6 As shown, the flow of this communication method is as follows:

[0545] S601, the first application function sends a first request message to the first network element. Correspondingly, the first network element receives the first request message from the first application function.

[0546] The first request message can be used to request data associated with the terminal device. That is, the first application function can send a first request message to the first network element to request the required data, such as measurement data from the terminal device. For example, when the first application function needs to obtain data from the terminal device, such as when training a model on the terminal device side, it can send a first request message to the first network element. The first request message will be described in detail below.

[0547] The first request message may include a first identifier, which may be used to indicate the identifier of a first chip associated with the data, or a first type allocation code. Specifically, the first identifier may include the identifier of the first chip (e.g., the first application function is chip OTT), in which case the first request message may be used to request data from the terminal device of the first chip; or, the first identifier may include a first type allocation code (which may be denoted as a first TAC, e.g., the first application function is terminal OTT), in which case the first request message may be used to request data from the terminal device of the first type allocation code. It is understood that the first chip may be associated with the first type allocation code, that is, the chip of the terminal device that provides the requested data for the first application function may be the first chip, and its type allocation code may be the first type allocation code. It is understood that the first chip may include at least one chip, and the first type allocation code may include at least a type allocation code; this application embodiment does not limit this.

[0548] Based on the above description, in one possible implementation, the first request message may also include the identifier of the first application function and / or the first condition.

[0549] The identifier for the first application function can be used to indicate or identify the first application function. For a detailed description, please refer to the relevant content in step S501 above; it will not be repeated here. The first condition can be used to determine the first terminal device; the first condition will be described in detail below.

[0550] In one possible implementation, the first type allocation code may include at least one type allocation code, and the first condition may be used to indicate at least one of the following: the number of first type allocation codes, the number of terminal devices for each type allocation code in the first type allocation codes, or information about the region to which the terminal devices belong, wherein the first terminal devices may be located within the region to which the terminal devices belong. For a detailed description of the first condition, please refer to the relevant content in step S501 above, which will not be repeated here.

[0551] It is understood that the above is merely an example, and the first condition may also include any other possible parameters or information. For example, the first condition may also include the total number of terminal devices corresponding to the at least one type allocation code, the proportion of terminal devices for each type allocation code in the at least one type allocation code, the capability requirements (such as processing power) of the terminal devices for the first application function, etc. This application embodiment does not limit these.

[0552] Based on the above description, the first request message may also include any other possible parameters or information, such as the data type of the data requested by the first application function (e.g., PDP, CER, CIR, SRS, sensing data, AI data, network data, IoT data, application data, on-network computing data), the data reporting method, etc. This application embodiment does not limit this.

[0553] It is understood that the naming of the first request message, the first identifier, the first chip, the first type allocation code, and the first condition mentioned above are merely examples, and can be replaced with any other possible names without limitation.

[0554] S602, the first network element sends a second request message to the second network element based on the first request message. Correspondingly, the second network element receives the second request message from the first network element.

[0555] That is, the first network element can send a second request message to the second network element based on the received first request message (if the first network element does not store the PEI of at least one terminal device (including the first terminal device)). This second request message can be used to request the acquisition of the terminal device associated with the first identifier. The second request message is determined based on the first request message, and the second request message may include the aforementioned first identifier and the service area information of the first network element. In other words, the first network element can send the first identifier and its own service area information from the first request message to the second network element through the second request message.

[0556] In one possible implementation, the second request message may also include an identifier of the first application function and / or a first condition.

[0557] That is, the first network element can also send the identifier of the first application function and / or the first condition in the first request message to the second network element through the second request message. For example, when the second request message includes the identifier of the first application function, the second network element can directly determine that the first identifier comes from the first application function based on the identifier of the first application function, or in other words, the terminal device associated with the first identifier queried by the first network element is associated with the first application function, so as to be used by the second network element to verify the permission of the first application function (to obtain data); when the second request message includes the first condition, it can be used by the second network element to subsequently determine the first terminal device that meets the first condition, so as to be used by the first network element to subsequently open the first data of the first terminal device to the first application function.

[0558] It is understood that the above are merely examples, and the second request message may include any other possible parameters or information, which are not limited in this embodiment. The naming of the second request message is merely an example, and it may be replaced with any other possible name, without limitation.

[0559] S603, the second network element sends a second response message to the first network element based on the second request message. Correspondingly, the first network element receives the second response message from the second network element.

[0560] The second network element can determine the terminal device (i.e., the first terminal device hereinafter referred to as the first terminal device) that provides the requested data for the first application function based on the second request message. The specific implementation of the second network element determining the first terminal device is described below.

[0561] In one possible implementation, the above method embodiment may further include:

[0562] The second network element acquires the PEI (information) of at least one terminal device (each).

[0563] In this configuration, the PEI of at least one terminal device can be used to indicate the type allocation code of each of the at least one terminal device. The second network element can store the PEIs of at least one terminal device (including the first terminal device). For example, the at least one terminal device can be a terminal device registered to the second network element (e.g., the second network element is an AMF), or the second network element can be used to manage the at least one terminal device (e.g., the second network element can be a UDM, UDR, etc.). For example, the PEI of the at least one terminal device can be pre-configured or pre-defined; or, the PEI of the at least one terminal device can be sent to the second network element by the at least one terminal device. For example, the at least one terminal device can send its own PEI to the second network element; or, if the second network element does not obtain the PEI of the at least one terminal device, the second network element can send PEI request messages to the at least one terminal device to request to obtain the PEI of the at least one terminal device; or, the PEI of the at least one terminal device can be sent to the second network element by other network elements or devices that store the PEI of the at least one terminal device.

[0564] It is understood that the above is only an example, and the second network element can also obtain the PEI of at least one terminal device (each) in any other possible way, without limitation.

[0565] The PEI can be used to identify the first terminal device. Specifically, in one possible implementation, the above method embodiment may further include:

[0566] The second network element determines the candidate terminal device based on the first identifier.

[0567] The second network element determines the first terminal device that meets the first condition.

[0568] At least one terminal device may include a candidate terminal device, and the type allocation code of the candidate terminal device may belong to the first type allocation code. The following describes, using implementations 1 and 2 as examples, the specific implementation of how the second network element determines the candidate terminal device based on the first identifier.

[0569] Implementation 1: The first identifier is used to indicate the identifier of the first chip.

[0570] In implementation 1, the second network element determines the first type allocation code based on the identifier of the first chip.

[0571] The second network element determines the candidate terminal device based on the first type allocation code and the PEI of at least one terminal device.

[0572] As can be understood from the above description, the first chip is associated with the first type allocation code (i.e., the aforementioned first TAC). Therefore, the second network element can determine the type allocation code, i.e., the first type allocation code, using the identifier of the first chip. Since the PEI can include a TAC, the first network element can determine the TAC of at least one terminal device based on its respective PEI, and filter out the terminal devices whose TAC belongs to the first TAC. These terminal devices are candidate terminal devices. It is understood that candidate terminal devices can include at least one terminal device, and this embodiment does not limit this.

[0573] Implementation 2: The first identifier is used to indicate the first type of allocation code.

[0574] In implementation 2, the second network element can directly determine the candidate terminal device based on the first type allocation code and the PEI of at least one terminal device. The implementation principle can be referred to the relevant content in implementation 1 above, and will not be repeated here.

[0575] Based on the above descriptions of Implementation 1 and Implementation 2, the second network element can determine the first terminal device among the candidate terminal devices that meets the first condition, according to the determined candidate terminal devices.

[0576] The candidate terminal device may include the first terminal device. That is, the second network element can filter the candidate terminal devices according to the first condition, and select the terminal devices that meet the first condition from the candidate terminal devices. The terminal devices that meet the first condition from the candidate terminal devices are the first terminal devices. It should be noted that the first terminal device is also located within the service area of ​​the first network element.

[0577] It is understood that the first type allocation code may include the type allocation code of the first terminal device. That is, the number of type allocation codes included in the first type allocation code may be greater than or equal to the number of type allocation codes of the first terminal device. For example, the first TAC may include three type allocation codes, namely TAC#a, TAC#b, and TAC#c. If the type allocation code of the first terminal device includes terminal devices with TACs of TAC#a, TAC#b, and TAC#c, then the number of type allocation codes included in the first type allocation code is equal to the number of type allocation codes of the first terminal device. If the type allocation code of the first terminal device does not include one or more of TAC#a, TAC#b, or TAC#c, such as TAC#c not being included in the type allocation code of the first terminal device, then the type allocation code of the first terminal device includes TAC#a and TAC#b. That is, the number of type allocation codes included in the first type allocation code is greater than the number of type allocation codes of the first terminal device. This application embodiment does not limit this.

[0578] After the second network element identifies the first terminal device, it can send a response message to the second request message, i.e., a second response message, to the first network element. The second response message may include the SUPI of the first terminal device, used to provide feedback to the first network element regarding the first terminal device that has provided the requested data for the first application function. It is understood that the SUPI of the first terminal device is merely an example, and it can be replaced with any other parameter or identifier that can be used to indicate or identify the first terminal device, without limitation.

[0579] It is understood that the second response message may also include any other parameters or information, without limitation. The naming of the second response message, candidate terminal device, and first terminal device mentioned above is merely an example, and may be replaced with any other possible naming, without limitation.

[0580] S604, the first network element sends a first response message to the first application function based on the SUPI of the first terminal device. Correspondingly, the first application function receives the first response message from the first network element.

[0581] The following is a detailed description of step S604.

[0582] In one possible implementation, the first network element sends a first response message to the first application function based on the SUPI of the first terminal device, including:

[0583] The first network element collects the first data from the first terminal device based on the SUPI of the first terminal device.

[0584] The first network element sends the first response message to the first application function based on the first data.

[0585] That is, the first network element can collect the first data of the first terminal device based on the SUPI of the first terminal device in the received second response message. For example, the first network element can establish a user plane connection with the first terminal device to collect the first data of the first terminal device. The specific implementation can refer to the prior art, which will not be elaborated here.

[0586] It is understood that the first terminal device may include at least one terminal device, and the first network element may aggregate the data collected from the at least one terminal device and send it to the first application function through a first response message. That is, the first response message may include first data associated with the first terminal device. The first response message may be a response message to the first request message.

[0587] Optionally, the first response message may also include a type assignment code for the first terminal device and / or an identifier for the chip of the first terminal device.

[0588] For example, the first network element can also de-identify or anonymize the first data, such as converting the SUPI of the first terminal device into an identifier that can be recognized by the first application function, such as the type allocation code of the first terminal device and / or the chip identifier of the first terminal device, and sending it to the first application function through a first response message, so that the first application function can determine the type allocation code and / or the chip identifier corresponding to the first data.

[0589] It is understandable that the first response message may include any other possible parameters or information, without limitation.

[0590] The first application function can obtain the required first data based on the received first response message, and use the data to perform subsequent steps, such as training the model on the first terminal device side. For its specific implementation, please refer to the existing technology, which will not be elaborated here.

[0591] It is understood that the naming of the first response message and the first data mentioned above is only an example, and it can be replaced with any other possible names without limitation.

[0592] In summary, the first network element can receive a first request message from a first application function requesting data associated with a terminal device. The first request message includes an identifier indicating a first chip associated with the data, or a first identifier of a first type allocation code. Based on the first request message, the first network element can send a second request message to a second network element. This second request message may include the first identifier and information about the service area of ​​the first network element, allowing the second network element to query a terminal device associated with the first identifier and located within the service area of ​​the first network element. The first network element receives a second response message from the second network element including the SUPI of the first terminal device. Based on the SUPI of the first terminal device, the first network element can open or provide the first data of the first terminal device to the first application function. This ensures that the first type allocation code includes the type allocation code of the first terminal device, and that the first terminal device is located within the service area of ​​the first network element. This guarantees that the first terminal device can provide the data required by the first application function (such as the first data), and that the first network element can collect the first data of the first terminal device, thereby meeting the needs of the first application function and improving the efficiency of the first application function in obtaining data from the terminal device.

[0593] In conjunction with the above embodiments, the first network element or the second network element can also verify whether the first application has the permission to obtain the requested data, in order to prevent unauthorized application functions from obtaining terminal data, thereby preventing the leakage of terminal device data and improving the security of the process by which application functions (such as the first application function) obtain terminal device data (such as measurement data). The following examples 1 and 2 will be used as examples for specific details.

[0594] Example 1: The first network element verifies whether the first application has permission to obtain the requested data.

[0595] Optionally, the above method embodiments further include:

[0596] The first network element obtains the first information.

[0597] Based on the first information, the first network element determines that the first chip belongs to the list of chips supported by the first application function and / or the list of type allocation codes (supported by the first application function).

[0598] The first information can be used to indicate a list of chips supported by the first application function, and / or a list of type allocation codes. The first information can be pre-configured or pre-defined, simplifying implementation; alternatively, the above method embodiments may further include:

[0599] The first network element receives the list of chips supported by the first application function, and / or the list of type assignment codes.

[0600] For example, the first application function can send its supported chip list and / or type allocation code list to the first network element via a registration (request) message. Alternatively, other network elements or devices that store the first application function's supported chip list and / or type allocation code list can send the first application function's supported chip list and / or type allocation code list to the first network element. This is not limited, and its implementation principle is similar to that in step S502 above, where the first network element obtains the list of data consumers allowed by the first chip manufacturer and / or the first terminal manufacturer. This can be understood with reference and is not limited.

[0601] It is understandable that the first application function can collect data from terminal devices corresponding to chips in its supported chip list. Similarly, the first application function can collect data from terminal devices corresponding to type allocation codes in its supported type allocation code list. When the first chip belongs to the chip list supported by the first application function, and / or the first type allocation code belongs to the type allocation code list supported by the first application function, the first network element can determine that the first application function has the permission to obtain the requested data. In this case, the first network element can send a second request message to the second network element. Conversely, the first network element does not need to send a second request message to the second network element. This improves the efficiency of the first application function in obtaining data from terminal devices and avoids wasting resources. In addition, in Example 1, the first network element can directly verify whether the first application function has the permission to obtain the data without querying other network elements (such as the second network element) or devices, thereby reducing signaling interaction of the first network element and reducing resource overhead.

[0602] Example 2: After the second network element receives the second request message from the first network element, it verifies whether the first application has the permission to obtain the requested data.

[0603] Optionally, the above method embodiments further include:

[0604] The second network element obtains the second information.

[0605] The second network element determines, based on the second information, that the first chip belongs to the list of chips supported by the first application function, and / or the list of type allocation codes supported by the first application function (if supported by the first application function).

[0606] The second information can be used to indicate the list of chips supported by the first application function and / or the list of type allocation codes. For a detailed description, please refer to the relevant description of the first information in Example 1 above, which will not be repeated here.

[0607] The second network element can verify whether it has permission to obtain the requested data from the first application function based on the second information. For example, when the first chip belongs to the chip list supported by the first application function, and / or the first type allocation code belongs to the type allocation code list supported by the first application function, the second network element can determine that the first application function has permission to obtain the requested data. In this case, the second network element can perform subsequent steps, such as identifying the first terminal device and sending a second response message to the first network element, without limitation. Conversely, the first network element may not need to perform steps such as identifying the first terminal device and sending a second response message to the first network element. This improves communication efficiency, reduces the resource overhead of the second network element, and enhances the security of the process by which the first application function obtains data from the terminal device.

[0608] It is understood that Examples 1 and 2 above can also be combined or coupled with each other. That is, both the first network element and the second network element can verify whether the first application has the permission to obtain the requested data, so as to improve the accuracy of the permission verification of the first application and thus improve the efficiency of the first application function in obtaining data from the terminal device.

[0609] It should be understood that the naming of the first information, the second information, the chip list, and the type allocation code list mentioned above are merely examples, and they can be replaced with any other possible names without limitation.

[0610] The above, in conjunction with the method embodiments, provides an overall overview of the communication method provided in this application. For ease of understanding, the above method is further described below in the following specific scenarios:

[0611] Scene 1: Figure 7 A flowchart illustrating a communication method provided in an embodiment of this application. Figure 3 This communication method mainly involves the interaction between: UE#1 (as described in the first terminal device above), AMF, UDM (as described in the second network element above), UDR, NWDAF (as described in the first network element above), chip OTT (as described in the first application function above), and terminal OTT. It can be understood that scenario 1 corresponds to the above... Figure 6 The communication method shown.

[0612] For example, such as Figure 7 As shown, the flow of this communication method is as follows:

[0613] S700a1, the chip OTT sends a device information registration request #a to the UDR. Correspondingly, the UDR receives the device information registration request #a from the chip OTT.

[0614] The Device Information Registration Request #a can be used to request the registration of the chip-based OTT with the UDR. The Device Information Registration Request #a can include at least one of the following: chip manufacturer ID, or chip ID (list), etc., without limitation. For example, the chip-based OTT can send the Device Information Registration Request #a to the UDR via NEF.

[0615] Optionally, NEF can also save the device information registration request #a for subsequent verification of data collection permissions.

[0616] S700a2, the UDR sends a device information registration response #a to the chip OTT. Correspondingly, the chip OTT receives the device information registration response #a from the UDR.

[0617] The device information registration response #a can be a response message to the device information registration request #a, and can be used to indicate that the UDR has received the device information registration request #a. For example, the UDR can send the device information registration response #a to the chip OTT via NEF.

[0618] S700b1, the OTT terminal sends a device information registration request #b to the UDR. Correspondingly, the UDR receives the device information registration request #b from the OTT terminal.

[0619] The Device Information Registration Request #b can be used to request the OTT terminal to register with the UDR. The Device Information Registration Request #b can include at least one of the following: terminal manufacturer ID, terminal device TAC (list), device information (hardware or software information: such as chip ID), or terminal device PEI, etc., without limitation. For example, the OTT terminal can send the Device Information Registration Request #b to the UDR via NEF.

[0620] Optionally, NEF can also save the device information registration request #b for subsequent verification of data collection permissions.

[0621] S700b2, the UDR sends a device information registration response #b to the terminal OTT. Correspondingly, the terminal OTT receives the device information registration response #b from the UDR.

[0622] The device information registration response #b can be a response message to the device information registration request #b, and can be used to indicate that the UDR has received the device information registration request #b. For example, the UDR can send the device information registration response #b to the terminal OTT via NEF.

[0623] It is understood that steps S700a1-S700b2 are optional. For example, the UDR may also be pre-configured with information such as the chip manufacturer ID and chip ID corresponding to the chip OTT, as well as the terminal manufacturer ID, TAC, device information, and PEI information corresponding to the terminal OTT, without limitation. In this case, steps S700a1-S700b2 do not need to be executed.

[0624] In S700c, UE#1 sends a UE registration request to the AMF. Correspondingly, the AMF receives the UE registration request from UE#1.

[0625] Specifically, UE#1 can send a UE registration request to the AMF for registration with the AMF.

[0626] Optionally, the UE registration request may include the PEI (information) of UE#1.

[0627] In S700d, the AMF sends a PEI acquisition request to UE#1. Correspondingly, UE#1 receives the PEI acquisition request from the AMF.

[0628] If the AMF fails to obtain the PEI of UE#1, such as when the UE registration request does not include the PEI of UE#1, the AMF can send a PEI acquisition request to UE#1 to obtain the PEI of UE#1.

[0629] Optionally, if the UE registration request indicates the data open capability of UE#1 (e.g., whether data development is supported), when the UE registration request indicates that UE#1 supports data development, the AMF can trigger the sending of a PEI acquisition request to UE#1 (e.g., performing step S700e below); otherwise, the AMF does not need to send a PEI acquisition request to UE#1 (i.e., does not need to perform step S700e below). In this way, the signaling interaction between the AMF and UE#1 can be reduced, and resource overhead can be reduced.

[0630] It is understandable that if the UE registration request includes the PEI of UE#1, then the AMF may not need to execute step S700d.

[0631] S700e, UE#1 sends its PEI to the AMF. Correspondingly, the AMF receives the PEI from UE#1.

[0632] UE#1 can send its PEI to the AMF based on the PEI acquisition request.

[0633] In S700f, the AMF sends a PEI update request to the UDM. Correspondingly, the UDM receives the PEI update request from the AMF.

[0634] The AMF can send the obtained PEI of UE#1 to the UDM via a PEI update request. It is understood that the PEI update request can also include any other possible parameters or information, without limitation. It is understood that UE#1 can be one of at least one UE registered with the AMF; therefore, based on the same principle, the AMF and UDM can obtain the PEI of at least one UE.

[0635] It is understood that the embodiments of this application do not limit the order of steps S700c-S700f and steps S700a1-S700b2.

[0636] S701, the OTT chip sends a data acquisition request to the NWDAF. Correspondingly, the NWDAF receives the data acquisition request from the OTT chip.

[0637] The data acquisition request (such as the first request message mentioned above) can be used to request data associated with the terminal device. The data acquisition request may include: the chip ID#1 associated with the data (such as the first identifier mentioned above, i.e., the identifier of the first chip).

[0638] Optionally, the data acquisition request may also include any of the following: chip OTTID (such as the identifier of the first application function mentioned above), data filtering conditions (such as the first conditions mentioned above, such as the number of TACs, the distribution of TACs, etc.), or the data type of the requested data, without limitation.

[0639] For example, a chip-based OTT can send a data acquisition request to the NWDAF via the NEF. In this case, if the NEF stores a device information registration request #a, it can also verify whether chip ID #1 belongs to the chip ID list in the device information registration request #a. This chip ID list can include chips supported by the chip-based OTT. When chip ID #1 belongs to the chip ID list, the chip-based OTT has the authority to collect data from the terminal device corresponding to chip ID #1. When the NEF determines that the chip-based OTT has the authority to collect data from the terminal device corresponding to chip ID #1, it can trigger the forwarding of the data acquisition request to the NWDAF.

[0640] S702, NWDAF sends a terminal device query request to UDM. Correspondingly, UDM receives the terminal device query request from NWDAF.

[0641] In other words, NWDAF can send a terminal device query request (such as the second request message mentioned above) to UDM based on the data acquisition request. This terminal device query request can be used to request the terminal device associated with chip ID#1. The terminal device query request may include: chip ID#1 and data filtering conditions.

[0642] Optionally, the terminal device query request may also include information such as the service area of ​​NWDAF, without limitation.

[0643] S703, UDM sends a TAC device information query request to UDR. Correspondingly, UDR receives the TAC device information query request from UDM.

[0644] UDM can send a TAC device information query request to UDR based on the terminal device query request. The TAC device information query request can be used to query the terminal device associated with chip ID#1. The TAC device information query request can include chip ID#1, or any other possible parameters or information, without limitation.

[0645] S704, the UDR sends a TAC device information query response to the UDM. Correspondingly, the UDM receives the TAC device information query response from the UDR.

[0646] The UDR can determine the TAC corresponding to chip ID #1, such as TAC#1, based on chip ID #1, device information registration request #a, and device information registration request #b in the TAC device information query request. The UDR can send a response message to the UDM for the terminal device query request, i.e., a TAC device information query response, which may include TAC#1. It can be understood that chip ID #1 may include at least one chip, and TAC#1 may include at least one TAC; therefore, TAC#1 can be understood as a TAC list.

[0647] It is understandable that the TAC device information query response may include any other possible parameters or information, without limitation.

[0648] S705, UDM determines UE#1.

[0649] Specifically, the UDM can determine the TAC of at least one UE based on the PEI of each UE. The UDM can query TAC#1 in the response based on the TAC device information and filter out UEs whose TAC belongs to TAC#1 from at least one UE, i.e., candidate UEs (such as the candidate terminal devices mentioned above).

[0650] UDM can filter out UEs that meet the data filtering conditions from the candidate U...

Claims

1. A communication method, characterized in that, Applied to the first network element, the method includes: Receive a first request message from a first application function; wherein the first request message is used to request to obtain data associated with a terminal device, and the first request message includes a first identifier, the first identifier being used to indicate a first chip manufacturer and / or a first terminal manufacturer associated with the data; If the first application function belongs to the data consumer list permitted by the first chip manufacturer and / or the first terminal manufacturer, a first response message is sent to the first application function; wherein, the first response message includes first data associated with the first terminal device, and the first terminal device is associated with the first identifier.

2. The method according to claim 1, characterized in that, The first identifier includes at least one of the following: the identifier of the first chip manufacturer, the identifier of the first terminal manufacturer, the identifier of the first chip, the first type allocation code, or the identifier of the terminal device; wherein, the first chip is the chip of the terminal device, and the first type allocation code is the type allocation code of the terminal device.

3. The method according to claim 2, characterized in that, The first request message further includes at least one of the following: the identifier of the first application function, the data type of the data, or a first condition; wherein the first condition is used to determine the first terminal device.

4. The method according to claim 3, characterized in that, The terminal device corresponds to at least one type allocation code, and the first condition is used to indicate at least one of the following: the number of the at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs; wherein, the first terminal device is located in the region to which the terminal device belongs.

5. The method according to claim 3 or 4, characterized in that, The method further includes: Based on the first request message, obtain the list of allowed data consumers; If the first application function belongs to the list of allowed data consumers, it is determined that the first application function has permission to access the data.

6. The method according to claim 5, characterized in that, The list of allowed data consumers is pre-configured or predefined; Alternatively, the method may further include: Receive the list of allowed data consumers.

7. The method according to claim 5 or 6, characterized in that, The method further includes: First information is obtained based on the permanent device identifier (PEI) of at least one terminal device; wherein the first information is used to indicate at least one of the following: information of the chip manufacturer of each of the at least one terminal device, information of the terminal manufacturer of each of the at least one terminal device, or information of the chip of each of the at least one terminal device; The first terminal device is determined based on the PEI of the at least one terminal device, the first information, and the first request message; wherein the at least one terminal device includes the first terminal device, and the first terminal device satisfies at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device, the first terminal manufacturer includes the terminal manufacturer of the first terminal device, or the first chip includes the chip of the first terminal device.

8. The method according to any one of claims 5-7, characterized in that, The terminal device is identified as the terminal device's General Public User Identifier (GPSI), and the method further includes: Based on the GPSI of the terminal device, determine the subscription permanent identifier SUPI corresponding to the GPSI; Based on the SUPI, determine the first type allocation code corresponding to the SUPI; Based on the first type of allocation code, the first chip manufacturer and / or the first terminal manufacturer are determined.

9. The method according to claim 3 or 4, characterized in that, The method further includes: According to the first request message, a second request message is sent to the second network element; wherein, the second request message is used to request to obtain the terminal device associated with the first identifier, and the second request message includes the first identifier; Receive a second response message from the second network element; wherein the second response message includes the SUPI of the first terminal device; The first terminal device is determined based on the SUPI of the first terminal device.

10. The method according to claim 9, characterized in that, The second request message also includes the first condition and information about the service area of ​​the first network element, wherein the first terminal device is within the service area of ​​the first network element.

11. The method according to claim 9 or 10, characterized in that, The second network element is any one of the following: a unified data management network element, a unified data storage network element, or an access and mobility management network element.

12. The method according to any one of claims 1-11, characterized in that, The list of allowed data consumers includes at least one of the following: an application function identifier, a chip manufacturer's application function identifier, the chip manufacturer's identifier, a terminal manufacturer's application function identifier, or the terminal manufacturer's identifier; wherein, the application function includes the first application function, the chip manufacturer includes the first chip manufacturer, and the terminal manufacturer includes the first terminal manufacturer.

13. The method according to any one of claims 1-12, characterized in that, The method further includes: Collect the first data from the first terminal device; Sending the first response message to the first application function includes: Based on the first data, the first response message is sent to the first application function; wherein the first response message further includes the type allocation code of the first terminal device, and / or the identifier of the chip of the first terminal device.

14. The method according to any one of claims 1-13, characterized in that, The first network element is any one of the following: a network open function network element, a network data analysis function network element, or a data collection and coordination function network element.

15. A communication method, characterized in that, Applied to a second network element, the method includes: Receive a second request message from a first network element; wherein the second request message is used to request to obtain a terminal device associated with a first identifier, the second request message includes the first identifier, the first identifier is used to indicate a first chip manufacturer and / or a first terminal manufacturer associated with the data, and the first identifier comes from a first application function; According to the second request message, a second response message is sent to the first network element; wherein, the second response message includes a permanent subscription identifier (SUPI) of the first terminal device, the first terminal device is associated with the first identifier, and the first application function belongs to the data consumer list allowed by the first chip manufacturer and / or the first terminal manufacturer.

16. The method according to claim 15, characterized in that, The first identifier includes at least one of the following: the identifier of the first chip manufacturer, the identifier of the first terminal manufacturer, the identifier of the first chip, the first type allocation code, or the identifier of the terminal device; wherein, the first chip is the chip of the terminal device, and the first type allocation code is the type allocation code of the terminal device.

17. The method according to claim 16, characterized in that, The method further includes: Based on the second request message, obtain the list of allowed data consumers; If the first application function belongs to the list of allowed data consumers, it is determined that the first application function has permission to access the data.

18. The method according to claim 17, characterized in that, The list of allowed data consumers is pre-configured or predefined; or, the method further includes: Receive the list of allowed data consumers.

19. The method according to any one of claims 16-18, characterized in that, The method further includes: Second information is obtained based on the permanent device identifier (PEI) of at least one terminal device; wherein the second information is used to indicate at least one of the following: information of the chip manufacturer of each of the at least one terminal device, information of the terminal manufacturer of each of the at least one terminal device, or information of the chip of each of the at least one terminal device; The first terminal device is determined based on the PEI of the at least one terminal device, the second information, and the second request message; wherein the at least one terminal device includes the first terminal device, and the first terminal device satisfies at least one of the following: the first chip manufacturer includes the chip manufacturer of the first terminal device, the first terminal manufacturer includes the terminal manufacturer of the first terminal device, or the first chip includes the chip of the first terminal device.

20. The method according to any one of claims 16-19, characterized in that, The second request message also includes a first condition and information about the service area of ​​the first network element. The first condition is used to determine the first terminal device, which is located within the service area of ​​the first network element.

21. The method according to claim 20, characterized in that, The terminal device corresponds to at least one type allocation code, and the first condition is used to indicate any of the following: the number of the at least one type allocation codes, the number of terminal devices for each type allocation code in the at least one type allocation code, or information about the region to which the terminal device belongs; wherein, the first terminal device is located in the region to which the terminal device belongs.

22. The method according to any one of claims 16-21, characterized in that, The terminal device is identified as the terminal device's General Public User Identifier (GPSI), and the method further includes: Based on the GPSI of the terminal device, determine the SUPI corresponding to the GPSI; Based on the SUPI, determine the first type allocation code corresponding to the SUPI; Based on the first type of allocation code, the first chip manufacturer and / or the first terminal manufacturer are determined.

23. The method according to any one of claims 15-22, characterized in that, The list of allowed data consumers includes at least one of the following: an application function identifier, a chip manufacturer's application function identifier, the chip manufacturer's identifier, a terminal manufacturer's application function identifier, or the terminal manufacturer's identifier; wherein, the application function includes the first application function, the chip manufacturer includes the first chip manufacturer, and the terminal manufacturer includes the first terminal manufacturer.

24. The method according to any one of claims 15-23, characterized in that, The first network element is any one of the following: a network opening function network element, a network data analysis function network element, or a data collection and coordination function network element; The second network element is any one of the following: a unified data management network element, a unified data storage network element, or an access and mobility management network element.

25. A communication device, characterized in that, Includes modules for performing the method as described in any one of claims 1-24.

26. A communication device, characterized in that, include: At least one processor; The at least one processor is configured to run a computer program or instructions to enable the method as described in any one of claims 1-24 to be implemented.

27. A communication chip, characterized in that, It stores instructions that, when the chip is running on a communication device, cause the method as described in any one of claims 1-24 to be implemented.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-24.

29. A computer program product, characterized in that, The computer program product includes: a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1-24.

Images