Third-party service management method / device / equipment and storage medium

Abstract

The invention provides a third-party service management method / device / equipment / storage medium, and belongs to the technical field of communication. An NEF network element receives a first management request sent by an AF network element and used for managing a third-party service, the first management request indicates the third-party service provided by a third-party application, and then the NEF network element manages the third-party service based on the first management request and returns a management result to the AF network element. Therefore, the third-party service management method provided by the invention can be used for managing the third-party service, so that the NRF network element knows the service provided by the third-party service, and the NRF network element discovers and uses the third-party service to provide the service for the NF network element.

Description

A third-party service management method / device / equipment and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a third-party service management method / device / equipment and storage medium. Background Art

[0002] In future network systems, a variety of new services (such as AI services and perception services) will be introduced to improve the richness of network services. These new services may be provided by nodes within the network or by third parties outside the network. When these new services are provided by third parties, there is currently no method for the network to manage and call services provided by third parties.

[0003] Summary of the Invention

[0004] The third-party service management method / device / equipment and storage medium proposed in this disclosure are used to manage third-party services provided by third-party applications.

[0005] In a first aspect, an embodiment of the present disclosure provides a third-party service management method, which is executed by an NEF network element and includes:

[0006] receiving a first management request for managing a third-party service sent by an application function AF network element, where the first management request indicates a third-party service provided by a third-party application;

[0007] managing the third-party service based on the first management request;

[0008] Return the management result to the AF network element.

[0009] In the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party services, such as specifically registering and / or deregistering the third-party services. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0010] In a second aspect, an embodiment of the present disclosure provides a third-party service management method, which is executed by an NRF network element and includes:

[0011] receiving a second management request for managing a third-party service sent by the NEF network element, where the second management request indicates a third-party service provided by a third-party application;

[0012] managing the third-party service based on the second management request;

[0013] Return the management result to the NEF network element.

[0014] In a third aspect, an embodiment of the present disclosure provides a third-party service management method, which is executed by an AF network element and includes:

[0015] Sending a first management request for managing a third-party service to an NEF network element, where the first management request indicates a third-party service provided by a third-party application;

[0016] Receive the management result returned by the NEF network element.

[0017] In a fourth aspect, an embodiment of the present disclosure provides a communication device, which is configured in an NEF network element, including:

[0018] a transceiver module, configured to receive a first management request for managing a third-party service sent by an application function AF network element, wherein the first management request indicates a third-party service provided by a third-party application;

[0019] a management module, configured to manage the third-party service based on the first management request;

[0020] The transceiver module is further configured to return a management result to the AF network element.

[0021] In a fifth aspect, an embodiment of the present disclosure provides a communication device, which is configured in an NRF network element, including:

[0022] a transceiver module, configured to receive a second management request for managing a third-party service sent by the NEF network element, wherein the second management request indicates a third-party service provided by a third-party application;

[0023] a management module, configured to manage the third-party service based on the second management request;

[0024] The transceiver module is further configured to return a management result to the NEF network element.

[0025] In a sixth aspect, an embodiment of the present disclosure provides a communication device, which is configured in an AF network element, including:

[0026] a transceiver module, configured to send a first management request for managing a third-party service to an NEF network element, wherein the first management request indicates a third-party service provided by a third-party application;

[0027] The transceiver module is further configured to receive the management result returned by the NEF network element.

[0028] In a seventh aspect, an embodiment of the present disclosure provides a communication system, the system comprising:

[0029] A first network element is configured to send a first management request for managing a third-party service, where the first management request indicates a third-party service provided by a third-party application;

[0030] a second network element, configured to receive the first management request for managing the third-party service and manage the third-party service based on the first management request;

[0031] The second network element is further configured to send a second management request for managing a third-party service, where the second management request indicates a third-party service provided by a third-party application;

[0032] a third network element, configured to receive the second management request for managing the third-party service, manage the third-party service based on the second management request, and return a management result to the second network element;

[0033] The second network element is further configured to return a management result to the first network element;

[0034] The first network element is further used to receive the management result returned by the second network element.

[0035] In an eighth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, it executes the method described in the first aspect above.

[0036] In a ninth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, it executes the method described in the second aspect above.

[0037] In a tenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, it executes the method described in the third aspect above.

[0038] In the eleventh aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the first aspect above.

[0039] In the twelfth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the second aspect above.

[0040] In the thirteenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the third aspect above.

[0041] In a fourteenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the first aspect above.

[0042] In a fifteenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the second aspect above.

[0043] In the sixteenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the third aspect above.

[0044] In aspect seventeen, an embodiment of the present disclosure provides a communication system, which includes the communication device described in aspect four to the communication device described in aspect six, or the system includes the communication device described in aspect eight to the communication device described in aspect ten, or the system includes the communication device described in aspect eleven to the communication device described in aspect thirteen, or the system includes the communication device described in aspect fourteen to the communication device described in aspect sixteen.

[0045] In the eighteenth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions used by the above-mentioned network device, and when the instructions are executed, the terminal device executes the method described in any one of the above-mentioned aspects from the first to the third aspects.

[0046] In a nineteenth aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in any one of the first to third aspects above.

[0047] In a twentieth aspect, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a network device in implementing the functions described in any one of the methods described in aspects one to three, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system further comprises a memory for storing computer programs and data necessary for the source slave node. The chip system may be composed of a chip or may include a chip and other discrete devices.

[0048] In a twenty-first aspect, the present disclosure provides a computer program which, when executed on a computer, enables the computer to execute the method described in any one of the first to third aspects above. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] The above and / or additional aspects and advantages of the present disclosure will become apparent and readily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0050] FIG1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0051] FIG2 is a flow chart of a third-party service management method provided by another embodiment of the present disclosure;

[0052] FIG3 is a flow chart of a third-party service management method provided in yet another embodiment of the present disclosure;

[0053] FIG4 is a flow chart of a third-party service management method provided by another embodiment of the present disclosure;

[0054] FIG5 is a flow chart of a third-party service management method provided by another embodiment of the present disclosure;

[0055] FIG6 is a flow chart of a third-party service management method provided in yet another embodiment of the present disclosure;

[0056] FIG7 is a flow chart of a third-party service management method provided by another embodiment of the present disclosure;

[0057] FIG8 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure;

[0058] FIG9 is a flow chart of a third-party service management method provided by another embodiment of the present disclosure;

[0059] FIG10 is a flow chart of a third-party service management method provided in yet another embodiment of the present disclosure;

[0060] FIG11 is a flow chart of a third-party service management method provided by another embodiment of the present disclosure;

[0061] FIG12 is a flow chart of a third-party service management method provided by another embodiment of the present disclosure;

[0062] FIG13 is a flow chart of a third-party service management method provided in yet another embodiment of the present disclosure;

[0063] FIG14 is a flow chart of a third-party service management method provided by yet another embodiment of the present disclosure;

[0064] FIG15 is a flow chart of a third-party service management method provided in yet another embodiment of the present disclosure;

[0065] FIG16 is a flow chart of a third-party service management method provided by yet another embodiment of the present disclosure;

[0066] FIG17 is a flow chart of an interactive method for third-party service registration provided in another embodiment of the present disclosure;

[0067] FIG18 is a flow chart of an interactive method for deregistering a third-party service provided in yet another embodiment of the present disclosure;

[0068] FIG19 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure;

[0069] FIG20 is a schematic structural diagram of a communication device provided by another embodiment of the present disclosure;

[0070] FIG21a is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure;

[0071] FIG21 b is a schematic structural diagram of a communication system provided by an embodiment of the present disclosure;

[0072] FIG22 is a block diagram of a user equipment provided by one embodiment of the present disclosure;

[0073] FIG23 is a block diagram of a network-side device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0074] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible implementations consistent with the present disclosure. Rather, they are merely examples of apparatuses and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0075] The terms used in the embodiments of the present disclosure are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present disclosure. The singular forms "a," "an," and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0076] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the words "if" and "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0077] The embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be understood as limiting the present disclosure.

[0078] To facilitate understanding, the terms involved in this application are first introduced.

[0079] 1. Artificial Intelligence (AI)

[0080] AI is a new technical science that studies and develops theories, methods, technologies and application systems for simulating, extending and expanding human intelligence.

[0081] 2. Network Repository Function (NRF) network element

[0082] The NRF network element stores and maintains NF information in the network and provides NF discovery / selection / subscription functions, that is, you can request information about a certain NF from the NRF, such as the IP address.

[0083] 3. Network Exposure Function (NEF) network element

[0084] The NEF network element securely opens the services provided by other NFs in the network to third parties, AFs, etc., and securely transmits information sent by AFs to the network, acting as a service layer security gateway.

[0085] 4. Application Function (AF) Network Element

[0086] AF network element, a network element that provides applications. The authorization server can be deployed as an AF.

[0087] The various network elements / functions involved in the embodiments of the present disclosure may be an independent hardware device or a function implemented by computer code within a hardware device, and the embodiments of the present disclosure do not limit this.

[0088] In order to better understand the method for determining a transmission configuration indication state disclosed in an embodiment of the present disclosure, the communication system to which the embodiment of the present disclosure is applicable is first described below.

