Communication method and communication device

Abstract

The invention discloses a communication method and a communication device, and the method comprises the steps: receiving a service request message, obtaining an execution method of a first service, and executing the first service according to the execution method of the first service. Wherein the service request message is used for requesting to execute the first service, and the execution method of the first service comprises the network service called when the first service is executed and the calling logic of the network service. According to the technical scheme, registration and management of the first service are realized based on a design thought of a dynamic network function, 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] Currently, 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. That is, the SMF needs to determine the next execution action based on the current service status, and the execution logic of the process is implemented within the NF based on standardized definitions, which makes the function of the SMF very limited.

[0004] The existing network architecture has complex logic, requires strong coupling between network functions and has fixed calling logic. The network function upgrade and update cycle is long, which is not conducive to flexible and lightweight network deployment and management. Summary of the invention

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

[0006] 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.

[0007] The method includes: determining an execution method of a first service, the execution method of the first service including a network service called when executing the first service, and a calling logic of the network service; sending the execution method to a third network element, wherein the third network element supports the first service.

[0008] Exemplarily, the first network element may be a business management function, and the third network element may be a service control function.

[0009] According to the solution provided in the present application, the first network element can provide the third network element with a method for executing the first service, or in other words, the first network element can orchestrate the network services called when executing the first service, so that the third network element can execute the first service on demand, thereby reducing the management complexity during network operation and maintenance and ensuring flexible and lightweight network deployment and management.

[0010] In certain implementations of the first aspect, before sending the execution method to the third network element, the method also includes: receiving a first query message from the third network element, the first query message is used to obtain the execution method of the first service, and the first query message includes an identifier of the first service.

[0011] Based on the above method, the first network element may feedback the execution method of the first service to the third network element based on the query request of the third network element.

[0012] In some implementations of the first aspect, configuration information is sent to the second network element, where the configuration information includes an identifier of the first service, and the configuration information is used to indicate a trigger condition for executing the first service.

[0013] Exemplarily, the second network element may be a gateway.

[0014] Based on the above method, the first network element supports configuring the trigger conditions for the second network element to execute the first service. Therefore, the second network element can trigger the execution of the first service when the trigger conditions of the first service are met. That is, the second network element triggers a service request to the third network element to execute the first service, thereby realizing on-demand triggering of the execution of the first service and improving the utilization rate of network resources.

[0015] In certain implementations of the first aspect, a registration request message is received, the registration request message is used to request registration of a first service, and the registration request message includes an identifier of the first service; and a registration response message is sent, the registration response message is used to indicate a registration result of the first service.

[0016] Based on the above solution, the first network element supports registration and management services for network functions or network services for the first business, provides business-oriented network service lifecycle management based on the design concept of dynamic network functions, and improves the utilization rate of network resources.

[0017] In certain implementations of the first aspect, the registration request message further includes information of a third network element, and the method further includes: saving a correspondence between the information of the third network element and the first service.

[0018] Based on the above scheme, through the correspondence between the information of the third network element and the first business, the third network element corresponding to different network services can be determined, so that the third network element supports the provision of network services at different levels, can provide network services on demand, and ensure flexible and lightweight network deployment and management.

[0019] In certain implementations of the first aspect, a second query message is received from a second network element, the second query message is used to obtain information of a third network element, and the second query message includes an identifier of the first service; based on the correspondence between the saved information of the third network element and the first service, the information of the third network element is sent to the second network element.

[0020] Based on the above solution, the first network element can feedback the address information of the third network element to the second network element based on the query request of the second network element, so that the second network element can trigger the sending of a service request to execute the first service to the third network element according to the address information of the third network element.

[0021] In certain implementations of the first aspect, a notification message is received from a third network element, the notification message includes an identifier of the first service, and the notification message is used to create context information of the first service; the context information of the first service is created; or, the context information of the first service is received from the third network element.

[0022] Based on the above solution, during the execution of the first service, the first network element and / or the third network element can create and maintain the context information of the first service, so as to facilitate the management and control of the first service in the current network.

[0023] 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.

[0024] The method includes: receiving a first service request message, the first service request message is used to request execution of a first service, the first service request message includes an identifier of the first service; sending a second service request message to a third network element, the second service request message is used to request execution of the first service, and the third network element supports the first service.

[0025] Exemplarily, the second network element may be a gateway.

[0026] According to the solution provided in the present application, the second network element supports the routing function, that is, it can forward the service request message from the service requester to the third network element, so that the third network element can provide the first service on demand, reduce the management complexity during network operation and maintenance, and ensure flexible and lightweight network deployment and management.

[0027] In certain implementations of the second aspect, configuration information is received from a first network element, where the configuration information is used to indicate a trigger condition of a first service, the configuration information includes an identifier of the first service, and the first network element supports management of the first service; and a second service request message is sent to a third network element, including: when the trigger condition of the first service is met, a second service request message is sent to the third network element.

[0028] Based on the above solution, the second network element can trigger a request to execute the first service when the triggering condition of the first service is met, and trigger the execution request of the first service on demand, thereby improving the utilization rate of network resources.

[0029] In certain implementations of the second aspect, before sending a second service request message to a third network element, the method also includes: sending a query message to the first network element, the query message being used to obtain information about the third network element, the query message including an identifier of the first service, and the first network element supporting management of the first service; and receiving information about the third network element from the first network element.

[0030] In certain implementations of the second aspect, the network service called when executing the first business includes a first network service and a second network service, and the method also includes: receiving a first service call request message from the first network function, the first service call request message is used to request to call the second network service, the first network function supports calling the first network service, and the service call request message includes an identifier of the second network function that supports calling the second network service; sending a second service call request message to the second network function according to the stored address information of the second network function, the second service call request message is used to call the second network service; receiving a third execution result from the second network function; and sending the third execution result to the first network function.

[0031] Based on the above solution, the second network element maintains the address information of the second network function and supports the information forwarding function between the first network function and the second network function, which can ensure the normal execution of the first service and realize flexible and lightweight network deployment and management.

[0032] In certain implementations of the second aspect, before sending the second service call request message to the second network function, the method also includes: receiving configuration information from a third network element, the configuration information including address information of the second network function; and saving the address information of the second network function.

[0033] Based on the above solution, the second network element supports maintaining the address information of the second network function and provides addressing logic, that is, it can trigger initiation of a second service call request to the second network function according to the address information of the second network function, so as to better provide the first service.

[0034] In certain implementations of the second aspect, the method further includes: receiving an update message, where the update message is used to update relevant information of the first service.

[0035] Based on the above scheme, during the execution of the first service, the relevant information of the first service may change. By sending an update message, the first network element, the second network element, or the network function (or the network service instance) supporting the network service can timely update the information associated with the first service, thereby realizing the management and control of the first service.

[0036] In certain implementations of the second aspect, the network service called when executing the first service includes a first network service and a second network service, and the relevant information of the first service includes one or more of the following: information of the first network service and / or the second network service; or, context information of the first service; or, policy information and / or contract information associated with the first service.

