Service calling method and network device

Abstract

The present disclosure provides a service invocation method and a network device. The method, which is applied to a service provider, includes receiving a service request for a first service sent from a service user by the first service provider, and sending a service response for the first service from the first service provider to the service user. The service response for the first service includes service invocation information or a service invocation result for at least one second service related to the first service. The service invocation information is for instructing the service user to invoke the second service.

Description

[Technical field]

[0001] [CROSS REFERENCE TO RELATED APPLICATIONS] This application claims priority from Chinese Patent Application No. 201910941178.9, filed in China on September 30, 2019, the entire contents of which are incorporated herein by reference. [Technical field] The present disclosure relates to the field of communication technology, and in particular to a service invoking method and a network device. [Background technology]

[0002] The core network of 5G (fifth generation mobile communication technology) adopts a service-based architecture (see Figure 1, where NSSF (Network Slice Selection Function), NEF (network exposure function), NRF (NF Repository Function), PCF (Policy Control Function), UDM (Unified Data Management), AF (application function), AUSF (Authentication Server Function), AMF (Access and Mobility Management Function), SMF (Session Management Function), UE (User Equipment), RAN ((Radio) Access Network), UPF (User plane Function), DN (Data network)). The interfaces between NFs adopt service-based interfaces, and it has been revealed that the 5G service-based interfaces use the HTTP / 2+TCP protocol. When designing the 5G business flow, it is necessary to define the service invocation logic of all related network functions (NFs), some NFs support the service provider function of the corresponding service, and some NFs support the service consumer function of the corresponding service. The service consumer NF needs to write the trigger condition of the service invocation, the service name of the service invocation, and the resource address related to the service invocation into the business processing logic, and it will discover the service provider NF through the service discovery mechanism and the NF selection mechanism before making the service invocation.

[0003] In order to enable the reuse of services in multiple different business processes, the concept of 5G service design is to atomize services, separate / isolate services, and enable service reuse. However, the service atomization design of the 5G Core Network (5GC) complicates business processing processes. Summary of the Invention [Problem to be solved by the invention]

[0004] Therefore, the present disclosure provides a service invocation method and network equipment to solve the problem in the prior art that the service atomization design of the 5G core network complicates business processing processes. [Means for solving the problem]

[0005] In order to solve the above technical problem, as a first aspect, the present disclosure provides a service invocation method. In the method, A service request for a first service transmitted from a service user is received by a first service provider; A service response of the first service is transmitted from the first service provider to the service user; The service response of the first service includes service invocation information or a service invocation result of at least one second service related to the first service, and the service invocation information is intended to instruct the service user to invoke the second service.

[0006] Optionally, the service invocation information comprises: The service name of the second service, the service provider address of the second service, parameters required for invoking the second service, a resource address related to the second service, an operation method for a resource related to the second service, and at least one of a prerequisite for the second service.

[0007] Optionally, the service invocation result is It contains at least one of the following: data, the address of a resource, and a response code.

[0008] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The service invocation result of the second service includes an address of a contract data resource and an address of a subscription resource.

[0009] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The service invocation information of the second service includes service invocation information of a contract data download service and service invocation information of a contract data modification subscription service.

[0010] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service; The service invocation information of the second service includes service invocation information of a contract data download service.

[0011] Optionally, when the service request of the first service is a contract data download service request, the second service includes a contract data change subscription service; The service invocation information of the second service includes service invocation information of a contract data change subscription service.

[0012] As a second aspect, the present disclosure further provides a service invocation method. In the method, A service request for a first service is sent from a service user to a first service provider; A service response of the first service is received by the service user, the service response including service invocation information or a service invocation result for instructing the service user to invoke the second service of at least one second service related to the first service; If the service response of the first service includes the service call information, the service user initiates a second service call based on the service call information, thereby obtaining a service call result of the second service.

[0013] Optionally, the service invocation information comprises: The service name of the second service, the service provider address of the second service, parameters required for invoking the second service, a resource address related to the second service, an operation method for a resource related to the second service, and at least one of a prerequisite for the second service.

[0014] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The service invocation result of the second service includes an address of a contract data resource and an address of a subscription resource.

[0015] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The service invocation information of the second service includes service invocation information of a contract data download service and service invocation information of a contract data modification subscription service.

[0016] In a third aspect, the present disclosure further provides a network device. The network device, which is the first service provider, a first receiving module for receiving a service request for a first service sent from a service user; a response module for sending a service response of the first service to the service user; The service response of the first service includes service invocation information or a service invocation result of at least one second service related to the first service, and the service invocation information is intended to instruct the service user to invoke the second service.

[0017] Optionally, the service invocation information comprises: The service name of the second service, the service provider address of the second service, parameters required for invoking the second service, a resource address related to the second service, an operation method for a resource related to the second service, and at least one of a prerequisite for the second service.

[0018] Optionally, the service invocation result includes at least one of data, an address of a resource, and a response code.

[0019] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The service invocation result of the second service includes an address of a contract data resource and an address of a subscription resource.

