Communication method, communication device and communication system

Abstract

Provided are a communication method, a communication device and a communication system. In the method, a server network element sends a first request to a first NEF network element, instructing the first NEF network element by means of the first request to execute a sample alignment task, wherein the first request comprises N NEF network element identifiers, and the N NEF network element identifiers are used by the first NEF network element to determine N NEF network elements; and upon receiving the first request, the first NEF network element sends target sample information to the server network element, wherein the target sample information is determined on the basis of sample information obtained by the N NEF network elements from different client network elements. The method enables a server network element to complete a sample alignment task by means of a single NEF network element in scenarios where multiple client network elements communicate with different NEF network elements.

Description

A communication method, communication device, and communication system

[0001] This application claims priority to Chinese Patent Application No. 2024112170149, filed on August 29, 2024, entitled "A Communication Method, Communication Device and Communication System", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] In mobile communication networks, some client network elements need to communicate with server network elements through network exposure function (NEF) network elements. To ensure data consistency between the server network element and multiple client network elements, the server network element needs to perform sample alignment with multiple client network elements through NEF network elements. However, in situations where multiple client network elements communicate with different NEF network elements, the server network element cannot achieve sample alignment through a single NEF network element. Summary of the Invention

[0004] This application provides a communication method, communication device, and communication system that can solve the problem that server-side network elements cannot achieve sample alignment through a single NEF network element.

[0005] Firstly, this application provides a communication method. This method is applied to a server-side network element and may include: sending a first request to a first network open function (NAF) network element, the first request including N ...

[0006] In the above scheme, when multiple client network elements communicate with different network open function network elements, the first request sent to the first network open function network element carries N network open function network element identifiers, enabling the first network open function network element to determine from which to obtain sample information. Thus, the first network open function network element can perform a sample alignment task based on the sample information obtained from the N network open function network elements. In other words, the server network element can complete the sample alignment task through the first network open function network element.

[0007] In one possible implementation, the method further includes: sending a second request to each of the N Network Open Functions (NOF) elements, wherein the second request includes master network element information, and the master network element information is used to instruct the first NOF element to determine the target sample information based on the sample information obtained by the N NOF elements.

[0008] In one possible implementation, the first request also includes main network element information.

[0009] In the above scheme, the request carries the main network element information. The main network element information can be used to instruct N network open function network elements. The first network open function network element is the network element that performs the sample alignment task. That is, the first network open function network element determines the target sample information based on the sample information obtained by the N network open function network elements.

[0010] In one possible implementation, the method further includes: sending a first request to the first network open function element based on the identity identifier of the first network open function element, wherein the identity identifier of the first network open function element is used to instruct the first network open function element to perform a sample alignment task.

[0011] In the above scheme, when the first network open function network element is pre-configured as the network open function network element that performs the sample alignment task, the server network element can determine that the first network open function network element is the network open function network element that performs the sample alignment task through the identity identifier of the first network open function network element.

[0012] In one possible implementation, before sending the first request to the first network open function element, the method further includes: sending a fourth request to N network open function elements, the fourth request being used to instruct the collection of sample information.

[0013] In the above scheme, before sending the first request, the network open function element is instructed to collect sample information, which can ensure that when the first network open function element performs the sample alignment task, all N network open function elements obtain the sample information.

[0014] In one possible implementation, the method further includes receiving response messages from N network open function elements, the response messages indicating successful acquisition of sample information.

[0015] In one possible implementation, the method further includes: sending the third sample information of the server network element to the first network open function network element, wherein the target sample information is determined based on the third sample information and the sample information obtained by N network open function network elements.

[0016] In the above scheme, the sample information of the server network element and the sample information of multiple client network elements can be aligned through the first network open function network element. The sample information of the multiple client network elements consists of sample information obtained by the first network open function network element and N network open function network elements.

[0017] In one possible implementation, the method further includes: determining sample information for the server-side network element to perform the vertical federation task based on the target sample information. The target sample information can be a subset of the sample information for the vertical federation task, or it can be the complete set of sample information for the vertical federation task.

[0018] Secondly, this application also provides a communication method. This method is applied to a Network Open Functions (NOF) element and may include: receiving a first request from a server element, the first request including N NOF identifiers, the first request being used to request the execution of a sample alignment task, where N is equal to or greater than 1; receiving sample information from the N NOF identifiers representing the N NOF elements; and sending target sample information to the server element, the target sample information being determined based on the sample information obtained from the N NOF elements.

[0019] In one possible implementation, the first request also includes master network element information, which is used to instruct the first network open function network element to determine the target sample information based on the sample information obtained by N network open function network elements.

[0020] In one possible implementation, before receiving sample information from N Network Open Functions (NOF) elements, the method further includes sending a third request to the N NOF elements, the third request being used to request the acquisition of sample information.

[0021] In one possible implementation, the third request includes main network element information and / or service identifier.

[0022] In one possible implementation, before receiving the first request, the method further includes: receiving a fourth request from a server network element, the fourth request being for requesting the collection of sample information; and obtaining the first sample information from a first client communicating with a first network open function element. After receiving the first request, the method further includes: determining target sample information based on the first sample information and the sample information obtained from N network open function elements.

[0023] In one possible implementation, after obtaining the first sample information, the method further includes: sending a response message to the server network element, the response message indicating that the sample information was successfully obtained.

[0024] In one possible implementation, the first request also includes third sample information of the server network element, and the method further includes: determining the target sample information based on the third sample information and sample information obtained from N network open function network elements.

[0025] Thirdly, this application also provides a communication method. This method is applied to a network open function element (NIC), comprising: receiving a second request from a server NIC, the second request including master NIC information, the master NIC information being used to instruct a first NIC to determine target sample information based on sample information obtained from N NICs, the master NIC information including a first NIC identifier, the N NICs including NICs, and N being greater than or equal to 1; and sending the second sample information to the first NIC identified by the first NIC identifier.

[0026] In one possible implementation, before sending the second sample information to the first network open function element, the method further includes: receiving a third request from the first network open function element, the third request being used to request the acquisition of sample information.

[0027] In one possible implementation, the third request includes main network element information, and the method further includes: sending second sample information to the first network open function network element when the main network element information in the third request is the same as the main network element information in the second request.

[0028] In one possible implementation, the third request includes a service identifier, and the method further includes: determining the second sample information to be sent based on the service identifier.

[0029] In one possible implementation, before receiving the second request, the method further includes: receiving a fourth request from a server network element, the fourth request being used to instruct the collection of sample information; and obtaining the second sample information from a second client communicating with a second network open function network element.

[0030] In one possible implementation, after obtaining the second sample information, the method further includes: sending a response message to the server network element, the response message indicating that the sample information was successfully obtained.

[0031] Fourthly, this application also provides a communication method. This method is applied to a Network Open Functions (NOF) element and includes: determining configuration information of the NOF element and sending the configuration information to a Network Storage Functions (NSF) element. The configuration information includes functional information, which is used to instruct the NOF element to support sample alignment tasks in a vertical federated association.

[0032] In one possible implementation, the functional information includes the alliance information of the vertical federation.

[0033] In one possible implementation, the method further includes: receiving the alliance information from the operation and maintenance management system.

[0034] In one possible implementation, the alliance information includes one or more of the following: the alliance identifier of the vertical federation alliance, the task identifier of the vertical federation task supported by the vertical federation alliance, the service identifier of the analysis service supported by the vertical federation alliance, and configuration information of one or more members of the vertical federation alliance; wherein the configuration information of the members includes one or more of the following: member identifier, member type, member identity information, member capability information, task identifier of the supported vertical federation task, service identifier of the supported analysis service, network information, and equipment vendor information.

[0035] In one possible implementation, the vertical federation includes a server network element and multiple client network elements, and the method further includes: receiving a first request from the server network element, the first request being used to request the execution of the sample alignment task; determining target sample information based on sample information obtained from the multiple client network elements; and sending the target sample information to the server network element.

[0036] Fifthly, this application also provides a communication device. This communication device is applied to a server-side network element and includes a transmitting module and a receiving module.

[0037] The sending module is used to send a first request to the first network open function network element. The first request includes N network open function network element identifiers. The N network open function network element identifiers are used by the first network open function network element to determine the N network open function network elements. The first request is used to request the execution of a sample alignment task. N is equal to or greater than 1.

[0038] The receiving module is used to receive target sample information from the first network open function element. The target sample information is determined based on the sample information obtained from N network open function elements.

[0039] In one possible implementation, the sending module is further configured to send a second request to each of the N Network Open Functions (NOF) elements. The second request includes master network element information, which is used to instruct the first NOF element to determine the target sample information based on the sample information obtained by the N NOF elements.

[0040] In one possible implementation, the first request also includes main network element information.

[0041] In one possible implementation, the sending module is further configured to send a first request to the first network open function element based on the identity identifier of the first network open function element, wherein the identity identifier of the first network open function element is used to instruct the first network open function element to perform a sample alignment task.

[0042] In one possible implementation, before sending the first request to the first network open function element, the sending module is further configured to send a fourth request to N network open function elements, the fourth request being used to instruct the collection of sample information.

[0043] In one possible implementation, the receiving module is further configured to receive response messages from N Network Open Functions (NOF) elements, the response messages indicating successful acquisition of sample information. In another possible implementation, the sending module is further configured to send third sample information of the server element to the first NOF element, the target sample information being determined based on the third sample information and the sample information acquired by the N NOF elements.

[0044] Sixthly, this application also provides a communication device. This communication device is applied to a first network open function element and includes a receiving module and a transmitting module.

[0045] The receiving module is used to receive a first request from a server network element. The first request includes N network open function network element identifiers. The first request is used to request the execution of a sample alignment task, where N is equal to or greater than 1.

[0046] The receiving module is also used to receive sample information from N Network Open Functions Network Elements identified by N Network Open Functions Network Element Identifiers.