[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 includes: receiving a service request message, the service request message is used to request the execution of a first service, the service request message includes an identifier of the first service; obtaining an execution method of the first service, the execution method includes a network service called when executing the first service, and a calling logic of the network service; and executing the first service according to the execution method of the first service.

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

[0041] According to the solution provided in the present application, after receiving the service request message, the third network element can determine the network service called when executing the first service and the calling logic of the network service according to the execution method of the first service, and then 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, obtaining an execution method of the first service includes: sending a query message to a first network element, the query message is used to obtain the execution method of the first service, the query message includes an identifier of the first service, and the first network element supports management of the first service; receiving the execution method of the first service from the first network element.

[0043] In certain implementations of the third aspect, the method also includes: sending a notification message to the first network element, the notification message including an identifier of the first service, the notification message being used to create context information of the first service; or, creating context information of the first service; sending the context information of the first service to the first network element, the first network element supporting management of the first service.

[0044] In certain implementations of the third aspect, before receiving a service request message, the method also includes: receiving a first registration request message, the first registration request message is used to request registration of the first service, and the first network element supports the management of the first service; sending a second registration request message to the first network element, the second registration request message is used to request registration of the first service; receiving a second registration response message from the first network element, the second registration response message is used to indicate the registration result of the first service; sending a first registration response message, the first registration response message is used to indicate the registration result of the first service.

[0045] In certain implementations of the third aspect, the network service called when executing the first business includes a first network service and a second network service, and executing the first business according to the execution method of the first business includes: sending a service call request message to the first network function according to the execution method of the first business, the service call request message is used to request the first network function to call the first network service; sending first configuration information to the first network function, the first configuration information includes address information of the second network function, and the address information of the second network function is used by the first network function to determine the second network function that supports calling the second network service; and receiving a first execution result from the first network function.

[0046] In certain implementations of the third aspect, the network service called when executing the first service includes a first network service and a second network service, and executing the first service according to the execution method of the first service includes: sending a service call request message to the first network function according to the execution method of the first service, the service call request message is used to request the first network function to call the first network service; sending second configuration information to the second network element, the second configuration information includes address information of the second network function, the address information of the second network function is used by the second network element to determine the second network function that supports calling the second network service, and the second network element is used to store address information of one or more network functions; receiving a second execution result from the first network function.

[0047] In certain implementations of the third aspect, when the relevant information of the first service changes, an update message is sent, where the update message is used to update the relevant information of the first service.

[0048] In certain implementations of the third aspect, the network service called when executing the first service includes a first network service and a second network service, and the relevant information of the first service includes one or more of the following: information of the first network service and / or the second network service; or, context information of the first service; or, policy information and / or contract information associated with the first service.

[0049] 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.

[0050] 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.

[0051] 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.

[0052] According to the solution provided in this application, the service requester can request the second network element to obtain the first service on demand, thereby improving network resource utilization and reducing network operation and maintenance costs.

[0053] In certain implementations of the fourth aspect, before sending the service request message to the second network element, the method further includes: acquiring identification information of the first service.

[0054] In certain implementations of the fourth aspect, obtaining identification information of the first service includes: obtaining identification information of the first service from a first network element; or obtaining identification information of the first service from an application function, wherein the identification information of the first service is generated by the application function or the first network element, and the first network element supports management of the first service.

[0055] 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.

[0056] 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.

[0057] In certain implementations of the fifth aspect, the device includes: a processing unit, used to determine an execution method of the first service, the execution method including a network service called when executing the first service, and a calling logic of the network service; a transceiver unit, used to send the execution method to a third network element, wherein the third network element supports the first service.

[0058] 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.

[0059] 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.

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

[0061] The transceiver unit can perform the receiving and sending processing in the aforementioned second aspect and its possible implementations. Optionally, the device also includes a processing unit, which can perform other processing except receiving and sending in the aforementioned second aspect and its possible implementations.

[0062] 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.

[0063] In certain implementations of the seventh aspect, the device includes: a transceiver unit, used to receive a service request message, the service request message is used to request the execution of a first service, the service request message includes an identifier of the first service; a processing unit, used to obtain an execution method of the first service, the execution method includes a network service called when executing the first service, and a calling logic of the network service; the processing unit is also used to execute the first service according to the execution method of the first service.

[0064] 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.

[0065] 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.

[0066] 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.

[0067] The transceiver unit can perform the receiving and sending processing in the aforementioned fourth aspect and its possible implementations. Optionally, the device also includes a processing unit, which can perform other processing except receiving and sending in the aforementioned fourth aspect and its possible implementations.

[0068] 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.

[0069] In certain implementations of the ninth aspect, at least one processor is coupled to at least one memory, and the at least one memory stores the computer program or instruction. Optionally, the communication device also includes the at least one memory. Optionally, the at least one processor is integrated with the at least one memory.

[0070] 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.

[0071] 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 fourth aspect, or any possible implementation of these aspects, is implemented.

[0072] 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.

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

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

[0075] Among them, the technical effects of the technical solutions of the fifth to thirteenth 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

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

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

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

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

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

[0081] Figure 6 is a schematic diagram of an interaction flow of a communication method 600 provided in an embodiment of the present application;

[0082] Figure 7 is a schematic diagram of an interaction flow of a communication method 700 provided in an embodiment of the present application;

[0083] Figure 8 is a schematic diagram of a communication device 800 provided in an embodiment of the present application;

[0084] Fig. 9It is a schematic diagram of a communication device 900 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0085] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0086] 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.

[0087] 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.

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

[0089] 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.

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

[0091] 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.).

[0092] (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.

[0093] 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).

[0094] 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.

[0095] 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.

[0096] 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.

[0097] 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.

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

[0099] 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.

[0100] 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.

[0101] 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.

[0102] 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.

[0103] 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 UE 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. The credentials of the above-mentioned subscribers can be a small file stored in a long-term key stored in a mobile phone chip card or information related to the encryption of the mobile phone chip 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 embodiments of the present application, no distinction or restriction is made for the convenience of description.

[0104] 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.

[0105] 7. AUSF 137 is a control plane function provided by the operator and is usually used for primary authentication, i.e., authentication between UE 110 (subscribed user) and the operator network.

[0106] 8. AMF 138 is a control plane network function provided by the operator network, responsible for access control and mobility management of UE 110 accessing the operator network, including, for example, mobility status management, allocation of user temporary identity, authentication and authorization of users, etc.

[0107] 9. SMF 139 is a control plane network function provided by the operator network, responsible for managing the protocol data unit (PDU) session of UE 110 (including session establishment, modification and release), for selection and reselection of user plane functions, allocation of Internet Protocol (IP) addresses of terminal devices, quality of service (QoS) control, etc. Among them, a PDU session is a channel for transmitting PDUs, and terminal devices transmit PDUs to and from DN 140 through PDU sessions. PDU sessions are established, maintained and deleted by SMF network function 139. SMF network function 139 includes session management (such as session establishment, modification and release, including tunnel maintenance between user plane function UPF 130 and (R)AN120), selection and control of UPF network function 130, service and session continuity (SSC) mode selection, roaming and other session-related functions.

[0108] 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.

[0109] 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.

[0110] 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.

[0111] 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.

[0112] The current mobile communication network architecture is designed based on independent network elements (or NFs). 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. That is, the network architecture logic is complex, the network functions need to be strongly coupled and the calling logic is fixed, and the network function upgrade and update cycle is long, which is not conducive to flexible and lightweight network deployment and management.

[0113] In order to solve the above technical problems, this application adds business management functions, gateway and service control functions 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.

[0114] 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 function 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.

[0115] 2. Gateway (GW) 141 mainly manages the service interface provided by the network and receives external API call requests. Common functions also include authentication, routing, rate limiting, billing, monitoring, analysis, policy, alarm and security. In the embodiment of the present application, GW 141 is mainly responsible for maintaining the address information and addressing logic of NF or service control function 142 (or having a routing function). For example, GW can send messages to service control function 142 or NF based on the addressing logic.

[0116] 3. The service control function 142 is a control plane network function provided by the operator network, which is mainly responsible for the life cycle management of network services. In the embodiment of the present application, the service control function 142 can receive service requests, and pull up (cold start) or select (hot start) the NF (or a finer-grained network service) corresponding to the service to provide services and manage the life cycle of the NF.

[0117] 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.

[0118] 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 7 The method shown should be understood as follows. Figures 2 to 7 The method embodiments shown can be combined with each other. Figures 2 to 7 The steps in the method embodiments shown can be referenced to each other. In the embodiments of the present application, Figures 3 to 7 The method embodiment shown can be regarded as implementing Figure 2 Possible implementations of the functions of the method embodiment shown, Figure 3 and Figure 4 This section mainly describes the definition / registration of the first service and the triggering process of the first service. Figure 5 and Figure 6 This section mainly describes how the network service instance (or network function NF) calls the corresponding network service after the third network element starts or selects the network service. Figure 7 The update process when the information related to the first business changes during the execution of the first business is mainly described.

[0119] 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.

[0120] Figure 22 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 GW shown), a third network element (for example, 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.

[0121] S210, the service requester sends a first service request message to the second network element, and correspondingly, the second network element receives the first service request message from the service requester.

[0122] The first service request message is used to request execution of the first service.

[0123] Exemplarily, the first business may be a business or service provided by the current 5G network, such as a protocol data unit (PDU) session establishment / update business, a registration business, a positioning business, etc., or it may be a business 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.

[0124] Exemplarily, the service requester may be a terminal device, a third-party application server, a network function, or a wireless access network function, etc., which is not limited in this application.

[0125] Optionally, the first service request message may include one or more of the following information, that is, the first service may be indicated in plain text.

[0126] (1) Information of the service requester, such as the identifier of the service requester (such as NF ID, UE ID, or AF ID, etc.);

[0127] (2) relevant information of the first service, for example, including one or more of the following: an identifier or name of the first service (such as Service ID / name), 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);

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

[0129] Optionally, the first service request message itself may implicitly indicate the first service, and the first service request message may not carry relevant information of the first service. For example, if the first service request message is a session establishment request message, it can be determined that the first service is a session establishment service.

[0130] In a possible implementation, if the first service in the above step S210 is indicated in plain text, then before executing the above step S210, the service requester obtains relevant information of the first service, that is, the method further includes the following step S201.

[0131] S201: A service requester obtains relevant information of a first service.

[0132] In the first example, the service requester obtains the relevant information of the first service from the first network element. For example, during the definition / registration process of the first service, the service requester can obtain the identifier of the first service from the service registration response message. For specific implementation methods, see the relevant description of the following step S203.

[0133] In the second example, the service requester obtains relevant information of the first service from the application function, wherein the relevant information of the first service may be generated by the application function; or, the relevant information of the first service may be generated by the first network element and sent by the first network element to the application function.

[0134] In a possible implementation, before executing step S210, the first network element may define / register the first service, that is, the method further includes the following steps S202-S203.