[0020] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The service invocation information of the second service includes service invocation information of a contract data download service and service invocation information of a contract data modification subscription service.

[0021] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service; The service invocation information of the second service includes service invocation information of a contract data download service.

[0022] Optionally, when the service request of the first service is a contract data download service request, the second service includes a contract data change subscription service; The service invocation information of the second service includes service invocation information of a contract data change subscription service.

[0023] In a fourth aspect, the present disclosure further provides a network device. The network devices that are service users a sending module for sending a service request for the first service to a first service provider; a second receiving module for receiving a service response of the first service, the service response including service invocation information or a service invocation result for instructing the service user to invoke the second service of at least one second service related to the first service; and a service invocation module for initiating a second service invocation based on the service invocation information to obtain a service invocation result of the second service when the service response of the first service includes the service invocation information.

[0024] Optionally, the service invocation information comprises: The service name of the second service, the service provider address of the second service, parameters required for invoking the second service, a resource address related to the second service, an operation method for a resource related to the second service, and at least one of a prerequisite for the second service.

[0025] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The service invocation result of the second service includes an address of a contract data resource and an address of a subscription resource.

[0026] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The service invocation information of the second service includes service invocation information of a contract data download service and service invocation information of a contract data modification subscription service.

[0027] In a fifth aspect, the present disclosure further provides a network device. The network device, which is the first service provider, A transceiver and a processor, The transceiver includes: receiving a service request for a first service sent from a service user; Further, a service response of the first service is sent to the service user; The service response of the first service includes service invocation information or a service invocation result of at least one second service related to the first service, and the service invocation information is intended to instruct the service user to invoke the second service.

[0028] Optionally, the service invocation information comprises: The service name of the second service, the service provider address of the second service, parameters required for invoking the second service, a resource address related to the second service, an operation method for a resource related to the second service, and at least one of a prerequisite for the second service.

[0029] Optionally, the service invocation result includes at least one of data, an address of a resource, and a response code.

[0030] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The service invocation result of the second service includes an address of a contract data resource and an address of a subscription resource.

[0031] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The service invocation information of the second service includes service invocation information of a contract data download service and service invocation information of a contract data modification subscription service.

[0032] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service; The service invocation information of the second service includes service invocation information of a contract data download service.

[0033] Optionally, when the service request of the first service is a contract data download service request, the second service includes a contract data change subscription service; The service invocation information of the second service includes service invocation information of a contract data change subscription service.

[0034] In a sixth aspect, the present disclosure further provides a network device. The network devices that are service users A transceiver and a processor, The transceiver includes: Sending a service request for the first service to a first service provider; Further, a service response of the first service is received, the service response including service invocation information or a service invocation result for instructing the service user to invoke the second service of at least one second service related to the first service; Furthermore, if the service response of the first service includes the service invocation information, a second service invocation is initiated based on the service invocation information to obtain a service invocation result of the second service.

[0035] Optionally, the service invocation information comprises: The service name of the second service, the service provider address of the second service, parameters required for invoking the second service, a resource address related to the second service, an operation method for a resource related to the second service, and at least one of a prerequisite for the second service.

[0036] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The service invocation result of the second service includes an address of a contract data resource and an address of a subscription resource.

[0037] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The service invocation information of the second service includes service invocation information of a contract data download service and service invocation information of a contract data modification subscription service.

[0038] In a seventh aspect, the present disclosure further provides a network device. The network device, which is the first service provider, Memory, A processor; and a computer program stored in the memory and executable by the processor, the computer program realizing, when executed by the processor, any one of the above-mentioned first service provider side service invocation methods.

[0039] In an eighth aspect, the present disclosure further provides a network device. The network devices that are service users Memory, A processor; and a computer program stored in the memory and executable by the processor, the computer program realizing, when executed by the processor, any one of the above-mentioned service invocation methods on the service user side.

[0040] In a ninth aspect, the present disclosure further provides a computer-readable storage medium. The computer-readable storage medium, A computer program is stored which, when executed by a processor, implements any one of the above service invocation methods. Effect of the Invention

[0041] In an embodiment of the present disclosure, after a service request for a first service sent by a service user is received by the first service provider, if a second service that needs to be later invoked by the service user can be determined, the service invocation information or service invocation result of the second service can be carried in the service response of the first service, thereby optimizing the business processing logic and reducing the complexity of business processing. [Brief description of the drawings]