[0047] The sending module is used to send target sample information to the server network element. The target sample information is determined based on the sample information obtained from N network open function network elements.

[0048] In one possible implementation, the first request also includes master network element information, which is used to instruct the first network open function network element to determine the target sample information based on the sample information obtained by N network open function network elements.

[0049] In one possible implementation, before receiving sample information from N Network Open Functions (NOF) elements, the sending module is further configured to send a third request to the N NOF elements, the third request being used to request the acquisition of sample information.

[0050] In one possible implementation, the third request includes main network element information and / or service identifier.

[0051] In one possible implementation, before receiving the first request, the receiving module is further configured to receive a fourth request from a server network element, the fourth request being for requesting the collection of sample information; and to obtain the first sample information from a first client communicating with the first network open function network element. After receiving the first request, the processing module included in the communication device is further configured to determine target sample information based on the first sample information and the sample information obtained by N network open function network elements.

[0052] In one possible implementation, after obtaining the first sample information, the sending module is also used to send a response message to the server network element, the response message indicating that the sample information was successfully obtained.

[0053] In one possible implementation, the first request also includes third sample information of the server network element, and the processing module included in the communication device is further configured to determine the target sample information based on the third sample information and sample information obtained by N network open function network elements.

[0054] Seventhly, this application also provides a communication device. This communication device is applied to a network open function element and includes a receiving module and a transmitting module.

[0055] The receiving module is used to receive a second request from a server network element. The second request includes master network element information. The master network element information is used to instruct the first network open function network element to determine the target sample information based on the sample information obtained by N network open function network elements. The master network element information includes the identifier of the first network open function network element. The N network open function network elements include the second network open function network element, and N is greater than or equal to 1.

[0056] The sending module is used to send the second sample information to the first network open function network element identified by the first network open function network element identifier.

[0057] In one possible implementation, before sending the second sample information to the first network open function element, the receiving module is further configured to receive a third request from the first network open function element, the third request being used to request the acquisition of sample information.

[0058] In one possible implementation, the third request includes main network element information, and the sending module is further configured to send second sample information to the first network open function network element when the main network element information in the third request is the same as the main network element information in the second request.

[0059] In one possible implementation, the third request includes a service identifier, and the sending module is further configured to determine the second sample information to be sent based on the service identifier.

[0060] In one possible implementation, before receiving the second request, the receiving module is further configured to receive a fourth request from the server network element, the fourth request being used to instruct the collection of sample information; and to obtain the second sample information from the second client communicating with the second network open function network element.

[0061] In one possible implementation, after obtaining the second sample information, the sending module is also used to send a response message to the server network element, the response message indicating that the sample information was successfully obtained.

[0062] Eighthly, this application also provides a communication device. This communication device is applied to a network open function element and includes a transmitting module.

[0063] In the operation, maintenance, and management section, the sending module determines the configuration information of the network open function element and sends this configuration information to the network storage function element. The configuration information includes functional information, which instructs the network open function element to support sample alignment tasks in a vertical federated association.

[0064] In one possible implementation, the functional information includes the alliance information of the vertical federation.

[0065] In one possible implementation, the communication device further includes a receiving module. The receiving module is used to receive the alliance information from the operation and maintenance management system.

[0066] In one possible implementation, the vertical federation includes a server network element and multiple client network elements. The receiving module is further configured to receive a first request from the server network element, the first request requesting the execution of a sample alignment task. The communication device also includes a processing module, configured to determine target sample information based on sample information obtained from the multiple client network elements. The sending module is further configured to send the target sample information to the server network element.

[0067] Ninthly, this application also provides a communication device, characterized in that it includes a processor and a memory, the processor being configured to execute instructions stored in the memory to cause the communication device to implement the communication method provided by the first aspect or any possible implementation of the first aspect, or to implement the communication method provided by the second aspect or any possible implementation of the second aspect, or to implement the communication method provided by the third aspect or any possible implementation of the third aspect, or to implement the communication method provided by the fourth aspect or any possible implementation of the fourth aspect.

[0068] In a tenth aspect, this application also provides a communication system. This communication system includes at least one communication device provided in the ninth aspect.

[0069] Eleventhly, this application also provides a chip. The chip is used to execute the communication method provided by the first aspect or any possible implementation thereof, or to execute the communication method provided by the second aspect or any possible implementation thereof, or to execute the communication method provided by the third aspect or any possible implementation thereof, or to execute the communication method provided by the fourth aspect or any possible implementation thereof.

[0070] In a twelfth aspect, this application also provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the communication method provided by the first aspect or any possible implementation thereof, or to perform the communication method provided by the second aspect or any possible implementation thereof, or to perform the communication method provided by the third aspect or any possible implementation thereof, or to perform the communication method provided by the fourth aspect or any possible implementation thereof.

[0071] In a thirteenth aspect, this application also provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the communication method provided by the first aspect or any possible implementation of the first aspect, or to perform the communication method provided by the second aspect or any possible implementation of the second aspect, or to perform the communication method provided by the third aspect or any possible implementation of the third aspect, or to perform the communication method provided by the fourth aspect or any possible implementation of the fourth aspect.

[0072] Any of the devices, communication equipment, communication systems, computer storage media, or computer program products provided above are used to perform the methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects of the corresponding solutions in the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0073] Figure 1 is a schematic diagram of the structure of a mobile communication network provided in an embodiment of this application;

[0074] Figures 2 to 6 are flowcharts of a communication method provided in an embodiment of this application;

[0075] Figure 7 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0076] Figure 8 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0077] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings.

[0078] In the description of the embodiments of this application, the words "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the words "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a specific manner.

[0079] In the description of the embodiments in this application, the term "and / or" is merely a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, B existing alone, and A and B existing simultaneously. Furthermore, unless otherwise stated, the term "multiple" means two or more. For example, multiple systems refer to two or more systems, and multiple screen terminals refer to two or more screen terminals.

[0080] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. The terms "comprising," "including," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0081] Before introducing the embodiments of this application, the terms mentioned in the embodiments of this application will be explained or described.

[0082] A vertical federation alliance (or vertical federated learning group) is an alliance of two or more members (or participants, or entities) that share resources to participate in joint activities or achieve common results. The members and their information are pre-configured. All or some members of a vertical federation alliance participate in a vertical federation task. A vertical federation task may include training a machine learning model and / or using the machine learning model for inference. A vertical federation task may also be called a vertical federation activity, a vertical federated learning task, a learning task, or a federated task, etc. Members of a vertical federation alliance may include one or more of the following: natural persons, companies, organizations, network elements, and networks. Members of a vertical federation alliance may also be a combination of various types of members, including natural persons, companies, organizations, network elements, and networks.

[0083] Vertical federations can be identified or distinguished through federation information. This information may include one or more of the following: the federation identity (ID), the task identifiers of the vertical federation tasks supported by the federation, the service identifiers of the analytics services supported by the federation, and the configuration information of the members of the federation.

[0084] The alliance identifier is used to identify vertical federal alliances.

[0085] The service identifier of the analysis service is used to identify the analysis services supported by the vertical federation. A vertical federation can support one or more analysis services. The analysis service can be associated with a model, meaning the model can be used to execute the analysis service. In other words, the model supports the analysis service identified by the service identifier. The model can include the machine learning model mentioned above. The analysis service can be, for example, facial recognition or network performance analysis. In the communications field, analysis services can include, for example, terminal anomaly detection and terminal session analysis (such as quality of service analysis).

[0086] The configuration information of a member may include one or more of the following: member identifier, member type, member identity information, member capability information, task identifier of supported vertical federated tasks, service identifier of supported analysis services, network information, and equipment vendor information.

[0087] Network data analytics function (NWDAF) network elements are key network elements in the core network of mobile communication networks. They are used to collect data (including data from user equipment, access network equipment, core network equipment, and third-party application equipment, or one or more of these). This data can be data from the user equipment, access network equipment, core network equipment, or third-party application equipment itself, or data from the user equipment on that specific access network equipment, core network equipment, or third-party application equipment. The collected data is then analyzed, and the analysis results are output for use by the network, network management equipment, and applications in decision-making. NWDAF network elements can utilize machine learning models for data analysis. The Third Generation Partnership Project (3GPP) has separated the training and inference functions of NWDAF network elements. An NWDAF network element can support only model training, only data inference, or both. The NWDAF network element supporting model training can also be called a training NWDAF network element, or an NWDAF network element supporting the model training logical function (MTLF) (abbreviated as MTLF). The training NWDAF network element can train the model based on the acquired data to obtain the trained model. The NWDAF network element supporting data inference can also be called an inference NWDAF network element, or an NWDAF network element supporting the analytics logical function (AnLF) (abbreviated as AnLF). The inference NWDAF network element can input input data into the trained model to obtain analysis results or inference data. In this embodiment, the training NWDAF network element refers to an NWDAF network element that at least supports model training. As a possible implementation method, the training NWDAF network element can also support data inference. The inference NWDAF network element refers to an NWDAF network element that at least supports data inference. As a possible implementation method, the inference NWDAF network element can also support model training. If an NWDAF network element supports both model training and data inference functions, then the NWDAF network element can be called a training NWDAF network element, an inference NWDAF network element, a training-inference NWDAF network element, or an NWDAF network element.In this embodiment of the application, the NWDAF network element can be a separate network element or it can be co-located with other network elements. For example, the NWDAF network element can be set in a policy control function (PCF) network element or an access and mobility management function (AMF) network element.

[0088] Network repository function (NRF) network elements can provide network element discovery capabilities, that is, based on requests from other network elements, provide network element information corresponding to the appropriate network element type. NRF network elements can also provide network element management services, such as network element registration, updating, deregistration, and network element status subscription and push.