[0089] The 5G service-oriented network architecture abstracts the functions of network elements into multiple services. Compared to traditional network architectures, the 5G service-oriented architecture adds two new network elements: the NEF and NRF. The NEF securely provides 3GPP network element services and capabilities to external parties, acting as a security gateway. External calls to internal network functions must be routed through the NEF, preventing direct exposure of internal network elements and potential security risks. This external environment can include third parties within the operator's network, AF, edge computing network elements, and more.

[0090] Please refer to Figure 1, which is a schematic diagram of a 5G service-oriented network architecture provided by an embodiment of the present disclosure. Figure 1 includes network elements included in the 5G service-oriented network architecture and interfaces used for communication between each network element.

[0091] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0092] The third-party service management method / device / equipment and storage medium provided by the embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0093] FIG2 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an NEF network element. As shown in FIG2 , the third-party service management method may include the following steps:

[0094] Step 201: Receive a first management request for managing a third-party service sent by an AF (Application Function) network element.

[0095] In one embodiment of the present disclosure, the first management request indicates a third-party service that can be provided by a third-party application. The third-party application can be an application other than a terminal device, a network device, and a network element of the network control plane. The third-party service can be, for example, a gaming service or a voice service provided by the third-party application.

[0096] Furthermore, in one embodiment of the present disclosure, the first management request may be sent by a third-party application to the NEF network element through the AF network element.

[0097] Furthermore, in one embodiment of the present disclosure, the first management request may be a first registration request for registering a third-party service and / or a first deregistration request for deregistering a third-party service. This part will be described in detail in subsequent embodiments.

[0098] In addition, in one embodiment of the present disclosure, the NEF network element may receive the first management request for managing the third-party service sent by the AF network element through an SBI (Southbound Interface) interface.

[0099] Step 202: Manage the third-party service based on the first management request.

[0100] In one embodiment of the present disclosure, when the first management request is a first registration request, the NEF network element performs registration management for the third-party service based on the first registration request. Furthermore, in another embodiment of the present disclosure, when the first management request is a first deregistration request, the NEF network element performs deregistration management for the third-party service based on the first deregistration request. The specific registration and deregistration management procedures will be described in detail in subsequent embodiments.

[0101] Step 203: Return the management result to the AF network element.

[0102] In one embodiment of the present disclosure, when the first management request is a first registration request for registering a third-party service, the management result may include a registration success response or a registration failure response.

[0103] Furthermore, in one embodiment of the present disclosure, when the first management request is a first deregistration request for deregistering a third-party service, the management result may include a deregistration success response or a deregistration failure response.

[0104] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0105] FIG3 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an NEF network element. As shown in FIG3 , the third-party service management method may include the following steps:

[0106] Step 301: Receive a first registration request sent by an AF network element for registering a third-party service.

[0107] In one implementation of the present disclosure, the first registration request may be sent from the AF network element to the NEF network element when a third-party application needs to register a third-party service.

[0108] Furthermore, in one embodiment of the present disclosure, the first registration request may include registration information of the third-party service for which registration is requested.

[0109] Specifically, in one embodiment of the present disclosure, the registration information may include at least one of the following:

[0110] The ID (Identifier) ​​of the NF (Network Function) corresponding to the third-party service;

[0111] NF type corresponding to the third-party service;

[0112] NF support business corresponding to third-party services;

[0113] The PLMN (Public Land Mobile Network) ID corresponding to the third-party application.

[0114] In one embodiment of the present disclosure, the NF type corresponding to the third-party service may be the NF type to which the third-party service belongs, and the NF type may include an AI service type, a perception service type, etc. For example, if the third-party service is a voice service, the NF type corresponding to the third-party service may be an AI service type.

[0115] Furthermore, in one embodiment of the present disclosure, the NF support service corresponding to the third-party service may include at least one of the following:

[0116] The business operations required to implement the third-party service;

[0117] The actual execution strategy when executing this business.

[0118] For example, assuming that the third-party service is a voice service, the NF support service corresponding to the third-party service may include the voice service and the actual execution strategy when executing the voice service (such as the actual charging strategy when actually executing the voice service, etc.).

[0119] Step 302: Determine whether the third-party service meets the authorization conditions based on the registration information of the third-party service.

[0120] In one embodiment of the present disclosure, a method for an NEF network element to determine whether a third-party service meets authorization conditions based on registration information of the third-party service may include the following steps:

[0121] Step 1: Determine whether the third-party application is eligible for registration.

[0122] Specifically, in one embodiment of the present disclosure, a list is stored in the NEF network element, which includes the IDs of the PLMNs corresponding to third-party applications that have the ability to provide services to the NF network element. Based on this, the NEF network element can check whether the list includes the ID of the PLMN corresponding to the third-party application in the first registration request. If the list does not include the ID of the PLMN in the first registration request, it means that the third-party application corresponding to the third-party service requested to be registered in the first registration request does not have the ability to provide services to the NF network element, and it is determined that the third-party service does not meet the authorization conditions; if the list includes the ID of the PLMN in the first registration request, it means that the third-party application corresponding to the third-party service requested to be registered in the first registration request has the ability to provide services to the NF network element, and step 2 is further executed.

[0123] Step 2: Determine whether the third-party service is eligible for registration.

[0124] In one embodiment of the present disclosure, whether the third-party service is eligible for registration may be determined based on the NF type corresponding to the third-party service and the NF support service corresponding to the third-party service in the first registration request.

[0125] Specifically, in one embodiment of the present disclosure, the PCF (Policy Control Function) will broadcast the standard execution policy and admission policy corresponding to each service under each NF type to the NEF network element. The standard execution policy is specifically a standard execution policy defined for each service. For example, the standard execution measurement corresponding to the voice service may be, for example, a standard charging policy. In addition, the admission policy is used to determine whether the third-party service is eligible for registration; the admission policy specifically includes: if the deviation between the actual execution policy corresponding to the service to be executed when implementing the third-party service to be registered and the standard execution policy corresponding to the service to be executed when implementing the third-party service to be registered is less than a preset threshold, then the third-party service to be registered is eligible for registration; if the deviation between the actual execution policy corresponding to the service to be executed when implementing the third-party service to be registered and the standard execution policy corresponding to the service to be executed when implementing the third-party service to be registered is not less than a preset threshold, then the third-party service to be registered is not eligible for registration.

[0126] Based on this, in one embodiment of the present disclosure, after the NEF network element determines the standard execution policy and admission policy corresponding to each service, the NEF network element can determine the standard execution policy corresponding to the third-party service requested to be registered by the first registration request based on the NF type corresponding to the third-party service included in the first registration request and the service required to be executed when implementing the third-party service. Afterwards, it is determined whether the third-party service requested to be registered by the first registration request is eligible for registration based on the standard execution policy corresponding to the third-party service requested to be registered by the first registration request and the above-mentioned admission policy. Wherein, when it is determined whether the third-party service requested to be registered by the first registration request is eligible for registration, it is determined that it meets the authorization conditions; when it is determined that the third-party service requested to be registered by the first registration request is not eligible for registration, it is determined that it does not meet the authorization conditions.

[0127] Step 303: In response to determining that the third-party service meets the authorization condition, the ID of the NF corresponding to the third-party service is stored.

[0128] Among them, in one embodiment of the present disclosure, in response to determining that the third-party service meets the authorization conditions, the NEF network element can store the ID of the NF corresponding to the third-party service and the ID of the PLMN in a corresponding manner, so that when the subsequent NRF network element successfully registers the third-party service, the NEF network element can call the third-party service based on the ID of the PLMN corresponding to the third-party application and the ID of the NF corresponding to the third-party service.

[0129] Step 304: Send a second registration request for registering a third-party service to the NRF network element.

[0130] In one embodiment of the present disclosure, the second registration request may include registration information and NEF ID.

[0131] Furthermore, in one embodiment of the present disclosure, the NEF network element may send a second registration request for registering a third-party service to the NRF network element through Nnrf_NFManagement_NFRegister.

[0132] Furthermore, in one embodiment of the present disclosure, after receiving the second registration request for registering the third-party service, the NRF network element may complete registration management of the third-party service according to the registration information and NEF ID included in the second registration request.

[0133] Step 305: Receive a registration success response sent by the NRF network element.

[0134] In one embodiment of the present disclosure, the registration success response is used to indicate that the third-party service has completed registration in the NRF network element.

[0135] Step 306: Return a registration success response to the AF network element.

[0136] Among them, in one embodiment of the present disclosure, the registration success response is used to indicate that the third-party service has been successfully registered. At this time, the network device can subsequently call the third-party service, such as the network device can subsequently provide the third-party service to the NF network element by calling the AF network element.

[0137] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0138] FIG4 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an NEF network element. As shown in FIG4 , the third-party service management method may include the following steps:

[0139] Step 401: Receive a first registration request sent by an AF network element for registering a third-party service.

[0140] Step 402: Determine whether the third-party service meets the authorization conditions based on the registration information of the third-party service.