[0042] [Figure 1] Figure 1 is a diagram showing the service architecture of a 5G core network. [Diagram 2] FIG. 2 is a diagram showing a service discovery flow. [Diagram 3] FIG. 3 is a diagram showing a service invocation flow. [Figure 4] Figure 4 shows the business flow for 5G user registration. [Diagram 5] FIG. 5 is a diagram showing a specific flow of three service calls: location registration, downloading contract data, and subscribing to changes in contract data. [Figure 6] FIG. 6 is a diagram illustrating a flow of a service invocation method according to the first embodiment of the present disclosure. [Figure 7] FIG. 7 is a diagram showing a specific flow of three service calls, namely, location registration, download of contract data, and subscription to changes in contract data, in an embodiment of the present disclosure. [Figure 8] FIG. 8 is a diagram illustrating the execution flow of different service invocations based on service invocation information in an embodiment of the present disclosure. [Figure 9] FIG. 9 is a diagram showing another specific flow of three service calls, namely, location registration, download of contract data, and subscription to contract data changes, in an embodiment of the present disclosure. [Figure 10] FIG. 10 is a diagram illustrating a flow of a service calling method according to the second embodiment of the present disclosure. [Figure 11] FIG. 11 is a diagram illustrating a configuration of a network device according to the third embodiment of the present disclosure. [Figure 12] FIG. 12 is a diagram illustrating a configuration of a network device according to the fourth embodiment of the present disclosure. [Figure 13] FIG. 13 is a diagram illustrating a configuration of a network device according to the fifth embodiment of the present disclosure. [Figure 14] FIG. 14 is a diagram illustrating a configuration of a network device according to the sixth embodiment of the present disclosure. [Figure 15] FIG. 15 is a diagram illustrating a configuration of a network device according to a seventh embodiment of the present disclosure. [Figure 16] FIG. 16 is a diagram illustrating a configuration of a network device according to an eighth embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0043] In order to make the objectives, technical means and advantages of the embodiments of the present disclosure clearer, the technical means of the embodiments of the present disclosure will be described below clearly and completely with reference to the accompanying drawings of the embodiments of the present disclosure. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, and are not all of them. Based on the embodiments of the present disclosure, all other embodiments that can be made by those skilled in the art without creative work shall belong to the protection scope of the present disclosure.

[0044] Business processing based on the service-based architecture mainly includes the following flows. Service Registration: A service provider NF registers its services in an NF Repository Function NRF, and registers all the services it provides and related information, including the information necessary for a service user to discover this NF. (The description information of an NF (NFProfile) provides the information necessary for a service user to discover the services of this NF, such as the authentication service function AUSF (Authentication Server Function), and AUSF information (ausfInfo) is provided.) Service Discovery: Referring to FIG. 2, a service consumer NF issues a service discovery request (Nnrf_NFDiscovery_Request) to the NRF, and discovers, through the NRF, a provider NF of a specific service (related to the business flow of a higher-level application) that needs to be invoked. Service call: Referring to FIG. 3, when the service user receives a service discovery response from the NRF, the service user transmits a service request to the service provider NF indicated in the service discovery response, and receives a service response returned from the service provider.

[0045] Referring to Figure 4, the business flow of 5G user registration is as follows: 1. A terminal (User Equipment) user transmits a registration request to a (radio) access network (R) AN (Radio Access Network). 2. In the access network, select an Access and Mobility Management Function (AMF selection). 3. In the access network, a Registration Request is sent to the new AMF. 4. The new AMF requests the original AMF to transfer the terminal user's context information (Namf_Communication_UEContextTransfer). 5. The original AMF returns the terminal user's context information to the new AMF (Namf_Communication_UEContextTransfer response). 6. The new AMF sends an Identity Request to the terminal user. 7. The terminal user sends an Identity Response to the new AMF. 8. The new AMF selects the AUSF (AUSF selection). 9. The authentication process (Authentication / Security) between the terminal user and the core network is carried out. 10. The new AMF sends a registration completion notification, which is the result of the terminal user's registration, to the original AMF (Namf_Communication_RegistrationCompleteNotify). 11. Identity Request / Response, which is the identity acquisition process between the new AMF and the terminal user. 12. The new AMF requests a device identifier check from the equipment identity register (EIR) (N5g-eir_EquipmentIdentityCheck_Get). 13. The new AMF selects Unified Data Management (UDM). 14a. The new AMF performs terminal user location registration to UDM (Nudm_UECM_Registration). 14b. The new AMF obtains the terminal user's contract data from the UDM (Nudm_SDM_Get). 14c. The new AMF subscribes to changes in the terminal user's contract data to the UDM (Nudm_SDM_Subscribe). 14d. The UDM notifies the original AMF of the terminal user deregistration (Nudm_UECM_DeregistrationNotify). 14e. The original AMF unsubscribes the terminal user from the associated subscription to UDM (Nudm_SDM_Unsubscribe). 15. The new AMF selects the Policy Control Function (PCF) (PCF selection). 16. The new AMF requires the UDM to provide user access policies (AM Policy Association Establishment / Modification). 17. The new AMF updates or releases the Protocol Data Unit (PDU) session to the Session Management Function (SMF) (Nsmf_PDUSession_UpdateSMContext / Nsmf_PDUSession_ReleaseSMContext). 18. If the terminal user simultaneously has a non-3GPP (Third Generation Partnership Projects) access method, the new AMF needs to establish a connection with the Non-3GPP InterWorking Function / Trusted Non-3GPP Gateway Function (N3IWF / TNGF) that connects to the terminal user (N2 AMF Mobility Request). 19.N3 IWF / TNGF returns a response to the new AMF (N2 AMF Mobility Response). 19a. The new AMF performs terminal user location registration to UDM (access type: "non-3GPP access") (Nudm_UECM_Registration). 19b. The UDM notifies the original AMF of the terminal user deregistration (Nudm_UECM_DeregistrationNotify). 19c. The UDM notifies the original AMF of the deletion of the terminal user's associated subscription (Nudm_SDM_Unsubscribe). 21. The new AMF sends a registration acceptance message (RegistrationAccept) to the terminal user. 21b. The new AMF requests user policy control from the PCF (UEPolicyAssociationEstablishment). 22. The UE responds with a Registration Complete message (Registration Complete) to the new AMF. 23. When the UDM requests the terminal user to receive information such as a slice contract information change instruction and return a confirmation, the AMF notifies the UDM by sending Nudm_SDM_Info and provides the UE confirmation. 24. The AMF sends an indication of the voice support capability of the IP Multimedia Subsystem IMS (IP Multiple Subsystem) to the UDM via Nudm_UECM_Update.