[0089] Application function (AF) network elements refer to various services at the application layer that can be used to analyze and process data from users, and to provide user data or analyzed and processed data to other network elements for analysis and processing. AF network elements can include those deployed by network operators (e.g., AF network elements providing high-definition voice communication) or those provided by third parties. Third-party provided AF network elements can include those provided by other operators and / or other service providers (e.g., video servers, game servers, etc.). For AF network elements deployed by network operators, they can communicate directly with other network elements within the same trusted domain, or they can communicate with other network elements outside the same trusted domain through NEF network elements. For third-party provided AF network elements, they can communicate with other network elements in the mobile communication network (e.g., NWDAF network elements) through NEF network elements in the mobile communication network.

[0090] Network exposure function (NEF) elements reside in the core network of mobile communication networks. NEF elements can communicate with application function (AF) elements provided by external third parties to manage access to network data exposed to the outside world. External AF elements can obtain internal core network data through NEF elements. Conversely, NEF elements can also communicate with AF elements within the core network.

[0091] An operation administration and maintenance (OAM) system refers to an entity used to perform network operation, management, and / or maintenance functions. Of course, in other embodiments, it can also be a collection of network elements or systems used to perform network operation, management, and maintenance functions.

[0092] Unified data management (UDM) network elements can record the mapping relationship between GPSI and SUPI. NEF network elements can realize the conversion between GPSI and SUPI through UDM network elements.

[0093] A subscription permanent identifier (SUPI) is an identifier used by 3GPP networks to identify users. Network elements in a 3GPP network can identify users through their SUPIs.

[0094] The generic public subscription identifier (GPSI) is an identifier used by external networks outside of the 3GPP network to identify users. Network elements in external networks can identify users through the GPSI.

[0095] User equipment (UE) refers to the terminal equipment used by a user. UE can include, but is not limited to, smartphones, tablets, laptops, IoT devices, wearable devices, etc., allowing users to connect to mobile communication networks wirelessly and perform operations such as voice calls, data transmission, and internet access.

[0096] In a vertical federated association, the data maintained by the members of the association can serve as sample information for vertical federated tasks. Vertical federated tasks generally require members to use data from the same objects. Members of a vertical federated association can ensure sample consistency through sample alignment, that is, using data from the same objects for vertical federated tasks. Sample alignment can also be understood as the members of the vertical federated association determining which common objects' data to use for performing vertical federated tasks.

[0097] In mobile communication networks, members of a vertical federation alliance maintain data from different user equipment (UEs). UE data can include traffic data or service data. Members of a vertical federation alliance can ensure the use of data from the same UE for vertical federation tasks through sample alignment. Taking network elements as an example, members of a vertical federation alliance can include server-side network elements and client-side network elements. Server-side network elements are those that actively participate in vertical federation tasks, while client-side network elements are those that passively participate. When a server-side network element needs to perform sample alignment through NEF network elements, due to the large number of client-side network elements, the server-side network element may communicate with multiple client-side network elements through different NEF network elements. In this situation, the server-side network element cannot achieve sample alignment. This will be explained in detail below with reference to point 1.

[0098] Figure 1 is a schematic diagram of a mobile communication network provided in an embodiment of this application. This mobile communication network may include, but is not limited to, a 5G network. The mobile communication network may include a core network, an access network, and user equipment (e.g., UE1 to UE4). The user equipment accesses the core network through the access network.

[0099] As shown in Figure 1, the core network may include NWDAF network elements, NRF network elements, multiple NEF network elements (e.g., NEF network element 10 and NEF network element 20), and multiple AF network elements (e.g., AF network element 11, AF network element 12, and AF network element 21). The core network may also include an OAM system and UDM network elements (not shown in Figure 1). It should be noted that the network elements mentioned in this application refer to entities in the network used to implement specific functions, which may be physical devices or applications or software components deployed in physical devices. The number and type of network elements in the mobile communication network are not limited to those shown in Figure 1. In other embodiments, the mobile communication network may also include other numbers and / or types of network elements. The number of UEs in the mobile communication network is not limited to the number shown in Figure 1.

[0100] Taking the vertical federation members, including NWDAF, AF11, AF12, and AF21 in the network shown in Figure 1, as an example, the NWDAF element can act as a server element, while AF11, AF12, and AF21 can act as client elements. To ensure object consistency, NWDAF and AF elements need to perform sample alignment. As shown in Figure 1, AF11 and AF12 communicate with the NWDAF element through NEF10, and AF21 communicates with the NWDAF element through NEF20. That is, NEF10 provides services to AF11 and AF12, and NEF20 provides services to AF21. The NWDAF element can belong to a 3GPP network, while AF11, AF12, and AF21 may not belong to a 3GPP network. In some embodiments, AF network element 11, AF network element 12, and AF network element 21 may also belong to a 3GPP network, while the NWDAF network element may not belong to a 3GPP network. That is to say, the embodiments of this application do not impose specific restrictions on the networks to which the NWDAF network element and the AF network element belong, nor do they impose specific restrictions on whether the NWDAF network element and the AF network element belong to the same network.

[0101] In the case where AF network element 11, AF network element 12, and AF network element 21 and NWDAF network element are members of a vertical federation, NWDAF network element cannot achieve sample alignment because AF network element 11 and AF network element 12 communicate with NEF network element 10, and AF network element 21 communicates with NEF network element 20.

[0102] Therefore, embodiments of this application provide a communication method that can solve the above-mentioned problems.

[0103] In a communication method provided in this application embodiment, a server network element sends a first request to a first NEF network element, instructing the first NEF network element to perform a sample alignment task. The first request includes N NEF network element identifiers, which are used by the first NEF network element to identify N NEF network elements. After receiving the first request, the first NEF network element determines the target sample information based on the sample information obtained by the N N NEF network elements from different client network elements. This method enables the server network element to complete the sample alignment task through a single NEF network element, even when multiple client network elements communicate with different NEF network elements.

[0104] Next, taking the NWDAF network element shown in Figure 1 as the server network element, and the NEF network element 10 and NEF network element 20 shown in Figure 1 as the first NEF network element and the second NEF network element as the second NEF network element, the communication method provided in the embodiments of this application will be introduced.

[0105] Figure 2 is a flowchart of a communication method provided in an embodiment of this application. In the method shown in Figure 2, the NWDAF network element instructs the NEF network element 10 to determine the target sample information based on the sample information obtained by the NEF network element 20, thereby completing the sample alignment task through the NEF network element 10. As shown in Figure 2, the method may include steps S201-S210. The steps shown in Figure 2 are described below.

[0106] S201, the AF network element sends the configuration information of the AF network element to the NEF network element.

[0107] In the network shown in Figure 1, each AF network element can send its configuration information to the NEF network element during the registration process to register with the NEF network element. This step can specifically include S201a and S201b as shown in Figure 2. It should be noted that S201a and S201b in this embodiment are only used to distinguish the registration process of different AF network elements and do not indicate a sequential relationship.

[0108] In S201a, AF network element 11 can send its configuration information to NEF network element 10 to register with NEF network element 10. AF network element 12 can also send its configuration information to NEF network element 10 to register with NEF network element 10.

[0109] In S201b, AF network element 21 can send configuration information of AF network element 21 to NEF network element 20.

[0110] For example, the configuration information of an AF network element may include one or more of the AF network element identifier and the alliance information of the vertical federation to which the AF network element belongs. The specific alliance information of the vertical federation to which the AF network element belongs can be found in the description of the alliance information of the vertical federation described above in the embodiments of this application, and will not be repeated here.

[0111] In some embodiments, the configuration information of the AF network element can also be configured in the NEF network element through the OAM system.

[0112] S202, the NEF network element sends the configuration information of the NEF network element to the NRF network element.

[0113] In the core network shown in Figure 1, after the AF network element registers with the NEF network element, the NEF network element can send the NEF network element's configuration information to the NRF network element during the registration process.

[0114] For example, NEF network element 10 can send its configuration information to NRF network element during the registration process. Optionally, NEF network element 20 can also send its configuration information to NRF network element during the registration process.

[0115] The configuration information of a NEF network element includes the configuration information of AF network elements registered with the NEF network element. Optionally, the configuration information of a NEF network element may also include the NEF network element identifier (NEF Instance ID).

[0116] In the core network shown in Figure 1, the NWDAF network element can also send its configuration information to the NRF network element to register with it. In some embodiments, the AF network element can obtain the NWDAF network element's configuration information from the NRF network element through the NEF network element. The NWDAF network element's configuration information may include the NWDAF network element identifier and the association information of its vertical federation alliance. The association information of the vertical federation alliance to which the NWDAF network element belongs can be specifically referred to the above description of the association information of the vertical federation alliance in the embodiments of this application, and will not be repeated here.

[0117] S203, the NWDAF network element obtains the configuration information of M NEF network elements from the NRF network element, where M is equal to or greater than 2.

[0118] This step may include S203a and S203b as shown in Figure 2.

[0119] In S203a, an NWDAF network element can send a network element discovery request to an NRF network element. This request may include a network function type (NF type) field. The value of this NF type field is used by the NRF network element to determine the NEF network element type. The value of this NF type field allows the discovery of NEF network elements that communicate with the Z AF network elements that need to be aligned with the sample. These Z AF network elements may include all or some of the AF network elements in the vertical federation to which the NWDAF network element belongs.

[0120] In S203b, after receiving the network element discovery request, the NRF network element sends the configuration information of the M NEF network elements to the NWDAF network element. For example, the NRF network element can determine the configuration information of the M pre-registered NEF network elements based on the network element type field, and then send the configuration information of the M NEF network elements to the NWDAF network element. Taking Figure 1 as an example, the configuration information of the M NEF network elements may include the configuration information of NEF network element 10 and the configuration information of NEF network element 20.