[0141] For a detailed description of steps 401 and 402, please refer to the above embodiment description, which will not be elaborated here in the embodiment of the present disclosure.

[0142] Step 403: In response to the registration information of the third-party service not meeting the authorization condition, it is determined that the registration of the third-party service has failed.

[0143] Among them, in one embodiment of the present disclosure, when the registration information of the third-party service does not meet the authorization conditions, it means that the third-party application may not be eligible for registration, or the third-party service may not be eligible for registration. At this time, the third-party service requested by the first registration request cannot be registered, and it is determined that the third-party service registration has failed.

[0144] Step 404: Return a registration failure response to the AF network element.

[0145] In one embodiment of the present disclosure, the registration failure response is used to indicate that the third-party service has not been successfully registered.

[0146] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0147] FIG5 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an NEF network element. As shown in FIG5 , the third-party service management method may include the following steps:

[0148] Step 501: Receive a first deregistration request for deregistering a third-party service sent by an AF network element.

[0149] In one implementation of the present disclosure, the first deregistration request may be sent to the NEF network element via the AF network element when the third-party application needs to deregister a third-party service.

[0150] Furthermore, in one embodiment of the present disclosure, the first deregistration request may include deregistration information of the third-party service requested for deregistration.

[0151] Specifically, in one embodiment of the present disclosure, the cancellation information includes at least one of the following:

[0152] The ID of the NF corresponding to the third-party service;

[0153] The PLMN ID corresponding to the third-party application.

[0154] Step 502: Determine whether the third-party service meets the cancellation conditions based on the cancellation information of the third-party service.

[0155] In one embodiment of the present disclosure, whether a third-party service meets the cancellation conditions can be determined based on the ID of the NF in the first cancellation request. Specifically, the NEF network element searches whether it has stored the ID of the NF in the first cancellation request. If the NEF network element stores the ID of the NF in the first cancellation request, it indicates that the third-party service corresponding to the ID of the NF has been registered. In this case, the third-party service can be cancelled, and it is determined that the third-party service meets the cancellation conditions. If the NEF network element does not store the ID of the NF in the first cancellation request, it indicates that the third-party service corresponding to the ID of the NF has not been registered. In this case, the third-party service cannot be cancelled, and it is determined that the third-party service does not meet the cancellation conditions.

[0156] And, in another embodiment of the present disclosure, whether the third-party service meets the deregistration conditions can be determined based on the NF ID and PLMN ID in the first deregistration request. Specifically, multiple third-party services will be registered for a third-party application. In this case, the ID of a PLMN in the NEF network element will be associated with the IDs of multiple different NFs. And, a third-party service may be registered to multiple different third-party applications. In this case, the ID of an NF in the NEF network element may be associated with the IDs of multiple different PLMNs. For example, third-party application 1 and third-party application 2 both provide voice services and are both registered in the NEF network element. Therefore, the ID#1 of the PLMN corresponding to the third-party application 1 in the NEF network element is associated with the ID of the NF corresponding to the voice service. At the same time, the ID#1 of the PLMN corresponding to the third-party application 2 is also associated with the ID of the NF corresponding to the voice service.

[0157] Based on this, when you want to cancel a third-party service, you should also need to clarify which third-party application you want to cancel the third-party service for. If there is no association between the third-party application you specify and the third-party service you want to cancel, it means that the third-party service you want to cancel has not been registered for the third-party application, and the third-party service cannot be cancelled for the third-party application, and the cancellation conditions are not met; if there is an association between the third-party application you specify and the third-party service you want to cancel, it means that the third-party service you want to cancel has been registered for the third-party application, and the third-party service can be cancelled for the third-party application, and the cancellation conditions are met.

[0158] For example, assuming that PLMN ID#1 in the NEF network element is associated with NF ID#1 and NF ID#2, and PLMN ID#2 is associated with NF ID#1, based on this, if the first deregistration request in the above step 501 includes NF ID#2 and PLMN ID#2, then since there is no association between NF ID2 and PLMN ID#2 in the NEF network element, it is determined that the third-party service does not meet the deregistration condition; if the first deregistration request in the above step 501 includes NF ID#2 and PLMN ID#1, then since there is an association between NF ID#2 and PLMN ID#1 in the NEF network element, it is determined that the third-party service meets the deregistration condition.

[0159] Step 503: In response to determining that the third-party service meets the deregistration condition, a second deregistration request for deregistering the third-party service is sent to the NRF network element.

[0160] In one embodiment of the present disclosure, the second deregistration request may include deregistration information.

[0161] And, in one embodiment of the present disclosure, the NEF network element may send a second deregistration request for deregistering the third-party service to the NRF network element through Nnrf_NFManagement_NFDeregister.

[0162] Furthermore, in one embodiment of the present disclosure, after the NRF network element receives the second deregistration request for deregistering the third-party service, it can complete the deregistration management of the third-party service according to the deregistration message included in the second deregistration request.

[0163] Step 504: In response to receiving the deregistration success response sent by the NRF network element, the ID of the NF corresponding to the third-party service is deleted.

[0164] In one embodiment of the present disclosure, the deregistration success response is used to indicate that the third-party service has completed deregistration in the NRF network element. At this time, the NEF network element can delete the ID of the NF, or delete the association between the ID of the NF and the ID of the PLMN, thereby completing the deregistration of the third-party service in the NEF network element.

[0165] Step 505: Return a deregistration success response to the AF network element.

[0166] In one embodiment of the present disclosure, the registration success response is used to indicate that the third-party service has been successfully deregistered. At this time, the network device cannot subsequently call the third-party service.

[0167] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0168] FIG6 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an NEF network element. As shown in FIG6 , the third-party service management method may include the following steps:

[0169] Step 601: Receive a first deregistration request for deregistering a third-party service sent by an AF network element.

[0170] Step 602: Determine whether the third-party service meets the cancellation conditions based on the cancellation information of the third-party service.

[0171] For a detailed description of steps 601 and 602, please refer to the above embodiment description, which will not be elaborated here in the embodiment of the present disclosure.

[0172] Step 603: In response to the cancellation information of the third-party service not meeting the cancellation condition, determine that the cancellation of the third-party service has failed.

[0173] Step 604: Return a deregistration failure response to the AF network element.

[0174] In one embodiment of the present disclosure, the registration failure response is used to indicate a third-party service deregistration failure.

[0175] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0176] FIG7 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an NRF network element. As shown in FIG7 , the third-party service management method may include the following steps:

[0177] Step 701: Receive a second management request for managing a third-party service sent by an NEF network element.

[0178] In one embodiment of the present disclosure, the second management request indicates a third-party service provided by a third-party application.

[0179] Furthermore, in one embodiment of the present disclosure, the third-party service may be a service provided by a third-party application (such as a game service, a voice service, etc.), and the third-party application may be an application other than a terminal device, a network device, and a network element of a network control plane.

[0180] Furthermore, in one embodiment of the present disclosure, the second management request may be a second registration request for registering a third-party service and / or a second deregistration request for deregistering a third-party service. For a detailed description of the second registration request and the second deregistration request, please refer to the above embodiment.

[0181] Step 702: Manage the third-party service based on the second management request.

[0182] In one embodiment of the present disclosure, when the second management request is a second registration request, the NRF network element performs registration management for the third-party service based on the second registration request. Furthermore, in another embodiment of the present disclosure, when the second management request is a second deregistration request, the NRF network element performs deregistration management for the third-party service based on the second deregistration request. The specific registration and deregistration management procedures will be described in detail in subsequent embodiments.

[0183] Step 703: Return the management result to the NEF network element.

[0184] In one embodiment of the present disclosure, when the second management request is a second registration request for registering a third-party service, the management result may include a registration success response.

[0185] Furthermore, in one embodiment of the present disclosure, when the second management request is a second deregistration request for deregistering a third-party service, the management result may include a deregistration success response.

[0186] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0187] FIG8 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an NRF network element. As shown in FIG8 , the third-party service management method may include the following steps:

[0188] Step 801: Receive a second registration request sent by an NEF network element for registering a third-party service.

[0189] In one embodiment of the present disclosure, the second registration request may include registration information and an NEF ID of the third-party service for which registration is requested.

[0190] Furthermore, in one embodiment of the present disclosure, the registration information may include at least one of the following:

[0191] The ID of the NF corresponding to the third-party service;

[0192] NF type corresponding to the third-party service;

[0193] NF support business corresponding to third-party services;

[0194] The PLMN ID corresponding to the third-party application.

[0195] Furthermore, in one embodiment of the present disclosure, the NRF network element may receive the second registration request for registering the third-party service sent by the NEF network element through Nnrf_NFManagement_NFRegister.

[0196] For a detailed introduction to the registration information, please refer to the relevant introduction in the above embodiments, which will not be elaborated in detail in the embodiments of the present disclosure.

[0197] Step 802: Perform registration management on the third-party service based on the second registration request.

[0198] In one embodiment of the present disclosure, the method for managing registration of a third-party service based on the second registration request may include at least one of the following:

[0199] Generate corresponding configuration files for third-party service registration based on the third-party service registration information and NEF ID;

[0200] Set the availability status of the third-party service to Available.