[0046] 14a / b / c in Figure 4 correspond to location registration, contract data download, and subscription to contract data changes, respectively. These three service calls are three independent service / business operations, and to complete them, the AMF needs to call the UDM service three times. In addition, the service consumer NF needs to obtain the address of the service provider NF through service discovery in the NRF before the service call, so the above three service calls also require a service discovery process. If the service discovery result is not cached, three service discovery processes are required. For the specific flow of the three service calls of location registration, contract data download, and contract data change subscription mentioned above, refer to Figure 5. The service discovery request sent first by the AMF carries the terminal identifier (UE ID), target network function type (NF type): UDM, and service name: Nudm_UECM_Registration, the service discovery response sent first by the UDM contains a UDM list, the service discovery requests sent second and third times by the AMF carry the UDM instance identifier (ID), and the service discovery responses sent second and third times by the UDM contain the service address of the UDM.

[0047] Meanwhile, in 4G (fourth generation mobile communication technology) networks, location registration, contract data download and subscription of contract data modification can be completed in one interaction. The response message (update location ACK) of location registration carries user contract data. And when location registration is successful, the home subscriber service HSS (Home Subscriber Server) supports initiating contract data modification flow to the mobility management entity MME (Mobile Management Entity) by default.

[0048] Comparing the user attachment workflows of 4G and 5G, it can be seen that the service atomization design of the 5G core network has increased the number of steps in the workflow.

[0049] Please refer to Fig. 6. Fig. 6 is a diagram showing the flow of a service invocation method according to the first embodiment of the present disclosure. A step 61 in which a service request for a first service sent from a service user is received by a first service provider; and a step 62 in which a service response of the first service is sent from the first service provider to the service user. The service response of the first service includes service invocation information or a service invocation result of at least one second service related to the first service, and the service invocation information is intended to instruct the service user to invoke the second service.

[0050] The first service provider and the second service provider may be the same NF.

[0051] In an embodiment of the present disclosure, after a service request for a first service sent by a service user is received by a first service provider, if a second service that needs to be called later by the service user can be determined, the service invocation information or service invocation result of the second service is carried in the service response of the first service (mainly applicable when the first service provider and the second service provider are the same NF and the service provider can obtain the service invocation result of the second service based on the currently obtained information), thereby optimizing the business processing logic and reducing the complexity of business processing.

[0052] In particular, in one embodiment, the service invocation information is used to direct the invocation of a second service, thereby eliminating the need for a service user's service invocation logic, while the service invocation information is used to direct the second service provider, thereby eliminating the need for a service user's service discovery process.

[0053] The above service invocation method will be exemplified below.

[0054] A specific service provider NF selected in one business flow may provide service invocation information for one or more next service invocations to the service user based on business processing logic, thereby eliminating the service discovery process and service invocation logic of the service user.

[0055] Therefore, in one optional embodiment of the present disclosure, the service response of the first service includes service invocation information of at least one second service related to the first service, and the service invocation information is for directing the invocation of the second service by the service user.

[0056] Optionally, the service invocation information includes at least one of a service name of the second service, a service provider address of the second service, parameters required for service invocation of the second service (including required service request message headers and message bodies), a resource address related to the second service, an operation method for a resource related to the second service, and a precondition for the second service (the second service is invoked only if the precondition is satisfied).

[0057] Here, the operation methods for resources specifically include increase (that is, increase), decrease (that is, deletion), modification (that is, correction), and check (that is, inquiry).

[0058] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call information of the second service includes service call information for the contract data download service and service call information for the contract data change subscription service.

[0059] Also, referring to FIG. 7, when the service request for the first service is a location registration service request, the second service may include only a contract data download service, and the service call information of the second service includes service call information of the contract data download service.

[0060] Then, when the UDM receives a contract data download service request sent from the AMF, the contract data download service request is a service request for a first service, the second service includes a contract data change subscription service, and the service invocation information of the second service includes service invocation information of the contract data change subscription service.

[0061] That is, when the service request for the first service is a contract data download service request, the second service includes a contract data change subscription service, and the service invocation information of the second service includes service invocation information of the contract data change subscription service.