[0121] In some embodiments, the network element discovery request may also include association information of the vertical federation to which the NWDAF network element belongs. In this way, the NRF network element can determine which NEF network elements communicate with AF network elements in the same federation as the NWDAF network element based on the association information of the vertical federation to which the NWDAF network element belongs, and then send the configuration information of the NEF network element to the NWDAF network element. Specifically, the NRF network element can compare the association information of the NWDAF network element with the association information of the AF network elements in the pre-registered configuration information of the NEF network elements; if they match, the NRF network element sends the configuration information of the NEF network element to the NWDAF network element.

[0122] S204, NWDAF network element determines the main network element identifier.

[0123] When M equals or is greater than 2, it indicates that the NWDAF network element needs to communicate with Z AF network elements through different NEF network elements. In this case, the NWDAF network element can use one of the M NEF network element identifiers as the primary network element identifier. Optionally, the NWDAF network element can use other NEF network element identifiers from the M NEF network element identifiers as secondary network element identifiers. Taking Figure 1 as an example, the NWDAF network element can use the network element identifier of NEF network element 10 as the primary network element identifier. Optionally, the NWDAF network element can use the network element identifier of NEF network element 20 as the secondary network element identifier.

[0124] The primary network element identifier is used to identify the primary network element. The primary network element is used to perform the sample alignment task. For example, the primary network element performing the sample alignment task may specifically include: determining the target sample information based on the sample information obtained by the secondary network element. The primary network element performing the sample alignment task may also specifically include: determining the target sample information based on the sample information obtained by both the primary and secondary network elements. Furthermore, the primary network element performing the sample alignment task may also specifically include: determining the target sample information based on the sample information supported by the server-side network element, as well as the sample information obtained by the primary and secondary network elements.

[0125] The auxiliary network element identifier is used to identify the auxiliary network element. The auxiliary network element provides sample information to the main network element to assist it in performing sample alignment tasks. It should be noted that the number of auxiliary network elements mentioned in this embodiment is not limited to one. That is, in practice, multiple auxiliary network elements may be included.

[0126] In some embodiments, the NEF network element may store its identity identifier. The NEF network element's identity identifier is used to indicate whether it is a primary or secondary network element. When the NEF network element's identity identifier indicates a primary network element, that NEF network element is used to perform the sample alignment task. When the NEF network element's identity identifier indicates a secondary network element, that NEF network element is used to provide the primary network element with the acquired sample information to assist in performing the sample alignment task. Optionally, the secondary network element can determine the primary network element through the primary network element information sent by the NWDAF network element. The secondary network element can also determine the primary network element based on the sample alignment request sent by the primary network element. The secondary network element can also determine the primary network element through pre-stored primary network element information.

[0127] Optionally, the configuration information sent by the NEF network element to the NRF network element may also include the identity identifier of the NEF network element. In this way, the NWDAF network element can determine the primary network element identifier and the secondary network element identifier based on the identity identifiers of the M NEF network elements. For example, when the identity identifier of NEF network element 10 indicates a primary network element, the NWDAF network element can use the network element identifier of NEF network element 10 as the primary network element identifier and the network element identifier of NEF network element 20 as the secondary network element identifier. That is, NEF network element 10 is the primary network element performing the sample alignment task, and NEF network element 20 is the secondary network element assisting in performing the sample alignment task.

[0128] S205, the NWDAF network element sends a sample alignment request to NEF network element 10 and NEF network element 20.

[0129] As described in S204, NEF network elements include primary network elements and secondary network elements. NWDAF network elements can send sample alignment requests to both primary and secondary network elements. The following description uses NEF network element 10 as the primary network element and NEF network element 20 as the secondary network element as an example.

[0130] In the case where the NWDAF network element sends a sample alignment request to NEF network element 10 and NEF network element 20, as shown in S205a of Figure 2, the NWDAF network element can send a sample alignment request R1 to NEF network element 10. This sample alignment request R1 is used to request NEF network element 10 to perform a sample alignment task.

[0131] In some embodiments, the sample alignment request R1 may include N NEF network element identifiers. NEF network element 10 can determine N NEF network elements based on these N NEF network element identifiers. These N NEF network elements are auxiliary network elements, and they belong to the M NEF network elements described in S204. Wherein, N is equal to or greater than 1.

[0132] In some embodiments, the sample alignment request R1 may further include master network element information. The master network element information is used to instruct NEF network element 10 to determine the target sample information based on the sample information obtained from N NEF network elements. That is, NEF network element 10 can determine that it is the master network element performing the sample alignment task based on the master network element information. Optionally, the master network element information may include a master network element identifier, such as the network element identifier of NEF network element 10. NEF network element 10 can determine that it is the master network element performing the sample alignment task based on the master network element identifier included in the master network element information in the sample alignment request R1.

[0133] In some embodiments, the sample alignment request R1 may further include auxiliary network element information. This auxiliary network element information instructs NEF network element 20 to provide sample information to NEF network element 10. The auxiliary network element information may include an auxiliary network element identifier, such as the network element identifier of NEF network element 20. NEF network element 10 can determine that NEF network element 20 is the auxiliary network element performing the sample alignment task based on the auxiliary network element information in the sample alignment request R1.

[0134] In some embodiments, the sample alignment request R1 may further include L first AF network element identifiers, where L is equal to or greater than 1. The L first AF network element identifiers belong to the aforementioned Z AF network element identifiers. The NEF network element 10 can obtain sample information from the L AF network elements identified by the L first AF network element identifiers.

[0135] In some embodiments, the sample alignment request R1 may also include a service identifier. The NEF network element 10 can determine from which AF network elements it needs to obtain sample information based on the service identifier.

[0136] In some embodiments, the sample alignment request R1 may also include third sample information supported by the NWDAF network element. The NEF network element 10 can perform sample alignment based on the third sample information. The specific process will be described in S209 and will not be repeated here.

[0137] In the case where the NWDAF network element sends a sample alignment request to NEF network element 10 and NEF network element 20, as shown in S205b of Figure 2, the NWDAF network element can send a sample alignment request R2 to NEF network element 20. This sample alignment request R2 is used to request NEF network element 20 to assist in performing the sample alignment task.

[0138] In some embodiments, the sample alignment request R2 may include primary network element information. This primary network element information indicates that NEF network element 10 is the primary network element performing the sample alignment task. Optionally, the sample alignment request R2 may also include secondary network element information. This secondary network element information indicates that NEF network element 20 is the secondary network element performing the sample alignment task.

[0139] In some embodiments, the sample alignment request R2 may further include P second AF element identifiers. Wherein, P is equal to or greater than 1. The P second AF element identifiers belong to the aforementioned Z AF element identifiers.

[0140] In some embodiments, the sample alignment request R2 may also include a service identifier. The NEF network element 20 can determine from which AF network elements it needs to obtain sample information based on the service identifier.

[0141] S206, the NEF network element obtains sample information from the AF network element.

[0142] As described in S204, NEF network elements are divided into main network elements and auxiliary network elements. The following is an introduction using NEF network element 10 as the main network element and NEF network element 20 as the auxiliary network element.

[0143] For NEF network element 10, after receiving the sample alignment request R1 from NWDAF network element 10, NEF network element 10 can obtain the first sample information from the AF network elements registered with NEF network element 10. The first sample information is the sample information supported by the AF network elements registered with NEF network element 10.

[0144] In some embodiments, when the sample alignment request R1 includes L first AF network element identifiers, NEF network element 10 can obtain first sample information from the L first AF network elements identified by the L first AF network element identifiers. Taking the L first AF network element identifiers including the network element identifier of AF network element 11 as an example, NEF network element 10 can obtain first sample information from AF network element 11.

[0145] In some embodiments, where the sample alignment request R1 does not include L first AF element identifiers, NEF element 10 can obtain first sample information from one or more AF elements registered with NEF element 10. For example, NEF element 10 can obtain first sample information from AF element 11 and AF element 12.

[0146] In some embodiments, when the sample alignment request R1 includes a service identifier, the NEF network element 10 can determine which AF network elements it needs to obtain sample information from based on the service identifier. Specifically, the NEF network element 10 can compare the service identifier included in the sample alignment request R1 with the service identifier of the analysis service supported by the AF network element 11 registered with the NEF network element 10. When the two are the same, the NEF network element 10 can obtain the first sample information from the AF network element 11.

[0147] For NEF network element 20, after receiving the sample alignment request R2 from NWDAF network element 20, it can obtain the second sample information from the AF network elements registered with NEF network element 20. The second sample information is the sample information supported by the AF network elements registered with NEF network element 20.

[0148] In some embodiments, when the sample alignment request R2 includes P second AF network element identifiers, NEF network element 20 can obtain second sample information from the P second AF network elements identified by the P second AF network element identifiers. Taking the P second AF network element identifiers including the network element identifier of AF network element 21 as an example, NEF network element 20 can obtain second sample information from AF network element 21.

[0149] In some embodiments, if the sample alignment request R2 does not include P second AF element identifiers, NEF element 20 can obtain the second sample information from one or more AF elements registered with NEF element 20. For example, NEF element 20 can obtain the second sample information from AF element 21.

[0150] In some embodiments, when the sample alignment request R2 includes a service identifier, the NEF network element 20 can determine from which AF network elements it needs to obtain sample information based on the service identifier. Specifically, the NEF network element 20 can compare the service identifier included in the sample alignment request R2 with the service identifier of the analysis service supported by the AF network element 21 registered with the NEF network element 20. When the two are the same, the NEF network element 20 can obtain the second sample information from the AF network element 21.

[0151] In some embodiments, when the sample alignment request R2 includes master network element information, the NEF network element 20 can compare the master network element information in the sample alignment request R2 with the network element identifier of the NEF network element 20. If they are different, it is determined that the NEF network element 20 is not the master network element performing the sample alignment task. Then, the second sample information is obtained, and the system waits for the master network element to send the sample alignment request.