[0201] It should be noted that, in one embodiment of the present disclosure, when a corresponding configuration file is generated and stored for the third-party service registration based on the third-party service registration information and NEF ID, it indicates that the third-party service has been registered with the NRF network element. In addition, when the NRF network element sets the availability status corresponding to the third-party service to available, it also indicates that the third-party service has been registered with the NRF network element.

[0202] Furthermore, in one embodiment of the present disclosure, the method for setting the availability status corresponding to the third-party service to available may include: setting availability status information for the third-party service, and indicating that the third-party service is available by setting the availability status information corresponding to the third-party service to a first value. In one embodiment of the present disclosure, the first value may be 1.

[0203] Step 803: Return a registration success response to the NEF network element.

[0204] For a detailed description of other contents of this embodiment, please refer to the relevant description in the above embodiments, and the embodiments of the present disclosure will not be described in detail here.

[0205] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0206] FIG9 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an NRF network element. As shown in FIG9 , the third-party service management method may include the following steps:

[0207] Step 901: Receive a second registration request sent by an NEF network element for registering a third-party service.

[0208] Step 902: Register and manage the third-party service based on the second registration request.

[0209] For a detailed description of steps 901 and 902, please refer to the above embodiment description, which will not be elaborated here in the embodiment of the present disclosure.

[0210] Step 903: Send a first notification message to a specific NF network element.

[0211] In one embodiment of the present disclosure, a specific NF may be a NF that has subscribed to a service change event, where the service change event may include a service registration event and / or a service deregistration event. Furthermore, the specific NF may be understood as a NF that needs to be notified when a service change event (such as a service registration event and / or a service change event) occurs.

[0212] Furthermore, in one embodiment of the present disclosure, the first notification message is used to notify the specific NF network element that the third-party service has completed registration. The first notification message may include the PLMD ID corresponding to the third-party application and the ID of the NF corresponding to the third-party service.

[0213] Furthermore, in one embodiment of the present disclosure, the first notification message is sent to a specific NF network element so that the specific NF network element can be informed that the third-party service indicated by the first notification message has been registered, so that the specific NF network element can subsequently request to use the third-party service.

[0214] For a detailed description of other contents of this embodiment, please refer to the relevant description in the above embodiments, and the embodiments of the present disclosure will not be described in detail here.

[0215] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0216] FIG10 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an NRF network element. As shown in FIG10 , the third-party service management method may include the following steps:

[0217] Step 1001: Receive a second deregistration request for deregistering a third-party service sent by an NEF network element.

[0218] In one embodiment of the present disclosure, the second deregistration request may include deregistration information of the third-party service requested for deregistration.

[0219] Furthermore, in one embodiment of the present disclosure, the cancellation information may include at least one of the following:

[0220] The ID of the NF corresponding to the third-party service;

[0221] The PLMN ID corresponding to the third-party application.

[0222] Furthermore, in one embodiment of the present disclosure, the NRF network element may receive, through Nnrf_NFManagement_NFDeregister, a second deregistration request for deregistering a third-party service sent by the NEF network element.

[0223] Step 1002: Perform deregistration management on the third-party service based on the second deregistration request.

[0224] In one embodiment of the present disclosure, the method for managing deregistration of a third-party service based on the second deregistration request may include at least one of the following:

[0225] Delete the configuration file corresponding to the third-party service based on the corresponding deregistration information of the third-party service;

[0226] Set the availability status of the third-party service to unavailable.

[0227] It should be noted that, in one embodiment of the present disclosure, when the configuration file corresponding to the third-party service is deleted based on the deregistration information of the third-party service, it indicates that the third-party service has completed deregistration in the NRF network element. Also, when the NRF network element sets the available status corresponding to the third-party service to unavailable, it may also indicate that the third-party service has completed deregistration in the NRF network element.

[0228] Furthermore, in one embodiment of the present disclosure, the method for setting the availability status corresponding to the third-party service to unavailable may include: setting availability status information for the third-party service, and indicating that the third-party service is unavailable by setting the availability status information corresponding to the third-party service to a second value. In one embodiment of the present disclosure, the second value may be 0.

[0229] Step 1003: Return a deregistration success response to the NEF network element.

[0230] For a detailed description of other contents of this embodiment, please refer to the relevant description in the above embodiments, and the embodiments of the present disclosure will not be described in detail here.

[0231] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0232] FIG11 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an NRF. As shown in FIG11 , the third-party service management method may include the following steps:

[0233] Step 1101: Receive a second deregistration request for deregistering a third-party service sent by an NEF network element.

[0234] Step 1102: Perform deregistration management on the third-party service based on the second deregistration request.

[0235] Among them, the detailed description of steps 1101 and 1102 can be referred to the description of the above embodiment, and the embodiment of the present disclosure will not be repeated here.

[0236] Step 1103: Send a second notification message to the specific NF network element.

[0237] In one embodiment of the present disclosure, a specific NF may be a NF that has subscribed to a service change event, where the service change event may include a service registration event and / or a service deregistration event. Furthermore, the specific NF may be understood as a NF that needs to be notified when a service change event (such as a service registration event and / or a service change event) occurs.

[0238] Furthermore, in one embodiment of the present disclosure, the second notification message is used to notify the specific NF network element that the third-party service has completed deregistration. The second notification message may include the PLMD ID corresponding to the third-party application and the ID of the NF corresponding to the third-party service.

[0239] Furthermore, in one embodiment of the present disclosure, the second notification message is sent to a specific NF network element so that the specific NF network element can be informed that the third-party service indicated by the second notification message has been deregistered, so that the specific NF network element can no longer request to use the third-party service.

[0240] For a detailed description of other contents of this embodiment, please refer to the relevant description in the above embodiments, and the embodiments of the present disclosure will not be described in detail here.

[0241] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0242] FIG12 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an AF network element. As shown in FIG12 , the third-party service management method may include the following steps:

[0243] Step 1201: Send a first management request for managing a third-party service to an NEF network element.

[0244] In one embodiment of the present disclosure, the first management request indicates a third-party service provided by a third-party application.

[0245] Furthermore, in one embodiment of the present disclosure, the third-party service may be a service provided by a third-party application (such as a game service, a voice service, etc.), and the third-party application may be an application other than a terminal device, a network device, and a network element of a network control plane.

[0246] Furthermore, in one embodiment of the present disclosure, the first management request may be a first registration request for registering a third-party service and / or a first deregistration request for deregistering a third-party service. This part will be described in detail in subsequent embodiments.

[0247] Step 1202: Receive the management result returned by the NEF network element.

[0248] In one embodiment of the present disclosure, when the first management request is a first registration request for registering a third-party service, the management result may include a registration success response or a registration failure response.

[0249] Furthermore, in one embodiment of the present disclosure, when the first management request is a first deregistration request for deregistering a third-party service, the management result may include a deregistration success response or a deregistration failure response.

[0250] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0251] FIG13 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an AF network element. As shown in FIG13 , the third-party service management method may include the following steps:

[0252] Step 1301: Send a first registration request for registering a third-party service to an NEF network element.

[0253] In one embodiment of the present disclosure, the first registration request may include registration information of a third-party service.

[0254] Furthermore, in one embodiment of the present disclosure, the registration information may include at least one of the following:

[0255] The ID of the NF corresponding to the third-party service;

[0256] NF type corresponding to the third-party service;

[0257] NF support business corresponding to third-party services;

[0258] The PLMN ID corresponding to the third-party application.

[0259] Step 1302: Receive a registration success response returned by the NEF network element.

[0260] Among them, in one embodiment of the present disclosure, the registration success response is used to indicate that the third-party service has been successfully registered. At this time, the network device can subsequently call the third-party service, such as the network device can subsequently provide the third-party service to the NF network element by calling the AF network element.

[0261] For a detailed description of other contents of this embodiment, please refer to the relevant description in the above embodiments, and the embodiments of the present disclosure will not be described in detail here.

[0262] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0263] FIG14 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an AF network element. As shown in FIG14 , the third-party service management method may include the following steps:

[0264] Step 1401: Send a first registration request for registering a third-party service to an NEF network element.

[0265] Step 1402: Receive a registration failure response returned by the NEF network element.

[0266] In one embodiment of the present disclosure, the registration failure response is used to indicate that the third-party service has not been successfully registered. In this case, the network device cannot call the third-party service.

[0267] For a detailed description of other contents of this embodiment, please refer to the relevant description in the above embodiments, and the embodiments of the present disclosure will not be described in detail here.

[0268] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0269] FIG15 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an AF network element. As shown in FIG15 , the third-party service management method may include the following steps:

[0270] Step 1501: Send a first deregistration request for registering a third-party service to an NEF network element.

[0271] In one embodiment of the present disclosure, the first deregistration request includes deregistration information of the third-party service.

[0272] Furthermore, in one embodiment of the present disclosure, the deregistration information may include at least one of the following:

[0273] The ID of the NF corresponding to the third-party service;

[0274] The PLMN ID corresponding to the third-party application.

[0275] For a detailed description of other contents of this embodiment, please refer to the relevant description in the above embodiments, and the embodiments of the present disclosure will not be described in detail here.