[0062] In the prior art, the service provider NF may return different response codes or instructions to the service user based on the business processing logic, and the service user NF executes different subsequent processing based on the response code or instruction. Specifically, after receiving the response code returned from the service provider, the service user needs to determine the business processing branch based on the response code.

[0063] In an embodiment of the present disclosure, when the first service provider responds to a service request of a first service, in addition to obtaining a response code for the service request of the first service, the first service provider also obtains service invocation information of a second service corresponding to the response code, and carries the response code and the service invocation information of the second service in the service response of the first service, so that the service user can directly initiate a call to the second service based on the service invocation information of the second service after receiving the service response, which saves the service user the operation of matching the response code with a business process branch, and simplifies the service invocation logic and / or service discovery process of the service user.

[0064] For example, referring to FIG. 8, the service user sends an A service request to the first service provider. When the first service provider receives the A service request, it performs a corresponding transaction process, and obtains a corresponding response code and service invocation information of the corresponding second service. Specifically, if the response code is 1, the corresponding second service is the B service, and if the response code is 2, the corresponding second service is the C service. Finally, it conveys the response code and the service invocation information of the second service corresponding to the response code to the A service response. When the service user receives the A service response, it obtains the response code and the service invocation information of the corresponding second service therein, and starts the second service based on the service invocation information of the second service. Specifically, if the A service response contains the service invocation information of the B service, it starts the B service invocation (the service provider of the B service is the same as the service provider of the A service). If the A service response contains the service invocation information of the C service, it starts the C service invocation (the service provider of the C service is different from the service provider of the A service).

[0065] In another optional embodiment of the present disclosure, the service response of the first service includes a service invocation result of at least one second service related to the first service.

[0066] Optionally, the service invocation result includes at least one of data, an address of a resource, and a response code.

[0067] Here, the service call result of the data resource specifically includes data and / or the address of the data resource. If the service response only includes the address of the data resource, the service user can obtain the corresponding data based on the address. Moreover, the data may be selectively available or not available at the service provider.

[0068] For the three service calls in the 5G user attachment process, namely location registration by AMF, download of contract data, and subscription to contract data changes, the call order is fixed and the service user / service provider is fixed, enabling flow optimization.

[0069] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call result of the second service includes the address of a contract data resource and the address of a subscription resource.

[0070] In an embodiment of the present disclosure, after receiving a location registration service request, the UDM, which is a service provider, can perform optimization on multiple interrelated business processing logics.

[0071] Specifically, the operation of the UDM after receiving the location registration service request is specifically as follows: 1. The UDM receives a location registration service request and obtains the terminal identifier (UE ID) and AMF address. 2. The UDM queries the contract data of the UE based on the UE ID, and obtains the address of the contract data resource of the UE. 3. The UDM subscribes to contract data changes for the UE and obtains the address of the subscribed resource. 4. The UDM provides the addresses of the contract data resource and subscription resource in the location registration response.

[0072] Therefore, referring to Figure 9, the AMF can obtain the addresses of the contract data resources and subscription resources from the location registration response without invoking a service to the UDM for downloading the contract data and subscribing to the contract data or initiating a service discovery process.

[0073] Of course, in another selectable embodiment, when the service request of the first service is a location registration service request, the second service may only include a contract data download service, and accordingly, the service call result of the second service only includes the address of a contract data resource; when the service request of the first service is a contract data download service request, the second service includes a contract data change subscription service, and the service call result of the second service includes the address of a subscription resource.

[0074] Please refer to FIG. 10, which is a diagram illustrating a flow of a service invocation method according to the second embodiment of the present disclosure. Step 101 in which a service request for a first service is sent from a service user to a first service provider; Step 102, a service response of the first service is received by the service user, the service response including service invocation information or a service invocation result for instructing the service user to invoke the second service of at least one second service related to the first service; and step 103, in which, if the service response of the first service includes the service invocation information, the service user initiates a second service invocation based on the service invocation information, thereby obtaining a service invocation result of the second service.

[0075] In an embodiment of the present disclosure, after a service request for a first service sent by a service user is received by the first service provider, if a second service that needs to be later invoked by the service user can be determined, the service invocation information or service invocation result of the second service can be carried in the service response of the first service, thereby optimizing the business processing logic and reducing the complexity of business processing.

[0076] Optionally, the service invocation information includes at least one of a service name of the second service, a service provider address of the second service, parameters required for service invocation of the second service, a resource address related to the second service, an operation method for a resource related to the second service, and a prerequisite for the second service.

[0077] Optionally, the service invocation result includes at least one of data, an address of a resource, and a response code.

[0078] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call result of the second service includes the address of a contract data resource and the address of a subscription resource.

[0079] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call information of the second service includes service call information for the contract data download service and service call information for the contract data change subscription service.

[0080] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service, and the service invocation information of the second service includes service invocation information of a contract data download service.

[0081] Optionally, when the service request for the first service is a contract data download service request, the second service includes a contract data change subscription service, and the service invocation information of the second service includes service invocation information of the contract data change subscription service.

