Communication method and communication device

Abstract

A communication method and a communication device, the method comprising: a second network element can obtain a service call logic of a first service from a first network element or a third network element, execute the first service according to the service call logic of the first service, and provide the first service for a user. Wherein the service calling logic of the first service comprises a network service called when the first service is executed and a calling rule of the network service. According to the technical scheme of the invention, the calling logic of the network service is separated from the execution logic of the network service, the operation cost is reduced, and flexible and portable network deployment and management can be provided.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art

[0002] The fifth generation (5G) mobile communication network architecture is designed based on independent network elements (or network functions (NF)). When providing network services for a certain business, it is necessary to define the interaction process between multiple network elements. In addition, when providing network services to the outside world, all network elements need to be deployed in advance to respond to different business requests.

[0003] For example, when the session management function (SMF) establishes a session for a terminal device (e.g., user equipment (UE)), it needs to first obtain user subscription data from the unified data management function (UDM), and then obtain session policies from the policy control function (PCF), and control the user plane function (UPF) to forward user plane data packets for the UE. It can be seen that when providing services, the execution logic of the service process is implemented within the NF based on standardized definitions, and there is a strong coupling between different NFs. The network architecture logic is complex, which is not conducive to flexible and lightweight network deployment and management. Summary of the invention

[0004] The present application provides a communication method and a communication device, which can provide flexible and convenient network deployment and management.

[0005] In a first aspect, a communication method is provided, which can be executed by a first network element, or can also be executed by a chip or circuit of the first network element, which is not limited in the present application. For ease of description, the following description is given by taking the execution by the first network element as an example.

[0006] The method includes: receiving a request message for requesting a first network element to configure a service calling logic of a first service, wherein the service calling logic of the first service includes a network service called when executing the first service and a calling rule of the network service; and sending the service calling logic of the first service.

[0007] Exemplarily, the first network element may be a service management function.

[0008] According to the above scheme, the first network element can configure the service call logic of the first service for other functions or network elements (for example, the second network element, the third network element or the fourth network element) according to the request message. It should be understood that the first network element supports the orchestration of the network service called when executing the first service, and supports the configuration of the service call logic of the first service to other functions or network elements, that is, the service call logic of the first service provided by the mobile network can be flexibly configured and managed, or the mobile network can be used as a cloud service provision platform, which can provide the first service on demand and is easy to open to users.

[0009] In certain implementations of the first aspect, the method further includes: sending configuration information to a fourth network element, the configuration information including information of the first service and information of a network function, the network function supports calling a network service, and the fourth network element supports discovery of the network function.

[0010] Based on the above solution, the first network element performs network orchestration and service call logic design and management for the execution of the first service, and can configure the corresponding service call logic, service discovery, etc. for use by other nodes (for example, the fourth network element).

[0011] In certain implementations of the first aspect, a configuration update message is sent, where the configuration update message is used to update subscription information and / or policy information associated with the first service.

[0012] Based on the above solution, during the execution of the first service, the contract information and / or policy information associated with the first service may change, and sending an update message facilitates timely updating of the contract information and / or policy information associated with the first service, that is, by synchronizing the contract information and / or policy information associated with the first service, the network can authorize the user's behavior through the contract, and formulate rules for the services provided by the network through the policy, so as to achieve management and control of the first service.

[0013] In a second aspect, a communication method is provided, which may be executed by a second network element, or may be executed by a chip or circuit of the second network element, which is not limited in the present application. For ease of description, the following description is given by taking the execution by the second network element as an example.

[0014] The method comprises: obtaining a service calling logic of a first business, the service calling logic of the first business comprising a network service called when executing the first business and a calling rule of the network service; and executing the first business according to the service calling logic of the first business.

[0015] Exemplarily, the second network element may be a gateway or an execution function, and supporting the first service may be understood as: the second network element may initiate a service call request to the network function according to the service call logic of the first service until the execution of the first service is completed.

[0016] According to the solution provided in the present application, after obtaining the service call logic of the first service, the second network element can determine the network service called when executing the first service and the calling rules of the network service, and execute the first service on demand, thereby improving network resource utilization, reducing network operation and maintenance costs, and realizing flexible deployment and management of network services.

[0017] In certain implementations of the second aspect, before obtaining the service call logic of the first service, the method also includes: receiving a first request message, the first request message is used to request configuration of the service call logic of the first service; sending a second request message to the first network element, the second request message is used to request the first network element to configure the service call logic of the first service, and the first network element supports the management of the first service.

[0018] Exemplarily, the first network element may be a service management function.

[0019] Based on the above scheme, the second network element can forward the request message from the service requester to the first network element, requesting the first network element to configure the service call logic of the first service. The service call logic of the first service can be flexibly configured, so that the mobile network can be used as a cloud service provider platform, which is easy to open to users.

[0020] In certain implementations of the second aspect, executing the first business according to the service call logic of the first business includes: receiving a first business request message from a service requester, the first business request message being used to request execution of the first business; and executing the first business according to the first business request message and the service call logic of the first business.

[0021] Based on the above solution, the second network element can execute the first service according to the service call logic of the first service as needed based on the first service request message from the service requester, thereby reducing network operation costs.

[0022] In certain implementations of the second aspect, executing the first business according to the service call logic of the first business includes: receiving a second business request message, the second business request message is used to request execution of the first business, the second business request message includes an identifier of the first business; executing the first business according to the second business request message and the service call logic of the first business.

[0023] Exemplarily, when the second network element is a gateway, the second network element receives the service request message from the execution function. It should be understood that the service request message can be the service request message #a received by the execution function from the service requester, or it can be the service request message #b obtained after formatting the service request message #a, for example. The present application does not limit this.

[0024] In certain implementations of the second aspect, executing the first business according to the service call logic of the first business includes: sending a service call request message to a network function according to the service call logic of the first business, the service call request message is used to request the network function to call a network service, and the service call request message includes an identifier of the first business.

[0025] Based on the above solution, the calling logic of the network service in the mobile network is separated from the network service execution logic, that is, the second network element can initiate a service call request of the first service to the network function according to the service call logic of the first service. In other words, the network function (service) participating in the execution of the first service no longer needs to obtain the complete service call logic of the first service, but only needs to provide network services to the outside world, and the calling logic of the first service is processed by the second network element. As a result, the implementation method of the network function is simplified, the operating cost is lower, and the network service can be called on demand.

[0026] In certain implementations of the second aspect, the service invocation request message further includes first indication information, where the first indication information is used to indicate a current execution stage or step of the first service.

[0027] Based on the above scheme, the second network element can indicate the current execution stage or step of the first service to the network function, so that the network function can determine the next one or more network services to call, that is, it provides a way to separate the execution of the first service from the calling of the network service, simplifies the implementation of the network function, improves the utilization rate of network resources, and reduces the cost of network operation and maintenance.

[0028] In certain implementations of the second aspect, a service call response message is received from a network function, where the service call response message includes a feedback result, where the feedback result is used to indicate that the network service call is successful.

[0029] In certain implementations of the second aspect, the service invocation response message further includes second indication information, where the second indication information is used to indicate a current execution stage or step of the first service.

[0030] Based on the above scheme, after determining the current execution stage or step of the first service, the second network element can determine the next one or more network services to call, improve network resource utilization, reduce network operation and maintenance costs, and realize flexible deployment and management of network services.

[0031] In certain implementations of the second aspect, before sending a service call request message to a network function according to the service call logic of the first service, the method also includes: sending a query message to a fourth network element, the query message being used to obtain information about the network function, the query message including an identifier of the first service; receiving information about the network function from the fourth network element; and the fourth network element supporting discovery of the network function.

[0032] In certain implementations of the second aspect, obtaining the service call logic of the first service includes: sending a third request message to a third network element, the third request message is used to obtain the service call logic of the first service, and the third network element supports the first service; receiving the service call logic of the first service from the third network element.

[0033] In some implementations of the second aspect, obtaining the service calling logic of the first service includes: receiving the service calling logic of the first service from a first network element, where the first network element supports management of the first service.

[0034] Based on the above solution, the second network element can obtain the service calling logic of the first service from the first network element or the third network element, and the mobile network can provide the service calling logic of the first service to the outside through various channels to achieve flexible configuration and management.

[0035] In some implementations of the second aspect, before receiving the service calling logic of the first service from the first network element, the method further includes: sending a fourth request message to the first network element, where the fourth request message is used to obtain the service calling logic of the first service.

[0036] Based on the above scheme, the second network element can send a request message to the first network element to obtain the service call logic of the first service, and then the first network element can feedback the service call logic of the first service to the second network element based on the request message, that is, the service call logic of the first service provided by the mobile network can be flexibly configured and managed, or in other words, the mobile network can be used as a cloud service provision platform, which can provide the first service on demand and is easy to open to users.

[0037] The beneficial effects of the above-mentioned second aspect and some implementation methods of the second aspect can be referred to the relevant description of the first aspect, which will not be repeated here.

[0038] In a third aspect, a communication method is provided, which can be executed by a third network element, or can also be executed by a chip or circuit of the third network element, which is not limited in this application. For ease of description, the following description is given by taking the execution by the third network element as an example.

[0039] The method comprises: receiving a first request message, the first request message is used to obtain the service calling logic of the first business, the first request message comprises the identifier of the first business; and sending the service calling logic of the first business.

[0040] Exemplarily, the third network element may be a service control function.

[0041] According to the above scheme, after receiving the first request message, the third network element sends the service call logic of the first service, so that the second network element can execute the first service on demand, improve network resource utilization, reduce network operation and maintenance costs, and realize flexible deployment and management of network services.

[0042] In certain implementations of the third aspect, before sending the service call logic of the first service, the method further includes: receiving the service call logic of the first service from a first network element, the first network element supporting management of the first service.

[0043] In certain implementations of the third aspect, before receiving the service calling logic of the first service from the first network element, the method further includes: sending a request message to the first network element, where the request message is used to obtain the service calling logic of the first service.

[0044] The beneficial effects of the third aspect and certain implementation methods of the third aspect can be referred to the relevant description of the first aspect, which will not be repeated here.

[0045] In a fourth aspect, a communication method is provided, which can be executed by a service requester, or can also be executed by a chip or circuit of the service requester, which is not limited in this application. For ease of description, the following description is taken as an example of execution by the service requester.

[0046] The method includes: sending a service request message to a second network element, the service request message is used to request execution of a first service, and the service request message includes an identifier of the first service; receiving a service response message from the second network element, the service response message is used to indicate an execution result of the first service.

[0047] In certain implementations of the fourth aspect, before sending a service request message to the second network element, the method also includes: sending a first request message to the second network element, the first request message being used to request configuration of the service call logic of the first service; receiving a first response message from the second network element, the first response message being used to indicate a configuration result of the service call logic of the first service.

[0048] In certain implementations of the fourth aspect, a configuration update message is received, where the configuration update message is used to update subscription information and / or policy information associated with the first service.

[0049] The beneficial effects of the fourth aspect and certain implementation methods of the fourth aspect can be referred to the relevant description of the first aspect, and will not be repeated here.

[0050] In the fifth aspect, a communication device is provided, which can be used for the first network element of the first aspect, and may include modules or units corresponding to the methods / operations / steps / actions described in the first aspect. The modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0051] In certain implementations of the fifth aspect, the device includes: a transceiver unit, used to receive a request message, the request message is used to request the first network element to configure the service call logic of the first service, the service call logic of the first service includes the network service called when executing the first service and the calling rules of the network service; the transceiver unit is also used to send the service call logic of the first service.

[0052] The transceiver unit may perform the reception and transmission processing in the aforementioned first aspect and possible implementations thereof, and the processing unit may perform other processing except reception and transmission in the aforementioned first aspect and possible implementations thereof.

[0053] In the sixth aspect, a communication device is provided, which can be used for the second network element of the second aspect, and may include modules or units corresponding to the methods / operations / steps / actions described in the second aspect. The modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0054] In certain implementations of the sixth aspect, the device includes: a processing unit, used to obtain a service call logic for a first business, the service call logic for the first business including a network service called when executing the first business and a calling rule for the network service; the processing unit, also used to execute the first business according to the service call logic for the first business.

[0055] The transceiver unit may perform the reception and transmission processing in the aforementioned second aspect and possible implementations thereof, and the processing unit may perform other processing except reception and transmission in the aforementioned second aspect and possible implementations thereof.