[0276] Step 1502: Receive a deregistration success response returned by the NEF network element.

[0277] In one embodiment of the present disclosure, the registration success response is used to indicate that the third-party service has been successfully deregistered. At this time, the network device cannot subsequently call the third-party service.

[0278] For a detailed description of other contents of this embodiment, please refer to the relevant description in the above embodiments, and the embodiments of the present disclosure will not be described in detail here.

[0279] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0280] FIG16 is a flow chart of a third-party service management method provided by an embodiment of the present disclosure. The method is executed by an AF network element. As shown in FIG16 , the third-party service management method may include the following steps:

[0281] Step 1601: Send a first deregistration request for registering a third-party service to an NEF network element.

[0282] Step 1602: Receive a deregistration failure response returned by the NEF network element.

[0283] In one embodiment of the present disclosure, when the AF network element receives a deregistration failure response returned by the NEF network element, it indicates that the deregistration of the third-party service has failed.

[0284] For a detailed description of other contents of this embodiment, please refer to the relevant description in the above embodiments, and the embodiments of the present disclosure will not be described in detail here.

[0285] In summary, in the third-party service management method provided in the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0286] Based on the above description, FIG17 is an interactive method for third-party service registration provided by an embodiment of the present disclosure. As shown in FIG17 , the interactive method may include the following steps:

[0287] Step 1701: The AF network element sends a new registration request for a third-party service (ie, the first registration request in the above embodiment) to the NEF network element to perform a service registration process in the core network.

[0288] Step 1702: The NEF network element authorizes the registration request of the AF network element. If the NEF network element authorizes successfully, the NEF network element stores the ID of the NF corresponding to the third-party service and executes steps 1704 to 1705; if the authorization fails, execute step 1703.

[0289] Step 1703: Return a Result value (False) to the AF network element (ie, the registration failure response in the above embodiment), indicating that the authorization has failed, and end the process.

[0290] Step 1704: The NEF network element sends the registration information of the third-party service and the NEF ID to the NRF network element through Nnrf_NFManagement_NFRegister (such as carried in the above-mentioned second registration request and sent to the NRF network element).

[0291] Step 1705: The NRF network element generates a corresponding configuration file for the third-party service registration based on the registration information and NEF ID based on the third-party service, and sets the corresponding available status of the third-party service to available, notifying all other NF network elements that have subscribed to the service change event, such as sending a first notification message to all other NF network elements (this step is not shown in Figure 17), and the NRF network element returns a registration success response to the AF network element through the NEF network element.

[0292] Based on the above description, FIG18 is an interactive method for deregistering a third-party service provided by an embodiment of the present disclosure. As shown in FIG18 , the interactive method may include the following steps:

[0293] Step 1801: The AF network element sends a deregistration request for a third-party service (ie, the first deregistration request in the above embodiment) to the NEF network element to perform a service registration process in the core network.

[0294] Step 1802: The NEF network element searches for the ID of the NF in the deregistration request to see whether it has been successfully registered. If the ID of the NF is not found, the third-party service has not been successfully registered, and step 1803 is executed; if the ID of the NF is found, the third-party service has been successfully registered, and steps 1804 to 1805 are executed.

[0295] Step 1803: Return a Result value (False) to the AF network element (ie, the deregistration failure response in the above embodiment), indicating that the deregistration has failed, and the process ends.

[0296] Step 1804: The NEF network element sends the deregistration information of the third-party service to the NRF network element through Nnrf_NFManagement_NFDeregister (such as carried in the above-mentioned second deregistration request and sent to the NRF network element).

[0297] Step 1805: The NRF network element deletes the configuration file corresponding to the third-party service based on the deregistration information corresponding to the third-party service, and sets the availability status of the third-party service to unavailable, notifying all other NFs that have subscribed to the service change event, such as sending a second notification message to all other NF network elements (this step is not shown in Figure 18), and the NRF network element returns a successful deregistration response to the AF through the NEF network element.

[0298] In the embodiments provided above, the methods provided in the embodiments of the present application are described from the perspectives of a network device and a UE, respectively. In order to implement the functions of the methods provided in the embodiments of the present application, the network device and the UE may include a hardware structure and a software module, and implement the functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. One of the functions described above may be performed in the form of a hardware structure, a software module, or a hardware structure plus a software module.

[0299] FIG19 is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure. As shown in FIG19 , the device may include:

[0300] The transceiver module 1901 is configured to receive a first management request for managing a third-party service sent by an application function AF network element, where the first management request indicates a third-party service provided by a third-party application;

[0301] A management module 1902 is configured to manage the third-party service based on the first management request;

[0302] The transceiver module 1901 is further configured to return the management result to the AF network element.

[0303] In summary, in the communication device provided in the embodiment of the present disclosure, the NEF network element will receive a first management request sent by the AF network element for managing a third-party service. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0304] Optionally, in one embodiment of the present disclosure, the transceiver module 1901 is further configured to:

[0305] receiving a first registration request sent by the AF network element for registering a third-party service, where the first registration request includes registration information of the third-party service;

[0306] Registration information includes at least one of the following:

[0307] The ID of the NF corresponding to the third-party service;

[0308] NF type corresponding to the third-party service;

[0309] NF support business corresponding to third-party services;

[0310] The PLMN ID corresponding to the third-party application.

[0311] Optionally, in one embodiment of the present disclosure, the management module 1902 is further configured to:

[0312] Determine whether the third-party service meets the authorization conditions based on the registration information of the third-party service;

[0313] In response to determining that the third-party service meets the authorization condition, storing an ID of the NF corresponding to the third-party service;

[0314] Sending a second registration request for registering a third-party service to the network storage function NRF network element, where the second registration request includes registration information and NEF ID;

[0315] Receive the registration success response sent by the NRF network element.

[0316] Optionally, in one embodiment of the present disclosure, the transceiver module 1901 is further configured to:

[0317] Return a registration success response to the AF network element.

[0318] Optionally, in one embodiment of the present disclosure, the management module 1902 is further configured to:

[0319] Determine whether the third-party service meets the authorization conditions based on the registration information of the third-party service;

[0320] In response to the registration information of the third-party service not satisfying the authorization condition, it is determined that the third-party service registration has failed.

[0321] Optionally, in one embodiment of the present disclosure, the transceiver module 1901 is further configured to:

[0322] Return a registration failure response to the AF network element.

[0323] Optionally, the transceiver module 1901 is further configured to:

[0324] receiving a first deregistration request for deregistering a third-party service sent by the AF network element, where the first deregistration request includes deregistration information of the third-party service;

[0325] The deregistration information includes at least one of the following:

[0326] The ID of the NF corresponding to the third-party service;

[0327] The PLMN ID corresponding to the third-party application.

[0328] Optionally, in one embodiment of the present disclosure, the management module 1902 is further configured to:

[0329] determining whether the third-party service meets a cancellation condition based on the cancellation information of the third-party service;

[0330] In response to determining that the third-party service meets the deregistration condition, sending a second deregistration request for deregistering the third-party service to the NRF network element, where the second deregistration request includes the deregistration information;

[0331] In response to receiving a deregistration success response sent by the NRF network element, the ID of the NF corresponding to the third-party service is deleted.

[0332] Optionally, in one embodiment of the present disclosure, the transceiver module 1901 is further configured to:

[0333] A deregistration success response is returned to the AF network element.

[0334] Optionally, in one embodiment of the present disclosure, the transceiver module 1901 is further configured to:

[0335] determining whether the third-party service meets a cancellation condition based on the cancellation information of the third-party service;

[0336] In response to the deregistration information of the third-party service not satisfying a deregistration condition, it is determined that the deregistration of the third-party service has failed.

[0337] Optionally, in one embodiment of the present disclosure, the transceiver module 1901 is further configured to:

[0338] Return a deregistration failure response to the AF network element.

[0339] FIG20 is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure. As shown in FIG20 , the device may include:

[0340] The transceiver module 2001 is configured to receive a second management request for managing a third-party service sent by an NEF network element, where the second management request indicates a third-party service provided by a third-party application;

[0341] A management module 2001 is configured to manage the third-party service based on the second management request;

[0342] The transceiver module 2001 is further configured to return a management result to the NEF network element.

[0343] In summary, in the communication device provided in the embodiment of the present disclosure, the NEF network element will receive a first management request sent by the AF network element for managing a third-party service. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0344] Optionally, in one embodiment of the present disclosure, the transceiver module 2001 is further configured to:

[0345] receiving a second registration request sent by the NEF network element for registering a third-party service, where the second registration request includes registration information of the third-party service and an NEF ID;

[0346] The registration information includes at least one of the following:

[0347] The ID of the NF corresponding to the third-party service;

[0348] NF type corresponding to the third-party service;

[0349] NF support business corresponding to third-party services;

[0350] The PLMN ID corresponding to the third-party application.

[0351] Optionally, in one embodiment of the present disclosure, the management module 2002 is further configured to:

[0352] Generate a corresponding configuration file for the third-party service registration based on the registration information and NEF ID of the third-party service;

[0353] The availability status corresponding to the third-party service is set to available.