[0082] The technical solutions according to the embodiments of the present disclosure correspond to the above embodiment 1, have the same inventive ideas, and can achieve the same technical effects. For details, please refer to the above embodiment 1, and the description will not be repeated here.

[0083] Referring to FIG. 11, FIG. 11 is a diagram illustrating a configuration of a network device according to a third embodiment of the present disclosure. The network device 110 is a first service provider. The network device includes: a first receiving module 111 for receiving a service request for a first service sent from a service user; a response module 112 for sending a service response of the first service to the service user. The service response of the first service includes service invocation information or a service invocation result of at least one second service related to the first service, and the service invocation information is intended to instruct the service user to invoke the second service.

[0084] In an embodiment of the present disclosure, after a service request for a first service sent by a service user is received by the first service provider, if a second service that needs to be later invoked by the service user can be determined, the service invocation information or service invocation result of the second service can be carried in the service response of the first service, thereby optimizing the business processing logic and reducing the complexity of business processing.

[0085] Optionally, the service invocation information includes at least one of a service name of the second service, a service provider address of the second service, parameters required for the service invocation of the second service (including a required service request message header and a message body), a resource address related to the second service, an operation method for a resource related to the second service, and a prerequisite for the second service.

[0086] Optionally, the service invocation result includes at least one of data, an address of a resource, and a response code.

[0087] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call result of the second service includes the address of a contract data resource and the address of a subscription resource.

[0088] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call information of the second service includes service call information for the contract data download service and service call information for the contract data change subscription service.

[0089] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service, and the service invocation information of the second service includes service invocation information of a contract data download service.

[0090] Optionally, when the service request for the first service is a contract data download service request, the second service includes a contract data change subscription service, and the service invocation information of the second service includes service invocation information of the contract data change subscription service.

[0091] The embodiment of the present disclosure is a product embodiment corresponding to the above method embodiment 1, so it will not be repeated here, and for details, please refer to the above embodiment 1.

[0092] Referring to FIG. 12, FIG. 12 is a diagram illustrating a configuration of a network device according to a fourth embodiment of the present disclosure. The network device 120 is a service user. The network device includes: a sending module 121 for sending a service request for the first service to a first service provider; a second receiving module 122 for receiving a service response of the first service, the service response including service invocation information or a service invocation result for instructing the service user to invoke the second service of at least one second service related to the first service; and a service invocation module 123 for initiating a second service invocation based on the service invocation information to obtain a service invocation result of the second service when the service response of the first service includes the service invocation information.

[0093] In an embodiment of the present disclosure, after a service request for a first service sent by a service user is received by the first service provider, if a second service that needs to be later invoked by the service user can be determined, the service invocation information or service invocation result of the second service can be carried in the service response of the first service, thereby optimizing the business processing logic and reducing the complexity of business processing.

[0094] Optionally, the service invocation information includes at least one of a service name of the second service, a service provider address of the second service, parameters required for the service invocation of the second service (including a required service request message header and a message body), a resource address related to the second service, an operation method for a resource related to the second service, and a prerequisite for the second service.

[0095] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call result of the second service includes the address of a contract data resource and the address of a subscription resource.

[0096] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call information of the second service includes service call information for the contract data download service and service call information for the contract data change subscription service.

[0097] The embodiment of the present disclosure is a product embodiment corresponding to the above method embodiment 2, so it will not be repeated here, and for details, please refer to the above embodiment 2.

[0098] Referring to FIG. 13, FIG. 13 is a diagram illustrating a configuration of a network device according to a fifth embodiment of the present disclosure. The network device 130 is a first service provider and includes a transceiver 131 and a processor 132 . The transceiver 131 is receiving a service request for a first service sent from a service user; Furthermore, a service response of the first service is transmitted to the service user. The service response of the first service includes service invocation information or a service invocation result of at least one second service related to the first service, and the service invocation information is intended to instruct the service user to invoke the second service.

[0099] In an embodiment of the present disclosure, after a service request for a first service sent by a service user is received by the first service provider, if a second service that needs to be later invoked by the service user can be determined, the service invocation information or service invocation result of the second service can be carried in the service response of the first service, thereby optimizing the business processing logic and reducing the complexity of business processing.

[0100] Optionally, the service invocation information includes at least one of a service name of the second service, a service provider address of the second service, parameters required for invoking the second service (including a required service request message header and a message body), a resource address related to the second service, an operation method for a resource related to the second service, and a prerequisite for the second service.

[0101] Optionally, the service invocation result includes at least one of data, an address of a resource, and a response code.

[0102] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call result of the second service includes the address of a contract data resource and the address of a subscription resource.

[0103] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call information of the second service includes service call information for the contract data download service and service call information for the contract data change subscription service.

[0104] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service, and the service invocation information of the second service includes service invocation information of a contract data download service.

[0105] Optionally, when the service request for the first service is a contract data download service request, the second service includes a contract data change subscription service, and the service invocation information of the second service includes service invocation information of the contract data change subscription service.