[0056] In the seventh aspect, a communication device is provided, which can be used for the third network element of the third aspect, and may include modules or units corresponding to the methods / operations / steps / actions described in the third aspect. The modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0057] In certain implementations of the seventh aspect, the device includes: a transceiver unit, used to receive a first request message, the first request message is used to obtain the service call logic of a first service, the first request message includes an identifier of the first service; the transceiver unit is also used to send the service call logic of the first service.

[0058] The transceiver unit may perform the reception and transmission processing in the aforementioned third aspect and possible implementations thereof, and the processing unit may perform other processing except reception and transmission in the aforementioned third aspect and possible implementations thereof.

[0059] In the eighth aspect, a communication device is provided, which can be used for the service requester of the fourth aspect, and may include modules or units corresponding to the methods / operations / steps / actions described in the fourth aspect. The modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0060] In certain implementations of the eighth aspect, the device includes: a transceiver unit, used to send a service request message to a second network element, the service request message is used to request execution of a first service, and the service request message includes an identifier of the first service; the transceiver unit is also used to receive a service response message from the second network element, the service response message is used to indicate an execution result of the first service.

[0061] The transceiver unit may perform the receiving and sending processing in the aforementioned fourth aspect and possible implementations thereof, and the processing unit may perform other processing except receiving and sending in the aforementioned fourth aspect and possible implementations thereof.

[0062] In a ninth aspect, a communication device is provided, comprising at least one processor, wherein the at least one processor is used to execute a computer program or instruction, and / or, through a logic circuit, so that the communication device performs a method as in any aspect of the first to fourth aspects, or any possible implementation of these aspects.

[0063] In some implementations, at least one processor is coupled to at least one memory, and the at least one memory stores the above-mentioned computer program or instruction. Optionally, the communication device also includes the above-mentioned at least one memory. Optionally, at least one processor is integrated with at least one memory.

[0064] In the tenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive information and / or data to be processed, and send the information and / or data to be processed to the processor, and the processor is used to process the information and / or data to be processed, so that a communication device in which the chip is installed executes a method as in any aspect of the first aspect or the second aspect, or any possible implementation of these aspects.

[0065] In the eleventh aspect, a computer-readable storage medium is provided, in which computer instructions are stored. When the computer instructions are executed on a computer, the method in any aspect from the first to the third aspect, or any possible implementation of these aspects, is implemented.

[0066] In a twelfth aspect, a computer program product is provided, the computer program product comprising a computer program code, and when the computer program code is run on a computer, the method in any aspect from the first to the fourth aspect, or any possible implementation of these aspects, is implemented.

[0067] In a thirteenth aspect, a communication system is provided, comprising a communication device as described in any one or more of aspects from the fifth to the seventh aspects.

[0068] Optionally, the communication system may also include the communication device described in the eighth aspect.

[0069] Among them, the technical effects of the technical solutions of the fifth to twelfth aspects can refer to the description of the corresponding technical effects of the first to fourth aspects and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] Figure 1 is a schematic diagram of a network architecture applicable to an embodiment of the present application;

[0071] Figure 2 is a schematic diagram of an interaction flow of a communication method 200 provided in an embodiment of the present application;

[0072] Figure 3 is a schematic diagram of an interaction flow of a communication method 300 provided in an embodiment of the present application;

[0073] Figure 4 is a schematic diagram of an interaction flow of a communication method 400 provided in an embodiment of the present application;

[0074] Figure 5 is a schematic diagram of an interaction flow of a communication method 500 provided in an embodiment of the present application;

[0075] Figure 6 is a schematic diagram of a communication device 600 provided in an embodiment of the present application;

[0076] Figure 7 It is a schematic diagram of a communication device 700 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0077] The technical solution provided in the present application can be applied to various communication systems, for example: a fourth generation (4G) communication system, such as a long term evolution (LTE) communication system, a 5G communication system, such as a 5G new radio (NR), a 5G core network (5G Core, 5GC), or various communication systems evolved after 5G, such as a sixth generation (6G) communication system, etc. The technical solution provided in the present application can also be applied to device to device (D2D) communication, vehicle to everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication system or other communication systems.

[0078] In the communication system, the part operated by the operator can be called a public land mobile network (PLMN), or an operator network, etc. PLMN is a network established and operated for the purpose of providing land mobile communication services to the public. It is mainly a public network where mobile network operators (MNOs) provide mobile broadband access services to users. The PLMN described in the embodiments of the present application may specifically be a network that meets the requirements of the 3GPP standard, referred to as a 3GPP network. 3GPP networks generally include but are not limited to 5G mobile communication networks, 4G mobile communication networks, and other communication systems that have evolved after 5G, such as 6G mobile communication networks.

[0079] For ease of description, the embodiments of the present application will be described using PLMN or 5G network as an example.

[0080] Figure 1 1 is a schematic diagram of a network architecture 100 applicable to an embodiment of the present application, taking the 5G network architecture based on service-based architecture (SBA) in a non-roaming scenario defined in the 3GPP standardization process as an example. Figure 1As shown, the network architecture may include a terminal device part, a data network (DN) part and an operator network PLMN part. The operator network PLMN part may include but is not limited to a (radio) access network ((R)AN) 120 and a core network (CN) part.

[0081] The functions of each network element are briefly described below.

[0082] The terminal device part may include UE 110. The UE 110 in the present application is a device with wireless transceiver function, which can communicate with one or more core network (CN) devices via the access network device (or also referred to as access device) in the (radio) access network (R) AN 120. The UE 110 may also be referred to as user equipment (UE), access terminal, terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, user agent or user device, etc. The terminal device 110 may also be a device for providing voice and / or data connectivity to the user, or may also be an Internet of Things device. For example, UE 110 includes a handheld device with wireless communication function, a computing device or other device connected to a wireless modem, a vehicle-mounted device, a wearable device, a drone device or an Internet of Things, a terminal in the Internet of Vehicles, a 5G network and any form of terminal in the future network, a relay user device or a terminal in the future evolved 6G network, etc. Currently, UE 110 can be: a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device (such as a smart watch, a smart bracelet, a pedometer, a smart glasses, etc.), a vehicle-mounted device (such as a car, a bicycle, an electric car, an airplane, a ship, a train, a high-speed rail, etc.), a satellite terminal, a virtual reality (VR) device, an augmented reality (AR) device, a smart point of sale (POS) machine, a customer-premises equipment (CPE), a wireless terminal in industrial control, a smart home device (such as a refrigerator, a TV, an air conditioner, an electric meter, etc.), an intelligent robot, a robotic arm, a workshop equipment, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, or a wireless terminal in a smart home, a flying device (such as an intelligent robot, a hot air balloon, a drone, an airplane), etc. UE 110 may also be a vehicle device, such as a vehicle device, a vehicle-mounted module, a vehicle-mounted chip, an on-board unit (OBU) or a telematics box (T-BOX), etc. UE 110 may also be other devices with terminal functions, for example, UE 110 may also be a device that functions as a terminal in D2D communication. The embodiments of the present application do not limit the type or category of terminal devices.UE 110 may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; may also be deployed on water (such as a ship); and may also be deployed in the air (such as an airplane, a balloon, a satellite, etc.).

[0083] (R)AN 120 may include one or more access network elements or access network devices (also referred to as network devices), that is, the network device is a node in (R)AN 120, and may also be referred to as a RAN node (or device). The interface between the access network device and the terminal device may be a Uu interface (or referred to as an air interface, that is, the message exchanged between the access network device and the terminal device may be referred to as an air interface message). Of course, in future communications, the interface name may remain unchanged or may be replaced by other names, and this application is not limited thereto. (R)AN 120 is a device that provides wireless communication functions for UE 110, and may connect the terminal device to a node or device of a wireless network. The network architecture 100 may include one or more (R)AN 120, and multiple (R)AN 120 may be nodes of the same type or nodes of different types. (R)AN 120 may be regarded as a subnetwork of an operator network, and is an implementation system between a service node in an operator network and UE 110. For example, UE 110 may connect to a service node of an operator network through (R)AN 120 to obtain services provided by the service node.

[0084] In one possible scenario, the (R)AN 120 includes, but is not limited to, a next generation node base station (gNB) in a 5G system, an evolved Node B (eNode B) in long term evolution (LTE), a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved node B, or home node B, HNB), a base band unit (BBU), a transmission point (TRP), a transmitting point (TP), a small base station device, a mobile switching center, or a next generation base station in a 6G mobile communication system, a base station in a future mobile communication system, an access point (AP) in a satellite or WiFi system, an integrated access and backhaul (IAB) node, a mobile switching center non-terrestrial communication network (non-terrestrial) (R)AN 120 is a network device in a (Network-to-Network (NTN)) communication system, that is, it can be deployed on a high-altitude platform or a satellite, in which case the satellite can support the functions of (R)AN 120. In addition, (R)AN 120 can also be deployed on land, such as outdoors; or, it can also be deployed on the water, such as a ship. (R)AN 120 can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a CRAN scenario. (R)AN 120 can also be a device that acts as a base station in device-to-device (D2D) communication, Internet of Vehicles communication, drone communication, and machine communication. Optionally, the network device can also be a server, a wearable device, a vehicle or a vehicle-mounted device, etc. For example, the access network device in the vehicle to everything (V2X) technology can be a road side unit (RSU).

[0085] In another possible scenario, multiple (R)AN 120s collaborate to assist the terminal in achieving wireless access, and different (R)AN 120s respectively implement part of the functions of the base station. For example, the (R)AN 120 may be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU may be separately configured, or may be included in the same network element, such as a baseband unit (BBU). The RU may be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). It is understandable that the (R)AN 120 may be a CU node, a DU node, or a device including a CU node and a DU node. In addition, the CU may be classified as a network device in the access network RAN, or the CU may be classified as a network device in the core network CN, which is not limited here.

[0086] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, CU, CU-CP, CU-UP, DU and RU are described as examples in this application. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0087] The CN part may include but is not limited to the following network functions (NF): user plane function (UPF) 130, network exposure function (NEF) 131, network function repository function (NRF) 132, policy control function (PCF) 133, unified data management function (UDM) 134, application function (AF) 135, authentication server function (AUSF) 137, access and mobility management function (AMF) 138, session management function (SMF) 139.

[0088] The data network DN 140, also referred to as a packet data network (PDN), is usually a network located outside the operator's network, such as a third-party network.

[0089] The following is a brief description of the NF functions included in CN.

[0090] 1. UPF 130 is a user plane function provided by the operator and is the user plane function for the operator network to communicate with DN 140. UPF 130 network functions include data packet routing and transmission, data packet detection, service usage reporting, quality of service (QoS) processing, uplink data packet detection, downlink data packet storage and other user plane related functions.

[0091] 2. NEF 131 is a control plane function provided by the operator, which mainly enables third parties to use the services provided by the network, supports the network to open its capabilities, event and data analysis, provide PLMN security configuration information from external applications, and convert interactive information inside and outside the PLMN.

[0092] 3. NRF 132 is a control plane function provided by the operator and can be used to maintain real-time information of network functions and services in the network.

[0093] 4. PCF 133 is a control plane function provided by the operator, which mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network function, and is responsible for obtaining user subscription information related to policy decisions. Exemplarily, PCF 133 can be divided into two PCFs with different functions, namely UE-PCF and SM-PCF.

[0094] 5. UDM 134 is a control plane function provided by the operator, which is responsible for storing information such as subscriber permanent identifier (SUPI), generic public subscriber identifier (GPSI), and credentials of subscribers in the operator network. SUPI will be encrypted during transmission, and the encrypted SUPI is called a hidden user subscription identifier (SUCI). The information stored by the UDM network function 134 can be used for authentication and authorization of the terminal device 110 to access the operator network. Among them, the subscribers of the above-mentioned operator network can specifically be users who use the services provided by the operator network, such as users who use China Telecom's mobile phone core card (subscriber identity module, SIM) card, or users who use China Mobile's mobile phone core card. The credentials of the above-mentioned subscribers can be a small file storing long-term keys stored in the mobile phone core card or information related to the encryption of the mobile phone core card, which is used for authentication and / or authorization. It should be noted that permanent identifiers, credentials, security contexts, authentication data, and tokens are equivalent to information related to verification / authentication and authorization. In the embodiment of the present application, no distinction or restriction is made for the convenience of description.

[0095] 6. AF 135 is a control plane function provided by the operator. It mainly provides corresponding services by interacting with other NFs in the PLMN, such as providing roaming UE with access network selection information, guiding the routing of data flows, and accessing NEF131.