[0152] In some embodiments, when the sample alignment request R2 includes auxiliary network element information, the NEF network element 20 can compare the auxiliary network element information in the sample alignment request R2 with the network element identifier of the NEF network element 20. If they are the same, the NEF network element 20 is determined to be the auxiliary network element performing the sample alignment task. Then, the second sample information is obtained, and the main network element is waited for the main network element to send the sample alignment request.

[0153] In some embodiments, where the sample alignment request R2 does not include primary and secondary network element information, NEF network element 20 can be configured as a secondary network element through the OAM system. Specifically, the OAM system can send the identity identifier of NEF network element 20 to NEF network element 20, and NEF network element 20 stores this identity identifier. The identity identifier of NEF network element 20 indicates that it is a secondary network element performing the sample alignment task, meaning it needs to provide sample information to the primary network element. Thus, after receiving the sample alignment request R2, NEF network element 20 can determine that it is a secondary network element through its stored identity identifier, then obtain the second sample information, and wait for the primary network element to send the sample alignment request.

[0154] In some embodiments, if the sample alignment request R2 does not include primary network element information and secondary network element information, NEF network element 20 can also determine the primary network element through the sample alignment request R3 sent by NEF network element 10. For details, please refer to the description in S208 below.

[0155] In some embodiments, when the sample alignment request R2 does not include primary network element information and secondary network element information, and NEF network element 10 does not send sample alignment request R3, NEF network element 20 can determine the primary network element based on the pre-stored primary network element information. For details, please refer to the description in S208 below.

[0156] S207, NEF element 10 sends a sample alignment request R3 to NEF element 20.

[0157] NEF network element 10 can determine itself as the main network element based on the main network element information included in the sample alignment request R1. Specifically, NEF network element 10 can compare the main network element information in the sample alignment request R1 with its network element identifier. If they are the same, it indicates that NEF network element 10 is the main network element performing the sample alignment task.

[0158] In some embodiments, where the sample alignment request R1 includes or excludes master network element information, the NEF network element 10 may store its identity identifier. The identity identifier of the NEF network element 10 is used to indicate that the NEF network element 10 is the master network element performing the sample alignment task. After receiving the sample alignment request R1, the NEF network element 10 can read its identity identifier from its storage space and determine that the NEF network element 10 is the master network element based on the identity identifier.

[0159] After determining NEF network element 10 as the primary network element, NEF network element 10 can send a sample alignment request to the N NEF network elements identified by the N NEF network element identifiers included in the sample alignment request R1. These N NEF network elements are secondary network elements. Taking NEF network element 20 as an example, as shown in Figure 2, NEF network element 10 can send a sample alignment request R3 to NEF network element 20. This sample alignment request R3 is used to request the acquisition of sample information from NEF network element 20.

[0160] In some embodiments, if the sample alignment request R1 does not include N NEF network element identifiers, the NEF network element 10 may pre-store auxiliary network element identifiers. For example, the NEF network element 10 may pre-store N NEF network element identifiers. When the NEF network element 10 receives the sample alignment request R1, it can read the N N NEF network element identifiers from its storage space and then send the sample alignment request to the N N NEF network elements identified by the N N NEF network element identifiers.

[0161] The following section uses the example of NEF network element 10 sending a sample alignment request R3 to NEF network element 20 to illustrate the sample request sent by the main network element to the auxiliary network element.

[0162] In some embodiments, the sample alignment request R3 may include master network element information. This master network element information can be used by NEF network element 20 to verify NEF network element 10 and determine whether to send sample information. The specific process will be described in S208 and will not be repeated here.

[0163] In some embodiments, the sample alignment request R3 may also include a service identifier. This service identifier can be used by NEF network element 20 to determine which sample information to send to NEF network element 10. The specific process will be described in S208 and will not be repeated here.

[0164] S208, NEF network element 20 receives sample alignment request R3 from NEF network element 10 and sends second sample information to NEF network element 10.

[0165] When NEF network element 20 receives a sample alignment request R3 from NEF network element 10, it can determine that NEF network element 10 is the master network element and can send the second sample information to NEF network element 10.

[0166] In some embodiments, when both sample alignment request R2 and sample alignment request R3 include master network element information, NEF network element 20 can compare the master network element information in sample alignment request R3 with the master network element information in sample alignment request R2. If they are the same, it can send the second sample information to NEF network element 10.

[0167] In some embodiments, when the sample alignment request R2 does not include main network element information and the sample alignment request R3 includes main network element information, the main network element identifier can be stored in the NEF network element 20. The NEF network element 20 can compare the pre-stored main network element identifier with the network element identifier of the NEF network element 10. If they are the same, the second sample information is sent to the NEF network element 10.

[0168] In some embodiments, where the sample alignment request R3 includes a service identifier, NEF network element 20 can determine which sample information to send based on the service identifier in the sample alignment request R3. Specifically, NEF network element 20 can compare the service identifiers of the analysis services supported by AF network element 21 communicating with NEF network element 20. If they are the same, NEF network element 20 can send the sample information obtained from AF network element 21 to NEF network element 10.

[0169] In some embodiments, when NEF network element 20 receives a sample alignment request R2 sent by NWDAF network element, and the sample alignment request R2 includes master network element information, NEF network element 20 can determine that the master network element is NEF network element 10 based on the master network element information included in the sample alignment request R2. After obtaining the second sample information, it can actively send the second sample information to NEF network element 10. That is, NEF network element 10 may not execute S207.

[0170] In some embodiments, when NEF network element 20 receives a sample alignment request R2 from NWDAF network element, and the sample alignment request R2 does not include master network element information, NEF network element 20 may store master network element information. NEF network element 20 can determine the master network element as NEF network element 10 based on the stored master network element information. After obtaining the second sample information, it can actively send the second sample information to NEF network element 10. That is, NEF network element 10 may not execute S207.

[0171] In some embodiments, after receiving the second sample information from the NEF network element 20, the NEF network element 10 sends a response message to the NEF network element 20 to indicate that the second sample information has been received.

[0172] S209, NEF network element 10 receives the second sample information from NEF network element 20 and determines the target sample information based on the second sample information.

[0173] NEF network element 10 can find the intersection of the first sample information acquired by NEF network element 10, the second sample information acquired by N NEF network elements, and the third sample information supported by NWDAF, and use the result of the intersection as the target sample information. The N N NEF network elements include NEF network element 20.

[0174] In some embodiments, NEF network element 10 can also find the intersection of the second sample information obtained by N NEF network elements, and use the result of the intersection as the target sample information. The N N NEF network elements include NEF network element 20.

[0175] In some embodiments, the NEF network element 10 can also find the intersection of the first sample information acquired by the NEF network element 10 and the second sample information acquired by N NEF network elements, and use the result of the intersection as the target sample information. In other words, the target sample information is the intersection of the first sample information acquired by the NEF network element 10 and the second sample information acquired by the N NEF network elements.

[0176] In some embodiments, the sample information may include a User Equipment Identifier (UEI). Taking the intersection of the first, second, and third sample information as an example, in the network shown in Figure 1, the UEI obtained by NEF network element 10 includes a first GPSI, the UEI obtained by N NEF network elements includes a second GPSI, and the UEI supported by NWDAF includes a third SUPI. NEF network element 10 can convert the first and second GPSI into a first and a second SUPI through a Unified Data Management (UDM) network element, and then use the result of the intersection of the first, second, and third SUPI as the target sample information. Furthermore, before sending the second GPSI to NEF network element 10, the N NEF network elements can also convert the second GPSI into a second SUPI through a UDM network element. This eliminates the need for the first NEF network element to convert the second GPSI again.

[0177] In some embodiments, the sample information may further include the Internet Protocol (IP) address of the User Equipment (UE). Taking the intersection of the first sample information, the second sample information, and the third sample information as an example, the NEF network element 10 can use the intersection of the UE's IP address obtained by the NEF network element 10, the UE's IP addresses obtained by N NEF network elements, and the UE's IP address supported by the NWDAF network element as the target sample information. In some embodiments, the sample information may further include an Application Function Specific ID (AF Specific ID). The NEF network element 10 can use the intersection of the AF Specific ID obtained by the NEF network element 10, the AF Specific ID obtained by N NEF network elements, and the AF Specific ID supported by the NWDAF network element as the target sample information.

[0178] S210, NEF network element 10 sends the target sample information to NWDAF network element.

[0179] NEF element 10 can also send the target sample information to L first AF elements, and send the target sample information to P second AF elements via NEF element 20. The target sample information can be a subset or the entire set of sample information used by the NEF element, the L first AF elements, and the P second AF elements to perform vertical federation tasks.

[0180] In the method embodiment shown in Figure 2 above, the sample alignment request R1 sent by the NWDAF network element to the NEF network element 10 includes N NEF network element identifiers. This allows the NEF network element 10 to determine which NEF network elements the sample information obtained is based on for sample alignment, thereby enabling the NWDAF network element to achieve sample alignment through the NEF network element 10.

[0181] Figure 3 is a flowchart of another communication method provided in an embodiment of this application. As shown in Figure 3, the method may include steps S301 to S311.

[0182] S301, the AF network element sends the configuration information of the AF network element to the NEF network element.

[0183] S302, the NEF network element sends the configuration information of the NEF network element to the NRF network element.

[0184] S303, the NWDAF network element obtains the configuration information of M NEF network elements from the NRF network element, where M is equal to or greater than 2.

[0185] S304, NWDAF network element determines the main network element identifier.

[0186] The specific processes of S301 to S304 mentioned above can be referred to the above description of S201 to S204 shown in Figure 2, and will not be repeated here.

[0187] S305, the NWDAF network element sends a sample alignment request R1 to the NEF network element 10.

[0188] The M NEF network elements include primary network elements and secondary network elements. NWDAF network elements can send sample alignment requests only to the primary network element, and obtain sample information from the secondary network elements through the primary network element. Taking NEF network element 10 as the primary network element, the NWDAF network element can send sample alignment request R1 only to NEF network element 10.