[0106] The embodiment of the present disclosure is a product embodiment corresponding to the above method embodiment 1, so it will not be repeated here, and for details, please refer to the above embodiment 1.

[0107] Referring to FIG. 14, FIG. 14 is a diagram illustrating a configuration of a network device according to a sixth embodiment of the present disclosure. The network device 140 is a service user and includes a transceiver 141 and a processor 142 . The transceiver 141 is Sending a service request for the first service to a first service provider; Further, a service response of the first service is received, the service response including service invocation information or a service invocation result for instructing the service user to invoke the second service of at least one second service related to the first service; Furthermore, if the service response of the first service includes the service invocation information, a second service invocation is initiated based on the service invocation information to obtain a service invocation result of the second service.

[0108] In an embodiment of the present disclosure, after a service request for a first service sent by a service user is received by the first service provider, if a second service that needs to be later invoked by the service user can be determined, the service invocation information or service invocation result of the second service can be carried in the service response of the first service, thereby optimizing the business processing logic and reducing the complexity of business processing.

[0109] Optionally, the service invocation information includes at least one of a service name of the second service, a service provider address of the second service, parameters required for invoking the second service (including a required service request message header and a message body), a resource address related to the second service, an operation method for a resource related to the second service, and a prerequisite for the second service.

[0110] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call result of the second service includes the address of a contract data resource and the address of a subscription resource.

[0111] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call information of the second service includes service call information for the contract data download service and service call information for the contract data change subscription service.

[0112] The embodiment of the present disclosure is a product embodiment corresponding to the above method embodiment 2, so it will not be repeated here, and for details, please refer to the above embodiment 2.

[0113] Referring to FIG. 15, FIG. 15 is a diagram illustrating a configuration of a network device according to a seventh embodiment of the present disclosure. The network device 150 is a first service provider and includes a processor 151 , a memory 152 , and a computer program stored in the memory 152 and executable by the processor 151 . When the computer program is executed by the processor 151, A step of receiving a service request for a first service sent from a service user by a first service provider; A step of transmitting a service response of the first service from the first service provider to the service user is realized. The service response of the first service includes service invocation information or a service invocation result of at least one second service related to the first service, and the service invocation information is intended to instruct the service user to invoke the second service.

[0114] In an embodiment of the present disclosure, after a service request for a first service sent by a service user is received by the first service provider, if a second service that needs to be later invoked by the service user can be determined, the service invocation information or service invocation result of the second service can be carried in the service response of the first service, thereby optimizing the business processing logic and reducing the complexity of business processing.

[0115] Optionally, the service invocation information includes at least one of a service name of the second service, a service provider address of the second service, parameters required for invoking the second service (including a required service request message header and a message body), a resource address related to the second service, an operation method for a resource related to the second service, and a prerequisite for the second service.

[0116] Optionally, the service invocation result includes at least one of data, an address of a resource, and a response code.

[0117] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call result of the second service includes the address of a contract data resource and the address of a subscription resource.

[0118] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call information of the second service includes service call information for the contract data download service and service call information for the contract data change subscription service.

[0119] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service, and the service invocation information of the second service includes service invocation information of a contract data download service.

[0120] Optionally, when the service request for the first service is a contract data download service request, the second service includes a contract data change subscription service, and the service invocation information of the second service includes service invocation information of the contract data change subscription service.

[0121] The specific operation process of the embodiment of the present disclosure is the same as that of the above method embodiment 1, so it will not be described repeatedly here, and for details, please refer to the description of the method steps in the above embodiment 1.

[0122] Eighth embodiment Referring to FIG. 16, FIG. 16 is a diagram illustrating a configuration of a network device according to an eighth embodiment of the present disclosure. The network device 160 is a service user and includes a processor 161 , a memory 162 , and a computer program stored in the memory 162 and executable by the processor 161 . When the computer program is executed by the processor 161, a service request for a first service being sent from a service user to a first service provider; receiving, by the service user, a service response of the first service, the service response including service invocation information or a service invocation result for instructing the service user to invoke at least one second service related to the first service; If the service response of the first service includes the service invocation information, a step is realized in which the service user initiates a second service invocation based on the service invocation information, thereby obtaining a service invocation result of the second service.

[0123] In an embodiment of the present disclosure, after a service request for a first service sent by a service user is received by the first service provider, if a second service that needs to be later invoked by the service user can be determined, the service invocation information or service invocation result of the second service can be carried in the service response of the first service, thereby optimizing the business processing logic and reducing the complexity of business processing.

[0124] Optionally, the service invocation information includes at least one of a service name of the second service, a service provider address of the second service, parameters required for invoking the second service (including a required service request message header and a message body), a resource address related to the second service, an operation method for a resource related to the second service, and a prerequisite for the second service.

[0125] Optionally, when the service request of the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call result of the second service includes the address of a contract data resource and the address of a subscription resource.

[0126] Optionally, when the service request for the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service, and the service call information of the second service includes service call information for the contract data download service and service call information for the contract data change subscription service.