[0135] S202, other nodes or functions send a service registration request message to the first network element, and correspondingly, the first network element receives the service registration request message from other nodes or functions. The service registration request message is used to request the definition or registration of the first service. The definition or registration of the first service can be understood as: arranging the network service called by the first service, that is, determining the network service called when executing the first service and the calling logic of the network service (also referred to as the execution method of the first service). Optionally, the service registration request message carries relevant information of the first service.

[0136] Exemplarily, other nodes or functions may be terminal equipment, an operator's operation and maintenance management system, a third-party application server, a network function, or a wireless access network function, etc., which is not limited in this application. It should be understood that the other nodes or functions here include the service requester in step S210.

[0137] S203, the first network element sends a service registration response message to other nodes or functions, the service registration response message is used to indicate the registration result of the first service, the registration result includes registration success or registration failure. Optionally, the service registration response message includes the registration result.

[0138] It should be understood that the embodiment of the present application is performed when the first service is successfully registered. At this time, other nodes or functions support the use of the first service.

[0139] In the embodiment of the present application, the execution subject of the orchestration of the network service called by the first business may be the first network element, or other nodes or functions, and the specific implementation methods may refer to the following methods 1 and 2. Among them, in method 1, the orchestration of the network service is performed by other nodes or functions, and in method 2, the orchestration of the network service is performed by the first network element.

[0140] Method 1:

[0141] Exemplarily, other nodes or functions notify the first network element of the customized arrangement of the network service called when executing the first service through the service registration request message of step S202. At this time, the service registration request message may include one or more of the following information:

[0142] (1) Relevant information of the first service, for which the specific content and interpretation can be found in the relevant description of the above step S210;

[0143] (2) information about the network service (NF Service) or network service instance (NF Service Instance) called when executing the first service, such as the identifier and / or address information of the network service;

[0144] Exemplarily, assuming that the first service is a PDU session establishment service, the network service called when executing the PDU session establishment service includes obtaining the UE's session subscription information, obtaining the UE's session policy information, and establishing an end-to-end communication channel for the UE (i.e., the connection between UE-RAN-UPF-DN). Correspondingly, the network service instance (or network function NF) can be UDM, PCF, SMF, etc.

[0145] (3) The triggering condition of the first service includes one or more of the following:

[0146] a) Service request message; for example, when the second network element receives a service request message for a first service, it may trigger execution of the first service.

[0147] b) Related information of the first service; for example, when the second network element receives related information for the first service (for example, the identifier or name of the first service), it can trigger the execution of the first service.

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

[0149] 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.

[0150] It should be understood that the above-mentioned triggering of executing the first service can be understood as: the second network element sends a service request message to the third network element to request the execution of the first service, that is, the second network element can request the third network element to execute the first service based on the above-mentioned triggering conditions, or in other words, in response to the above-mentioned triggering conditions, the second network element can request the third network element to execute the first service.

[0151] Method 2:

[0152] Exemplarily, other nodes or functions request the first network element to orchestrate the network service called by the first service. For example, the first network element may make a selection 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 for orchestration based on the input parameters of the first service. After the orchestration is completed, in response to the service registration request message of step S202, the first network element may carry the identifier or name of the first service in the service registration response message of step S203 above and send it to other nodes or functions to indicate that the definition or registration of the first service has been completed.

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