[0096] 7. AUSF 137 is a control plane function provided by the operator, and is usually used for primary authentication, i.e., authentication between the terminal device 110 (subscriber) and the operator network.

[0097] 8. AMF 138 is a control plane network function provided by the operator network, responsible for access control and mobility management of the terminal device 110 accessing the operator network, such as mobility status management, allocation of user temporary identity, authentication and authorization of users, etc.

[0098] 9. SMF 139 is a control plane network function provided by the operator network, responsible for managing the protocol data unit (PDU) session of the terminal device 110 (including the establishment, modification and release of the session), and is used for the selection and reselection of the user plane function network element, the allocation of the Internet protocol (IP) address of the terminal device, and the quality of service (QoS) control. Among them, the PDU session is a channel for transmitting PDU, and the terminal device transmits PDU to and from the DN 140 through the PDU session. The PDU session is established, maintained and deleted by the SMF network function 139. The SMF network function 139 includes session management (such as session establishment, modification and release, including tunnel maintenance between the user plane function UPF 130 and (R)AN 120), selection and control of the UPF network function 130, service and session continuity (SSC) mode selection, roaming and other session-related functions.

[0099] It should be understood that the above network element or NF can be a physical entity in a hardware device, or a software instance running on dedicated hardware, or a virtualized function instantiated on a shared platform (e.g., a cloud platform). In short, an NF can be implemented by hardware or by software. In addition, the hardware (or software) that implements all the functions of an NF can be one or more.

[0100] It should be understood that Figure 1 The AMF, SMF, UPF, NEF, AUSF, NRF, PCF, UDM, etc. shown in the figure can be understood as network elements used to implement different functions in the core network. These network elements can be combined into network slices as needed. They can be independent devices or integrated in the same device to implement different functions. This application does not limit the specific form of the above network elements.

[0101] It should also be understood that the above naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation to this application. This application does not exclude the possibility of using other naming in 5G networks and other future networks. For example, in a 6G network, some or all of the above network elements may use the terminology in 5G, or may use other names.

[0102] It should also be understood that Figure 1Where Nnef, Nnrf, Npcf, Nudm, Nausf, Namf, Nsmf, Naf, N1, N2, N3, N4, N6, and N9 are interface serial numbers. For example, the meaning of the above interface serial numbers can be found in the meaning defined in the 3GPP standard protocol, and this application does not limit the meaning of the above interface serial numbers. In addition, Figure 1 The interface name between the various network functions is only an example. In a specific implementation, the interface name of the system architecture may also be other names, which is not limited in this application.

[0103] The current mobile communication network architecture is designed based on independent network elements (or NFs). When providing services, the execution logic of the service process is implemented within the NF based on standardized definitions, and there is strong coupling between different NFs. The network architecture logic is complex, that is, the network architecture logic is complex, the network functions need to be strongly coupled and the calling logic is fixed, the network function upgrade and update cycle is long, which is not conducive to flexible and lightweight network deployment and management.

[0104] In order to solve the above technical problems, this application adds business management function, gateway / execution function and service control function on the basis of the current network architecture. Figure 1 As shown, the following first briefly describes the business management function, gateway and service control function.

[0105] 1. The service management function 136 may be a control plane function or a management plane function provided by an operator, and the services mainly provided include but are not limited to: service registration, update, deregistration, subscription / notification, authorization control, service discovery, token management and authentication, service orchestration, selection of network services (NF services) supporting services, etc. In the embodiment of the present application, the service management function 136 is mainly used to orchestrate the network service of the first service and configure the service call logic of the first service.

[0106] 2. The gateway (GW) or execution function 141 mainly manages the service interface provided by the network and receives external application programming interface (API) call requests. Common functions also include identity authentication, routing, rate limiting, billing, monitoring, analysis, policy, alarm and security. In the embodiment of the present application, the GW or execution function 141 can mainly obtain the service call logic of the first service and provide the first service to the service requester according to the service call logic of the first service. For example, the GW or execution function sends a service call request to the network service instance for calling the network service, etc.

[0107] Optionally, in the embodiment of the present application, there may be multiple GWs, which are regarded as distributed execution functions, wherein the execution function may be an execution node or network element defined by future standards, and may be implemented as a logical function, for example, the execution function is co-located with the AMF. In addition, the execution function may also be named by other names, which is not limited by the present application.

[0108] 3. The service control function 142 is a control plane network function provided by the operator network. It can obtain the service call logic of the first service from the first network element, and can also provide the service call logic of the first service to the second network element to manage the life cycle of the NF.

[0109] Based on the above-mentioned newly added network function NF (or network element), the present application provides a communication method and a communication device, which can provide network services on demand and provide flexible and lightweight network deployment and management.

[0110] The communication method provided by the embodiment of the present application will be described in detail below with reference to the accompanying drawings. The embodiment provided by the present application can be applied to any communication scenario in which a transmitting device and a receiving device communicate, for example, it can be applied to the above Figure 1 The present application proposes the following Figures 2 to 5 The method shown should be understood as follows. Figures 2 to 5 The method embodiments shown can be combined with each other. Figures 2 to 5 The steps in the method embodiments shown can be referenced to each other. In the embodiments of the present application, Figures 3 to 5 The method embodiment shown can be regarded as implementing Figure 2 Possible implementations of the functions of the method embodiment shown, Figure 3 The following mainly describes the arrangement of the network service of the first business and the configuration of the service call logic of the first business. Figure 4 and Figure 5 It is in Figure 3 On the basis of the configuration scheme of the service call logic shown, examples are given of the process of the second network element executing the first service when the service call logic of the first service is configured in the second network element (for example, an execution function or a gateway), so that the network function providing network services and the service call logic of the second network element processing the first service are separated, which facilitates flexible and lightweight network deployment and management.

[0111] It should be noted that the network service in the embodiment of the present application can be replaced by a network function service. For the convenience of description, the present application takes the network service as an example for description. The network service instance in the embodiment of the present application refers to an instance of a network service, which can be understood as a network function NF or network element that can call or execute the network service, that is, the network service instance can be a specific NF. In addition, the first service in the embodiment of the present application is not the same as the network service called when executing the first service. For the convenience of distinction and description, the first service can be represented by Service, or transaction, or service flow, and the network service can be represented by NF Service.

[0112] Figure 2 2 is a flow chart of the communication method 200 provided in the embodiment of the present application. Figure 2 As shown, the method flow may be performed by a first network element (eg, Figure 1 The service management function shown), the second network element (for example, Figure 1 The execution function / gateway shown), a third network element (e.g., Figure 1 The method is executed by a service control function shown in the figure, or by a module and / or device (for example, a chip or an integrated circuit, etc.) with corresponding functions installed in the first network element, the second network element, and the third network element, which is not limited in this application. For the convenience of description, the following description is based on the first network, the second network element, and the third network element as the execution subject, and the method includes the following multiple steps.

[0113] S210, the second network element obtains the service calling logic of the first service.

[0114] Exemplarily, the first service may be a service or service provided by the current 5G network, such as a protocol data unit (PDU) session establishment / update service, a registration service, a positioning service, etc., or it may be a service or service provided by a new network added in the future, such as a perception service, a computing service, a data service, an artificial intelligence (AI) service, a cloud terminal service, a data compression service, an AI model training service, a virtual user creation service, etc.

[0115] The service call logic of the first service includes: the network service (NFservice) called when executing the first service and the calling rule of the network service. The calling rule of the network service includes one or more of the following: the calling sequence of one or more network services, the processing method of the execution result of the network service instance corresponding to each network service calling the network service, the exception processing method, the log reporting rule or the service quality rule.

[0116] For example, the network service called when executing the first service includes a first network service and a second network service, the first network function supports calling the first network service, and the second network function supports calling the second network service, then the calling rules of the network service may include one or more of the following:

[0117] (1) The calling order of the first network service and the second network service, for example, the calling order of the first network service precedes the calling order of the second network service, that is, the first network service is called first, and then the second network service is called after the call is successful;

[0118] (2) a processing method of an execution result #1 of the first network function calling the first network service, for example, the execution result #1 indicates whether the first network service is successfully called, or an output result obtained by calling the first network service, and the processing method may be to report the execution result #1 to the second network element (for example, the execution function or the GW);

[0119] (3) a processing method of the execution result #2 of the second network function calling the second network service, for example, the execution result #2 indicates whether the second network service is successfully called, or the output result obtained by calling the second network service, and the processing method may be to report the execution result #2 to the second network element (for example, the execution function or the GW);

[0120] (4) Exception handling method, such as determining the exception handling method based on a timer or event trigger.

[0121] Exemplarily, after the second network element sends a call request message for the first network service to the first network function, a timer can be started. If the execution result of the first network function calling the first network service is not received when the timer expires, the second network element can feedback the failure of the first service execution to the service requester, or the second network element can re-send the call request message for the first network service to the first network function, or if there are other network functions that also support calling the first network service, the second network element can also send the call request message for the first network service to other network functions.

[0122] Exemplarily, when the location of the terminal device changes, or the QoS requirement of the first service cannot be met, or the billing quota of the terminal device is insufficient, the second network element may notify the service requester to stop executing the first service, etc.

[0123] (5) Log reporting rules or service quality rules, for example, used to indicate the service QoS requirements that need to be met during the execution of the first service, such as the maximum transmission rate, minimum delay, or minimum packet loss rate that needs to be met when transmitting data, the computing power and memory size that can be provided by the computing service, and the perception accuracy and perception range of the perception service.

[0124] It should be noted that the present application does not limit the number of network services called when executing the first service, for example, it also includes a third network service. Optionally, the third network function supports the third network service. Among them, the calling rules of the third network service can refer to the relevant description of the calling rules of the first network service and the second network service. Exemplarily, after the first network function calls the first network service, the execution result #1 is obtained, and the second network element can choose to call the second network service based on the execution result #1. After the second network function calls the second network service, the execution result #2 is obtained, and the second network element can choose to call the third network service based on the execution result #2. Optionally, if the second network element itself has the configuration or function of calling the first network service, the second network element does not need to send a service request to call the first network service to the first network function. Similarly, if the second network element itself has the configuration or function of calling the second network service, the second network element does not need to send a service request to call the second network service to the second network function.

[0125] Exemplarily, taking the establishment of a PDU session for a UE by SMF as an example, the SMF may first request the UDM to obtain the UE's session subscription information. After receiving the UE's session subscription information, the SMF may request the PCF to obtain the UE's session policy information. Then, the SMF may establish the UE's user plane transmission channel based on the UE's session subscription information and / or session policy information, that is, establish a transmission channel between the RAN and the UPF, allocate an IP address to the UE, configure QoS execution rules, etc., and complete the session establishment. Optionally, if the SMF itself is configured with the UE's session subscription information and / or session policy information, the SMF may omit sending a service call request to the UDM and / or PCF, and this application does not limit this.

[0126] Next, the implementation manner of the second network element acquiring the service calling logic of the first service in the above step S210 is described.

[0127] In the first example, the second network element may obtain the service calling logic of the first service from the first network element, that is, execute the following step S204.

[0128] S204, the first network element sends the service calling logic of the first service to the second network element, and correspondingly, the second network element receives the service calling logic of the first service from the first network element.

[0129] For example, the service call logic of the first service may be dynamically configured (dynamically configured) by the first network element through signaling or messages, or may be pre-configured (pre-configured), for example, the corresponding code, table or other method that can be used to indicate the service call logic of the first service may be pre-saved in the second network element. This application does not limit the implementation method.

[0130] For another example, the second network element sends a request message #a to the first network element, and correspondingly, the first network element receives a request message #a from the third network element. The request message #a is used to obtain the service call logic of the first service. Optionally, the request message #a may include an identifier of the first service. Further, the first network element sends the service call logic of the first service to the second network element, and correspondingly, the second network element receives the service call logic of the first service from the first network element.

[0131] Based on this, the first network element can actively send the service call logic of the first service to the second network element, or send the service call logic of the first service based on the request message #a of the second network element. In the present application, the first network element can also configure the service call logic of the first service for the second network element (for example, see the following step S203) or other network functions.

[0132] In the second example, the second network element may obtain the service calling logic of the first service from the third network element, that is, execute the following steps S206-S207.

[0133] S206, the second network element sends a request message #3 to the third network element, and correspondingly, the third network element receives the request message #3 from the second network element, wherein the request message #3 is used to obtain the service call logic of the first service.

[0134] S207, the third network element sends the service calling logic of the first service to the second network element, and correspondingly, the second network element receives the service calling logic of the first service from the third network element.

[0135] In the third example, the second network element may also obtain the service call logic of the first service from other network functions. For example, the second network element obtains the service call logic of the first service from the NRF. The specific implementation method refers to the above-mentioned description of the second network element obtaining the service call logic of the first service from the first network element or the third network element. This application does not limit this.

[0136] In a possible implementation, before executing the above step S207, the third network element obtains the service calling logic of the first service, that is, the method further includes the following step S203.

[0137] S203, the first network element sends the service calling logic of the first service to the third network element, and correspondingly, the third network element receives the service calling logic of the first service from the first network element.

[0138] For example, the service call logic of the first service may be dynamically configured (dynamically configured) by the first network element through signaling or messages, or may be pre-configured (pre-configured), for example, the corresponding code, table or other method that can be used to indicate the service call logic of the first service may be pre-saved in the third network element. The present application does not limit the implementation method.

[0139] For another example, the third network element sends a request message #b to the first network element, and correspondingly, the first network element receives the request message #b from the third network element. The request message #b is used to obtain the service call logic of the first service. Optionally, the request message #b may include an identifier of the first service. Further, the first network element sends the service call logic of the first service to the third network element, and correspondingly, the third network element receives the service call logic of the first service from the first network element.

[0140] Based on this, the first network element may actively send the service calling logic of the first service to the third network element, or may send the service calling logic of the first service based on the request message #b of the third network element.

[0141] In a possible implementation, the first network element actively configuring the service call logic of the first service for the second network element and / or the third network element in the above steps S203 and / or S204 may be triggered based on the configuration request of the service requester. That is, before executing the above steps S203 and / or S204, the service requester may request the first network element to configure the service call logic of the first service, which can also be understood as: the service requester requests the first network element to orchestrate the network service called when executing the first service, that is, the method further includes the following steps S201-S202a.

[0142] S201, a service requester sends a request message #1 to a second network element, and correspondingly, the second network element receives the request message #1 from the service requester, wherein the request message #1 is used to request a first network element to configure a service call logic of a first service.

[0143] Exemplarily, the service requester may be a terminal device, a third-party application server, a core network function, or a wireless access network function, etc., and this application does not limit this.

[0144] Optionally, request message #1 includes one or more of the following parameters (1)-(6). It should be noted that when the service requester is a UE, the parameter included in request message #1 is (1); when the service requester is an OAM, the parameters also included in request message #1 are one or more of (2) to (6). That is to say, at this time, the calling logic of the first service can be provided by OAM to the first network element. The first network element in this application is mainly responsible for orchestrating the network service of the first service and configuring the service calling logic of the first service.

[0145] (1) Information related to the first business.

[0146] Exemplarily, the relevant information of the first service includes one or more of the following: an identifier or name (service ID / name) of the first service, address information of the first service (such as IP address, MAC address, etc.), a fully qualified domain name (FQDN) of the first service, and an application programming interface API. For example, when the first service is a PDU session establishment / update service, the identifier of the first service may be a PDU session establishment / modification service; when the first service is a registration service, the identifier of the first service may be a registration service. That is, the first service may be indicated in plain text, and optionally, the request message #1 itself may implicitly indicate the first service, and then the request message #1 may not carry the relevant information of the first service. For example, when request message #1 is a session establishment request message, it can be determined that the first service is a session establishment service.

[0147] (2) Business parameters.

[0148] It should be understood that the service parameters represent the parameters required for executing the first service, and the service parameters required for different services may be different. For example, the service parameters include one or more of the following: network identification (PLMN ID, or non-public network (NPN ID)), slice type or identification, data network name (data network name, DNN), bearer information, interface information, location information, QoS parameters, ubiquitous sensor network (USN) type or identification, application identification (application ID, APP ID), etc.

[0149] (3) Information of the service requester.

[0150] Exemplarily, it is used to indicate the information of the service requester supporting the use of the first service. For example, the information of the service requester may include an identifier of the service requester (such as NF ID, UE ID, or AF ID, etc.).

[0151] (4) Triggering condition of the first service.

[0152] Exemplarily, the triggering condition of the first service may be one or more of the following:

[0153] a) Service request message; for example, when the second network element receives a service request message for a first service from a service requester, execution of the first service may be triggered.