[0127] The specific operation process of the embodiment of the present disclosure is the same as that of the above method embodiment 2, so it will not be described repeatedly here, and for details, please refer to the description of the method steps in the above method embodiment 2.

[0128] A ninth embodiment of the present disclosure provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the computer program realizes the steps of the service invocation method of any one of the above-mentioned first and second embodiments. For details, please refer to the description of the steps of the method in the above corresponding embodiment.

[0129] The computer readable storage medium includes permanent or non-permanent, removable or non-removable media, and may be implemented by any method or technology to store information. Information may be computer readable instructions, data structures, program modules, or other data. Examples of computer storage media capable of storing information accessible by a computing device include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), electrically erasable read only memory (EEPROM), flash memory storage media or other internal storage technologies, compact disc read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage media, magnetic cassette magnetic tape, magnetic disk or other magnetic storage device or other non-transmission media.

[0130] It will be understood that the embodiments described in the embodiments of the present disclosure can be realized in hardware, software, firmware, middleware, microcode, or a combination thereof. In the case of a hardware realization, the processing unit may be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in the embodiments of the present disclosure, or a combination thereof.

[0131] In the case of a software implementation, the techniques described in the embodiments of the present disclosure may be implemented by modules (e.g., processes, functions, etc.) that perform the functions described in the embodiments of the present disclosure. The software code is stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.

[0132] The above are the selectable embodiments of the present disclosure. Those skilled in the art can make various improvements and modifications without departing from the principles described in the present disclosure. These improvements and modifications also fall within the scope of protection of the present disclosure.

Claims

1. A service invocation method, comprising: A service request for a first service transmitted from a service user NF is received by a first service provider NF; a step of transmitting a service response of the first service from the first service provider NF to the service user NF; The service response of the first service includes service invocation information or a service invocation result of at least one second service related to the first service, the service invocation information being for instructing the service user NF to invoke the second service; The first service provider NF and the service user NF are corresponding network functions NF in a 5G core network, The service call information is At least one of a service name of the second service, a service provider address of the second service, a parameter required for invoking the second service, a resource address related to the second service, an operation method for a resource related to the second service, and a prerequisite for the second service is included, The first service provider NF includes a UDM, and the service user NF includes an AMF; The service invoking method, wherein the first service includes a location registration service or a contract data download service, and the second service includes at least one of a contract data download service and a contract data change subscription service.

2. The method of claim 1 , wherein the service invocation result includes at least one of data, an address of a resource, and a response code.

3. When the service request for the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The method of claim 1 , wherein the service call information of the second service includes service call information of a contract data download service and service call information of a contract data change subscription service.

4. When the service request for the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The method of claim 1 , wherein the service invocation result of the second service includes an address of a contract data resource and an address of a subscription resource.

5. When the service request for the first service is a location registration service request, the second service includes a contract data download service; The method of claim 1 , wherein the service call information of the second service includes service call information of a contract data download service.

6. When the service request of the first service is a contract data download service request, the second service includes a contract data change subscription service; The method of claim 1 , wherein the service call information of the second service includes service call information of a contract data change subscription service.

7. A service invocation method, comprising: a service request for a first service being sent from a service consumer NF to a first service provider NF; A service response of the first service is received by the service user NF, the service response including service invocation information or a service invocation result for instructing the service user NF to invoke at least one second service related to the first service; and if the service response of the first service includes the service invocation information, the service user NF initiates a second service invocation based on the service invocation information, thereby obtaining a service invocation result of the second service; The first service provider NF and the service user NF are corresponding network functions NF in a 5G core network, The service call information is At least one of a service name of the second service, a service provider address of the second service, a parameter required for invoking the second service, a resource address related to the second service, an operation method for a resource related to the second service, and a prerequisite for the second service is included, The first service provider NF includes a UDM, and the service user NF includes an AMF; The service invoking method, wherein the first service includes a location registration service or a contract data download service, and the second service includes at least one of a contract data download service and a contract data change subscription service.

8. When the service request for the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The method of claim 7 , wherein the service invocation result of the second service includes an address of a contract data resource and an address of a subscription resource.

9. When the service request for the first service is a location registration service request, the second service includes a contract data download service and a contract data change subscription service; The method of claim 7 , wherein the service call information of the second service includes service call information of a contract data download service and service call information of a contract data change subscription service.

10. In a network device that is a first service provider NF, Memory, A processor; and a computer program stored in the memory and executable by the processor, the computer program implementing the steps of the service invocation method according to any one of claims 1 to 6 when executed by the processor.

11. In a network device which is a service user NF, Memory, A processor; and a computer program stored in the memory and executable by the processor, the computer program implementing the steps of the service invocation method according to any one of claims 7 to 9 when executed by the processor.

12. A computer-readable storage medium storing a computer program which, when executed by a processor, causes the steps of the service invocation method according to any one of claims 1 to 6 to be realized.

13. A computer-readable storage medium storing a computer program which, when executed by a processor, causes the steps of the service invocation method according to any one of claims 7 to 9 to be realized.

Images