[0354] Optionally, in one embodiment of the present disclosure, the transceiver module 2001 is further configured to:

[0355] A registration success response is returned to the NEF network element.

[0356] Optionally, in one embodiment of the present disclosure, the apparatus is further configured to:

[0357] Sending a first notification message to a specific NF network element; the specific NF network element is a network element that has subscribed to the service change event, and the first notification message is used to indicate that the third-party service has completed registration.

[0358] Optionally, in one embodiment of the present disclosure, the transceiver module 2001 is further configured to:

[0359] receiving a second deregistration request for deregistering a third-party service sent by the NEF network element, where the second deregistration request includes deregistration information of the third-party service;

[0360] The deregistration information includes at least one of the following:

[0361] The ID of the NF corresponding to the third-party service;

[0362] The PLMN ID corresponding to the third-party application.

[0363] Optionally, in one embodiment of the present disclosure, the management module 2002 is further configured to:

[0364] Deleting a configuration file corresponding to the third-party service based on the deregistration information corresponding to the third-party service;

[0365] The availability status of the third-party service is set to unavailable.

[0366] Optionally, in one embodiment of the present disclosure, the transceiver module 2001 is further configured to:

[0367] The NEF network element returns a deregistration success response.

[0368] Optionally, in one embodiment of the present disclosure, the apparatus is further configured to:

[0369] Sending a second notification message to a specific NF network element; the specific NF network element is a network element that has subscribed to the service change event, and the second notification message is used to indicate that the third-party service has completed deregistration.

[0370] FIG21a is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure. As shown in FIG21a , the device may include:

[0371] The transceiver module 2101a is configured to send a first management request for managing a third-party service to the NEF network element, where the first management request indicates a third-party service provided by a third-party application;

[0372] The transceiver module 2101a is further configured to receive the management result returned by the NEF network element.

[0373] In summary, in the communication device provided in the embodiment of the present disclosure, the NEF network element will receive a first management request sent by the AF network element for managing a third-party service. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided in the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0374] Optionally, in one embodiment of the present disclosure, the transceiver module 2101a is further configured to:

[0375] Sending a first registration request for registering a third-party service to the NEF network element, where the first registration request includes registration information of the third-party service;

[0376] The registration information includes at least one of the following:

[0377] The ID of the NF corresponding to the third-party service;

[0378] NF type corresponding to the third-party service;

[0379] NF support business corresponding to third-party services;

[0380] The PLMN ID corresponding to the third-party application.

[0381] Optionally, in one embodiment of the present disclosure, the transceiver module 2101a is further configured to:

[0382] Receive a registration success response returned by the NEF network element.

[0383] Optionally, in one embodiment of the present disclosure, the transceiver module 2101a is further configured to:

[0384] Receive a registration failure response returned by the NEF network element.

[0385] Optionally, in one embodiment of the present disclosure, the transceiver module 2101a is further configured to:

[0386] Sending a first deregistration request for registering a third-party service to the NEF network element, where the first deregistration request includes deregistration information of the third-party service;

[0387] The deregistration information includes at least one of the following:

[0388] The ID of the NF corresponding to the third-party service;

[0389] The PLMN ID corresponding to the third-party application.

[0390] Optionally, in one embodiment of the present disclosure, the transceiver module 2101a is further configured to:

[0391] Receive a deregistration success response returned by the NEF network element.

[0392] Optionally, in one embodiment of the present disclosure, the transceiver module 2101a is further configured to:

[0393] Receive a deregistration failure response returned by the NEF network element.

[0394] FIG21 b is a schematic diagram of the structure of a communication system provided by an embodiment of the present disclosure. As shown in FIG21 b , the system may include:

[0395] The first network element (i.e., the AF network element in the above embodiment) 2101b is configured to send a first management request for managing a third-party service, where the first management request indicates a third-party service provided by a third-party application;

[0396] The second network element (i.e., the NEF network element in the above embodiment) 2102b is configured to receive a first management request for managing a third-party service and manage the third-party service based on the first management request;

[0397] The second network element 2102b is further configured to send a second management request for managing a third-party service, where the second management request indicates a third-party service provided by a third-party application;

[0398] The third network element (i.e., the NRF network element in the above embodiment) 2103b is configured to receive the second management request for managing the third-party service, manage the third-party service based on the second management request, and return a management result to the second network element;

[0399] The second network element 2102b is further configured to return a management result to the first network element;

[0400] The first network element 2101b is further configured to receive the management result returned by the second network element.

[0401] In one embodiment of the present disclosure, the first network element, the second network element, and the third network element can communicate with each other.

[0402] For a detailed description of other contents of this embodiment, please refer to the relevant description in the above embodiments, and the embodiments of the present disclosure will not be described in detail here.

[0403] In summary, in the communication system provided by the embodiment of the present disclosure, the NEF network element will receive a first management request for managing a third-party service sent by the AF network element. The first management request indicates that there is a third-party service provided by a third-party application. Afterwards, the NEF network element will manage the third-party service based on the first management request and return the management result to the AF network element. That is, in the third-party service management method provided by the present disclosure, the NEF network element can manage the third-party service, such as specifically registering and / or deregistering the third-party service. In this way, the NEF network element can know which third-party services the third-party application can provide. The network can then call the third-party service through the NEF network element, thereby improving the richness of network services.

[0404] Optionally, the above communication system can be used to register third-party services, specifically:

[0405] The first network element is configured to send a first registration request for registering a third-party service, where the first registration request indicates a third-party service provided by a third-party application;

[0406] a second network element, configured to receive a first registration request for registering a third-party service and perform registration management on the third-party service based on the first registration request;

[0407] The second network element is further configured to send a second registration request for registering a third-party service, where the second registration request indicates a third-party service provided by a third-party application;

[0408] The third network element is configured to receive a second registration request for registering the third-party service, perform registration management on the third-party service based on the second registration request, and return a registration success response to the second network element;

[0409] The second network element is further configured to return a registration success response or a registration failure response to the first network element;

[0410] The first network element is further configured to receive a registration success response or a registration failure response returned by the second network element.

[0411] Optionally, the above communication system can be used to deregister third-party services, specifically:

[0412] The first network element is configured to send a first deregistration request for deregistering a third-party service, where the first deregistration request indicates a third-party service provided by a third-party application;

[0413] a second network element, configured to receive a first deregistration request for deregistering a third-party service and perform deregistration management on the third-party service based on the first deregistration request;

[0414] The second network element is further configured to send a second deregistration request for deregistering the third-party service, where the second deregistration request indicates a third-party service provided by the third-party application;

[0415] The third network element is configured to receive a second deregistration request for deregistering the third-party service, perform deregistration management on the third-party service based on the second deregistration request, and return a deregistration success response to the second network element;

[0416] The second network element is further configured to return a deregistration success response or a deregistration failure response to the first network element;

[0417] The first network element is further configured to receive a deregistration success response or a deregistration failure response returned by the second network element.

[0418] Optionally, in one embodiment of the present disclosure, the second network element 2102b is further configured to:

[0419] receiving a first registration request sent by a first network element for registering a third-party service, where the first registration request includes registration information of the third-party service;

[0420] The registration information includes at least one of the following:

[0421] The identification ID of the network function NF corresponding to the third-party service;

[0422] NF type corresponding to the third-party service;

[0423] NF support business corresponding to third-party services;

[0424] The ID of the Public Land Mobile Network (PLMN) corresponding to the third-party application.

[0425] Optionally, in one embodiment of the present disclosure, the second network element 2102b is further configured to:

[0426] determining whether the third-party service meets authorization conditions based on the registration information of the third-party service;

[0427] In response to determining that the third-party service meets the authorization condition, storing the ID of the NF corresponding to the third-party service;

[0428] Sending a second registration request for registering a third-party service to a third network element, where the second registration request includes the registration information and an ID of the second network element;

[0429] Receive a registration success response sent by the third network element.

[0430] Optionally, in one embodiment of the present disclosure, the second network element 2102b is further configured to:

[0431] Return a registration success response to the first network element.

[0432] Optionally, in one embodiment of the present disclosure, the second network element 2102b is further configured to:

[0433] determining whether the third-party service meets authorization conditions based on the registration information of the third-party service;

[0434] In response to the registration information of the third-party service not satisfying an authorization condition, it is determined that the registration of the third-party service has failed.

[0435] Optionally, in one embodiment of the present disclosure, the second network element 2102b is further configured to:

[0436] Return a registration failure response to the first network element.

[0437] Optionally, in one embodiment of the present disclosure, the second network element 2102b is further configured to:

[0438] receiving a first deregistration request for deregistering a third-party service sent by a first network element, where the first deregistration request includes deregistration information of the third-party service;

[0439] The deregistration information includes at least one of the following:

[0440] The ID of the NF corresponding to the third-party service;

[0441] The PLMN ID corresponding to the third-party application.

[0442] Optionally, in one embodiment of the present disclosure, the second network element 2102b is further configured to:

[0443] determining whether the third-party service meets a cancellation condition based on the cancellation information of the third-party service;