[0154] b) Related information of the first service; for example, when the second network element receives the related information of the first service (eg, service ID / name), it may trigger the execution of the first service.

[0155] c) Timer; for example, the second network element may start a timer and trigger execution of the first service after the timer expires.

[0156] d) Trigger event; for example, the trigger event may be one or more of the following: the service requester (such as UE) enters a certain location, the subscription information or policy information of the service requester (such as UE) changes, etc., that is, when the trigger event occurs or is about to occur, the second network element may trigger the execution of the first service. Optionally, the second network element may obtain the above trigger event from the PCF / UDM / UDR, or the UE, or the first network element.

[0157] That is, when the triggering condition of the first service is met, the second network element can trigger the execution of the first service. It should be understood that triggering the execution of the first service can be: the second network element sends a service call message to the network function to request the call of the network service, or in other words, in response to the above triggering condition, the second network element can request the network function to call the network service corresponding to the first service.

[0158] (5) Information related to network services.

[0159] Exemplarily, the relevant information of the network service includes one or more of the following: specific operation information of the network service called when executing the first business (such as the name of the network service, the name of the API, or the function name, etc.), or interface information (such as address information, or a uniform resource locator (URL). Among them, the function name can be understood as the name of a standardized network service, such as Service Name, or can be understood as a model in cloud computing, such as Function name of Function-as-a-Service (FaaS).

[0160] (6)NF calling logic.

[0161] Exemplarily, the NF calling logic includes one or more of the following: information about the network service called when executing the first business, function name, interface information (such as API information), the calling sequence of the network service, the processing method of the execution result of the network function calling the network service, and the processing method of the exception. For specific explanations, please refer to the relevant description of the above step S210.

[0162] It should be noted that, for the terminal device or AF, the NF call logic may not be open for direct use, so the NF call logic can be standardized, that is, the binding relationship between the first service and the service call logic can be defined by the standard, or defined by the operator (i.e., the provider of the network service). At this time, for the second network element, when receiving the identifier or name of the first service, it can determine the network service called when executing the first service and the call logic of the network service, and then execute the first service based on the call logic of the network service.

[0163] Optionally, the above parameters can be carried in the request message #1 and sent to the first network element, or can be obtained by the first network element through other channels, such as through the network management page, and the service requester fills in or edits the above parameters through the setting window in the page and sends them to the first network element, wherein the UE can transmit the request message #1 and the above parameters to the first network element through the user plane data through the application (application, APP), and the AF can send the request message #1 and the above parameters to the first network element through the capability exposure interface.

[0164] S202, the second network element sends a request message #2 to the first network element, and correspondingly, the first network element receives the request message #2 from the second network element, wherein the request message is used to request the first network element to configure the service call logic of the first service.

[0165] It should be understood that based on the above steps S201-S202, the first network element can orchestrate the network services (e.g., the first network service and the second network service) called when the first service is executed. For example, the first network element can select based on the granularity of the network service, and after determining the first network service and the second network service called when executing the first service, select a suitable network service instance (NF service instance) for orchestration based on the input parameters of the first service.

[0166] Exemplarily, the input parameters of the first service include one or more of the following:

[0167] (1) Location information can be used to indicate the scope in which the first service can be provided, for example, whether the first service can be provided only in a certain area or not in certain areas.

[0168] (2) The service type of the first service can be used to distinguish the attributes of the service, such as connection service, computing service, perception service, AI service, etc.

[0169] (3) Capability information, which mainly refers to the capabilities of terminal devices. For example, it can support the provision of the first service for 6G terminal devices, or support the provision of perception-related first services for terminal devices with perception capabilities.

[0170] (4) A user number segment or user identifier may be used to indicate a user who supports the first service.

[0171] Optionally, the input parameters of the first service may be obtained by the third network element from the UDM and / or PCF.

[0172] S202a, the first network element sends a response message #1 to the service requester, and correspondingly, the service requester receives the response message #1 from the first network element. The response message #1 carries relevant information of the first service, such as service ID / name. Based on the above step S201, when the service requester is a UE, the response message #1 can be used to indicate the orchestration result (e.g., orchestration success or failure) of the network service (e.g., the first network service and the second network service) for the first service, and when the service requester is an OAM or AF, the response message #1 can be used to indicate that the service call logic of the first service is about to be configured or has been configured.

[0173] It should be understood that the technical solution of the present application is implemented when the first network element successfully orchestrates the network service.

[0174] It should be noted that the present application does not specifically limit the timing of step S202a. For example, step S202a may be performed after step S203 and / or S204, or before S203 and / or S204, that is, the first network element may notify the service requester after completing the orchestration of the first network service and the second network service, and the configuration of the service call logic of the first service; or, the service requester may be notified after receiving the request message #2 from the service requester in step S202, and then the first network service and the second network service are orchestrated, and the service call logic of the first service is configured, and the present application does not limit this.

[0175] Optionally, the response message #1 may also carry one or more of the following information:

[0176] (1) information about the network service or network service instance called when executing the first service;

[0177] (2) The triggering condition of the first service, see the relevant description of step S201 for details;

[0178] (3) Other parameters, such as quality of service (QoS) parameters of the first service.

[0179] Optionally, the first network element may send a response message #1 to the service requester through the second network element. For example, the first network element sends a response message #2 to the second network element, and then the second network element sends a response message #3 to the service requester, wherein the response message #2 and the response message #3 are used to indicate the orchestration results of the first network service and the second network service.

[0180] Exemplarily, Table 1 shows the orchestration result of the network service called when executing the first service. As shown in Table 1, for the first service (for example, the identifier / name of the first service is Service 11), based on the above steps S201-S203, it can be known that the first network element or other node or function determines that the network services called when executing Service 11 are NFService_1 and NF Service_2, and selects appropriate network service instances, namely NF Service_1_1 and NF Service_2_1, according to the corresponding input parameters (for example, one or more of the location information, the service type of the first service, the capability information, and the user number segment), to complete the orchestration of the network service and the network service instance. It should be understood that the network service instance (or network function) supports calling the corresponding network service, for example, NF Service_1_1 supports calling NF Service_1, and NFService_2_1 supports calling NF Service_2. Optionally, Service 11 can be executed when the triggering condition of the first service is met, for example, when the third network element receives Service 11 or the IP address used to indicate Service 11, it is determined to execute Service 11. Similarly, for the first service Service 22, the first network element or other node or function determines that the corresponding network services to be called when executing Service 22 are NF Service_1 and NF Service_3, and selects appropriate network service instances according to input parameters, namely NF Service_1_1, NF Service_1_2 and NF Service_3_1. Among them, NF Service_1_1 and NF Service_1_2 both support calling NF Service_1, and NF Service_3_1 supports calling NF Service_2. Optionally, Service 22 can be executed when the triggering condition of the first service is met, for example, when the third network element receives a service request message or the subscription information of the UE changes, it is determined to execute Service 22.

[0181] Table 1

[0182]

[0183] It should be understood that the above Table 1 is only an example given for ease of understanding and does not constitute any limitation on the technical solution of the present application. The triggering conditions of the first service in Table 1, the information contained in the input parameters and their interpretations can be referred to the above related descriptions and will not be described here.

[0184] Optionally, the response message #1 is also used to indicate a method for requesting to obtain the first service. For example, the response message #1 includes an identifier or name (Service ID / service name) of the first service, and / or an API, etc., which is used by the service requester to request the first service from the first network element by carrying the API and / or Service ID / servicename in the service request message when the service requester expects to obtain the first service.

[0185] Optionally, based on the completion of the orchestration of the first network service and the second network service, the service requester may initiate a service request to the second network element to obtain the first service. That is, before executing step S210, the service requester may initiate a service request for the first service to the second network element, that is, the method further includes the following step S205.

[0186] S205, the service requester sends a service request message to the second network element, and correspondingly, the second network element receives the service request message from the service requester, wherein the service request message is used to request the second network element to execute the first service.

[0187] Exemplarily, the service requester may be a terminal device, a third-party application server, a core network function, or a wireless access network function, etc., and this application does not limit this.

[0188] Optionally, the service request message includes an identifier or name of the first service, that is, the first service can be indicated in plain text; or, the service request message itself can implicitly indicate the first service, and the service request message may not carry relevant information about the first service. For example, if the service request message is a session establishment request message, the message itself can determine that the first service is a session establishment service; or, the second network element can determine that the API or FQDN carried in the service request message is the API or FQDN corresponding to the first service, and the API or FQDN itself can determine the first service that the service requester expects to obtain.

[0189] Optionally, the service request message may also include one or more of the following information: information of the service requester, relevant information of the first service, an application programming interface API, or other parameters. For specific interpretations, please refer to the above-mentioned related descriptions.

[0190] Further, the second network element may obtain the service calling logic of the first service, and execute the first service according to the service calling logic of the first service. For specific implementation methods, refer to the relevant description of steps S210 and S220.

[0191] Exemplarily, Table 2 shows the network services called when executing the first service and the calling logic of the network services. As shown in Table 2, for the first service (for example, the identifier / name of the first service is Service 1), the corresponding network services called are NF Service_1 and NF Service_2, wherein the network service instance NF Service_1_1 supports calling NF Service_1, and the network service instance NF Service_2_1 supports calling NF Service_2.

[0192] For example, the second network element can send a service call request message #a to NF Service_1_1 to request the call of NF Service_1. The service call request message #a can carry the call order Order=1, service input parameter A1 (for example, information of the service requester, relevant information of the first service, expected service quality parameters, etc.), the specific service / operation of the called network service 1, and the sending address of the execution result is the second network element (execution function or GW). Then, after NF Service_1_1 calls NF Service_1, it can obtain the execution result #1, which is used to indicate whether the call of NF Service_1 is successful. Further, NF Service_1_1 can send a service call response message #a to the second network element, and the service call response message #a includes the execution result #1 and the call order Order=1; then the second network element continues to send a service call request message #b to NF Service_1_2, for requesting NF Service_1_2 to call NF Service_2, and the service call request message #b carries the relevant information of the first service and the call order Order=2, the service input parameter A2 (for example, the information of the service requester, the relevant information of the first service, the expected service quality parameter, etc.), the specific service / operation of the called network service 2, and the sending address of the execution result is the second network element (execution function or GW), then after NF Service_1_2 calls NFService_2, the execution result #2 can be obtained to indicate whether NF Service_2 is successfully called. Further, NFService_1_2 can send a service call response message #b to the second network element, and the service call response message #b includes the execution result #2 and the call order Order=2. Optionally, if the second network element is a GW, the GW sends the execution result #1 and the execution result #2 to the execution function / NF, or sends the output result #3 obtained by combining the output result #1 and the output result #2 to the execution function or the service requester.

[0193] Table 2

[0194]

[0195] It should be understood that the above Table 2 is only an example given for ease of understanding and does not constitute any limitation to the technical solution of the present application.

[0196] S220: The second network element executes the first service according to the service calling logic of the first service.

[0197] Below, taking the example that the network services called when the second network element executes the first service include the first network service and the second network service, the specific implementation method of executing the first service is described, including the following method 1 and method 2. Optionally, in method 1, one or more GWs can maintain the service call logic of the first service, so the GW obtains the current execution stage or step of the first service and executes the first service. The GW in this method can be regarded as a distributed execution function. In method 2, a single execution function can maintain the service call logic of the first service and execute the first service. The one execution function can be regarded as a centralized execution function.

[0198] It should be noted that the first network function supports calling the first network service, and the second network function supports the second network service. Among them, the first network function and the second network function can be UE, or NF, or AF, or RAN, which is not limited in this application. In the embodiment of the present application, the number of network functions and / or network services associated with the first service is not limited. It can be understood that the same network function supports calling one or more network services, and different network functions can support the same network service.

[0199] Method 1:

[0200] Exemplarily, the second network element is a gateway GW, and the service call logic of the first service is configured in the GW, that is, the GW can receive a service request message from the execution function or the service requester. Further, the GW executes the first service according to the service call logic of the first service, and the specific implementation method may include the following steps S208-S215.

[0201] S208, GW#1 sends a service call request message #1 to the first network function according to the service call logic of the first service, and correspondingly, the first network function receives the service call request message #1 from GW#1. The service call request message #1 is used to request the first network function to call the first network service.

[0202] Exemplarily, the service invocation request message #1 includes an identifier of the first service.

[0203] Optionally, the service invocation request message #1 may further include one or more of the following:

[0204] (1) indication information #1, where the indication information #1 is used to indicate the current execution phase or step of the first service, for example, a first network service is about to be called;

[0205] It should be noted that the "current execution stage or step" here can be the last stage or step that has been completed, or it can be the stage or step that is about to be performed, and this application does not limit this.

[0206] (2) Address information of GW#2, used to instruct the first network function to send the output result to GW#2.

[0207] For example, the first network function can send the execution result of calling the first network service to GW#2 through the address information of GW#2. Optionally, there can be one or more GWs, and each GW is configured with the service call logic of the first service. For example, when there is only one GW, GW#1 and GW#2 are the same. Optionally, the address information of GW#2 can be carried in the service call request message #1 and sent to the first network function, or it can not be sent to the first network function. For another example, when there are multiple GWs, the GW#2 indicated by the address information of GW#2 can be the same GW as GW#1 in step S208, or it can be a different GW, and this application does not limit this.

[0208] S209: The first network function calls the first network service.

[0209] S211, the first network function sends a service call response message #1 to GW#2, and correspondingly, GW#2 receives the service call response message #1 from the first network function, and the service call response message #1 includes an execution result #1. The execution result #1 is used to indicate whether the first network service is successfully called, or is the output result of calling the first network service.

[0210] Optionally, the service invocation response message #1 may also include indication information #2, where the indication information #2 is used to indicate the current execution phase or step of the first service, for example, the first network service has been invoked and / or the second network service is about to be invoked.

[0211] It should be noted that if GW#1 and GW#2 are different GWs, the address information of GW#2 is carried in the service call request message #1 of step S208. If the address information of GW#2 is not carried in the service call request message #1 of step S208, it can be considered that GW#1 and GW#2 are the same GW, or it can be considered that the first network function can feed back the execution result #1 to any GW after calling the first network service. It should be understood that each GW is configured with the service call logic of the first service.

[0212] S212, GW#2 sends a service call request message #2 to the second network function according to the service call logic of the first service, and correspondingly, the second network function receives the service call request message #2 from GW#2. The service call request message #2 is used to request the second network function to call the second network service.

[0213] Exemplarily, the service invocation request message #2 includes an identifier of the first service.

[0214] Optionally, the service invocation request message #2 may further include one or more of the following:

[0215] (1) Indication information #3, where the indication information #3 is used to indicate the current execution stage or step of the first service, for example, the first network service has been called and / or the second network service is about to be called.

[0216] (2) Address information of GW#2, used to instruct the second network function to send the output result to GW#2.

[0217] S213: The second network function calls the second network service.

[0218] S214, the second network function sends a service call response message #2 to GW#2, and correspondingly, GW#2 receives the service call response message #2 from the second network function, and the service call response message #2 includes an execution result #2. The execution result #2 is used to indicate whether the second network service is successfully called, or is the output result of calling the second network service.

[0219] Optionally, the service invocation response message #2 may also include indication information #4, where the indication information #4 is used to indicate the current execution phase or step of the first service. For example, the second network service has been invoked.

[0220] S215, GW#2 sends a service response message to the execution function or NF, and correspondingly, the execution function or NF receives the service response message from GW#2. The service response message is used to indicate execution result #1 and execution result #2, or to indicate whether the first service is successfully executed.

[0221] Optionally, execution result #1 and execution result #2 can be combined into execution result #3, and the service response message includes execution result #3. For example, if execution result #1 indicates that the first network service call is successful, and execution result #2 indicates that the second network service call is successful, then execution result #3 indicates that the first service is successfully executed; for another example, if execution result #1 indicates that the first network service call fails, and / or execution result #2 indicates that the second network service call fails, then execution result #3 indicates that the first service fails.

[0222] Optionally, when there are multiple GWs executing the first service, the service context generated during the entire network service call process does not need to be maintained by the GW. Therefore, in the above steps S208 and S212, the GW may carry database (DB) information, such as a DB identifier or a DB address, in the service call request message, and the database is used to store the context information of the first service. In other words, in this implementation, the context information of the first service is saved by the database. This is because considering the existence of multiple GWs, assuming that the context information of the first service exists in one or more GWs, if the one or more GWs fail, the context of the first service may be damaged or lost, which may cause the first service to fail to execute normally. When the context information of the first service is stored in the database, any one of the multiple GWs can obtain the context information of the first service from the database in a timely manner, which can ensure the availability of the first service and improve the user experience.

[0223] Exemplarily, the context information of the first service includes one or more of the following, and specific interpretations can refer to the above related descriptions.

[0224] (1) information related to the first business;

[0225] (2) information of the service requester, such as information of the service requester supporting or requesting to use the first service (such as UEID);

[0226] (3) information about the network service, such as an identifier of the network service called when executing the first service;

[0227] (4) Information about the network service instance, such as the identifier and / or address information of the network service instance that supports calling the network service;

[0228] (5) the method for executing the first business;

[0229] (6) information about a third network element supporting the first service, such as an identifier and / or address information of a service control function;

[0230] (7) Session identification information of the first service (such as service session ID), used to identify that the session is a session for the first service.

[0231] (8) information about a network function corresponding to the first service, such as an identifier, address information, or load status of the network function, where the network function supports calling a network service. Optionally, the network function and the network service instance may be equivalent;

[0232] (9) The binding relationship between other network nodes or functions and the first service, for example, the binding relationship between the UE identifier and the first service identifier, can be used to indicate that the UE supports the use of the first service, or that the UE requests to use the first service.

[0233] (10) Database information, for example, the database stores data and / or execution results generated during the execution of the first service.

[0234] Optionally, before executing the above step S208, GW#1 obtains the address information of the first network function; similarly, before executing the above step S212, GW#2 obtains the address information of the second network function. Correspondingly, the method also includes steps S216 and S217.

[0235] S216, GW#1 obtains information about the first network function from the service discovery function (ie, an instance of the fourth network element).

[0236] Exemplarily, the information of the first network function includes an identifier and / or address information of the first network function. For example, GW#1 sends a query message to the service discovery function, where the query message is used to obtain the information of the first network function, and the query message includes an identifier of the first service. Correspondingly, the service discovery function sends the information of the first network function to GW#1.

[0237] S217, GW#2 obtains information about the second network function from the service discovery function. For specific implementation methods, please refer to the relevant description of step S216 above. GW#.

[0238] Optionally, the first network element sends configuration information to the service discovery function, and correspondingly, the service discovery function receives the configuration information from the first network element. The configuration information includes the identifier of the first service and the information of the network function. For example, assuming that the network service called by the first service includes the first network service and the second network service, the configuration information includes the information of the first network function and the information of the second network function. The information of the network function includes the identifier and / or address information of the network function.

[0239] Based on the above method 1, taking the first service as a session establishment service, such as a PDU session establishment service as an example, when the SMF establishes a session for the UE, it needs to use at least one of the UE's session subscription information and session policy information, and the SMF needs to establish an end-to-end communication channel for the UE, that is, a connection between the UE-RAN-UPF-DN. For example, when GW#1 receives a PDU session establishment request from the execution function or NF or UE side, and obtains the service call logic of the first service from the first network element, GW#1 first sends a service call request message #1 to SMF#1 to request SMF#1 to establish a PDU session for the UE. After receiving the service call request message #1, SMF#1 creates a session context for the UE, and carries the execution result #1 in the service call response message #1 to feed back to GW#1 or GW#2. Then, GW#1 or GW#2 (if GW#2 does not have the service call logic for the first service, it can obtain the service call logic for the first service from the first network element) confirms the need to execute the next step based on the execution result #1 and the call order Order=2 carried in the service call response message #1, that is, to obtain the session subscription information of the UE from the UDM. For example, GW#1 or GW#2 can send a service call request message #2 to the UDM to request the session subscription information of the UE. The UDM can carry the session subscription information as the execution result #2 in the service call response message #2 and feedback it to GW#1 or GW#2 or GW#3. Then, GW#1 or GW#2 or GW#3 confirms the need to execute the next step based on the execution result #2 and the call order Order=3 carried in the service call response message #2, that is, to obtain the session policy information of the UE from the PCF. The PCF can carry the session policy information as the execution result #3 in the service call response message #3 and feed it back to GW#1 or GW#2 or GW#3 or GW#4, and so on. Then, any GW sends a service call request message #4 to SMF#2 to request SMF#2 to establish the user plane transmission pipeline of the UE based on the session subscription information and / or session policy of the UE, that is, to establish the transmission channel between RAN and UPF, allocate an IP address to the UE, configure QoS execution rules, etc. Among them, SMF#1 and SMF#2 can be the same SMF or different SMFs. After the user plane transmission pipeline is established, SMF#2 can feed back the execution result #4, that is, the feedback information of the completion of the session establishment service, to any GW.

[0240] It should be noted that during the execution of the first service, if multiple GWs are involved in the calling of different network services, the DB information can be carried in the service call request message, so that the network function can store the corresponding execution result in the DB after the network service call is completed, which is convenient for other network functions to use when calling the network service. For example, when SMF establishes a session, it can obtain the session contract information and / or session policy information stored in the DB by UDM and / or PCF, and when SMF completes the session establishment, it can store the session context in the DB, so that when a subsequent session change occurs, the session can be modified based on the session context.

[0241] Similarly, if the first business involves calling multiple network services, for example, for model training tasks in future AI services, it may be necessary to use the network's connection services, computing services, and data services at the same time. You can also refer to the above implementation method for execution, and the GW will call the corresponding network's connection services, computing services, and data services based on the service call logic of the model training task.

[0242] Method 2:

[0243] Exemplarily, the second network element is an execution function, and the service call logic of the first service is configured in the execution function, that is, the execution function receives a service request message from the service requester. Further, the execution function executes the first service according to the service call logic of the first service, and the specific implementation method may include the following steps S218-S224.

[0244] In one possible implementation, the execution function may obtain the subscription information and / or policy information associated with the user or the first service from the subscription management function or the policy control function according to the standard process or the local policy of the operator. In the present application, the subscription and / or policy associated with the first service may be used to determine whether the service requester (e.g., UE) has the right to use the first service, and the quality of service and service scope that the first service can provide, such as the locations where the first service can be used, or the QoS that the first service can provide.

[0245] Exemplarily, the contract information and / or policy information associated with the first service may include one or more of the following: information about the service requester that supports the use of the first service (e.g., UE ID), information such as bandwidth, scheduling priority, latency, etc. supported for executing the first service, or contract usage quota information for the first service (e.g., the traffic package of the first service, the quota package when multiple users request the first service at the same time).

[0246] Optionally, this implementation may occur before step S218, or may be performed as part of executing the first service, which is not limited in this application.

[0247] S218, the execution function sends a service call request message #a to the first network function according to the service call logic of the first business, and correspondingly, the first network function receives the service call request message #a from the execution function, wherein the service call request message #a is used to request the first network function to call the first network service.

[0248] Exemplarily, the service invocation request message #a includes an identifier of the first service.

[0249] Optionally, the service call request message #a may also include one or more of the following:

[0250] (1) indication information #a, where the indication information #a is used to indicate the current execution stage or step of the first service, for example, the first network service is about to be called;

[0251] (2) Address information or identification information of the execution function, used to instruct the first network function to send the output result to the execution function.

[0252] S219: The first network function calls the first network service.

[0253] S221, the first network function sends a service call response message #a to the execution function, and correspondingly, the execution function receives the service call response message #a from the first network function, and the service call response message #a includes an execution result #a. The execution result #a is used to indicate whether the first network service is successfully called, or is the output result of calling the first network service.

[0254] Optionally, the service call response message #a may also include indication information #b, where the indication information #b is used to indicate the current execution phase or step of the first service, for example, the first network service has been called and / or the second network service is about to be called.

[0255] S222, the execution function sends a service call request message #b to the second network function according to the service call logic of the first service, and correspondingly, the second network function receives the service call request message #b from the execution function, wherein the service call request message #b is used to request the second network function to call the second network service.

[0256] Exemplarily, the service invocation request message #b includes an identifier of the first service.

[0257] Optionally, the service call request message #b may also include one or more of the following:

[0258] (1) Indication information #c, where the indication information #c is used to indicate the current execution stage or step of the first service, for example, the first network service has been called and / or the second network service is about to be called.

[0259] (2) Address information of the execution function, used to instruct the second network function to send the output result to the execution function.

[0260] S223: The second network function calls the second network service.

[0261] S224, the second network function sends a service call response message #b to the execution function, and correspondingly, the execution function receives the service call response message #b from the second network function, and the service call response message #b includes an execution result #b. The execution result #b is used to indicate whether the second network service is successfully called, or is the output result of calling the second network service.

[0262] Optionally, the service invocation response message #b may also include indication information #d, where the indication information #d is used to indicate the current execution phase or step of the first service. For example, the second network service has been invoked.

[0263] Optionally, before executing the above step S218, the execution function may obtain information about the first network function, such as an identifier and / or address information of the first network function, from a service discovery function (i.e., an instance of the fourth network element). Exemplarily, the execution function sends a query message to the service discovery function, the query message is used to obtain information about the first network function, and the query message includes an identifier of the first service. Correspondingly, the service discovery function sends the information about the first network function to GW#1. Optionally, before executing the above step S222, the execution function may also obtain information about the second network function from the service discovery function. For specific implementation methods, please refer to the relevant description of the execution function obtaining information about the first network function.

[0264] Optionally, the context information of the first service may be stored in the execution function or in a database, which is not limited in the present application. The content and interpretation of the context information of the first service may refer to the relevant description of the above step S215.

[0265] Based on the above-mentioned method 2, taking the first service as a session establishment service, such as a PDU session establishment service as an example, when the SMF establishes a session for the UE, it needs to use at least one of the UE's session subscription information and session policy information, and the SMF needs to establish an end-to-end communication channel for the UE, that is, the connection between UE-RAN-UPF-DN. For example, when the UE initiates a PDU session establishment request, and after the execution function obtains the service call logic of the first service from the first network element, the execution function first sends a service call request message #1 to SMF#1 to request SMF#1 to create a session context for the UE. After receiving the service call request message #1, SMF#1 creates a session context for the UE and carries the execution result #1 in the service call response message #1 to feed back to the execution function; then, the execution function confirms that the next step needs to be executed according to the service call logic of the first service, that is, sending a service call request message #2 to the UDM to request to obtain the UE's session subscription information. After receiving the service call request message #2, the UDM can use the session subscription information as The execution result #2 is carried in the service call response message #2 and fed back to the execution function; then, the execution function confirms that the next step needs to be executed according to the service call logic of the first service, that is, obtaining the session policy information of the UE from the PCF, and the PCF can carry the session policy information as the execution result #3 in the service call response message #3 and feed it back to the execution function; then, the execution function confirms that the next step needs to be executed according to the service call logic of the first service, that is, sending a service call request message #4 to SMF#2 to request SMF#2 to establish the user plane transmission pipeline of the UE based on the session subscription information and / or session policy of the UE, that is, to establish the transmission channel between RAN and UPF, allocate an IP address to the UE, configure QoS execution rules, etc. After the user plane transmission pipeline is established, SMF#2 can feed back the execution result #4, that is, the feedback result of the completion of the session establishment service, to the execution function.

[0266] In a possible implementation, in response to the service establishment request message in step S205, after the first service is executed, the second network element may feed back the execution result of the first service to the service requester.

[0267] S220a, the second network element sends a service response message to the first network element, and correspondingly, the first network element receives the service response message from the second network element. The service response message includes execution result #1 and execution result #2, and the service response message is used to indicate the execution result of the first service (for example, execution success or execution failure), and correspondingly, it can also be understood as the success or failure of the call of the first network service and the second network service. Alternatively, the service response message can also be used to execute the output result of the first service, for example, for the positioning service, the output result can be location information, such as coordinate information.

[0268] Optionally, execution result #1 and execution result #2 can be combined into execution result #3, and the service response message includes execution result #3. For example, if execution result #1 indicates that the first network service call is successful, and execution result #2 indicates that the second network service call is successful, then execution result #3 indicates that the first service is successfully executed; for another example, if execution result #1 indicates that the first network service call fails, and / or execution result #2 indicates that the second network service call fails, then execution result #3 indicates that the first service fails.

[0269] Optionally, after the service call logic configuration of the first service is completed, the first network element may initiate a configuration update process to the service requester (e.g., UE / NF / AF) that supports the use of the first service, including the update of UE subscription information, subscription information and / or policy information associated with the user or the first service, etc. That is, the method further includes the following step S225.

[0270] S225, the first network element sends a configuration update message to the service requester, where the configuration update message is used to update the contract information and / or policy information associated with the first service. Correspondingly, the service requester receives the configuration update message from the first network element and updates the contract information and / or policy information associated with the first service. The content and interpretation of the contract information and / or policy information associated with the first service can be referred to the above related description.

[0271] In the present application, update can be understood as change, addition or deletion. If the contract information and / or policy information associated with the first service needs to be changed, the update message carries the updated contract information and / or policy information associated with the first service.

[0272] In one example, the first network element sends a configuration update message #1 to UDM / UDR / PCF to indicate an update of the contract information and / or policy information associated with the first service. Correspondingly, UDM / UDR / PCF sends a configuration update message #2 to the service requester (e.g., UE / AF / NF) to indicate an update of the contract information and / or policy information associated with the first service, wherein the configuration update message #1 and the configuration update message #2 include the updated contract information and / or policy information associated with the first service.

[0273] According to the solution provided by the present application, the first network element can flexibly configure the service call logic of the first service, so that the mobile network can be used as a cloud service provision platform to provide the first service to the service requester on demand, which is easy to open to users. In addition, the call logic of the network service in the mobile network is separated from the network service execution logic, and the service call logic of the first service is configured in the execution function or gateway, so that the network function involved in executing the first service no longer needs to obtain the complete service call logic, but only needs to call the network service and provide the network service supported by itself to the outside world, which can simplify the implementation method of the network function, call the network service on demand, and reduce the network operation cost.

[0274] Figure 3 The flow chart of the communication method 300 provided in the embodiment of the present application is as follows. Figure 3 As shown, the first network element is a service management function, the second network element is an execution function / GW, and the third network element is a service control function. In this implementation, the service management function configures the service call logic of the first service for the service control function / GW / other network function. The method includes the following steps. It should be understood that Figure 3 The method 300 shown can be viewed as described above. Figure 2 A specific implementation of the method shown. Figure 2 The relevant description in the embodiment shown is also applicable to this implementation. Figure 3 and Figure 2 There may be the same or similar technical means between them. Figure 2 The contents described in the embodiment shown are as follows. Figure 3 No more details.

[0275] S301a, OAM / NF sends a request message #1 to the service management function, and correspondingly, the service management function receives the request message #1 from OAM / NF.

[0276] S301b, AF sends a request message #2 to the service management function, and correspondingly, the service management function receives the request message #2 from AF.

[0277] Exemplarily, the AF sends a request message #2 to the service management function through the NEF.

[0278] S301c, the UE sends a request message #3 to the service management function, and correspondingly, the service management function receives the request message #3 from the UE.

[0279] Exemplarily, the UE sends a request message #3 to the service management function through the GW or the execution function.

[0280] That is, based on the above steps S301a to S301c, the service calling logic of the first service may be configured by the service management function based on the request message initiated by OAM / NF / AF / UE.

[0281] Among them, the content and interpretation of request message #1, request message #2, and request message #3, as well as the specific implementation method can refer to the relevant description of steps S201-S202 of the above method 200.

[0282] It should be noted that one or more of the above steps S301a-S301c are optional, or in other words, the present application does not limit OAM / NF, AF, or UE to send a service request message to the service management function. The execution of one or more of steps S301a-S301c is determined by the service requirements of the service requester (e.g., OAM / NF, AF, UE).

[0283] Further, based on the above steps S301a to S301c, the service management function may configure the service information related to the first service to the service control function or the service discovery function, that is, execute the following steps S302a to S303c.

[0284] S302a, the business management function sends configuration information #1 to the service discovery function, and correspondingly, the service discovery function receives configuration information #1 from the business management function.

[0285] The content, interpretation, and specific implementation of configuration information #1 may refer to the relevant description of step S217 of the above method 200.

[0286] S302b, the business management function sends configuration information #2 to the service control function, and correspondingly, the service control function receives configuration information #2 from the business management function.

[0287] Among them, configuration information #2 includes the service calling logic of the first business, and its interpretation and specific implementation method can refer to the relevant description of step S203 of the above method 200.

[0288] Further, in response to the above steps S301a to S301c, the service management function may send a response message to the UE / NF / AF / OAM, that is, execute the following steps S303a to S303c.

[0289] S303a, the service management function sends a response message #1 to the OAM / NF, and correspondingly, the OAM / NF receives the response message #1 from the service management function.

[0290] S303b, the service management function sends a response message #2 to the AF, and correspondingly, the AF receives a response message #2 from the service management function.

[0291] Exemplarily, the service management function network element sends a response message #2 to the AF through the NEF.

[0292] S303c, the service management function sends a response message #3 to the UE, and correspondingly, the UE receives a response message #3 from the service management function.

[0293] Exemplarily, the service management function sends a response message #3 to the UE via the GW / execution function.

[0294] Among them, the content and interpretation of response message #1, response message #2, and response message #3, as well as the specific implementation method can refer to the relevant description of step S202a of the above method 200.

[0295] It should be noted that one or more of the above steps S303a-S303c are optional, or in other words, the present application does not limit the service management function to sending a service response message to the OAM / NF, AF, or UE, and specifically responds based on the execution of one or more of the above steps S301a-S301c.

[0296] It should be understood that after the service call logic configuration of the first service is completed, the service management function can initiate a configuration update process of the subscription information and / or policy information associated with the first service to the UE / NF / AF / OAM that can use the service, including updating of UE subscription information, user or service policy updates, etc., that is, executing the following steps S304 to S305b.

[0297] S304, the service management function sends a configuration update message #1 to the UDM / UDR / PCF, and correspondingly, the UDM / UDR / PCF receives the configuration update message #1 from the service management function.

[0298] S305a, UDM / UDR / PCF sends a configuration update message #2 to the UE, and correspondingly, the UE receives a configuration update message #2 from the UDM / UDR / PCF.

[0299] S305b, UDM / UDR / PCF sends configuration update message #3 to AF, and correspondingly, AF receives configuration update message #3 from UDM / UDR / PCF.

[0300] Among them, the content and interpretation of configuration update message #1, configuration update message #2 and configuration update message # in the above steps S304-S305b, as well as the specific implementation method can refer to the relevant description of step S225 of the above method 200.

[0301] Figure 3In the scheme shown, the service management function can configure the service call logic of the first service for the service control function based on the request of the service requester, that is, to achieve flexible configuration of the service call logic of the first service, so that the mobile network can be used as a cloud service provision platform, which is easy to open to users and provide flexible and lightweight network deployment and management.

[0302] Figure 4 The flow chart of the communication method 400 provided in the embodiment of the present application is as follows. Figure 4 As shown, the first network element is a service management function, the second network element is an execution function / GW, and the third network element is a service control function. The service call logic of the first service in this implementation is configured in the execution function, and then the execution function executes the first service according to the service call logic, that is, the call logic of the network service is separated from the network service execution logic. The method includes the following steps. It should be understood that Figure 4 The method 400 shown can be viewed as described above. Figure 2 A specific implementation of the method shown. Figure 2 The relevant description in the embodiment shown is also applicable to this implementation. Figure 4 and Figure 2 There may be the same or similar technical means between them. Figure 2 The contents described in the embodiment shown are as follows. Figure 4 No more details.

[0303] It should be noted that Figure 4 The solution shown is based on the configuration process of the above method 300, that is, the service management function configures the service call logic of the first service for the service control function. Further, the execution function obtains the service call logic of the first service from the service control function when receiving the service request message, and executes the first service. The specific implementation method can be referred to the following description.

[0304] S401, UE / NF / AF sends a service request message to the execution function, and correspondingly, the execution function receives the service request message from UE / NF / AF / RAN.

[0305] The content, interpretation, and specific implementation of the service request message may refer to the relevant description of step S205 of the above method 200.

[0306] S402, executing a function to trigger a first service.

[0307] Exemplarily, executing the function to trigger the first service may be receiving a service request from an external source, such as the service request message of step S401, or may be triggered when a trigger condition of the first service is met. For the interpretation of the trigger condition, reference may be made to the relevant description of step S201 of the above method 200.

[0308] S403, the execution function obtains the contract information or authorization information associated with the first service or user from the UDM / UDR / PCF.

[0309] Among them, the content and interpretation of the contract information or authorization information associated with the first service or user, as well as the specific implementation method can refer to the relevant description of the above method 200.

[0310] S404: Execute a function to obtain the service calling logic of the first business.

[0311] Exemplarily, the execution function obtains the service call logic of the first service from the service control function. The content and interpretation of the service call logic of the first service, as well as the specific implementation method, can refer to the relevant description of steps S206-S207 of the above method 200.

[0312] Optionally, before obtaining the service call logic of the first service, the execution function may authenticate the UE, and execute step S404 if the UE is authenticated successfully. The specific implementation method of the execution function authenticating the UE may be: the execution function determines whether the UE is authorized to use the first service based on the contract information or authorization information associated with the first service or user obtained from the UDM / UDR / PCF, or determines whether the contract information of the first service contains the UE's identifier, etc.

[0313] It should be noted that if the execution function cannot determine the network function information of the service that needs to be called (such as Service ID / Service name), such as the identification or address information of the network function, the execution function can initiate a request to the service discovery function to obtain the network function information, that is, execute the following step S405.

[0314] S405 , the execution function obtains information of the network function that calls the network service from the service discovery function.

[0315] For the specific implementation, please refer to the relevant description of the above method 200.

[0316] S406: The execution function executes the first service according to the service calling logic of the first service.

[0317] For the specific implementation method, reference may be made to the related description of method 2 in step S220 of the above method 200.

[0318] S407, the execution function sends a service response message to the UE / AF / NF, and correspondingly, the UE / AF / NF receives the service response message from the execution function.

[0319] The content, interpretation, and specific implementation of the service response message may refer to the relevant description of step S220a of the above method 200.

[0320] Figure 4 In the scheme shown, the service management function can flexibly configure the service call logic of the first service, so that the mobile network can be used as a cloud service provision platform, which is easy to open to users. In addition, the call logic of the network service in the mobile network is separated from the network service execution logic, and the service call logic of the first service is configured in the execution function. The execution function executes the first service according to the service call logic of the first service, so that the network function participating in the execution of the first service no longer needs to obtain the complete service call logic, but only needs to provide the network service supported by itself to the outside world, which can simplify the implementation of the network function, call the network service on demand, and reduce the network operation cost. In addition, the execution function in this embodiment can be regarded as a centralized execution function, so the execution results obtained by the network service instance (or network function) after calling the network service are fed back to the execution function, and the execution function does not need to carry additional parameters such as the call order of the network service when sending the service call request message and receiving the service response message, which can save signaling overhead and improve the service efficiency of the entire process.

[0321] Figure 5 The flow chart of the communication method 500 provided in the embodiment of the present application is as follows. Figure 5 As shown, the first network element is a service management function, the second network element is an execution function / GW, and the third network element is a service control function. The service call logic of the first service in this implementation is configured in the GW, and then the GW executes the first service according to the service call logic, that is, the call logic of the network service is separated from the network service execution logic. The method includes the following steps. It should be understood that Figure 5 The method 500 shown can be viewed as described above. Figure 2 A specific implementation of the method shown. Figure 2 The relevant description in the embodiment shown is also applicable to this implementation. Figure 5 and Figure 2 There may be the same or similar technical means between them. Figure 2 The contents described in the embodiment shown are as follows. Figure 5 No more details.

[0322] It should be noted that Figure 5 The solution shown is based on the configuration process of the above method 300, that is, the service management function configures the service call logic of the first service for the service control function. Further, when receiving the service request message, the GW obtains the service call logic of the first service from the service control function and executes the first service. The specific implementation method can be referred to the following description.

[0323] S501, the UE sends a service request message #1 to the execution function / NF, and correspondingly, the execution function / NF receives the service request message #1 from the UE.

[0324] The content, interpretation, and specific implementation of the service request message #1 may refer to the relevant description of step S205 of the above method 200.

[0325] S502, the execution function / NF obtains the subscription information or authorization information associated with the first service or user from the UDM / UDR / PCF.

[0326] The content and interpretation of the contract information or authorization information associated with the first service or user, as well as the specific implementation method, can refer to the relevant description of step S403 of the above method 400.

[0327] S503, the execution function / NF sends a service request message #2 to the GW, and correspondingly, the GW receives the service request message #2 from the execution function / NF.

[0328] The content, interpretation, and specific implementation of the service request message #2 may refer to the relevant description of the above method 200.

[0329] S504, the GW obtains the service calling logic of the first service.

[0330] For example, if the GW does not have the service call logic (or rule) for executing the service locally, the GW can obtain the service call logic of the first service from the service control function. The content and interpretation of the service call logic of the first service, as well as the specific implementation method, can refer to the relevant description of steps S206-S207 of the above method 200.

[0331] It should be noted that if the GW cannot determine the network function information of the service to be called (such as Service ID / Servicename), such as the identifier or address of the network function, then the GW can initiate a request for service information to the service discovery function network element to obtain the network function information, that is, execute the following step S505.

[0332] S505, the GW obtains information of the network function that calls the network service from the service discovery function.

[0333] For the specific implementation, please refer to the relevant description of the above method 200.

[0334] S506: The GW executes the first service according to the service calling logic of the first service.

[0335] For the specific implementation method, please refer to the relevant description of method 1 in step S220 of the above method 200.

[0336] S507, GW sends a service response message #2 to the execution function / NF, and correspondingly, the execution function / NF receives the service response message #2 from the GW.

[0337] S508, the execution function / NF sends a service response message #1 to the UE, and correspondingly, the UE receives the service response message #1 from the execution function / NF.

[0338] The contents, interpretations, and specific implementations of the service response message #1 and the service response message #2 may refer to the relevant description of step S220a of the above method 200.

[0339] Figure 5 In the scheme shown, the service management function can flexibly configure the service call logic of the first service, so that the mobile network can be used as a cloud service provision platform, which is easy to open to users. In addition, the call logic of the network service in the mobile network is separated from the network service execution logic, and the service call logic of the first service is configured in the gateway. The gateway executes the first service according to the service call logic of the first service, so that the network function participating in the execution of the first service no longer needs to obtain the complete service call logic, but only needs to provide the network service supported by itself to the outside, which can simplify the implementation of the network function, call the network service on demand, and reduce the network operation cost. In addition, the multiple gateways in this embodiment can be regarded as distributed execution functions, so the network service instance (or network function) can feed back the execution results to different gateways after calling the network service. Considering that each network element is configured with the service call logic of the first service, even if one or some of the gateways fail, the normal execution of the first service can still be guaranteed, ensuring the operability of the first service and the user experience.

[0340] Combination of the above Figures 1 to 5 The communication method embodiment of the present application is described in detail. Figure 6 to Figure 7 The communication device side embodiment of the present application is described in detail. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0341] Figure 6 FIG. 6 is a schematic diagram of a communication device 600 provided in an embodiment of the present application. Figure 6As shown, the communication device 600 includes a processing module 601 and a communication module 602. The communication device 600 may be a first network element (e.g., a service management function), or a communication device applied to the first network element or used in combination with the first network element to implement the method executed by the first network element, such as a chip, a chip system, or a circuit; or, the communication device 600 may be a second network element (e.g., a gateway or an execution function), or a communication device applied to the second network element or used in combination with the second network element to implement the method executed by the second network element, such as a chip, a chip system, or a circuit; or, the communication device 600 may be a third network element (e.g., a service control function), or a communication device applied to the third network element or used in combination with the third network element to implement the method executed by the third network element, such as a chip, a chip system, or a circuit; or, the communication device 600 may be a service requester (e.g., a UE / AF / NF), or a communication device applied to the service requester or used in combination with the service requester to implement the method executed by the service requester, such as a chip, a chip system, or a circuit;