[0189] The sample alignment request R1 in this step can be referred to the description of sample alignment request R1 in the introduction of S205 shown in Figure 2 above, and will not be repeated here.

[0190] S306, NEF network element 10 obtains the first sample information from AF network element.

[0191] The process of NEF network element 10 acquiring the first sample information can be referred to the description of NEF network element 10 acquiring sample information in the introduction of S206 shown in Figure 2 above, and will not be repeated here.

[0192] S307, NEF element 10 sends a sample alignment request R3 to NEF element 20.

[0193] This step can be referred to the above description of S207 shown in Figure 2, and will not be repeated here.

[0194] S308, NEF network element 20 receives sample alignment request R3 from NEF network element 10 and obtains second sample information from AF network element.

[0195] When NEF network element 20 receives a sample alignment request R3 from NEF network element 10, it can determine that NEF network element 10 is the master network element. Then, it obtains the second sample information from the AF network elements registered with NEF network element 20 and sends the second sample information to NEF network element 10. The second sample information is the sample information supported by the AF network elements registered with NEF network element 20.

[0196] In some embodiments, when the sample alignment request R3 includes master network element information, the master network element identifier can be stored in the NEF network element 20. The NEF network element 20 can compare the pre-stored master network element identifier with the network element identifier of the NEF network element 10. If they are the same, the second sample information is sent to the NEF network element 10.

[0197] In some embodiments, when the sample alignment request R3 includes a service identifier, the NEF network element 20 can determine which AF network elements it needs to obtain sample information from based on the service identifier. Specifically, the NEF network element 20 can compare the service identifier included in the sample alignment request R3 with the service identifier of the analysis service supported by the AF network element 21 registered with the NEF network element 20. When the two are the same, the NEF network element 20 can obtain the second sample information from the AF network element 21.

[0198] S309, NEF element 20 sends the second sample information to NEF element 10.

[0199] S310, NEF network element 10 receives second sample information from NEF network element 20 and determines target sample information based on the second sample information.

[0200] S311, NEF network element 10 sends the target sample information to NWDAF network element.

[0201] The specific processes of S310 to S311 described above can be referred to the above description of S209 to S210 shown in Figure 2, and will not be repeated here.

[0202] Figure 4 is a flowchart of another communication method provided in an embodiment of this application. As shown in Figure 4, the method may include steps S401 to S412.

[0203] S401, the AF network element sends the configuration information of the AF network element to the NEF network element.

[0204] S402, the NEF network element sends the configuration information of the NEF network element to the NRF network element.

[0205] S403, the NWDAF network element obtains the configuration information of M NEF network elements from the NRF network element.

[0206] S404, NWDAF network element determines the main network element identifier.

[0207] In this embodiment, the specific processes of S401 to S404 can be referred to the description of S201 to S204 in the embodiment shown in Figure 2 above, and will not be repeated here.

[0208] S405, the NWDAF network element sends a sample collection request to the NEF network element.

[0209] An NWDAF network element can send a sample collection request to M NEF network elements to instruct the M NEF network elements to collect sample information. These M NEF network elements include a primary network element and secondary network elements. The following example uses NEF network element 10 as the primary network element and NEF network element 20 as the secondary network element.

[0210] For NEF network element 10, as shown in S405a of Figure 4, the NWDAF network element sends a sample collection request R4 to NEF network element 10. The sample collection request R4 may include a service identifier. Optionally, the sample collection request R4 may also include L first AF network element identifiers.

[0211] In some embodiments, the sample collection request R4 may further include L first AF network element identifiers, where L is equal to or greater than 1. The L first AF network element identifiers belong to the aforementioned Z AF network element identifiers. The NEF network element 10 can obtain sample information from the L AF network elements identified by the L first AF network element identifiers.

[0212] In some embodiments, the sample collection request R4 may also include a service identifier. The NEF network element 10 can determine from which AF network elements it needs to obtain sample information based on the service identifier.

[0213] For NEF network element 20, as shown in S405b of Figure 4, NWDAF network element sends a sample collection request R5 to NEF network element 20. The sample collection request R5 may include a service identifier. Optionally, the sample collection request R5 may also include P second AF network element identifiers.

[0214] In some embodiments, the sample collection request R5 may further include P second AF network element identifiers. Wherein, P is equal to or greater than 1. The P second AF network element identifiers belong to the aforementioned Z AF network element identifiers.

[0215] In some embodiments, the sample collection request R5 may also include a service identifier. The NEF network element 20 can determine from which AF network elements it needs to obtain sample information based on the service identifier.

[0216] S406, the NEF network element receives the sample collection request from the NWDAF network element and obtains sample information from the AF network element.

[0217] As mentioned earlier, the M NEF network elements are divided into primary network elements and secondary network elements. The following introduction will take NEF network element 10 as the primary network element and NEF network element 20 as the secondary network element as the example.

[0218] For NEF network element 10, after receiving the sample collection request R4 from NWDAF network element 10, NEF network element 10 can obtain the first sample information from the AF network elements registered with NEF network element 10. The first sample information is the sample information supported by the AF network elements registered with NEF network element 10.

[0219] In some embodiments, when the sample collection request R4 includes L first AF network element identifiers, NEF network element 10 can obtain first sample information from the L first AF network elements identified by the L first AF network element identifiers. Taking the L first AF network element identifiers including the network element identifier of AF network element 11 as an example, NEF network element 10 can obtain first sample information from AF network element 11.

[0220] In some embodiments, if the sample collection request R4 does not include L first AF element identifiers, NEF element 10 can obtain first sample information from one or more AF elements registered with NEF element 10. For example, NEF element 10 can obtain first sample information from AF element 11 and AF element 12.

[0221] In some embodiments, when the sample collection request R4 includes a service identifier, the NEF network element 10 can determine from which AF network elements it needs to obtain sample information based on the service identifier. Specifically, the NEF network element 10 can compare the service identifier included in the sample collection request R4 with the service identifier of the analysis service supported by the AF network element 11 registered with the NEF network element 10. When the two are the same, the NEF network element 10 can obtain the first sample information from the AF network element 11.

[0222] For NEF network element 20, after receiving a sample collection request R5 from NWDAF network element 20, it can obtain second sample information from the AF network elements registered with NEF network element 20. The second sample information is the sample information supported by the AF network elements registered with NEF network element 20.

[0223] In some embodiments, when the sample collection request R5 includes P second AF network element identifiers, NEF network element 20 can obtain second sample information from the P second AF network elements identified by the P second AF network element identifiers. Taking the P second AF network element identifiers including the network element identifier of AF network element 21 as an example, NEF network element 20 can obtain second sample information from AF network element 21.

[0224] In some embodiments, if the sample collection request R5 does not include P second AF element identifiers, NEF element 20 can obtain the second sample information from one or more AF elements registered with NEF element 20. For example, NEF element 20 can obtain the second sample information from AF element 21.

[0225] In some embodiments, when the sample collection request R5 includes a service identifier, the NEF network element 20 can determine which AF network elements it needs to obtain sample information from based on the service identifier. Specifically, the NEF network element 20 can compare the service identifier included in the sample collection request R5 with the service identifier of the analysis service supported by the AF network element 21 registered with the NEF network element 20. When the two are the same, the NEF network element 20 can obtain the second sample information from the AF network element 21.

[0226] S407, the NEF network element sends a response message to the NWDAF network element.

[0227] After the primary and secondary network elements obtain the sample information, they can send a response message to the NWDAF network element to indicate that the sample information was successfully obtained. As shown in S407a of Figure 4, NEF network element 10 can send a response message X1 to the NWDAF network element. Response message X1 indicates that NEF network element 10 successfully obtained the sample information. As shown in S407b of Figure 4, NEF network element 20 can send a response message X2 to the NWDAF network element. Response message X2 indicates that NEF network element 20 successfully obtained the sample information.

[0228] S408, the NWDAF network element receives the response message from the NEF network element and sends a sample alignment request to the NEF network element.

[0229] After the NWDAF network element determines, based on response messages X1 and X2, that both NEF network element 10 and NEF network element 20 have successfully obtained sample information, it sends a sample alignment request to the NEF network element. The specific process of the NWDAF network element sending the sample alignment request can be referred to the description of S205 in the embodiment shown in Figure 2 above, and will not be repeated here.

[0230] S409, NEF element 10 sends a sample alignment request R3 to NEF element 20.

[0231] S410, NEF network element 20 receives sample alignment request R3 from NEF network element 10 and sends second sample information to NEF network element 10.

[0232] S411, NEF network element 10 receives second sample information from NEF network element 20, and determines target sample information based on first sample information and second sample information.

[0233] S412, NEF network element 10 sends the target sample information to NWDAF network element.

[0234] The specific details of S409 to S412 can be found in the description of S207 to S210 in the embodiment shown in Figure 2 above, and will not be repeated here.

[0235] In the embodiment shown in Figure 4 above, NWDAF sends out a sample alignment request only after confirming that the response messages received from each NEF network element indicate that the sample information has been successfully acquired. This can avoid the problem of NEF network element 10 failing to align samples due to inconsistent time for each NEF network element to complete the collection of sample information.

[0236] Figure 5 is a flowchart of a communication method provided in an embodiment of this application. The method is executed by a server network element and a first Network Open Functions (NEF) network element. The server network element may include the NWDAF network element shown in Figure 1, and the first NEF network element may include the NEF network element 10 shown in Figure 1. As shown in Figure 5, the method may include steps S501 to S503.

[0237] S501, the first network open function network element receives the first request from the server network element.

[0238] The first request is used to request a first Network Open Functions (NOF) element to perform a sample alignment task. Performing the sample alignment task involves determining target sample information based on sample information obtained from N NOF elements. The target sample information can be a subset or the entire set of sample information used by the server and client elements to perform vertical federation tasks. A detailed description of this first request can be found in the above description of the sample alignment request R1 in S205 of Figure 2, and will not be repeated here.