[0154] (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.

[0155] (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.

[0156] (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.

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

[0158] Optionally, the service registration response message may also carry one or more of the following information, for which specific explanations can be found in the related descriptions of the above steps S210 and S203.

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

[0160] (2) Address information, API, FQDN, etc. of the first service;

[0161] (3) triggering condition of the first service;

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

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

[0164] 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.

[0165] Table 1

[0166]

[0167]

[0168] 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 relevant description of the above step S203 and will not be described here.

[0169] Optionally, in the above steps S202-S203, other nodes or functions may send a service registration request message to the first network element through a third network element. It should be understood that necessary processing may be performed between the source end and the destination end of the service registration request information, such as format changes, but the destination end can obtain and parse valid information from the source end. Exemplarily, other nodes or functions send a service registration request message #1 to the third network element, and then the third network element sends a service registration request message #2 to the third network element after receiving the service registration request message #1, wherein the service registration request message #1 and the service registration request message #2 are both used to request registration of the first service. Correspondingly, the first network element sends a service registration response message #2 to the third network element, and then the third network element sends a service registration response message #1 to other nodes or functions after receiving the service registration response message #2, wherein the service registration response message #1 and the service registration response message #2 are both used to indicate the registration result of the first service.

[0170] In an embodiment of the present application, the third network element may or may not have a binding relationship with the first service. For example, when the third network element has a binding relationship with the first service, the above-mentioned registration request message #2 may carry information about the third network element, such as the identifier and / or address information of the third network element. Correspondingly, the first network element saves the correspondence between the information of the third network element and the relevant information of the first service, that is, the first network element maintains (or saves) the correspondence. In other words, the registration and discovery of the third network element are completed by the first network element. Optionally, in actual deployment, the registration and discovery of the third network element may also be completed by other functions (or network elements), such as Figure 1 The NRF shown, or other network functions with service management and maintenance NF capabilities, is not limited in this application.

[0171] The binding relationship between the information of the third network element and the relevant information of the first service is described below, for example, including one or more of the following:

[0172] (1) A third network element (e.g., service control (SC)) with a granularity of network function or network service instance; for example, AMF-SC corresponding to AMF, indicating that the correspondence can be one-to-one; or {AMF / SMF / PCF}-SC corresponding to AMF / SMF / PCF, indicating that the correspondence can be many-to-one;

[0173] (2) SCs based on business or network services; for example, SCs corresponding to session establishment services, SCs corresponding to registration services, SCs corresponding to positioning services, SCs corresponding to computing services, SCs corresponding to data compression services, etc.

[0174] (3) SCs at slice or network granularity, such as SCs corresponding to network slices, SCs corresponding to subnetworks, or SCs corresponding to PLMNs;

[0175] (4) SC based on user granularity, such as SC corresponding to user number segment;

[0176] (5) SCs with different geographical locations / regions as granularity, such as SCs corresponding to region 1, SCs corresponding to region 2, etc.

[0177] It should be understood that the correspondence between the information of the third network element and the first service is only an example given for ease of understanding and does not constitute any limitation on the technical solution of the present application. Based on the correspondence between the information of the third network element and the first service, the technical solution of the present application supports providing the first service to the service requester (such as UE) in a specific area, slice, or subnet on demand, and flexibly deploying the third network element on demand to achieve control of the first service.

[0178] S220, the second network element sends a second service request message to the third network element, and the third network element receives the second service request message from the second network element.

[0179] It should be understood that the first service request message of the above step S210 and the second service request message of step S220 may be the same or different. For example, after receiving the first service request message, the second network element may perform necessary processing on the first service request message, such as format change, etc., to obtain the second service request message. However, the first service request message and the second service request message have the same functions, that is, the second service request message is used to request the execution of the first service.

[0180] Optionally, the content and interpretation of the second service request message may refer to the relevant description of step S210. Optionally, the second service request message may also explicitly or implicitly indicate the first service, and the details may refer to the relevant description of the first service request message.

[0181] In an example, the second network element may trigger the execution of the first service when the triggering condition of the first service is met. That is, when the triggering condition of the first service is met, the second service request message is sent to the third network element.

[0182] In a possible implementation, before executing step S220, the second network element obtains the triggering condition of the first service, that is, the method further includes the following step S204.

[0183] S204: The second network element obtains a triggering condition for the first service.

[0184] The content and interpretation of the triggering condition of the first service may refer to the relevant description of the above step S203.

[0185] In an example, the second network element may obtain the triggering condition of the first service from the first network element.

[0186] Exemplarily, the first network element sends configuration information to the second network element, and correspondingly, the second network element receives the configuration information from the first network element, and the configuration information includes the triggering condition of the first service. Optionally, before the second network element receives the configuration information from the first network element, the method also includes: the second network element sends a request message to the first network element to request to obtain the triggering condition of the first service. That is, the triggering condition of the first service can be actively sent by the first network element, or it can be sent by the first network element based on the request of the second network element, and this application does not limit this.

[0187] In a possible implementation, before executing step S220, the second network element determines information of a third network element that supports the first service, that is, the method further includes the following step S205.

[0188] S205, the second network element obtains information of the third network element, for example, identification and / or address information of the third network element.

[0189] In one example, the second network element may obtain information about the third network element from the first network element. For example, the second network element sends a query message to the first network element, and correspondingly, the first network element receives the query message from the second network element. The query message is used to obtain information about the third network element that supports the first service. The third network element that supports the first service can be understood as: the third network element has the function or ability to perform the first service. Further, the first network element may send information about the third network element to the second network element based on the correspondence between the above-mentioned stored information about the third network element and the relevant information about the first service.

[0190] Exemplarily, the query message may include one or more of the following:

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

[0192] (2) Information about the party requesting the service;

[0193] (3) Service location information, such as service location information supported by the third network element;

[0194] (4) Network information, such as the network information where the third network element is located (such as PLMN ID, slice information, data network name (DNN), etc.).

[0195] The contents and interpretations of (1) and (2) can be found in the relevant description of step S201 above.

[0196] Optionally, the query message may explicitly or implicitly indicate the first service. For example, the query message carries an identifier or name of the first service, or the query message itself may indicate the first service, in which case the query message may not carry relevant information about the first service. For example, the query message may be a session establishment service query message, which is used to obtain information about a third network element that supports the session establishment service, in which case the query message may not carry relevant information about the session establishment service.

[0197] S230, the third network element obtains an execution method of the first service.

[0198] The execution method of the first service includes: the network service called when executing the first service and the calling logic of the network service. In this application, the calling logic of the network service can be understood as an execution rule, such as the calling order of multiple network services called when executing the first service, the calling result of calling the network service, or the processing method of the execution result of executing the first service.

[0199] In a possible implementation, the method for executing the first service further includes one or more of the following:

[0200] (1) Service policy, which is used to indicate the rules or restrictions of the network services provided by the NF, such as the QoS, charging rules, location restrictions, user information restrictions, etc. of the network services that the NF can provide.

[0201] (2) NF lifecycle management policy, which is used to indicate the status processing policy of the network services provided by the NF, such as the timing / conditions for launching or selecting a network service (or a network service instance), the timing / conditions for releasing or deleting a network service (or a network service instance), etc.

[0202] In one example, the third network element obtains the execution method of the first service from the first network element.

[0203] For example, the execution method of the first service may be dynamically configured (dynamically configured) by the first network element through signaling or messages, or it may be pre-configured (pre-configured), for example, it may be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate the execution method of the first service in a third network element. This application does not limit its implementation method.

[0204] For another example, the third network element sends a query message to the first network element to obtain the execution method of the first service, wherein the query message may include relevant information of the first service. Correspondingly, after receiving the query message from the third network element, the first network element sends the execution method of the first service to the third network element.

[0205] Optionally, the third network element may also obtain the first execution method from other network functions. For example, the third network element may obtain the execution method of the first service from the NRF. For the specific implementation method, refer to the relevant description of the third network element obtaining the execution method of the first service from the first network element. This application does not limit this.

[0206] 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 third network element can determine that the network services called when executing Service 1 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 NFService_2.

[0207] For example, the third network element may 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 may carry the call sequence 1, the service input parameter A1 (e.g., information of the service requester, relevant information of the first service, expected service quality parameters, etc.) and the sending address of the execution result NFService_1_2 or GW. Then, after NF Service_1_1 calls NF Service_1, the execution result #1 may be obtained to indicate whether the call of NF Service_1 is successful. Further, NF Service_1_1 may send a service call request message #b to NF Service_1_2 or GW according to the sending address of the execution result to request NF Service_1_2 to call NFService_2. The service call request message #b may carry the execution result #1, the call sequence 2, the service input parameter A2 (e.g., information of the service requester, relevant information of the first service, expected service quality parameters, etc.) and the sending address of the execution result the third network element or GW. Then, after NF Service_1_2 calls NF Service_2, the execution result #2 may be obtained to indicate whether the call of NF Service_2 is successful. Further, NF Service_1_2 can send execution result #1 and execution result #2 to the third network element or GW according to the sending address of the execution result. Optionally, NF Service_1_2 can combine execution result #1 and execution result #2 to obtain execution result #3, and send execution result #3 to the third network element or GW. If NF Service_1_2 sends execution result #1 and execution result #2 (or execution result #3) to GW, GW also needs to further send execution result #1 and execution result #2 (or execution result #3) to the third network element, thus completing the execution operation of the first service.

[0208] Table 2

[0209]

[0210] 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.

[0211] S240: The third network element executes the first service according to the execution method of the first service.

[0212] Exemplarily, the third network element may select NF resources in a suitable location or area to pull up or select based on one or more of the information such as location / slice, cold start and hot start of NF resources, and load conditions of NF. For example, for the execution of the first service, the third network element selects to pull up or select the first network service and the second network service according to the execution method of the first service, and determines that the first network function supports calling the first network service, and the second network function supports calling the second network service. Optionally, the first network function and the second network function may be UE, or NF, or AF, or RAN, which is not limited in this application. In 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.

[0213] Optionally, before the third network element pulls up or selects the first network service and the second network service, the third network element may obtain the code or image of the network service instance called by the first service from the code library / image library, and then run it in an environment (such as a virtual machine, container, etc.) that can run the code or image, and use the network service provided by the network service instance. Figure 1 Related functions of UDM / UDR in the architecture.

[0214] Below, taking the network services called when the third network element executes the first service as an example, including the first network service and the second network service, the specific implementation method for the third network element to execute the first service according to the execution method of the first service is described, including the following method one or method two. Among them, in method one, the first network function and the second network function can exchange information, and the two can be activated and / or released at the same time. In method two, the address information of the network function is maintained by the second network element (for example, GW), that is, the addressing between the first network function and the second network function is routed through the second network element, and the information forwarding function between the first network function and the second network function is supported. That is, the first network function and the second network function do not need to be activated and / or released at the same time, that is, the first network function can be released after executing step S218, and the second network function can be released after executing step S222. This application does not limit this.

[0215] Method 1:

[0216] S206, the third network element sends configuration information #1 to the first network function, and correspondingly, the first network function receives configuration information #1 from the third network element, wherein the configuration information #1 is used to indicate address information of the second network function, and the address information of the second network function is used by the first network function to determine the next hop node, that is, the second network function that supports calling the second network service.

[0217] Optionally, the configuration information #1 may also be used to indicate complete path information, that is, address information of a first network function and address information of a second network function corresponding to the first network service and the second network service called when executing the first service.

[0218] S207, the third network element sends configuration information #2 to the second network function, and correspondingly, the second network function receives configuration information #2 from the third network element, wherein the configuration information #2 is used to indicate the address information of the first network function, and the address information of the first network function is used by the second network function to determine the previous hop node, that is, the first network function that supports calling the first network service.

[0219] S208, the third network element sends a service call request message #1 to the first network function according to the execution method of the first service, and correspondingly, the first network function receives the service call request message #1 from the third network element, wherein the service call request message is used to request to call the first network service.

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

[0221] S211, the first network function sends a service call request message #2 to the second network function according to the address information of the second network function, and correspondingly, the second network function receives the service call request message #2 from the first network function, wherein the service call request message #2 is used to request to call the second network service.

[0222] S212, the second network function calls the second network service and sends a service call response message #2 to the first network function. Correspondingly, the first network function receives the service call response message #2 from the second network function, wherein the service call response message #2 includes an execution result #2, which is used to indicate whether the second network service is successfully called, or is the output result of calling the second network service.

[0223] S213, the first network function sends a service call response message #1 to the third network element, and correspondingly, the third network element receives the service call response message #1 from the first network function. The service call response message #2 includes an execution result #1 and an execution result #2, and 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.

[0224] Optionally, execution result #1 and execution result #2 can be combined into execution result #3, and service call response message #2 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.

[0225] Optionally, the present application does not limit the order of executing the above steps S206 and S207, or S206 and S208, or S207 and S211.

[0226] Optionally, the configuration information #1 and the service call request message #1 in the above steps S206 and S208 can be sent simultaneously or separately, can be carried in two independent messages or carried in the same message, and this application does not limit this. The relevant descriptions of the configuration information #2 and the service call request message #2 in the above steps S207 and S211 are similar and will not be repeated here.

[0227] Optionally, the network service called by the third network element when executing the first service may also include a third network service, wherein the third network function supports calling the third network service, and the third network element may send configuration information #a to the second network function to indicate the address information of the third network function. After the second network function calls the second network service, a service call request message #a may be sent to the third network function according to the address information of the third network function to request the third network function to call the third network service. Further, after the third network function calls the third network service, an execution result #a may be sent to the second network function to indicate whether the third network service is successfully called. Subsequently, the second network function feeds back the execution result #a and the execution result #2 to the first network function, and the first network function feeds back the execution result #a, the execution result #2 and the execution result #1 to the third network element. The specific implementation method and the deformation of the execution result can refer to the above-mentioned related description.

[0228] Method 2:

[0229] S214, the third network element sends configuration information #3 to the second network element, and correspondingly, the second network element receives configuration information #3 from the third network element, wherein the configuration information #3 is used to indicate address information of the second network function, and the address information of the second network function is used by the second network element to determine the second network function that supports calling the second network service.

[0230] S215. The second network element stores address information of the second network function.

[0231] S216, the third network element sends a service call request message #3 to the first network function according to the execution method of the first service, and the first network function receives the service call request message #3 from the third network element, wherein the service call request message #3 is used to request the first network function to call the first network service.

[0232] S217: The first network function calls the first network service.

[0233] S218, the first network function sends a service call request message #4 to the second network element, and correspondingly, the second network element receives the service call request message #4 from the first network function, wherein the service call request message #4 is used to request to call the second network service.

[0234] S219, the second network element sends a service call request message #5 to the second network function according to the address information of the second network function, and correspondingly, the second network function receives the service call request message #5 from the second network element, wherein the service call request message #5 is used to request to call the second network service.

[0235] S221: The second network function calls the second network service.

[0236] S222, the second network function sends a service call response message #5 to the second network element, and correspondingly, the second network element receives the service call response message #5 from the second network function. The service call response message #5 includes an execution result #4, which is used to indicate whether the second network service is successfully called, or is an output result of calling the second network service.

[0237] S223, the second network element sends a service call response message #4 to the first network function, and correspondingly, the first network function receives a service call response message #4 from the second network element, wherein the service call message #4 includes an execution result #4.

[0238] S224, the first network function sends a service call response message #3 to the third network element, and correspondingly, the third network element receives the service response message #3 from the first network function, wherein the service response message #3 includes an execution result #4 and an execution result #5, and the execution result #5 is used to indicate whether the first network service is successfully called, or is the output result of calling the first network service.

[0239] Optionally, execution result #4 and execution result #5 can be combined into execution result #6, and in this case, service call response message #3 includes execution result #6. For example, if execution result #4 indicates that the first network service call is successful, and execution result #5 indicates that the second network service call is successful, then execution result #6 indicates that the first service is successfully executed; for another example, if execution result #4 indicates that the first network service call fails, and / or execution result #5 indicates that the second network service call fails, then execution result #6 indicates that the first service fails.

[0240] Optionally, the above steps S214-S215 can be executed before step S219, for example, after step S217 or S218, and the present application does not limit the order of execution.

[0241] Optionally, if there are multiple identical network services during the execution of the first service, the third network element may send a network service selection rule / policy to the second network element for the second network element to select the network service. For example, each network service in the network service selection rule / policy is associated with one or more of the following information: network information (such as PLMNID, slice information, DNN, etc.), service information (such as AF ID, application identity (APP ID), etc.), supported user information (such as UE ID, SUPI, generic public subscription identifier (GPSI)), location information (such as tracking area identity (TAI), cell identity (such as cell ID), etc.).

[0242] Optionally, if there are multiple network functions that support calling the same network service, the third network element may also send the load information of the multiple network functions to the second network element for load balancing. In other words, the second network element may select a suitable network function to provide the network service according to the load conditions of the multiple network functions, so that the first service can be executed normally and the user service experience is guaranteed.

[0243] Optionally, the network service called by the third network element when executing the first service may also include a third network service, wherein the third network function supports calling the third network service, and the third network element may also send configuration information #b to the second network element to indicate the address information of the third network function, and correspondingly, the second network element saves the address information of the third network function. Optionally, configuration information #3 and configuration information #b may be the same configuration information or different configuration information. For example, after the second network function calls the second network service, the above-mentioned execution result #4 and service call request message #b may be sent to the second network element, and the service call request message #b is used to request to call the third network service, and the second network element sends a service call request message #c to the third network function according to the saved address information of the third network function, for requesting the third network function to call the third network service. Furthermore, after the third network function calls the third network service, an execution result #b is sent to the second network element to indicate whether the third network service is called successfully. Subsequently, the second network element feeds back execution result #b and execution result #4 to the first network function, and the first network function feeds back execution result #b, execution result #4 and execution result #5 to the third network element. The specific implementation method and the deformation of the execution result can be referred to the above related description.

[0244] Optionally, the third network element may configure the network service called by the first service and its calling logic for the network service to the second network element. For example, after receiving the execution result of the second network function, the second network element initiates a service calling request for the third network service to the third network function according to the calling logic of the network service.

[0245] Optionally, the configuration information #1 and / or configuration information #2 in the above-mentioned method 1, and the configuration information #3 in the above-mentioned method 2 may further include one or more of the following:

[0246] (1) Service call logic of the first business.

[0247] For example, the third network element may configure all the calling logics of the first network service and the second network service called when executing the first service to the first network function, the second network function, and the second network element;

[0248] (2) The execution rules of the current network service and the service calling logic of the next one or more network services, that is, the third network element can only configure the execution rules of the current network service and the service calling logic of the next one or more network functions to the current network function.

[0249] For example, for configuration information #1, the first network function can obtain the execution rules of the first network service and the service call logic of the second network service. Optionally, if the above-mentioned network function that supports calling the second network service is also the first network function, it means that the third network element can configure the execution rules of the first network function and the service call logic of the second network function to the first network function, and then the first network function can continue to call the second network service according to the service call logic of the second network service after calling the first network service. Further optionally, if the network service called when executing the first business also includes the third network service, and the first network function still supports calling the third network service, it means that the third network element can configure the execution rules of the first network function and the service call logic of the second and third network functions to the first network function, and then the first network function can call the second and third network services in sequence according to the service call logic of the second and third network services after calling the first network service, and so on.

[0250] (3)Exception handling methods.

[0251] Exemplarily, the method of abnormal handling is determined based on a timer or event trigger. For example, after the first network function sends a call request message for the second network service to the second network function, it can start a timer. If the execution result of the second network function calling the second network service is not received when the timer expires, the first network function can report the failure of the first service execution to the third network element, or the first network function can resend the call request message for the second network service to the second network function; for another example, 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 first network function can report the location update message of the terminal device to the third network element, or notify the service requester and the first network element to stop the execution of the first service, etc.

[0252] (4) Rules for executing the first business.

[0253] Exemplarily, the execution rule of the first service may be a log reporting rule or a service quality rule, etc. For example, it is 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 need 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.

[0254] S250, the third network element sends a second service response message to the second network element, and the second network element receives the second service response message from the third network element. The second service response message is used to indicate the execution result of the first service, and the execution result includes execution success or execution failure, which can also be understood as the success or failure of the call of the first network service and the second network service. Alternatively, the second service response message can also be used to indicate the output result of executing the first service, for example, for a positioning service, the output result can be location information, such as coordinate information.

[0255] S260, the second network element sends a first service response message to the service requester, and the service requester receives the first service response message from the second network element. The first service response message is used to indicate the execution result of the first service, and the specific interpretation can refer to the relevant description of step S250.

[0256] It should be understood that the above steps S250-S260 can be regarded as the third network element indirectly sending the execution result of the first service to the first network element through the second network element. Optionally, the third network element can also directly send the execution result of the first service to the first network element, which is not limited in this application.

[0257] It should also be understood that, taking the case where the network services called when executing the first business are the first network service and the second network service, the execution result of the first business in the above steps S250-S260 can be execution result #1 and execution result #2, or execution result #3 in the above method one; or, it can also be execution result #4 and execution result #5, or execution result #6 in the above method two, and this application does not limit this.

[0258] Optionally, during the execution of the first service, the first network element and / or the third network element may create and maintain context information of the first service to facilitate management and control of the first service in the current network, that is, the method further includes the following method 1 and method 2. In method 1, the first network element creates and maintains the context information of the first service, and in method 2, the third network element creates and maintains the context information of the first service.

[0259] Method 1:

[0260] S222, the third network element sends a notification message to the first network element, and correspondingly, the first network element receives the notification message from the third network element.

[0261] The notification message includes relevant information of the first service (eg, an identifier or name ServiceID / name of the first service), and the notification message is used to request the first network element to create context information of the first service.

[0262] Optionally, the network (e.g., the third network element) can provide the first service for different service requesters, and then the network can allocate a service granularity identifier to each service requester using the first service to distinguish information of different service requesters. Therefore, the notification message can also include a service session identifier (Service Session ID), a transaction identifier (transaction ID), or a service flow identifier (Service flow ID), etc.

[0263] S223: The first network element creates context information of the first service according to the notification message.

[0264] Method 2:

[0265] S224, the third network element creates context information of the first service;

[0266] S225, the third network element sends the context information of the first service to the first network element, and correspondingly, the first network element supports receiving the context information of the first service from the third network element.

[0267] 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.

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

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

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

[0271] (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;

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

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

[0274] (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.

[0275] (8) information about a network function corresponding to the first service: for example, 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;

[0276] (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.

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

[0278] The first network element or the third network element creating the context information of the first service can be understood as storing the context information of the first service to achieve management and control of the first service.

[0279] In one possible implementation, during the execution of the first service, relevant information of the first service may change. Therefore, the first network element, the second network element, or the network function supporting the network service needs to promptly update the information associated with the first service to facilitate the network's management and control of the first service. That is, the method also includes the following steps S226-S227.

[0280] S226, the third network element sends an update message to the first network element / network function NF / second network element, and correspondingly, the first network element / network function NF / second network element receives an update message from the third network element, wherein the update message is used to update the relevant information of the first service. The relevant information of the first service can refer to the relevant description of the above step S210.

[0281] Exemplarily, for the identification information of the first service, the update message can be used to indicate that the identification of the first service is changed from Service ID#1 to Service ID#2, and Service ID#2 can be carried in the update message; or, when the first service is deregistered, the update message is used to indicate the deletion of relevant information of the first service.

[0282] Exemplarily, with respect to the information of the service requester that supports or requests the use of the first service (such as the identification and / or address information of the UE / AF / NF), if the NF no longer supports the use of the first service, the update message can be used to indicate the deletion of the NF information; if UE#1 that supports the use of the first service is changed to UE#2, the update message can be used to indicate the change of the UE information; if newly added operation administration and maintenance (OAM) supports the use of the first service, the update message can be used to indicate the addition of OAM information.

[0283] Optionally, the relevant information of the first service may further include one or more of the following:

[0284] (1) the method for executing the first business;

[0285] Exemplarily, to better meet user service requirements, if a third network service is added to the network service called by the first service, the update message may carry information of the third network service and the service calling logic of the third network service.

[0286] (2) Information about network service instances or network functions that support network services (e.g., identification and / or address information of network functions);

[0287] Exemplarily, based on the above (1), the update message may carry an identifier and / or address information of a third network function, and the third network function supports calling a third network service.

[0288] (3) Context information of the first service, the contents and interpretation of which can be referred to the relevant description of the above step S225.

[0289] (4) Policy information and / or contract information associated with the first service.

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

[0291] (5) Processing NF resources based on the status of the user or the first service, such as processing related to user mobility management and NF switching caused by UE switching;

[0292] (6) Dynamic NF resource management. For example, when the execution of the first service involves multiple NFs, different types of NFs may require different times to execute the corresponding network services. Therefore, each NF needs to be managed independently in its life cycle.

[0293] S227, the first network element / network function NF / second network element updates relevant information of the first service.

[0294] In the present application, update can be understood as change, addition or deletion. If the relevant information of the first service needs to be changed, the update message can carry the relevant information of the updated first service.

[0295] In the first example, during the execution of the first service, if it is found that the network service is unreachable (for example, NF fails, NF load is saturated, etc.), the terminal device moves causing the network function or network service to switch, etc., the third network element can send an update message to the second network element to request the second network element to change or delete the NF information.

[0296] In the second example, when the NF calls a network service, if a service abnormality is found (for example, the service policy of the NF changes, the service quality cannot be guaranteed, or the service quality cannot meet the needs of the first service, etc.), the third network element can send an update message to the network function supporting the network service to request the network function to change or release the NF resources, including: extending the activation time of the NF or releasing NF resources based on the NF lifecycle management policy, or starting a timer during the execution of the first service, and releasing the NF resources or ending the execution of the first service when the timer expires or times out.

[0297] In the third example, when one or more of the relevant information of the above-mentioned first service changes, for example, during the execution of the first service, the policy information and / or contract information associated with the first service changes, the third network element can send an update message to the first network element to request the first network element to update the policy information and / or contract information associated with the first service.

[0298] According to the solution provided in the present application, based on the design concept of dynamic network functions, a registration mechanism for the first service is introduced, that is, the first network element supports the registration or definition of the first service or the network service called when executing the first service, can flexibly configure the calling logic of the network service, provides life cycle management of the network service for the first service, improves the utilization rate of network resources, supports the execution of the first service on demand, reduces the network operation and maintenance costs, and realizes flexible and lightweight network deployment and management.

[0299] Figure 3 3 is a flow chart of the communication method 300 provided in the embodiment of the present application. Figure 3 As shown, the first network element is a service management function, the second network element is a gateway GW, and the third network element is a service control 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 Figure 3 No more details.

[0300] S301, OAM / UE / NF / AF sends a service registration request message to a service management function, and correspondingly, the service management function receives the service registration request message from OAM / UE / NF / AF. The service registration request message is used to request definition or registration of a first service.

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

[0302] S302, the service management function sends configuration information to the GW, and correspondingly, the GW receives the configuration information from the service management function, wherein the configuration information is used to configure the triggering condition of the first service.

[0303] The content, interpretation, and specific implementation of the configuration information may refer to the relevant description of step S204 of the above method 200.

[0304] S303, UE / NF / AF sends a service request message #1 to GW, and correspondingly, GW receives the service request message #1 from UE / NF / AF.

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

[0306] S304, GW selects a service control function.

[0307] Optionally, the GW may send a query message to the service management function to obtain information about the service control function, such as an identifier of the service control function or an address of the service control function. It should be understood that if the service management function maintains a service context corresponding to the service identifier / name, the service management function may feed back information about the service control function supporting provision of the first service in the service context to the GW. For specific implementation methods, reference may be made to the description of step S205 of the above method 200.

[0308] S305, the GW sends a service request message #2 to the service control function, and correspondingly, the service control function receives the service request message #2 from the GW.

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

[0310] S308: The service control function starts or selects a network service according to the execution method of the first service.

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

[0312] It should be understood that in the embodiments of the present application, pulling up can be understood as activation, and selecting can be understood as selecting an already activated one. For example, pulling up a network service can be activating a network service, and selecting a network service can be selecting an already activated network service. Optionally, pulling up can also be understood as a cold start, and selecting can also be understood as a hot start.

[0313] Optionally, before executing step S308, the service control function obtains an execution method of the first service.

[0314] For example, the execution method of the first service may be configured by the service management function or pre-configured to the service control function.

[0315] For example, if the service control function does not have the execution method of the first service locally, the service control function requests the service management function to obtain the execution method of the first service, that is, executes steps S306 and S307.

[0316] S306, the service control function sends a query message to the service management function, and correspondingly, the service management function receives the query message from the service control function network, wherein the query message is used to obtain the execution method of the first service.

[0317] S307: The service management function sends the execution method of the first service to the service control function.

[0318] For the specific implementation of the above steps S306 and S307, please refer to the relevant description of step S230 of the above method 200.

[0319] Optionally, during the execution of the first service, the service control function or the service management function may create context information of the first service, that is, execute steps S309 - S311 or steps S312 - S313 .

[0320] S309: The service control function creates context information of the first service.

[0321] S310: The service control function sends context information of the first service to the service management function. Correspondingly, the service management function receives the context information of the first service from the service control function.

[0322] S311: The service management function saves context information of the first service.

[0323] S312, the service control function sends a notification message to the service management function, and the service management function receives the notification message from the service control function, wherein the notification message is used to notify the service management function to create context information of the first service.

[0324] S313: The service management function creates context information of the first service.

[0325] The interpretation of the context information of the first service and the specific implementation of the above steps S309-S311 or steps S312-S313 may refer to the relevant description of steps S222-S223 or steps S224-S225 of the above method 200.

[0326] Figure 3 In the scheme shown, a business management function is introduced to register or define the first business or the network service called when executing the first business, supports flexible configuration of the calling logic of the network service, and provides life cycle management of the network service for the first business. At the same time, a gateway is introduced to support on-demand selection of a service control function, and requests the service control function to execute the first business, thereby improving network resource utilization and realizing flexible and lightweight network deployment and management.

[0327] 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 a gateway GW, and the third network element is a service control function. 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 and Figure 3 There may be the same or similar technical means between them. Figure 2 and Figure 3 The contents described in the embodiment shown are Figure 4 No more details.

[0328] S401, OAM / UE / NF / AF sends a service registration request message #1 to the service control function, and correspondingly, the service control function receives the service registration request message #1 from OAM / UE / NF / AF.

[0329] S402, the service control function sends a service registration request message #2 to the service management function, and correspondingly, the service management function receives the service registration request message #2 from the service control function.

[0330] S403: The service management function saves the corresponding relationship between the service control function and the first service.

[0331] Among them, the service registration request message #1, service registration request message #2, the content and interpretation of the corresponding relationship in the above steps S401-S403, and the specific implementation method can refer to the relevant description of step S202 of the above method 200.

[0332] S404, UE / NF / AF sends a service request message #1 to GW, and correspondingly, GW receives the service request message #1 from UE / NF / AF.

[0333] S405, the GW sends a query message to the service management function, and correspondingly, the service management function receives the query message from the GW.

[0334] S406, the business management function sends information of the service control function to the GW, and correspondingly, the GW receives information of the service control function from the business management function.

[0335] S407, the service management function sends a service request message #2 to the service control function, and correspondingly, the service control function receives the service request message #2 from the service management function.

[0336] S408: The service control function starts or selects a network service according to the execution method of the first service.

[0337] S409: The service control function creates context information of the first service.

[0338] S410: The service control function sends context information of the first service to the service management function. Correspondingly, the service management function receives the context information of the first service from the service control function.

[0339] S411: The service management function saves context information of the first service.

[0340] S412, the service control function sends a notification message to the service management function, and the service management function receives the notification message from the service control function, wherein the notification message is used to instruct the service management function to create context information of the first service.

[0341] S413: The service management function creates context information of the first service.

[0342] The interpretation of the parameters involved in the above steps S404-S408, S409-S413, and the specific implementation methods may refer to the relevant descriptions of steps S303-S308, S309-S313 of the above method 300.

[0343] Figure 4In the scheme shown, a business management function is introduced to register or define the first business or the network service called when executing the first business, supports flexible configuration of the calling logic of the network service, and provides life cycle management of the network service for the first business. At the same time, the business management function supports the registration and discovery of the service control function, and saves the correspondence between the service control function and the first business. It supports the design of corresponding service control functions for different business objects, provides network services at different levels, reduces the management complexity during network operation and maintenance, and provides more accurate services.

[0344] 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, taking the third network element as a service control function as an example, a first implementation method for executing the first service is provided, and the network services called by the service control function when executing the first service are network service #1 and network service #2 as an example for explanation. This method can be regarded as a further refinement of step S308 of the above method 300 or step S408 of method 400. The method includes the following multiple 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 Figures 2 to 4 There may be the same or similar technical means between them. Figures 2 to 4 The contents described in the embodiment shown are Figure 5 No more details.

[0345] S501, the service control function receives a service request message.

[0346] For example, for the specific implementation, please refer to the relevant description of step S305 of the above method 300 or step S407 of the above method 400.

[0347] Exemplarily, the service request message may include parameters supporting the invocation of network service #1, such as the identifier and / or address information of NF #1.

[0348] S502: The service control function obtains the code or image of the network service instance called by the first service.

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

[0350] S503: The service control function starts or selects network service #1 and network service #2 called by the first service.

[0351] S504: The service control function creates context information of the first service.

[0352] For the content and interpretation of the context information of the first service, as well as the specific implementation method, please refer to the relevant description of steps S309 to S313 of the above method 300.

[0353] S505, the service control function sends configuration information #1 to NF#1, and correspondingly, NF#1 receives the configuration information #1 from the service control function.

[0354] S506, the service control function sends configuration information #2 to NF#2, and correspondingly, network service #2 receives configuration information #2 from the service control function.

[0355] S507, the service control function sends a service invocation request message #1 to NF#1, and correspondingly, network service #1 receives the service invocation request message #1 from the service control function.

[0356] S508, NF#1 sends a service invocation request message #2 to NF#2, and correspondingly, NF#2 receives the service invocation request message #2 from NF#1.

[0357] S509, NF#2 sends a service invocation response message #2 to NF#1, and correspondingly, NF#1 receives the service invocation response message #2 from NF#2.

[0358] S510, NF#1 sends a service invocation response message #1 to the service control function, and correspondingly, the service control function receives the service invocation response message #1 from NF#1.

[0359] Among them, the contents and interpretations of the configuration information #1, configuration information #2, service call request message #1, service call request message #2, service call response message #1 and service call response message #2 involved in the above steps S505-S510, as well as the specific implementation methods can refer to the relevant description of method 1 of step S240 of the above method 200.

[0360] Figure 5 In the scheme shown, the service control function can dynamically pull up or select network services based on a trigger mechanism, so that different network functions can call corresponding network services respectively, realize the service control function to manage the life cycle of network services, improve network resource utilization, reduce network operation and maintenance costs, and realize flexible and lightweight network deployment and management.

[0361] Figure 6 The flow chart of the communication method 600 provided in the embodiment of the present application is as follows. Figure 6As shown, taking the third network element as a service control function as an example, a second implementation method for executing the first service is provided, and the network services called by the service control function when executing the first service are network service #1 and network service #2 as an example for explanation. This method can be regarded as a further refinement of step S308 of the above method 300 or step S408 of the method 400, and is parallel to the scheme of the above method 500. The method includes the following multiple steps. It should be understood that Figure 6 The method 600 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 6 and Figures 2 to 5 There may be the same or similar technical means between them. Figures 2 to 5 The contents described in the embodiment shown are Figure 6 No more details.

[0362] S601, the service control function receives a service request message.

[0363] S602: The service control function obtains the code or image of the network service instance called by the first service.

[0364] S603: The service control function starts or selects network service #1 and network service #2 called by the first service.

[0365] S604: The service control function creates context information of the first service.

[0366] For the service request message involved in the above steps S601-S604, the content and interpretation of the context information of the first service, and the specific implementation method, please refer to the relevant description of steps S501-S504 of the above method 500.

[0367] S605, the service control function sends configuration information to the GW, and correspondingly, the GW receives the configuration information from the service control function.

[0368] The configuration information is used to indicate the address of network service #2. In this implementation, the addressing between network service #1 and network service #2 is determined by routing through GW.

[0369] S606, GW saves the address information of NF#2.

[0370] S607, the service control function sends a service invocation request message #1 to NF#1, and correspondingly, NF#1 receives the service invocation request message #1 from the service control function.

[0371] S608, NF#1 sends a service invocation request message #2 to GW, and correspondingly, GW receives the service invocation request message #2 from NF#1.

[0372] S609, GW sends a service invocation request message #3 to NF#2 based on the address information of NF#2 maintained locally, and correspondingly, NF#2 receives the service invocation request message #3 from GW.

[0373] S610, NF#2 sends a service invocation response message #2 to GW, and correspondingly, GW receives the service invocation response message #2 from NF#2.

[0374] S611, GW sends a service invocation response message #2 to NF#1, and correspondingly, NF#1 receives the service invocation response message #2 from GW.

[0375] S612, NF#1 sends a service invocation response message #1 to the service control function, and correspondingly, the service control function receives the service invocation response message #1 from NF#1.

[0376] Among them, the content and interpretation of the configuration information, service call request message #1, service call request message #2, service call request message #3, service call response message #1, service call response message #2 and service call request message #3 involved in the above steps S605-S612, as well as the specific implementation methods can refer to the relevant description of method 2 of step S240 of the above method 200.

[0377] Figure 6 In the scheme shown, the service control function can dynamically pull up or select network services based on the trigger mechanism, and at the same time enhance the GW to maintain the address information and addressing logic of NF#2, so that different network functions can call the corresponding network services respectively, and realize the service control function to manage the life cycle of network services, improve the utilization of network resources, reduce the network operation and maintenance costs, and realize flexible and lightweight network deployment and management.

[0378] Figure 7 The flow chart of the communication method 700 provided in the embodiment of the present application is as follows. Figure 7 As shown, the first network element is a service management function, the second network element is a gateway GW, and the third network element is a service control function. This implementation method is described by example for the change of the relevant information of the first service during the execution of the first service by the service control function. The method includes the following steps. It should be understood that Figure 7 The method 700 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 7 and Figures 2 to 6 There may be the same or similar technical means between them. Figures 2 to 6 The contents described in the embodiment shown are Figure 7 No more details.

[0379] S701: The service control function obtains an execution method of a first service.

[0380] S702: The service control function starts network service #1 and network service #2 and starts executing the first service.

[0381] S703: Determine whether the relevant information of the first service is changed.

[0382] S704, the service control function sends an update message #1 to NF#1 and NF#2 to indicate information modification or release of the network service.

[0383] S705, the service control function sends an update message #2 to the GW to indicate the update or deletion of the NF information.

[0384] S706, the service control function sends an update message #3 to the service management function, which is used to instruct to update the context information of the first service.

[0385] Among them, the content and interpretation of update message #1, update message #2 and update message #3 involved in the above steps S701-S706, as well as the specific implementation method can refer to the relevant description of steps S226-S227 of the above method 200.

[0386] Figure 7 In the scheme shown, when executing the first service, the service control function can provide service-oriented network service lifecycle management by timely instructing the NF, service management function or GW to update relevant information of the first service to ensure user service experience.

[0387] Combination of the above Figures 1 to 7 The communication method embodiment of the present application is described in detail. Figures 8 to 9 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.

[0388] Figure 8 FIG. 8 is a schematic diagram of a communication device 800 provided in an embodiment of the present application. Figure 8As shown, the communication device 800 includes a processing module 801 and a communication module 802. The communication device 800 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 800 may be a second network element (e.g., a gateway), 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 800 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 800 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;

[0389] 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.

[0390] When the communication device 800 is applied to the first network element, the processing module 801 can be used to implement the processing function of the first network element in the above embodiments, and the communication module 802 can be used to implement the transceiver function of the first network element in the above embodiments.

[0391] When the communication device 800 is applied to the second network element, the processing module 801 can be used to implement the processing function of the second network element in the above embodiments, and the communication module 802 can be used to implement the transceiver function of the second network element in the above embodiments.

[0392] When the communication device 800 is applied to a third network element, the processing module 801 may be used to implement the processing function of the third network element in the above embodiments, and the communication module 802 may be used to implement the transceiver function of the third network element in the above embodiments.

[0393] When the communication device 800 is applied to a service requester, the processing module 801 may be used to implement the processing function of the service requester in the above embodiments, and the communication module 802 may be used to implement the sending and receiving function of the service requester in the above embodiments.

[0394] 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.).

[0395] 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.

[0396] Fig. 9 FIG. 9 is a schematic diagram of another communication device 900 provided in an embodiment of the present application. Fig. 9 As shown, optionally, the communication device 900 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.

[0397] The communication device 900 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 900 may include at least one processor 910. Optionally, the processor 910 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 900 may also include at least one memory 920. The memory 920 stores the necessary computer programs, computer programs or instructions and / or data for implementing any of the above examples; the processor 910 may execute the computer program stored in the memory 920 to complete the method in any of the above examples.

[0398] The communication device 900 may also include a communication interface 930, and the communication device 900 may exchange information with other devices through the communication interface 930. Exemplarily, the communication interface 930 may be a transceiver, a circuit, a bus, a module, a pin, or other types of communication interfaces. When the communication device 900 is a chip-type device or circuit, the communication interface 930 in the device 900 may also be an input-output circuit, which may input information (or receive information) and output information (or send information), and the processor 910 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.

[0399] 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 910 may cooperate with the memory 920 and the communication interface 930. The specific connection medium between the above-mentioned processor 910, memory 920 and communication interface 930 is not limited in this application.

[0400] Alternatively, if Fig. 9 As shown in , the processor 910, the memory 920 and the communication interface 930 are connected to each other via a bus 940. 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, Fig. 9 One bus 940 is shown, but this does not mean that there is only one bus or one type of bus.

[0401] 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.

[0402] 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).

[0403] 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.

[0404] 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.

[0405] 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, the second network element, the third network element or the service requester in the above-mentioned method embodiments are stored.

[0406] 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, the second network element, the third network element or the service requester in the above-mentioned method embodiments.

[0407] The embodiment of the present application further provides a communication system, the communication system comprising the first network element, the second network element, and the third network element in the above embodiments. Optionally, the communication system further comprises a service requester.

[0408] 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.

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

[0410] 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.

[0411] 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.

[0412] 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.

[0413] 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.

[0414] 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.

[0415] 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.

[0416] 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.

[0417] 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.

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

[0419] 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.

[0420] 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.

[0421] 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.

[0422] 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.

[0423] 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.

[0424] 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.

[0425] 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.

[0426] 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.

[0427] 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: Determining an execution method of the first business, the execution method including executing a network service called by the first business and a calling logic of the network service; The execution method is sent to a third network element, wherein the third network element supports the first service.

2. The method according to claim 1, characterized in that Before sending the execution method to the third network element, the method further includes: A first query message is received from the third network element, where the first query message is used to obtain an execution method of the first service, and the first query message includes an identifier of the first service.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: Send configuration information to the second network element, where the configuration information includes an identifier of the first service, and the configuration information is used to indicate a trigger condition for executing the first service.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: receiving a registration request message, where the registration request message is used to request registration of the first service; A registration response message is sent, where the registration response message is used to indicate a registration result of the first service.

5. The method according to claim 4, characterized in that The registration request message further includes information of the third network element, and the method further includes: The correspondence between the information of the third network element and the first service is saved.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: receiving a second query message from a second network element, where the second query message is used to obtain information about the third network element, and the second query message includes an identifier of the first service; According to the stored correspondence between the information of the third network element and the first service, the information of the third network element is sent to the second network element.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: receiving a notification message from the third network element, where the notification message includes an identifier of the first service, and the notification message is used to create context information of the first service; Creating context information of the first service; or, Receive context information of the first service from the third network element.

8. A communication method, characterized in that: include: receiving a first service request message, where the first service request message is used to request execution of a first service, and the first service request message includes an identifier of the first service; A second service request message is sent to a third network element, where the second service request message is used to request execution of the first service, and the third network element supports the first service.

9. The method according to claim 8, characterized in that The method further comprises: receiving configuration information from a first network element, where the configuration information is used to indicate a triggering condition of the first service, the configuration information includes an identifier of the first service, and the first network element supports management of the first service; The sending the second service request message to the third network element includes: When a trigger condition of the first service is met, the second service request message is sent to the third network element.

10. The method according to claim 8 or 9, characterized in that: Before sending the second service request message to the third network element, the method further includes: Sending a query message to the first network element, where the query message is used to obtain information about the third network element, where the query message includes an identifier of the first service, and the first network element supports management of the first service; The information of the third network element is received from the first network element.

11. The method according to any one of claims 8 to 10, characterized in that The network service called for executing the first service includes a first network service and a second network service, and the method further includes: receiving a first service invocation request message from a first network function, where the first service invocation request message is used to request invocation of the second network service, where the first network function supports invocation of the first network service, and the service invocation request message includes an identifier of the second network function supporting invocation of the second network service; Sending a second service invocation request message to the second network function according to the stored address information of the second network function, where the second service invocation request message is used to invoke the second network service; receiving a third execution result from the second network function; Sending the third execution result to the first network function.

12. The method according to claim 11, characterized in that Before sending the second service invocation request message to the second network function, the method further includes: receiving configuration information from the third network element, the configuration information including address information of the second network function; The address information of the second network function is saved.

13. The method according to any one of claims 8 to 12, characterized in that The method further comprises: An update message is received, where the update message is used to update relevant information of the first service.

14. The method according to claim 13, characterized in that The network service called for executing the first service includes a first network service and a second network service, and the relevant information of the first service includes one or more of the following: information of the first network service and / or the second network service; or, context information of the first service; or, The policy information and / or contract information associated with the first service.

15. A communication method, characterized in that: include: receiving a service request message, where 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; Acquire an execution method for the first business, the execution method including a network service called when executing the first business, and a calling logic of the network service; The first service is executed according to the execution method of the first service.

16. The method according to claim 15, characterized in that The method for obtaining the execution of the first service includes: Sending a query message to a first network element, where the query message is used to obtain an execution method of the first service, the query message includes an identifier of the first service, and the first network element supports management of the first service; A method for executing the first service is received from the first network element.

17. The method according to claim 15 or 16, characterized in that The method further comprises: sending a notification message to a first network element, where the notification message includes an identifier of the first service, and the notification message is used to create context information of the first service; or, Creating context information of the first service; The context information of the first service is sent to a first network element, and the first network element supports management of the first service.

18. The method according to any one of claims 15 to 17, characterized in that Before receiving the service request message, the method further includes: receiving a first registration request message, where the first registration request message is used to request registration of the first service; Sending a second registration request message to a first network element, where the second registration request message is used to request registration of the first service, and the first network element supports management of the first service; receiving a second registration response message from the first network element, where the second registration response message is used to indicate a registration result of the first service; A first registration response message is sent, where the first registration response message is used to indicate the registration result.

19. The method according to any one of claims 15 to 18, characterized in that The network service called by executing the first service includes a first network service and a second network service, and executing the first service according to the execution method of the first service includes: Sending a service invocation request message to a first network function according to the execution method of the first service, where the service invocation request message is used to request the first network function to invoke the first network service; Sending first configuration information to the first network function, where the first configuration information includes address information of a second network function, where the address information of the second network function is used by the first network function to determine a second network function that supports calling the second network service; A first execution result from the first network function is received.

20. The method according to any one of claims 15 to 18, characterized in that The network service called by executing the first service includes a first network service and a second network service, and executing the first service according to the execution method of the first service includes: Sending a service invocation request message to a first network function according to the execution method of the first service, where the service invocation request message is used to request the first network function to invoke the first network service; Sending second configuration information to the second network element, where the second configuration information includes address information of a second network function, where the address information of the second network function is used to determine a second network function that supports calling the second network service, and the second network element is used to store address information of one or more network functions; A second execution result from the first network function is received.

21. The method according to any one of claims 15 to 20, characterized in that The method further comprises: When the relevant information of the first service changes, an update message is sent, where the update message is used to update the relevant information of the first service.

22. The method according to claim 21, characterized in that The network service called for executing the first service includes a first network service and a second network service, and the related information of the first service includes one or more of the following: information of the first network service and / or the second network service; or, context information of the first service; or, The policy information and / or contract information associated with the first service.

23. 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.

24. The method according to claim 23, characterized in that Before sending the service request message to the second network element, the method further includes: Obtain identification information of the first service.

25. The method according to claim 24, characterized in that The acquiring identification information of the first service includes: Acquire identification information of the first service from a first network element; or, Acquire identification information of the first service from an application function, wherein the identification information of the first service is generated by the application function or a first network element, and the first network element supports management of the first service.

26. 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 7, or the one or more functional modules are used to execute the method according to any one of claims 8 to 14, or the one or more functional modules are used to execute the method according to any one of claims 15 to 22, or the one or more functional modules are used to execute the method according to any one of claims 23 to 25.

27. 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 7, or so that the device performs the method according to any one of claims 8 to 14, or so that the device performs the method according to any one of claims 15 to 22, or so that the device performs the method according to any one of claims 23 to 25.

28. 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 7, the second network element is used to execute the method according to any one of claims 8 to 14, and the third network element is used to execute the method according to any one of claims 15 to 22.

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

30. 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 7, or enables the computer to execute the method according to any one of claims 8 to 14, or enables the computer to execute the method according to any one of claims 15 to 22, or enables the computer to execute the method according to any one of claims 23 to 25.

31. 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 7, or the computer executes the method according to any one of claims 8 to 14, or the computer executes the method according to any one of claims 15 to 22, or the computer executes the method according to any one of claims 23 to 25.

Images