[0342] The communication module may also be referred to as a transceiver module, a transceiver, a transceiver, or a transceiver device, etc. The processing module may also be referred to as a processor, a processing board, a processing unit, or a processing device, etc. Optionally, the communication module is used to perform the sending operation and the receiving operation of the first network element, the second network element, the third network element, or the service requester in the above method, and the device used to implement the receiving function in the communication module may be regarded as a receiving unit, and the device used to implement the sending function in the communication module may be regarded as a sending unit, that is, the communication module includes a receiving unit and a sending unit.

[0343] When the communication device 600 is applied to the first network element, the processing module 601 can be used to implement the processing function of the first network element in the above embodiments, and the communication module 602 can be used to implement the transceiver function of the first network element in the above embodiments.

[0344] When the communication device 600 is applied to the second network element, the processing module 601 can be used to implement the processing function of the second network element in the above embodiments, and the communication module 602 can be used to implement the transceiver function of the second network element in the above embodiments.

[0345] When the communication device 600 is applied to a third network element, the processing module 601 may be used to implement the processing function of the third network element in the above embodiments, and the communication module 602 may be used to implement the transceiver function of the third network element in the above embodiments.

[0346] When the communication device 600 is applied to a service requester, the processing module 601 can be used to implement the processing function of the service requester in the above embodiments, and the communication module 602 can be used to implement the sending and receiving functions of the service requester in the above embodiments.