[0239] In some embodiments, the first request may include master network element information. The master network element information is used to instruct a first network open function (NOF) element to determine target sample information based on sample information obtained from N NOF elements.

[0240] In some embodiments, the server network element may also send a second request to each of the N Network Open Functions (NOF) network elements. The second request is used to request sample information to be provided to the first NOF network element. A detailed description of the second request can be found in the description of the sample alignment request R2 in S205 shown in Figure 2 above, and will not be repeated here.

[0241] In some embodiments, prior to S501, the server network element can also obtain the configuration information of the first Network Open Functions (NOF) network element through the NRF network element, and send a first request to the first NOF network element based on the identity identifier included in the configuration information of the first NOF network element. The identity identifier of the first NOF network element is used to instruct the first NOF network element to perform a sample alignment task. The process by which the server network element obtains the configuration information of the first NOF network element can be referred to the above description of S203 shown in Figure 3, and will not be repeated here.

[0242] In some embodiments, prior to S501, the server network element may send a fourth request to N Network Open Functions (NETF) network elements. This fourth request is used to instruct the collection of sample information. Optionally, in some embodiments, the server network element may also receive response messages from the N NETF network elements. These response messages are used to indicate successful acquisition of sample information. The process of pre-collecting sample information through the fourth request can be referred to the description of S305 and S306 in the embodiment shown in FIG3, and will not be repeated here. The description of the fourth request can be referred to the description of sample collection requests R4 and R5 in the embodiment shown in FIG3, and will not be repeated here.

[0243] In some embodiments, the server-side network element may also send third sample information supported by the server-side network element to the first network open function network element. This third sample information is used by the first network open function network element to determine the target sample information; the specific process will be described in S502 and will not be repeated here. It should be noted that the server-side network element can carry the third sample information through the first request, or it can send the third sample information after sending the first request or before sending the first request.

[0244] S502, the first NEF network element receives sample information from N Network Open Function Network Elements identified by N Network Open Function Network Element Identifiers.

[0245] In some embodiments, after receiving the first request, the first Network Open Function (NOF) element can send a third request to each of the N NOF elements to request the acquisition of sample information obtained by the N NOF elements. Upon receiving the third request, the N NOF elements can determine which sample information to send to the first NOF element based on the third request. The process by which the first NOF element acquires sample information from the N NOF elements can be specifically referred to in the description of S206 in the embodiment shown in Figure 2 above, and will not be repeated here. The third request can be referred to in the description of the sample alignment request R3 in S206 above, and will not be repeated here.

[0246] S503, the first NEF network element sends the target sample information to the server network element.

[0247] The target sample information is determined by the first network open function network element based on the first sample information obtained by the first network open function network element, the second sample information obtained by N network open function network elements, and the third sample information supported by the server network element. The specific process can be referred to the above description of S210 in Figure 2, and will not be repeated here.

[0248] In some embodiments, after N network open function network elements receive the second request from the server network element, they can also proactively send sample information to the first network open function network element.

[0249] In the above method embodiments, by carrying N network open function network element identifiers in the first request sent to the first network open function network element, the server network element can enable the first network open function network element to obtain sample information from the N network open function network elements, and determine the target sample information based on the sample information obtained from the N network open function network elements, thereby achieving sample alignment.

[0250] The request sent by the server network element carries the main network element information. The main network element information can be used to instruct the network open function network element to determine the target sample information based on the sample information obtained by N network open function network elements. That is, the first network open function network element performs the sample alignment task.

[0251] Figure 6 is a flowchart of another communication method provided in an embodiment of this application. This method can be applied to NEF network elements. As shown in Figure 6, the method may include steps S601 to S605.

[0252] S601, NEF network element determines the configuration information of NEF network element.

[0253] The configuration information of an NEF network element may include its functional information. This functional information indicates that the NEF network element supports sample alignment tasks in vertical federations. In addition, the configuration information of an NEF network element may also include one or more of the following: the network element identifier and other information about the NEF network element.

[0254] The aforementioned vertical federation can include server-side network elements and multiple client-side network elements. Specifically, the NEF network element supporting the sample alignment task in the vertical federation can allow the server-side network element to perform sample alignment based on sample information supported by multiple client-side network elements. For example, the server-side network element is an NWDAF network element, and the client-side network elements include AF network element 11, AF network element 12, and AF network element 21. The NWDAF network element can perform sample alignment based on the sample information supported by AF network element 11, AF network element 12, and AF network element 21 through the NEF network element.

[0255] Optionally, the functional information may include the alliance information of the vertical federation. The specific alliance information of the vertical federation can be found in the description of the alliance information of the vertical federation described above in the embodiments of this application, and will not be repeated here. In one implementation, the NEF network element can obtain the alliance information of the vertical federation from the OAM system. That is, the alliance information of the vertical federation can be configured in the NEF network element through the OAM system.

[0256] S602, the NEF network element sends the configuration information of the NEF network element to the NRF network element.

[0257] NEF network elements can send registration requests to NRF network elements to register with them. These registration requests may include the NEF network element's configuration information.

[0258] S603, the server network element obtains the configuration information of the NEF network element through the NRF network element and sends a sample alignment request to the NEF network element.

[0259] Taking the NWDAF network element as an example, the NWDAF network element can discover the NEF network element through the NRF network element. Specifically, the NWDAF network element can obtain the configuration information of the NEF network element through the NRF network element. The specific process by which the NWDAF network element obtains the configuration information of the NEF network element can be referred to the above description of S203 shown in Figure 2, and will not be repeated here.

[0260] The NWDAF network element determines, based on the functional information included in the NEF network element's configuration information, whether the NEF network element supports the sample alignment task of the vertical federation to which the NWDAF network element belongs, and then sends a sample alignment request to the NEF network element.

[0261] S604, the NEF network element receives a sample alignment request and determines the target sample information based on the sample information obtained from the client network element.

[0262] After receiving a sample alignment request from the NWDAF network element, the NEF network element obtains the sample information supported by each of the AF network elements 11, 12, and 21. Then, it can use the same sample information from the sample information supported by each of the AF network elements 11, 12, and 21 as the target sample information.

[0263] S605, the NEF network element sends the target sample information to the server network element.

[0264] NEF network elements can send target sample information to NWDAF network elements. Optionally, NEF network elements can also send target sample information to AF network elements 11, 12, and 21. The target sample information can be a subset or the entire set of sample information used by NWDAF network elements, AF network elements 11, 12, and 21 in vertical federation tasks.

[0265] As shown in Figure 6 above, the attribute information registered by the NEF network element to the NRF network element carries functional information, which allows the server network element to determine whether the NEF network element supports the sample alignment task of the consortium to which the server network element belongs. In other words, the NEF network element can communicate with client network elements in the consortium to which the server network element belongs. Therefore, the server network element can achieve sample alignment through this NEF network element.

[0266] This application also provides a communication device. This communication device can be used to execute all or part of the steps in the method embodiments shown in FIG2, FIG3, FIG4, FIG5, or FIG6.

[0267] Figure 7 is a schematic diagram of the structure of a communication device 700 provided in an embodiment of this application. As shown in Figure 7, the communication device 700 may include a transmitting module 701 and a receiving module 702.

[0268] When the communication device 700 is used to execute the steps in the method embodiments shown in FIG2, FIG3 or FIG4, the communication device 700 can be used to execute the steps executed by the NWDAF network element, the steps executed by the NEF network element 10, and the steps executed by the NEF network element 20.

[0269] When the communication device 700 is used to execute the steps in the method embodiment shown in FIG5, the communication device 700 can be applied to a server network element to execute the steps performed by the server network element. Specifically, the sending module 701 is used to send a first request to the first network open function network element. The first request includes N network open function network element identifiers, which are used by the first network open function network element to determine N network open function network elements. The first request is used to request the execution of a sample alignment task, where N is equal to or greater than 1. The receiving module 702 is used to receive target sample information from the first network open function network element, which is determined based on the sample information obtained from the N network open function network elements.

[0270] When the communication device 700 is used to execute the steps in the method embodiment shown in FIG5, the communication device 700 can also be applied to the first NEF network element to execute the steps executed by the first NEF network element. Specifically, as shown in FIG7, the communication device 700 may further include a processing module 703. The receiving module 702 is used to receive a first request from the server network element. The first request includes N Network Open Functions (NEF) network element identifiers. The N ...

[0271] When the communication device 700 is used to execute the steps in the method embodiment shown in FIG5, the communication device 700 can also be applied to the first NEF network element to execute the steps executed by the second NEF network element. Specifically, the receiving module 702 is used to receive a second request from the server network element. The second request includes master network element information, which instructs the first Network Open Functions (NOF) network element to determine target sample information based on sample information obtained from N NOF network elements, where the N NOF network elements include the second NOF network element, and N is greater than or equal to 1. The sending module 701 is used to send the second sample information to the first NOF network element.

[0272] When the communication device 700 is used to execute the steps in the method embodiment shown in FIG6, the communication device 700 can be used to execute the steps executed by the NEF network element.

[0273] It should be noted that the communication device 700 provided in the embodiment shown in Figure 7 is only illustrated by the division of the above-mentioned functional modules when executing the communication method. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the communication device 700 provided in the above embodiments belongs to the same concept as the method embodiments shown in Figures 2, 3, 4, 5 or 6. Its specific implementation process can be referred to the description in the method embodiments and the invention content, and will not be repeated here.

[0274] Figure 8 is a schematic diagram of the hardware structure of a communication device 800 provided in an embodiment of this application. The communication device 800 can be the server network element or client network element described above. Alternatively, the communication device 800 may have both server network elements and / or client network elements deployed within it.

[0275] Referring to Figure 8, the communication device 800 includes a processor 801, a memory 802, a communication interface 803, and a bus 804. The processor 801, memory 802, and communication interface 803 are connected to each other via the bus 804. The processor 801, memory 802, and communication interface 803 can also be connected using other methods besides the bus 804.