[0444] In response to determining that the third-party service meets the deregistration condition, sending a second deregistration request for deregistering the third-party service to a third network element, where the second deregistration request includes the deregistration information;

[0445] In response to receiving a successful deregistration response sent by the third network element, the ID of the NF corresponding to the third-party service is deleted.

[0446] Optionally, in one embodiment of the present disclosure, the second network element 2102b is further configured to:

[0447] Return a successful deregistration response to the first network element

[0448] Optionally, in one embodiment of the present disclosure, the second network element 2102b is further configured to:

[0449] determining whether the third-party service meets a cancellation condition based on the cancellation information of the third-party service;

[0450] In response to the deregistration information of the third-party service not satisfying a deregistration condition, it is determined that the deregistration of the third-party service has failed.

[0451] Optionally, in one embodiment of the present disclosure, the second network element 2102b is further configured to:

[0452] Return a deregistration failure response to the first network element.

[0453] Optionally, in one embodiment of the present disclosure, the third network element 2103b is further configured to:

[0454] receiving a second registration request sent by the second network element for registering a third-party service, where the second registration request includes registration information of the third-party service and an ID of the second network element;

[0455] The registration information includes at least one of the following:

[0456] The ID of the NF corresponding to the third-party service;

[0457] NF type corresponding to the third-party service;

[0458] NF support business corresponding to third-party services;

[0459] The PLMN ID corresponding to the third-party application.

[0460] Optionally, in one embodiment of the present disclosure, the third network element 2103b is further configured to:

[0461] Generate a corresponding configuration file for the third-party service registration based on the registration information of the third-party service and the ID of the second network element;

[0462] The availability status corresponding to the third-party service is set to available.

[0463] Optionally, in one embodiment of the present disclosure, the third network element 2103b is further configured to:

[0464] Return a registration success response to the second network element.

[0465] Optionally, in one embodiment of the present disclosure, the third network element 2103b is further configured to:

[0466] Sending a first notification message to a specific NF network element; the specific NF network element is a network element that has subscribed to the service change event, and the first notification message is used to indicate that the third-party service has completed registration.

[0467] Optionally, in one embodiment of the present disclosure, the third network element 2103b is further configured to:

[0468] receiving a second deregistration request for deregistering a third-party service sent by a second network element, where the second deregistration request includes deregistration information of the third-party service;

[0469] The deregistration information includes at least one of the following:

[0470] The ID of the NF corresponding to the third-party service;

[0471] The PLMN ID corresponding to the third-party application.

[0472] Optionally, in one embodiment of the present disclosure, the third network element 2103b is further configured to:

[0473] Deleting a configuration file corresponding to the third-party service based on the deregistration information corresponding to the third-party service;

[0474] The availability status of the third-party service is set to unavailable.

[0475] Optionally, in one embodiment of the present disclosure, the third network element 2103b is further configured to:

[0476] Return a successful deregistration response to the second network element.

[0477] Optionally, in one embodiment of the present disclosure, the third network element 2103b is further configured to:

[0478] Sending a second notification message to a specific NF network element; the specific NF network element is a network element that has subscribed to the service change event, and the second notification message is used to indicate that the third-party service has completed deregistration.

[0479] Optionally, in one embodiment of the present disclosure, the first network element 2101b is further configured to:

[0480] Sending a first registration request for registering a third-party service to the second network element, where the first registration request includes registration information of the third-party service;

[0481] The registration information includes at least one of the following:

[0482] The ID of the NF corresponding to the third-party service;

[0483] NF type corresponding to the third-party service;

[0484] NF support business corresponding to third-party services;

[0485] The PLMN ID corresponding to the third-party application.

[0486] Optionally, in one embodiment of the present disclosure, the first network element 2101b is further configured to:

[0487] Receive a registration success response returned by the second network element.

[0488] Optionally, in one embodiment of the present disclosure, the first network element 2101b is further configured to:

[0489] Receive a registration failure response returned by the second network element.

[0490] Optionally, in one embodiment of the present disclosure, the first network element 2101b is further configured to:

[0491] Sending a first deregistration request for registering a third-party service to the second network element, where the first deregistration request includes deregistration information of the third-party service;

[0492] The deregistration information includes at least one of the following:

[0493] The ID of the NF corresponding to the third-party service;

[0494] The PLMN ID corresponding to the third-party application.

[0495] Optionally, in one embodiment of the present disclosure, the first network element 2101b is further configured to:

[0496] Receive a successful deregistration response returned by the second network element.

[0497] Optionally, in one embodiment of the present disclosure, the first network element 2101b is further configured to:

[0498] Receive a deregistration failure response returned by the second network element.

[0499] Please refer to Figure 22, which is a schematic diagram of the structure of a communication device 2200 provided in an embodiment of the present application. Communication device 2200 can be a network device or a terminal device, or a chip, chip system, or processor that supports the network device to implement the above method, or a chip, chip system, or processor that supports the terminal device to implement the above method. This device can be used to implement the method described in the above method embodiment. For details, please refer to the description of the above method embodiment.

[0500] The communication device 2200 may include one or more processors 2201. The processor 2201 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control the communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.), execute computer programs, and process computer program data.

[0501] Optionally, the communication device 2200 may further include one or more memories 2202, on which a computer program 2204 may be stored. The processor 2201 executes the computer program 2204 to cause the communication device 2200 to perform the method described in the above method embodiment. Optionally, the memory 2202 may also store data. The communication device 2200 and the memory 2202 may be provided separately or integrated together.

[0502] Optionally, the communication device 2200 may further include a transceiver 2205 and an antenna 2206. The transceiver 2205 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, and is configured to implement transceiver functions. The transceiver 2205 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, and is configured to implement a transmitting function.

[0503] Optionally, the communication device 2200 may further include one or more interface circuits 2207. The interface circuit 2207 is configured to receive code instructions and transmit the code instructions to the processor 2201. The processor 2201 executes the code instructions to enable the communication device 2200 to perform the method described in the above method embodiment.

[0504] Communication device 2200 is a NEF network element: transceiver 2205 is configured to execute steps 201 and 203 in Figure 2; steps 301 and 304 to 306 in Figure 3; steps 401 and 404 in Figure 4; steps 501 and 503 to 505 in Figure 5; and steps 601 and 604 in Figure 6. Processor 2201 is configured to execute step 202 in Figure 2; steps 302 to 303 in Figure 3; steps 402 to 403 in Figure 4; step 502 in Figure 5; and steps 602 to 603 in Figure 6.

[0505] Communication device 2200 is an NRF network element: transceiver 2205 is configured to execute steps 701 and 703 in Figure 7; steps 801 and 803 in Figure 8; steps 901 and 903 in Figure 9; steps 1001 and 1003 in Figure 10; and steps 1101 and 1103 in Figure 11. Processor 2201 is configured to execute step 702 in Figure 7; step 802 in Figure 8; step 902 in Figure 9; step 1002 in Figure 10; and step 1102 in Figure 11.

[0506] Communication device 2200 is an AF network element: transceiver 2205 is configured to execute steps 1201 to 1202 in Figure 12; steps 1301 to 1302 in Figure 13; steps 1401 to 1402 in Figure 14; steps 1501 to 1502 in Figure 15; and steps 1601 to 1602 in Figure 16. Processor 2201 is configured to execute step 504 in Figure 5.

[0507] In one implementation, the processor 2201 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or may be used for transmitting or delivering signals.

[0508] In one implementation, processor 2201 may store a computer program 2203. Computer program 2203, when executed on processor 2201, enables communication device 2200 to perform the method described in the above method embodiment. Computer program 2203 may be embedded in processor 2201, in which case processor 2201 may be implemented by hardware.

[0509] In one implementation, the communication device 2200 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in this application can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0510] The communication device described in the above embodiments may be a network device or a terminal device, but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited to FIG. 22. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0511] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0512] (2) a collection of one or more ICs, optionally including a storage component for storing data and computer programs;

[0513] (3) ASIC, such as modem;

[0514] (4) Modules that can be embedded in other devices;

[0515] (5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

[0516] (6)Others, etc.

[0517] If the communication device can be a chip or a chip system, please refer to the schematic diagram of the chip structure shown in Figure 23. The chip shown in Figure 23 includes a processor 2301 and an interface 2302. The number of processors 2301 can be one or more, and the number of interfaces 2302 can be multiple.

[0518] Optionally, the chip further includes a memory 2303, which is used to store necessary computer programs and data.

[0519] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functions for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present application.

[0520] The present application also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0521] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0522] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0523] Those skilled in the art will understand that the various numerical numbers such as first and second involved in this application are only for the convenience of description and are not used to limit the scope of the embodiments of this application, and also indicate the order of precedence.

[0524] In this application, at least one can also be described as one or more, and multiple can be two, three, four or more, which is not limited in this application. In the embodiments of this application, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order of precedence or size between the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0525] The correspondences shown in the tables in this application can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values, which are not limited by this application. When configuring the correspondence between information and parameters, it is not necessary to configure all the correspondences shown in each table. For example, in the tables in this application, the correspondences shown in certain rows may not be configured. For another example, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables can also use other names that are understandable to the communication device, and the values ​​or representations of the parameters can also use other values ​​or representations that are understandable to the communication device. When implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables.