[0347] In addition, it should be noted that the aforementioned communication module and / or processing module can be implemented by a virtual module, for example, the processing module can be implemented by a software function unit or a virtual device, and the communication module can be implemented by a software function or a virtual device. Alternatively, the processing module or the communication module can also be implemented by a physical device, for example, if the device is implemented using a chip / circuit (such as an integrated circuit or a logic circuit, etc.). The communication module can be an input-output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operations) and output operations (corresponding to the aforementioned sending operations); the processing module is an integrated processor or microprocessor or circuit (such as an integrated circuit or a logic circuit, etc.).

[0348] The division of modules in this application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each example of this application may be integrated into one processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0349] Figure 7 FIG. 7 is a schematic diagram of another communication device 700 provided in an embodiment of the present application. Figure 7 As shown, optionally, the communication device 700 may be a chip or a chip system. Optionally, in the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices.

[0350] The communication device 700 can be used to implement the functions of any network element (e.g., the first network element, the second network element, the third network element, or the service requester) in the communication system described in the foregoing examples. The communication device 700 may include at least one processor 710. Optionally, the processor 710 is coupled to a memory, and the memory may be located within the device, or the memory may be integrated with the processor, or the memory may be located outside the device. For example, the communication device 700 may also include at least one memory 720. The memory 720 stores the necessary computer programs, computer programs or instructions and / or data for implementing any of the above examples; the processor 710 may execute the computer program stored in the memory 720 to complete the method in any of the above examples.