[0276] The memory 802 can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), flash memory, optical storage, hard disk, etc.

[0277] The processor 801 can be a general-purpose processor or a central processing unit (CPU). The processor 801 performs specific steps and / or operations by reading and executing contents stored in memory (e.g., memory 802). The processor 801 may include at least one circuit to perform all or part of the steps of the methods provided in the embodiments shown in FIG. 2, FIG. 3, FIG. 4, FIG. 5, or FIG. 6.

[0278] The communication interface 803 includes input / output (I / O) interfaces, physical interfaces, and logical interfaces for interconnecting devices within the communication device 800, as well as interfaces for interconnecting the communication device 800 with other devices (such as other computing devices or user equipment). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.

[0279] The bus 804 can be any type of communication bus used to interconnect the processor 801, memory 802 and communication interface 803, such as a system bus.

[0280] The aforementioned devices can be disposed on separate chips, or at least partially or entirely on the same chip. Whether to dispose of the devices independently on different chips or integrate them on one or more chips often depends on the needs of the product design. This application does not limit the specific implementation of the aforementioned devices.

[0281] The communication device 800 shown in Figure 8 is merely an example. In the implementation process, the communication device 800 may also include other components, which will not be listed one by one in this article.

[0282] Based on the communication device 800 shown in FIG8, this application embodiment also provides a communication system. The communication system may include multiple communication devices 800 shown in FIG7.

[0283] In one implementation, one or more communication devices 800 in the communication system can be used to perform the steps executed by the NWDAF network element in the method embodiment shown in FIG2, FIG3 or FIG4, and can also be used to perform the steps executed by the NEF network element 10 in the method embodiment shown in FIG2, FIG3 or FIG4, and can also be used to perform the steps executed by the NEF network element 20 in the method embodiment shown in FIG2, FIG3 or FIG4.

[0284] In one implementation, one or more communication devices 800 in the communication system can be used to execute the steps executed by the server network element in the method embodiment shown in FIG5, and can also be used to execute the steps executed by the first NEF network element in the method embodiment shown in FIG5, and can also be used to execute the steps executed by the second NEF network element in the method embodiment shown in FIG5.

[0285] In one implementation, one or more communication devices 800 in the communication system can be used for the steps performed by the NEF network element in the method embodiment shown in FIG6.

[0286] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or sample information center to another website, computer, server, or sample information center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a sample information storage device such as a server or sample information center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0287] It is understood that the 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. It should be understood that in the embodiments of this application, the order of the process numbers does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0288] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, Applied to a first network open function element, the method includes: Receive a first request from a server network element. The first request includes N network open function network element identifiers. The first request is used to request the execution of a sample alignment task. N is equal to or greater than 1. Receive sample information from the N Network Open Functions (NOF) elements identified by the N NOF element identifiers; The target sample information is sent to the server network element, and the target sample information is determined based on the sample information obtained by the N network open function network elements.

2. The method according to claim 1, characterized in that, The first request also includes master network element information, which is used to instruct the first network open function network element to determine the target sample information based on the sample information obtained by the N network open function network elements.

3. The method according to claim 1 or 2, characterized in that, Before receiving sample information from the N Network Open Functions (NICs) identified by the N NIC identifiers, the method further includes: A third request is sent to the N network open function elements, the third request being used to request the acquisition of sample information.

4. The method according to claim 3, characterized in that, The third request includes main network element information and / or service identifier.

5. The method according to any one of claims 1-4, characterized in that, Before receiving the first request, the method further includes: Receive a fourth request from the server network element, the fourth request being used to request the collection of sample information; First sample information is obtained from a first client that communicates with the first network open function network element; After receiving the first request, the method further includes: The target sample information is determined based on the first sample information and the sample information obtained from the N network open function elements.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Receive third sample information from the server network element. The target sample information is determined based on the third sample information and the sample information obtained from the N network open function elements.

7. A communication method, characterized in that, Applied to server-side network elements, the method includes: Send a first request to the first network open function element. The first request includes N network open function element identifiers. The N network open function element identifiers are used by the first network open function element to determine N network open function elements. The first request is used to request the execution of a sample alignment task. N is equal to or greater than 1. Receive target sample information from the first network open function element, wherein the target sample information is determined based on the sample information obtained from the N network open function elements.

8. The method according to claim 7, characterized in that, The method further includes: A second request is sent to each of the N network open function network elements. The second request includes master network element information, which is used to instruct the first network open function network element to determine the target sample information based on the sample information obtained by the N network open function network elements.

9. The method according to claim 7 or 8, characterized in that, The first request also includes main network element information.

10. The method according to claim 8 or 9, characterized in that, The method further includes: Based on the identity identifier of the first network open function element, the first request is sent to the first network open function element, and the identity identifier of the first network open function element is used to instruct the first network open function element to perform the sample alignment task.

11. The method according to any one of claims 7-10, characterized in that, Before sending the first request to the first network open function element, the method further includes: A fourth request is sent to the N network open function elements, the fourth request being used to instruct the collection of sample information.

12. The method according to any one of claims 7-11, characterized in that, The method further includes: The third sample information of the server network element is sent to the first network open function network element. The target sample information is determined based on the third sample information and the sample information obtained by the N network open function network elements.

13. A communication method, characterized in that, Applied to network open function elements, the method includes: Receive a second request from a server network element. The second request includes master network element information. The master network element information is used to instruct a first network open function network element to determine target sample information based on sample information obtained from N network open function network elements. The master network element information includes the identifier of the first network open function network element. The N network open function network elements include the network open function network element, and N is greater than or equal to 1. Send the second sample information to the first network open function network element identified by the first network open function network element identifier.

14. The method according to claim 13, characterized in that, Before sending the second sample information to the first network open function element, the method further includes: A third request is received from the first network open function element, the third request being used to request the acquisition of sample information.

15. The method according to claim 14, characterized in that, The third request includes main network element information, and the method further includes: If the main network element information in the third request is the same as the main network element information in the second request, the second sample information is sent to the first network open function network element.

16. The method according to claim 14 or 15, characterized in that, The third request includes a service identifier, and the method further includes: The second sample information is sent based on the service identifier.

17. The method according to any one of claims 13-16, characterized in that, Before receiving the second request, the method further includes: Receive a fourth request from the server network element, the fourth request being used to instruct the collection of sample information; The second sample information is obtained from a second client that communicates with the second network open function element.

18. A communication method, characterized in that, Applied to network open function elements, the method includes: The configuration information of the network open function element is determined, the configuration information including function information, the function information being used to indicate that the network open function element supports the sample alignment task of the vertical federation alliance; The configuration information is sent to the network storage function network element.

19. The method according to claim 18, characterized in that, The functional information includes the alliance information of the vertical federal alliance.

20. The method according to claim 19, characterized in that, The method further includes: Receive the alliance information from the operation and maintenance management system.

21. The method according to any one of claims 18-20, characterized in that, The vertical federation includes server-side network elements and multiple client-side network elements, and the method further includes: Receive a first request from the server network element, the first request being used to request the execution of the sample alignment task; Target sample information is determined based on sample information obtained from the multiple client network elements; The target sample information is sent to the server network element.

22. A communication device, characterized in that, The communication device, applied to server-side network elements, includes: The sending module is used to send a first request to a first network open function element. The first request includes N network open function element identifiers. The N network open function element identifiers are used by the first network open function element to determine N network open function elements. The first request is used to request the execution of a sample alignment task, where N is equal to or greater than 1. The receiving module is used to receive target sample information from the first network open function element, wherein the target sample information is determined based on the sample information obtained from the N network open function elements.

23. A communication device, characterized in that, The communication device, applied to the first network open function network element, includes: The receiving module is used to receive a first request from a server network element. The first request includes N network open function network element identifiers. The first request is used to request the execution of a sample alignment task, where N is equal to or greater than 1. The receiving module is also configured to receive sample information from the N Network Open Functions Network Elements identified by the N Network Open Functions Network Element Identifiers; The sending module is used to send target sample information to the server network element, wherein the target sample information is determined based on the sample information obtained by the N network open function network elements.

24. A communication device, characterized in that, The communication device, applied to network open function network elements, includes: The receiving module is used to receive a second request from a server network element. The second request includes master network element information. The master network element information is used to instruct a first network open function network element to determine target sample information based on sample information obtained from N network open function network elements. The master network element information includes the identifier of the first network open function network element. The N network open function network elements include the second network open function network element, and N is greater than or equal to 1. The sending module is used to send the second sample information to the first network open function network element identified by the first network open function network element identifier.

25. A communication device, characterized in that, The communication device, applied to network open function network elements, includes: The sending module is used to determine the configuration information of the network open function element and send the configuration information to the network storage function element. The configuration information includes function information, which is used to instruct the network open function element to support the sample alignment task of the vertical federation.

26. A communication device, characterized in that, The device includes a processor and a memory, the processor being configured to execute instructions stored in the memory to cause the communication device to perform the method of any one of claims 1 to 6, or the method of any one of claims 7 to 12, or the method of any one of claims 13 to 17, or the method of any one of claims 18 to 21.

27. A communication system, characterized in that, The communication system includes at least one communication device as described in claim 26.

28. A chip, characterized in that, The chip is used to perform the method according to any one of claims 1 to 6, or the method according to any one of claims 7 to 12, or the method according to any one of claims 13 to 17, or the method according to any one of claims 18 to 21.

29. A computer-readable storage medium, characterized in that, Includes instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 6, or the method of any one of claims 7 to 12, or the method of any one of claims 13 to 17, or the method of any one of claims 18 to 21.

30. A computer program product, characterized in that, Includes instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 6, or the method of any one of claims 7 to 12, or the method of any one of claims 13 to 17, or the method of any one of claims 18 to 21.

Images