[0526] The predefined in this application may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

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

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

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

Claims

1. A third-party service management method, characterized in that: Executed by the Network Exposure Function (NEF) element, including: receiving a first management request for managing a third-party service sent by an application function AF network element, where the first management request indicates a third-party service provided by a third-party application; managing the third-party service based on the first management request; Return the management result to the AF network element.

2. The method according to claim 1, wherein The receiving a first management request for managing a third-party service sent by the AF network element includes: receiving a first registration request sent by the AF network element for registering a third-party service, where the first registration request includes registration information of the third-party service; The registration information includes at least one of the following: The identification ID of the network function NF corresponding to the third-party service; NF type corresponding to the third-party service; NF support business corresponding to third-party services; The ID of the Public Land Mobile Network (PLMN) corresponding to the third-party application.

3. The method according to claim 2, wherein Managing the third-party service based on the first management request includes: determining whether the third-party service meets authorization conditions based on the registration information of the third-party service; In response to determining that the third-party service meets the authorization condition, storing the ID of the NF corresponding to the third-party service; Sending a second registration request for registering a third-party service to a network storage function (NRF) network element, where the second registration request includes the registration information and the NEF ID; Receive a registration success response sent by the NRF network element.

4. The method according to claim 3, wherein The returning the management result to the AF network element includes: A registration success response is returned to the AF network element.

5. The method according to claim 2, wherein Managing the third-party service based on the first management request includes: determining whether the third-party service meets authorization conditions based on the registration information of the third-party service; In response to the registration information of the third-party service not satisfying an authorization condition, it is determined that the registration of the third-party service has failed.

6. The method according to claim 5, wherein The returning the management result to the AF network element includes: A registration failure response is returned to the AF network element.

7. The method according to claim 1, wherein The receiving a first management request for managing a third-party service sent by the AF network element includes: receiving a first deregistration request for deregistering a third-party service sent by the AF network element, where the first deregistration request includes deregistration information of the third-party service; The deregistration information includes at least one of the following: The ID of the NF corresponding to the third-party service; The PLMN ID corresponding to the third-party application.

8. The method according to claim 7, wherein Managing the third-party service based on the first management request includes: determining whether the third-party service meets a cancellation condition based on the cancellation information of the third-party service; In response to determining that the third-party service meets the deregistration condition, sending a second deregistration request for deregistering the third-party service to the NRF network element, where the second deregistration request includes the deregistration information; In response to receiving a deregistration success response sent by the NRF network element, the ID of the NF corresponding to the third-party service is deleted.

9. The method according to claim 8, wherein The returning the management result to the AF network element includes: A deregistration success response is returned to the AF network element.

10. The method according to claim 7, wherein Managing the third-party service based on the first management request includes: determining whether the third-party service meets a cancellation condition based on the cancellation information of the third-party service; In response to the deregistration information of the third-party service not satisfying a deregistration condition, it is determined that the deregistration of the third-party service has failed.

11. The method according to claim 10, wherein The returning the management result to the AF network element includes: Return a deregistration failure response to the AF network element.

12. A third-party service management method, characterized in that: Executed by NRF network elements, including: receiving a second management request for managing a third-party service sent by the NEF network element, where the second management request indicates a third-party service provided by a third-party application; managing the third-party service based on the second management request; Return the management result to the NEF network element.

13. The method according to claim 12, wherein: The receiving a second management request for managing a third-party service sent by the NEF network element includes: receiving a second registration request sent by the NEF network element for registering a third-party service, where the second registration request includes registration information of the third-party service and an NEF ID; The registration information includes at least one of the following: The ID of the NF corresponding to the third-party service; NF type corresponding to the third-party service; NF support business corresponding to third-party services; The PLMN ID corresponding to the third-party application.

14. The method according to claim 13, wherein The managing the third-party service based on the second management request includes at least one of the following: Generate a corresponding configuration file for the third-party service registration based on the registration information and NEF ID of the third-party service; The availability status corresponding to the third-party service is set to available.

15. The method according to claim 14, wherein The returning the management result to the NEF network element includes: A registration success response is returned to the NEF network element.

16. The method according to claim 14, wherein The method further comprises: Sending a first notification message to a specific NF network element; the specific NF network element is a network element that has subscribed to the service change event, and the first notification message is used to indicate that the third-party service has completed registration.

17. The method according to claim 12, wherein The receiving a second management request for managing a third-party service sent by the NEF network element includes: receiving a second deregistration request for deregistering a third-party service sent by the NEF network element, where the second deregistration request includes deregistration information of the third-party service; The deregistration information includes at least one of the following: The ID of the NF corresponding to the third-party service; The PLMN ID corresponding to the third-party application.

18. The method according to claim 17, wherein The managing the third-party service based on the second service management request includes at least one of the following: Deleting a configuration file corresponding to the third-party service based on the deregistration information corresponding to the third-party service; The availability status of the third-party service is set to unavailable.

19. The method according to claim 18, wherein The returning the management result to the NEF network element includes: returning a deregistration success response to the NEF network element.

20. The method of claim 18, wherein: The method further comprises: Sending a second notification message to a specific NF network element; the specific NF network element is a network element that has subscribed to the service change event, and the second notification message is used to indicate that the third-party service has completed deregistration.

21. A third-party service management method, characterized in that: Executed by the AF network element, including: Sending a first management request for managing a third-party service to an NEF network element, where the first management request indicates a third-party service provided by a third-party application; Receive the management result returned by the NEF network element.

22. The method according to claim 21, wherein The sending of the first management request for managing the third-party service to the NEF network element includes: sending a first registration request for registering the third-party service to the NEF network element, where the first registration request includes registration information of the third-party service; The registration information includes at least one of the following: The ID of the NF corresponding to the third-party service; NF type corresponding to the third-party service; NF support business corresponding to third-party services; The PLMN ID corresponding to the third-party application.

23. The method according to claim 22, wherein The receiving the management result returned by the NEF network element includes: receiving a registration success response returned by the NEF network element.

24. The method of claim 22, wherein: The receiving the management result returned by the NEF network element includes: receiving a registration failure response returned by the NEF network element.

25. The method of claim 21, wherein The sending of the first management request for managing the third-party service to the NEF network element includes: sending a first deregistration request for registering the third-party service to the NEF network element, the first deregistration request including deregistration information of the third-party service; The deregistration information includes at least one of the following: The ID of the NF corresponding to the third-party service; The PLMN ID corresponding to the third-party application.

26. The method of claim 25, wherein: The receiving the management result returned by the NEF network element includes: receiving a deregistration success response returned by the NEF network element.

27. The method of claim 25, wherein: The receiving the management result returned by the NEF network element includes: receiving a deregistration failure response returned by the NEF network element.

28. A communication device, configured in a NEF network element, comprising: a transceiver module, configured to receive a first management request for managing a third-party service sent by an application function AF network element, wherein the first management request indicates a third-party service provided by a third-party application; a management module, configured to manage the third-party service based on the first management request; The transceiver module is further configured to return a management result to the AF network element.

29. A communication device, configured in an NRF network element, comprising: a transceiver module, configured to receive a second management request for managing a third-party service sent by the NEF network element, wherein the second management request indicates a third-party service provided by a third-party application; a management module, configured to manage the third-party service based on the second management request; The transceiver module is further configured to return the management result to the NEF network element.

30. A communication device, configured in an AF network element, comprising: a transceiver module, configured to send a first management request for managing a third-party service to an NEF network element, wherein the first management request indicates a third-party service provided by a third-party application; The transceiver module is further configured to receive the management result returned by the NEF network element.

31. A communication system, characterized in that: The system comprises: A first network element is configured to send a first management request for managing a third-party service, where the first management request indicates a third-party service provided by a third-party application; a second network element, configured to receive the first management request for managing the third-party service and manage the third-party service based on the first management request; The second network element is further configured to send a second management request for managing a third-party service, where the second management request indicates a third-party service provided by a third-party application; a third network element, configured to receive the second management request for managing the third-party service, manage the third-party service based on the second management request, and return a management result to the second network element; The second network element is further configured to return a management result to the first network element; The first network element is further used to receive the management result returned by the second network element.

32. A communication device, characterized in that: The device includes a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory so that the device performs the method according to any one of claims 1 to 11, or the processor executes the computer program stored in the memory so that the device performs the method according to any one of claims 12 to 20, or the processor executes the computer program stored in the memory so that the device performs the method according to any one of claims 21 to 27.

33. A communication device, characterized in that: include: processor and interface circuitry, wherein The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to execute the code instructions to perform the method according to any one of claims 1 to 11, or to execute the code instructions to execute the method according to any one of claims 12 to 20, or to execute the code instructions to execute the method according to any one of claims 21 to 27.

34. A computer-readable storage medium storing instructions, which, when executed, enable the method according to any one of claims 1 to 11 to be implemented, or when executed, enable the method according to any one of claims 12 to 20 to be implemented, or when executed, enable the method according to any one of claims 21 to 27 to be implemented.

Images