[0351] The communication device 700 may also include a communication interface 730, and the communication device 700 may exchange information with other devices through the communication interface 730. Exemplarily, the communication interface 730 may be a transceiver, a circuit, a bus, a module, a pin, or other types of communication interfaces. When the communication device 700 is a chip-type device or circuit, the communication interface 730 in the device 700 may also be an input-output circuit, which may input information (or receive information) and output information (or send information), and the processor 710 may be an integrated processor, a microprocessor, an integrated circuit, or a logic circuit, etc. The processor may determine the output information based on the input information.

[0352] The coupling in this application is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 710 may cooperate with the memory 720 and the communication interface 730. The specific connection medium between the above-mentioned processor 710, memory 720 and communication interface 730 is not limited in this application.

[0353] Alternatively, if Figure 7 As shown in , the processor 710, the memory 720 and the communication interface 730 are connected to each other via a bus 740. Optionally, the bus may include an address bus, a data bus, a control bus and other types of buses. In addition, for ease of representation, Figure 7 One bus 740 is shown, but this does not mean that there is only one bus or one type of bus.

[0354] It should be understood that the processor mentioned in the embodiments of the present application can be the following devices or part of the circuit used for processing functions in the following devices: central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0355] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0356] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0357] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0358] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions for implementing the methods executed by the first network element / second network element / third network element / service requester in the above-mentioned method embodiments are stored.

[0359] An embodiment of the present application also provides a computer program product, comprising instructions, which, when executed by a computer, implement the methods performed by the first network element / second network element / third network element / service requester in the above-mentioned method embodiments.

[0360] An embodiment of the present application also provides a communication system, which includes the first network element / second network element / third network element / service requester in the above embodiments.

[0361] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be described again here.

[0362] In order to facilitate understanding of the above embodiments provided in this application, the following points are explained:

[0363] 1) In this application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0364] 2) In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c. Where a, b and c can be single or multiple, respectively.

[0365] 3) In the present application, "first", "second" and various numerical numbers (e.g., #1, #2, etc.) indicate distinctions made for ease of description and are not used to limit the scope of the embodiments of the present application. For example, to distinguish between different messages, etc., rather than to describe a specific order or sequence. It should be understood that the objects described in this way can be interchanged where appropriate so as to be able to describe solutions other than the embodiments of the present application.

[0366] 4) In this application, descriptions such as "when...", "in the case of..." and "if" all mean that the device will take corresponding actions under certain objective circumstances. They do not limit the time, nor do they require the device to make judgments when implementing them, nor do they mean that there are other limitations.

[0367] 5) In this application, "used for indication" may include being used for direct indication and being used for indirect indication. When describing that a certain indication information is used for indicating A, it may include that the indication information directly indicates A or indirectly indicates A, but it does not mean that the indication information must carry A.

[0368] The indication method involved in the embodiments of the present application should be understood to include various methods that can enable the party to be indicated to know the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different. This application does not limit the sending method, for example.

[0369] The "indication information" in the embodiments of the present application may be an explicit indication, i.e., directly indicated by signaling, or obtained by combining other rules or other parameters or by deduction according to the parameters indicated by the signaling. It may also be an implicit indication, i.e., obtained by combining other rules or other parameters or by deduction according to a rule or relationship. The present application does not make any specific limitation on this.

[0370] 6) In this application, "protocol" may refer to a standard protocol in the field of communications, such as 5G protocol, NR protocol, and related protocols used in future communication systems, which are not limited in this application. "Predefined" may include pre-definition. For example, protocol definition. "Preconfiguration" may be implemented by pre-saving corresponding codes, tables, or other methods that can be used to indicate relevant information in the device, and this application does not limit its implementation method, for example.

[0371] 7) In this application, "communication" may also be described as "data transmission", "information transmission", "data processing", etc. "Transmission" includes "sending" and "receiving".

[0372] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0373] In the present application, under the premise of no logical contradiction, the examples may reference each other, for example, the methods and / or terms between method embodiments may reference each other, for example, the functions and / or terms between device embodiments may reference each other, for example, the functions and / or terms between device examples and method examples may reference each other.

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

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

[0376] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0378] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0379] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0380] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, characterized in that: include: receiving a request message, the request message being used to request a first network element to configure a service calling logic of a first service, the service calling logic of the first service including a network service called when executing the first service and a calling rule of the network service; Send the service call logic of the first business.

2. The method according to claim 1, characterized in that The method further comprises: Send configuration information to a fourth network element, where the configuration information includes an identifier of the first service and information about a network function, where the network function supports calling the network service, and where the fourth network element supports discovery of the network function.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: Send a configuration update message, where the configuration update message is used to update the subscription information and / or policy information associated with the first service.

4. A communication method, characterized in that: include: Acquire a service calling logic of a first business, where the service calling logic of the first business includes a network service called when executing the first business and a calling rule of the network service; The first service is executed according to the service calling logic of the first service.

5. The method according to claim 4, characterized in that Before obtaining the service calling logic of the first business, the method further includes: receiving a first request message, where the first request message is used to request configuration of a service call logic of the first service; A second request message is sent to the first network element, where the second request message is used to request the first network element to configure the service call logic of the first service, and the first network element supports the management of the first service.

6. The method according to claim 4 or 5, characterized in that: The executing the first service according to the service calling logic of the first service includes: receiving a first service request message from a service requester, wherein the first service request message is used to request execution of the first service; The first service is executed according to the first service request message and the service calling logic of the first service.

7. The method according to claim 4 or 5, characterized in that: The executing the first service according to the service calling logic of the first service includes: receiving a second service request message, where the second service request message is used to request execution of the first service, and the second service request message includes an identifier of the first service; The first service is executed according to the second service request message and the service calling logic of the first service.

8. The method according to any one of claims 4 to 7, characterized in that The executing the first service according to the service calling logic of the first service includes: A service call request message is sent to a network function according to the service call logic of the first service, wherein the service call request message is used to request the network function to call the network service, and the service call request message includes an identifier of the first service.

9. The method according to claim 8, characterized in that The service invocation request message also includes first indication information, where the first indication information is used to indicate a current execution stage or step of the first service.

10. The method according to claim 8 or 9, characterized in that: The method further comprises: A service call response message is received from the network function, wherein the service call response message includes a feedback result, and the feedback result is used to indicate that the network service call is successful.

11. The method according to claim 10, characterized in that The service invocation response message also includes second indication information, where the second indication information is used to indicate a current execution stage or step of the first service.

12. The method according to any one of claims 8 to 11, characterized in that Before sending a service call request message to the network function according to the service call logic of the first service, the method further includes: Sending a query message to a fourth network element, where the query message is used to obtain information about the network function, where the fourth network element supports discovery of the network function, and where the query message includes an identifier of the first service; Receive information about the network function from the fourth network element.

13. The method according to any one of claims 4 to 12, characterized in that The obtaining of the service calling logic of the first business includes: Sending a third request message to a third network element, where the third request message is used to obtain a service call logic of the first service, and the third network element supports the first service; The service calling logic of the first service is received from the third network element.

14. The method according to any one of claims 4 to 12, characterized in that The obtaining of the service calling logic of the first business includes: The service invocation logic of the first service is received from a first network element, and the first network element supports management of the first service.

15. The method according to claim 14, characterized in that Before receiving the service calling logic of the first service from the first network element, the method further includes: A fourth request message is sent to the first network element, where the fourth request message is used to obtain the service calling logic of the first service.

16. A communication method, characterized in that: include: receiving a first request message, where the first request message is used to obtain a service call logic of a first service, and the first request message includes an identifier of the first service; Send the service call logic of the first business.

17. The method according to claim 16, characterized in that Before sending the service calling logic of the first business, the method further includes: A service invocation logic of the first service is received from a first network element, where the first network element supports management of the first service.

18. The method according to claim 16 or 17, characterized in that Before receiving the service calling logic of the first service from the first network element, the method further includes: A request message is sent to the first network element, where the request message is used to obtain the service calling logic of the first service.

19. A communication method, characterized in that: include: Sending a service request message to the second network element, where the service request message is used to request execution of the first service, and the service request message includes an identifier of the first service; A service response message is received from the second network element, where the service response message is used to indicate an execution result of the first service.

20. The method according to claim 19, characterized in that Before sending the service request message to the second network element, the method further includes: Sending a first request message to the second network element, where the first request message is used to request configuration of a service call logic of the first service; A first response message is received from the second network element, where the first response message is used to indicate a configuration result of the service call logic of the first service.

21. The method according to claim 19 or 20, characterized in that The method further comprises: A configuration update message is received, where the configuration update message is used to update subscription information and / or policy information associated with the first service.

22. A communication device, characterized in that: include: a processor coupled to the memory; The processor is used to execute the computer program stored in the memory so that the device performs the method according to any one of claims 1 to 3, or so that the device performs the method according to any one of claims 4 to 15, or so that the device performs the method according to any one of claims 16 to 18, or so that the device performs the method according to any one of claims 19 to 21.

23. A communication device, characterized in that: include: One or more functional modules, wherein the one or more functional modules are used to execute the method according to any one of claims 1 to 3, or the one or more functional modules are used to execute the method according to any one of claims 4 to 15, or the one or more functional modules are used to execute the method according to any one of claims 16 to 18, or the one or more functional modules are used to execute the method according to any one of claims 19 to 21.

24. A communication system, characterized in that: include: A first network element, a second network element and a third network element, the first network element is used to execute the method according to any one of claims 1 to 3, the second network element is used to execute the method according to any one of claims 4 to 15, and the third network element is used to execute the method according to any one of claims 16 to 18.

25. The communication system according to claim 24, characterized in that It also includes a service requester, which is used to execute the method according to any one of claims 19 to 21.

26. A computer-readable storage medium, characterized in that: include: The computer-readable storage medium stores a computer program, which, when executed on a computer, enables the computer to execute the method according to any one of claims 1 to 3, or enables the computer to execute the method according to any one of claims 4 to 15, or enables the computer to execute the method according to any one of claims 16 to 18, or enables the computer to execute the method according to any one of claims 19 to 21.

27. A computer program product, characterized in that include: When the computer program product is executed on a computer, the computer executes the method according to any one of claims 1 to 3, or the computer executes the method according to any one of claims 4 to 15, or the computer executes the method according to any one of claims 16 to 18, or the computer executes the method according to any one of claims 19 to 21.

Images