Communication method, device and system, storage medium and program product

Abstract

The invention discloses a communication method, device and system, a storage medium and a program product. The first network element acquires service input data or an acquisition voucher of the service input data from the second network element according to the received service trigger event and sends a service request to the at least one third network element, and the at least one third network element executes the requested service according to the service request and sends service feedback to the first network element. The invention provides a new core network architecture realized without a server architecture, the first network element uniformly processes the service request and calls the at least one third network element in the network, and the third network elements have no coupling or are weak in coupling relationship, so that the flexibility of network deployment and management is improved.

Description

Communication method, device, system, storage medium and program product Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a communication method, device, system, storage medium, and program product. Background Art

[0002] In existing network architectures, the entire architecture is designed around network elements (or network functions), each of which performs a specific function. Each network element communicates with one or more specific network elements, creating a strong coupling between them and making network functions complex. Furthermore, the network architecture is logically complex, making disaster recovery difficult. Each network element must independently maintain user context, and failure of that element results in context loss. Consequently, existing network architectures lack flexibility for network deployment and management.

[0003] Summary of the Invention

[0004] The present application provides a communication method, device, system, storage medium, and program product to improve the flexibility of network deployment and management.

[0005] In a first aspect, a communication method is provided, comprising: a first network element obtaining service input data or a credential for obtaining the service input data from a second network element based on a received service trigger event; the first network element sending a service request to at least one third network element, the service request including the service input data or the credential for obtaining the service input data; and the first network element receiving service feedback from the at least one third network element, the service feedback including an execution result of the service.

[0006] In this aspect, a new core network architecture implemented by a serverless architecture is provided, in which the first network element can process different service requests and call at least one third network element in the network. There is no coupling or weak coupling relationship between the third network elements, which improves the flexibility of network deployment and management.

[0007] In one possible implementation, the first network element is used to process different service requests in the network, and the second network element is used to provide data storage services for the first network element and / or the at least one third network element, and the at least one third network element is a network element that provides network functions; wherein the at least one third network element includes: a session management function network element, an access and mobility management function network element, and a policy and control function network element.

[0008] In another possible implementation, the first network element sending a service request to at least one third network element includes: the first network element sending the service request to the at least one third network element according to the service execution logic; wherein the service execution logic includes at least one of the following information: the at least one third network element required to be invoked for each service, the scheduling order of the at least one third network element, the format of the service input data corresponding to each third network element, and the content of the service input data corresponding to each third network element. In this implementation, the service execution logic may correspond to a service provided by the network to the terminal. Specifically, the network functions required to be invoked for each service, the order of invocation, the format and content of the input data required to be provided by each network function, etc. can be referred to as the service execution logic. The service execution logic can be implemented as a script, a piece of code, etc., which can be pre-configured or configured to the first network element by a network function.

[0009] In another possible implementation, the method further includes: the first network element sending a scheduling request to a fourth network element, wherein the fourth network element is configured to provide network function discovery and selection services for the first network element; and the first network element receiving a scheduling response from the fourth network element, wherein the scheduling response includes at least one of the following information about the at least one third network element: capabilities, identification, address information, status information, and network information of the at least one third network element. In this implementation, the fourth network element provides network function discovery and selection services for the first network element.

[0010] In another possible implementation, the service feedback also includes an update result of the service input data; the method further includes: the first network element sending a data synchronization request to the second network element, the data synchronization request including the update result of the service input data; and the first network element receiving a data synchronization response from the second network element. In this implementation, after completing the service, the third network element may also update data in the second network element, such as updating the terminal context. Therefore, the service feedback may also include the update result of the service input data.

[0011] In another possible implementation, the service triggering event includes a service request from a fifth network element; and the method further includes: the first network element sending the service feedback to the fifth network element. In this implementation, the first network element may also process the service request from the fifth network element to implement service invocation between subnetworks.

[0012] In another possible implementation, the first network element and the fifth network element belong to different networks; the different networks are user-level networks or operator networks, or different user-level networks, or different network slices.

[0013] In another possible implementation, the service input data is processed user data. In this implementation, the security of the service input data transmission process can be improved.

[0014] In another possible implementation, the service input data is unprocessed user data; and the method further includes: the first network element processing the service input data to obtain processed user data.

[0015] In another possible implementation, the processed user data includes at least one of the following: encrypted user data, user data with user identification information removed, a temporary user identification, and an encrypted user identification.

[0016] In another possible implementation, the service triggering event includes at least one of the following: a communication service request initiated by the terminal, a communication service request initiated by the fifth network element, a periodic communication service, and an event-triggered communication service; the first network element sends a service request to at least one third network element, including: the first network element sends the service request to at least one third network element associated with the service triggering event, and the service request includes the service input data obtained by the first network element from the second network element and the execution result of the service obtained from other third network elements in the at least one third network element; and the first network element receives service feedback from the at least one third network element, including: the first network element receives service feedback from the at least one third network element, respectively.

[0017] In another possible implementation, the service triggering event is a session establishment request, and the service input data includes session subscription data; the first network element sends a service request to at least one third network element, including: the first network element sends a session policy request to the PCF, and the session policy request includes at least one of the following information: data network name DNN, network slice information; the first network element receives service feedback from the at least one third network element, including: the first network receives a session policy response from the PCF, and the session policy response includes a session policy, and the session policy is generated based on the DNN and / or the network slice information.

[0018] In another possible implementation, the first network element sends a service request to at least one third network element, further comprising: the first network element sends a session establishment request to the SMF, the session establishment request including session policy information or session subscription information; and the first network element receives service feedback from the at least one third network element, further comprising: the first network element receives a session establishment response from the SMF, the session establishment response including session context. In existing session creation scenarios, after receiving a session establishment request from a terminal, the RAN forwards it to the SMF. After receiving the session establishment request from the terminal, the SMF obtains session-related terminal subscription data from the UDM / UDR. This means that the SMF can directly access the terminal subscription data. The SMF then interacts with other network elements based on this terminal subscription data to perform subsequent session creation. This results in frequent transmission of user privacy data within the network, reducing security. In this implementation, the first network element uniformly obtains session-related subscription data from the second network element and sends it to the SMF. The SMF cannot directly access the session-related terminal subscription data, thus preventing frequent transmission of user privacy data within the network and improving data security.

[0019] In another possible implementation, the first network element sends a service request to at least one third network element, further comprising: the first network element performing user plane configuration on a user plane function network element.

[0020] In a second aspect, a communication method is provided, comprising: a second network element receiving an acquisition request from a first network element, the acquisition request being used to request service input data or an acquisition credential for the service input data, the acquisition credential for the service input data being a credential for obtaining the service input data; and the second network element sending an acquisition response to the first network element, the acquisition response including the service input data or the acquisition credential for the service input data. In this aspect, the first network element uniformly acquires the service input data or the acquisition credential for the service input data from the second network element, while the third network element cannot directly access the service input data, thereby preventing frequent transmission of user private data within the network and improving data security.

[0021] In one possible implementation, the first network element is used to process different service requests in the network, and the second network element is used to provide data storage services for the first network element and / or at least one third network element, and the at least one third network element is a network element that provides network functions; wherein the at least one third network element includes: a session management function network element, an access and mobility management function network element, and a policy and control function network element.

[0022] In existing communication systems, each third network element must independently maintain user plane context. If any third network element fails, the user plane context maintained by that third network element may be lost. In the above implementation, a separate second network element provides data storage services for the first network element and / or the third network element, eliminating the need for the first network element and each third network element to independently maintain relevant service data, thereby improving storage efficiency and data security.

[0023] In another possible implementation, the service input data is processed user data; and the method further includes: the second network element processing the service input data to obtain the processed user data.

[0024] In another possible implementation, the processed user data includes at least one of the following: encrypted user data, user data with user identification information removed, a temporary user identification, and an encrypted user identification.

[0025] In a third aspect, a communication method is provided, the method comprising: a third network element receiving a service request, the service request including service input data or a credential for obtaining the service input data; and the third network element executing the requested service according to the service request. In this aspect, a new core network architecture implemented by a serverless architecture is provided, wherein a first network element uniformly processes service requests and calls at least one third network element in the network. The third network elements are uncoupled or weakly coupled with each other, thereby improving the flexibility of network deployment and management. The first network element uniformly obtains service input data and sends it to a related third network element, or the first network element obtains a credential for obtaining service input data and sends the credential to a related third network element, and the related third network element obtains the service input data. The third network element cannot directly access the service input data, thereby avoiding frequent transmission of user privacy data in the network and improving data security.

[0026] In a possible implementation, the method further includes: the third network element sending service feedback to the first network element, where the service feedback includes an execution result of the service.

[0027] In another possible implementation, the first network element is used to process different service requests in the network, and the third network element is a network element that provides network functions; wherein the third network element includes any one of the following: a session management function network element, an access and mobility management function network element, and a policy and control function network element.

[0028] In another possible implementation, the third network element receiving the service request includes: the third network element receiving the service request from the first network element.

[0029] In another possible implementation, the method further includes: the third network element sends a registration request to a fourth network element, the registration request including at least one of the following information: the capabilities, identification, address information, status information, and network information of the third network element, wherein the fourth network element is used to provide network function discovery and selection services for the first network element; and the third network element receives a registration response from the fourth network element.

[0030] In another possible implementation, the third network element receiving the service request includes: the third network element receiving the service request from the fourth network element.

[0031] In another possible implementation, the service request includes the acquisition credentials of the service input data, and the third network element receives the service request, including: the third network element sends an acquisition request to the second network element based on the acquisition credentials, and the second network element is used to provide data storage services for the first network element and / or the third network element; and the third network element receives an acquisition response from the second network element, and the acquisition response includes the service input data.

[0032] In yet another possible implementation, the service input data is processed user data.

[0033] In another possible implementation, the processed user data includes at least one of the following: encrypted user data, user data with user identification information removed, a temporary user identification, and an encrypted user identification.

[0034] In another possible implementation, the service request includes the service input data obtained by the first network element from the second network element and the execution result of the service obtained from other third network elements among the at least one third network element.

[0035] In another possible implementation, the third network element is a PCF network element, and the service input data includes session subscription data; the third network element receives a service request, including: the third network element receives a session policy request, and the session policy request includes at least one of the following information: data network name DNN, network slice information; the third network element sends service feedback to the first network element, including: the third network element sends a session policy response to the first network element, and the session policy response includes a session policy, and the session policy is generated based on the DNN and / or the network slice information.

[0036] In another possible implementation, the third network element is an SMF network element; the third network element receives a service request, including: the third network element receives a session establishment request, and the session establishment request includes session policy information or session subscription information; the third network element sends service feedback to the first network element, including: the third network element sends a session establishment response to the first network element, and the session establishment response includes a session context.

[0037] In a fourth aspect, a communication method is provided, the method comprising: a fourth network element receiving a registration request from at least one third network element, the registration request including at least one of the following information: capabilities, identification, address information, status information, and network information of the third network element; the fourth network element sending a registration response to the at least one third network element; the fourth network element receiving a scheduling request from a first network element; the fourth network element determining at least one third network element to schedule based on the scheduling request; and the fourth network element sending a scheduling response to the first network element, the scheduling response including at least one of the following information about the at least one third network element to schedule: capabilities, identification, address information, and status information of the at least one third network element; or the fourth network element sending the scheduling request to the at least one third network element to schedule. In this aspect, the fourth network element provides a network function discovery and selection service for the first network element. A third network element providing a single network service may register the capabilities, identification, address information, status information, network information, and other information of the third network element with the fourth network element.

[0038] In one possible implementation, the first network element is used to process different service requests in the network, the at least one third network element is a network element that provides network functions, and the fourth network element is used to provide network function discovery and selection services for the first network element; wherein, the at least one third network element includes: a session management function network element, an access and mobility management function network element, and a policy and control function network element.

[0039] In a fifth aspect, a communication device is provided that can implement the communication method described in the first aspect. For example, the communication device can be a chip or a first network element. The method can be implemented through software, hardware, or hardware executing corresponding software.

[0040] In one possible implementation, the communication device includes a transceiver unit and a processing unit, wherein the processing unit is used to obtain service input data or a credential for obtaining the service input data from a second network element based on a received service trigger event; the transceiver unit is used to send a service request to at least one third network element, wherein the service request includes the service input data or a credential for obtaining the service input data; and the transceiver unit is further used to receive service feedback from the at least one third network element, wherein the service feedback includes an execution result of the service.

[0041] Optionally, the communication device is used to process service requests in the network, and the second network element is used to provide data storage services for the first network element and / or the at least one third network element, and the at least one third network element is a network element that provides network functions; wherein, the at least one third network element includes: a session management function network element, an access and mobility management function network element, and a policy and control function network element.

[0042] Optionally, the transceiver unit is also used to send the service request to the at least one third network element according to the execution logic of the service; wherein the execution logic of the service includes at least one of the following information: at least one third network element required to be called for each service, the scheduling order of the at least one third network element, the format of the service input data corresponding to each third network element, and the content of the service input data corresponding to each third network element.

[0043] Optionally, the transceiver unit is further used to send a scheduling request to a fourth network element, wherein the fourth network element is used to provide network function discovery and selection services for the first network element; and the transceiver unit is further used to receive a scheduling response from the fourth network element, wherein the scheduling response includes at least one of the following information of the at least one third network element: the capability, identification, address information, status information, and network information of the at least one third network element.

[0044] Optionally, the service feedback also includes the updated result of the service input data; the transceiver unit is further used to send a data synchronization request to the second network element, and the data synchronization request includes the updated result of the service input data; and the transceiver unit is further used to receive a data synchronization response from the second network element.

[0045] Optionally, the service triggering event includes a service request from a fifth network element; and the transceiver unit is further configured to send the service feedback to the fifth network element.

[0046] Optionally, the first network element and the fifth network element belong to different networks; the different networks are user-level networks or operator networks, or different user-level networks, or different network slices.

[0047] Optionally, the service input data is processed user data.

[0048] Optionally, the service input data is unprocessed user data; and the processing unit is further configured to process the service input data to obtain processed user data.

[0049] Optionally, the processed user data includes at least one of the following: encrypted user data, user data with user identification information removed, a temporary user identification, and an encrypted user identification.

[0050] Optionally, the service triggering event is a session establishment request, and the service input data includes session signing data; the transceiver unit is further used to send a session policy request to the PCF, and the session policy request includes at least one of the following information: data network name DNN, network slice information; the transceiver unit is also used to receive a session policy response from the PCF, and the session policy response includes a session policy, and the session policy is generated based on the DNN and / or the network slice information.

[0051] Optionally, the transceiver unit is further used to send a session establishment request to the SMF, wherein the session establishment request includes session policy information or session contract information; the transceiver unit is further used to receive a session establishment response from the SMF, wherein the session establishment response includes a session context.

[0052] In a sixth aspect, a communication device is provided that can implement the communication method described in the second aspect. For example, the communication device can be a chip or a second network element. The method can be implemented through software, hardware, or hardware executing corresponding software.

[0053] In one possible implementation, the communication device includes a transceiver unit and a processing unit; wherein the transceiver unit is used to receive an acquisition request from a first network element, the acquisition request is used to request to obtain service input data or an acquisition credential for the service input data, and the acquisition credential for the service input data is a credential for obtaining the service input data; and the transceiver unit is further used to send an acquisition response to the first network element, the acquisition response including the service input data or the acquisition credential for the service input data.

[0054] Optionally, the first network element is used to process different service requests in the network, and the communication device is used to provide data storage services for the first network element and / or at least one third network element, and the at least one third network element is a network element that provides network functions; wherein, the at least one third network element includes: a session management function network element, an access and mobility management function network element, and a policy and control function network element.

[0055] Optionally, the service input data is processed user data; and the processing unit is configured to process the service input data to obtain the processed user data.

[0056] Optionally, the processed user data includes at least one of the following: encrypted user data, user data with user identification information removed, a temporary user identification, and an encrypted user identification.

[0057] In a seventh aspect, a communication device is provided that can implement the communication method described in the third aspect. For example, the communication device can be a chip or a third network element. The method can be implemented through software, hardware, or hardware executing corresponding software.

[0058] In one possible implementation, the communication device includes a transceiver unit and a processing unit; wherein the transceiver unit is used to receive a service request, the service request includes service input data or a credential for obtaining the service input data; and the processing unit is used to execute the requested service according to the service request.

[0059] Optionally, the transceiver unit is further configured to send service feedback to the first network element, where the service feedback includes an execution result of the service.

[0060] Optionally, the first network element is used to process different service requests in the network, and the communication device is a device that provides network functions; wherein, the communication device includes any one of the following: a session management function network element, an access and mobility management function network element, and a policy and control function network element.

[0061] Optionally, the transceiver unit is further configured to receive a service request from the first network element.

[0062] Optionally, the transceiver unit is also used to send a registration request to a fourth network element, and the registration request includes at least one of the following information: the capabilities, identification, address information, status information, and network information of the third network element, wherein the fourth network element is used to provide network function discovery and selection services for the first network element; and the third network element receives a registration response from the fourth network element.

[0063] Optionally, the transceiver unit is further used to receive the service request from the fourth network element.

[0064] Optionally, the service request includes an acquisition credential for the service input data, and the transceiver unit is further used to send an acquisition request to a second network element based on the acquisition credential, and the second network element is used to provide data storage services for the first network element and / or the communication device; and the transceiver unit is further used to receive an acquisition response from the second network element, and the acquisition response includes the service input data.

[0065] Optionally, the service input data is processed user data.

[0066] Optionally, the processed user data includes at least one of the following: encrypted user data, user data with user identification information removed, a temporary user identification, and an encrypted user identification.

[0067] Optionally, the third network element is a PCF network element, and the service input data includes session subscription data; the transceiver unit is further used to receive a session policy request, and the session policy request includes at least one of the following information: data network name DNN, network slice information; the transceiver unit is also used to send a session policy response to the first network element, and the session policy response includes a session policy, and the session policy is generated based on the DNN and / or the network slice information.

[0068] Optionally, the third network element is an SMF network element; the transceiver unit is further used to receive a session establishment request, the session establishment request including session policy information or session contract information; the transceiver unit is further used to send a session establishment response to the first network element, the session establishment response including a session context.

[0069] In an eighth aspect, a communication device is provided that can implement the communication method of the fourth aspect. For example, the communication device can be a chip or a fourth network element. The method can be implemented through software, hardware, or hardware executing corresponding software.

[0070] In one possible implementation, the communication device includes a transceiver unit and a processing unit; wherein the transceiver unit is used to receive a registration request from at least one third network element, and the registration request includes at least one of the following information: the capability, identification, address information, status information, and network information of the third network element; the transceiver unit is also used to send a registration response to the at least one third network element; the transceiver unit is also used to receive a scheduling request from the first network element; the processing unit is used to determine the at least one third network element to be scheduled based on the scheduling request; and the transceiver unit is also used to send a scheduling response to the first network element, and the scheduling response includes at least one of the following information of the at least one third network element to be scheduled: the capability, identification, address information, and status information of the at least one third network element; or the transceiver unit is also used to send the scheduling request to the at least one third network element to be scheduled.

[0071] Optionally, the first network element is used to process different service requests in the network, the at least one third network element is a network element that provides network functions, and the communication device is used to provide network function discovery and selection services for the first network element; wherein, the at least one third network element includes: a session management function network element, an access and mobility management function network element, and a policy and control function network element.

[0072] In combination with any one of the fifth to eighth aspects, in another possible implementation, the communication device in any one of the fifth to eighth aspects includes a processor coupled to a memory; the processor is configured to support the device in performing the corresponding functions in the above-mentioned communication method. The memory is used to couple with the processor, which stores the necessary programs (instructions) and / or data for the device. Optionally, the communication device may further include a communication interface for supporting communication between the device and other network elements. Optionally, the memory may be located inside the communication device or outside the communication device. Optionally, the memory and the processor may be integrated together.

[0073] In combination with any one of the fifth to eighth aspects, in another possible implementation, the communication device in any one of the fifth to eighth aspects includes a processor and a transceiver, the processor is coupled to the transceiver, and the processor is used to execute a computer program or instruction to control the transceiver to receive and send information; when the processor executes the computer program or instruction, the processor is also used to implement the above method through a logic circuit or execute code instructions. The transceiver can be a transceiver, a transceiver circuit or an input-output interface, which is used to receive signals from other devices outside the communication device and transmit them to the processor or send signals from the processor to other devices outside the communication device. When the communication device is a chip, the transceiver is a transceiver circuit or an input-output interface.

[0074] When the communication device in any of the fifth to eighth aspects is a chip or chip module, the sending unit may be an output unit, such as an output circuit or a communication interface; and the receiving unit may be an input unit, such as an input circuit or a communication interface. When the communication device is a terminal or access network equipment, the sending unit may be a transmitter or a transmitter; and the receiving unit may be a receiver or a receiver.

[0075] In a ninth aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When a computer executes the computer program or instruction, the methods described in the above aspects are implemented.

[0076] In a tenth aspect, a computer program product comprising instructions is provided, which, when executed on a communication device, causes the communication device to execute the methods described in the above aspects.

[0077] In an eleventh aspect, a communication system is provided, which includes the communication device according to any one of the fifth to eighth aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0079] FIG2a is a schematic diagram of a communication system architecture based on a 5G network provided in an embodiment of the present application;

[0080] FIG2 b is a schematic diagram of another communication system architecture based on a 5G network provided in an embodiment of the present application;

[0081] FIG2c is a schematic diagram of another communication system architecture based on a 5G network provided in an embodiment of the present application;

[0082] FIG3 is a schematic diagram of the evolution of mobile network core network technology;

[0083] Figure 4 is a schematic diagram of the interaction logic between some network elements of the 5G core network;

[0084] FIG5 is a flow chart of a communication method provided in an embodiment of the present application;

[0085] FIG6 is a flow chart of another communication method provided in an embodiment of the present application;

[0086] FIG7 is a schematic diagram of the architecture of a multi-level network provided in an embodiment of the present application;

[0087] FIG8 is a flow chart of a communication method in a session establishment scenario according to an embodiment of the present application;

[0088] FIG9 is a flow chart of a communication method in another session establishment scenario according to an embodiment of the present application;

[0089] FIG10 is a flow chart of a communication method in a terminal registration scenario according to an embodiment of the present application;

[0090] FIG11 is a flow chart of a communication method in a service request scenario according to an embodiment of the present application;

[0091] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0092] FIG13 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0093] This application can be applied to, used in, or integrated into the core network architecture of mobile networks, including the fifth generation (5 th generation, 5G) mobile communication system, the sixth generation (6 th The core network architecture of the 6G generation mobile communication system, future evolved communication system or other communication systems is not limited in this application.

[0094] As shown in Figure 1, a schematic diagram of the architecture of a communication system provided in an embodiment of the present application is provided. The communication system 100 may include: a first network element 101, a second network element 102, and at least one third network element 103 (n third network elements are illustrated in the figure). The first network element 101 is configured to process different service requests in the network, the second network element 102 is configured to provide data storage services for the first network element 101 and / or the at least one third network element 103, and the at least one third network element 103 is a network element that provides network functions. Exemplarily, the first network element 101 is configured to obtain service input data or a credential for obtaining the service input data from the second network element 102 based on a received service trigger event. The first network element 101 is further configured to send a service request to the at least one third network element 103, the service request including the service input data or the credential for obtaining the service input data. Accordingly, upon receiving the service request, the third network element 103 is configured to execute the requested service according to the service request. Accordingly, the third network element 103 is further configured to send service feedback to the first network element 101, the service feedback including the service execution result.

[0095] Optionally, the communication system 100 may further include a fourth network element 104 (indicated by a dashed line in the figure). The fourth network element 104 is configured to provide network function discovery and selection services for the first network element 101. Exemplarily, the at least one third network element 103 is further configured to send a registration request to the fourth network element 104, where the registration request includes at least one of the following information: capabilities, identifier, address information, status information, and network information of the third network element 103. The fourth network element 104 is further configured to send a registration response to the at least one third network element 103. The fourth network element 104 is further configured to receive a scheduling request from the first network element 101. The fourth network element 104 is further configured to determine at least one third network element to be scheduled based on the scheduling request. The fourth network element 104 is further configured to send a scheduling response to the first network element 101, where the scheduling response includes at least one of the following information about the at least one third network element to be scheduled: capabilities, identifier, address information, and status information of the at least one third network element to be scheduled; or the fourth network element 104 is further configured to send the aforementioned scheduling request to the at least one third network element to be scheduled.

[0096] Exemplarily, the above-mentioned first network element 101 can also be called an execution node (EN), an execution network element, an execution network function, an execution device or an execution module in this embodiment. This application does not limit the name of the network element.

[0097] The above-mentioned second network element 102 can also be called a database (database, DB), a data storage network element, a data storage network function, a data storage module or a data storage device in this embodiment. This application does not limit the name of this network element.

[0098] The third network element 103 in this embodiment may also be referred to as a network function (NF), and this application does not limit the name of the network element.

[0099] The fourth network element 104 in this embodiment may also be referred to as a scheduling function, a scheduling module or a scheduling device. This application does not limit the name of the network element.

[0100] Here are several communication system architectures based on 5G networks:

[0101] As shown in Figure 2a, a schematic diagram of a communication system architecture based on a 5G network is provided for an embodiment of the present application. In this system architecture, the first network element 101 (EN) can serve as a network function of the system, located at the network entrance between the core network and the access network; the unified data management (UDM) and / or unified data repository (UDR) in the system can serve as the second network element 102 (DB); other network functions in the architecture can serve as the third network element 103; and the network repository function (NRF) and / or service communication proxy (SCP) in the system can serve as the fourth network element 104.

[0102] Figure 2b shows another schematic diagram of a 5G network-based communication system architecture according to an embodiment of the present application. The first network element 101 (EN) can also be integrated into existing access network functions. As shown in Figure 2b, the first network element 101 (EN) is integrated into a (radio) access network (R)AN.

[0103] Figure 2c shows another schematic diagram of a 5G network-based communication system architecture provided in an embodiment of the present application. The first network element 101 (EN) can also be integrated into existing core network functions. As shown in Figure 2c, the first network element 101 (EN) is integrated into the access and mobility management function (AMF).

[0104] The existing network architecture has a strong coupling relationship between network functions (network elements), the network functions are too "heavy", the network architecture logic is complex, disaster recovery is difficult, it is not friendly to three parties, and is not conducive to flexible and easy network deployment and management.

[0105] As shown in Figure 3, it is a schematic diagram of the evolution of mobile network core network technology, from the second generation (2 nd From the core network technology development trends of mobile communication networks from 2G to 5G, the transition from physical machine implementation in 2G to partial cloudification of the 5G core network, and the shift to internet technology (IT)-based mobile network development, has become a major trend in network development. In Figure 3, for 2G to 4G core networks, software and hardware are implemented on the same physical machine or machines. These machines are dedicated servers. A single physical network cannot support all service requirements (such as the Internet of Things (IoT), mobile broadband (MBB), and vehicle-to-everything (V2X)), or can only support these service requirements inefficiently. For the 5G core network, different network element functions can be implemented on the same general-purpose physical machine. By implementing network equipment with IT technology, operators can use general-purpose hardware to load different software-based network functions, simplifying deployment and reducing costs.

[0106] In 5G networks, virtualization technology can be used to logically divide the physical network into different virtual networks (i.e., network slices) (for example, in Figure 3, a physical machine can be logically divided into three sub-networks: Network 1 (for example, IoT), Network 2 (for example, MBB), and Network 3 (for example, V2X)), providing users with differentiated network connection services. If the original physical machine implementation method is still adopted, separate physical networks need to be deployed for different network slices (as in Figure 3, Network 1, Network 2, and Network 3 each require the deployment of one or more separate physical machines). A single physical network cannot or inefficiently support all business needs, which is not conducive to flexible network deployment.

[0107] Taking the core network of the existing 5G mobile communication system as an example, the entire network architecture is designed based on network elements (or network functions), each of which has a specific function. For example, the AMF is responsible for terminal access and mobility management, forwarding messages between network elements and terminals for other network elements in the network; the session management function (SMF) is responsible for managing the terminal's protocol data unit (PDU) sessions; the user plane function (UPF) forwards user plane data packets for terminals; and the policy control function (PCF) configures relevant policies for the AMF, SMF, and other network elements, such as access and mobility management policies (whether, when, and where a terminal can access the network) and session management policies (what application data can be transmitted in the terminal's PDU session, and what rules should be used for transmission, etc.). Figure 4 shows a schematic diagram of the interaction logic between some network elements in the existing 5G core network, illustrating the interaction logic of the aforementioned AMF, SMF, and PCF.

[0108] It should be noted that the above functional entity is just a name, and the name itself does not limit the entity. For example, the session management function entity may also be replaced by "session management function" or other names. Moreover, the session management function entity may also correspond to an entity that includes other functions in addition to the session management function. The user plane function entity may also be replaced by "user plane function" or other names, and the user plane function entity may also correspond to an entity that includes other functions in addition to the user plane function. The access and mobility management function can also be divided into two functions: access management function and mobility management function. A unified explanation is given here and no further details are given below.

[0109] In the existing network logical architecture shown in Figure 4, strong coupling is required between network elements. For example, for PDU session 1, AMF can only interact with SMF1. If SMF1 fails, the session management (SM) context is lost.

[0110] As can be seen, the current communication system has highly coupled network elements, complex network architecture logic, and difficult disaster recovery, making it unfriendly to three parties. Furthermore, each network element must independently maintain user-related context and directly access user subscription data (each network element obtains subscription information from the UDM / UDR based on the subscription data obtained and generates relevant context based on the subscription information). This results in frequent transmission of user privacy data within the network, reducing security.

[0111] Serverless computing (abbreviated as serverless), also known as Function-as-a-Service (FaaS), is a cloud computing model. Based on Platform as a Service (PaaS), serverless computing provides a microarchitecture where end users do not need to deploy, configure, or manage server services. Instead, the cloud platform provides all the server services needed to run the code.

[0112] Serverless computing doesn't mean servers are completely unnecessary. Rather, it means developers no longer have to worry about servers. Computing resources are presented as services, not servers. Serverless computing is a technology for building and managing microservices-based architectures. It allows developers to manage application deployments at the service level, rather than the server level. They can even manage the deployment of specific functions or ports, enabling developers to iterate quickly and develop software more rapidly.

[0113] However, at this stage, serverless computing is primarily applicable to event-based, short-duration tasks. User-written task functions are subject to execution time and resource constraints. Platform providers, therefore, have maximum scheduling authority and offer pay-per-use and pay-as-you-go pricing strategies. This has proven successful in service-driven scenarios with massive client bases, leveraging the on-demand elasticity and billing benefits of serverless computing. Clearly, this application scope is insufficient to meet the expectations of cloud vendors.

[0114] Although serverless computing has a wide range of applications, it also has limitations. Serverless computing is particularly suitable for the following scenarios:

[0115] -Asynchronous concurrency, components can be deployed and expanded independently;

[0116] - To cope with sudden or unpredictable service usage (mainly to save costs, because serverless computing applications are not charged when they are not running);

[0117] - Short-lived, stateless applications that are not sensitive to cold start times;

[0118] -Businesses that require rapid development and iteration.

[0119] Based on this, serverless computing is very suitable for real-time file processing, periodic data processing, and mobile and world wide web (Web) application backends.

[0120] However, the design concept of serverless computing is currently only used in IT networks and has not yet been involved in mobile network architecture design.

[0121] In response to the problems in existing network architectures where the coupling relationship between network functions (network elements) is strong, network functions are too "heavy", the network architecture logic is complex, disaster recovery is difficult, it is unfriendly to three parties, and it is not conducive to flexible and easy network deployment and management, the present application provides a communication solution, in which a first network element obtains service input data or a certificate for obtaining service input data from a second network element based on a received service trigger event, and sends a service request to at least one third network element, and at least one third network element executes the requested service based on the service request and sends service feedback to the first network element. The communication solution of the present application provides a core network architecture implemented with a new serverless architecture, which can realize the unified processing of service requests or processing of different service requests by the first network element, calling at least one third network element in the network, and there is no coupling or weak coupling relationship between each third network element, thereby improving the flexibility of network deployment and management.

[0122] FIG5 is a flow chart of a communication method provided in an embodiment of the present application. The method can be applied to the communication system shown in FIG1. ​​For example, the method may include the following steps:

[0123] S501. The first network element obtains service input data or a service input data acquisition credential from the second network element according to a received service triggering event.

[0124] In this embodiment, the first network element is used to process different service requests in the network.

[0125] The first network element can make subsequent service calls based on the logical relationship of business processing, or make subsequent service calls based on a type of template or a type of script, which contains the logical relationship of business processing. The first network element can provide services for different network types or business types. For example, there can be a first network element for a personal home network; there can be a corresponding first network element for a private network (such as a campus private network, a car network, etc.). Different first network elements can call different network services. For example, the first network element of a home network basically calls connection-type network services (such as session establishment or management services for large-bandwidth transmission); in addition to calling connection-type services, the first network element of the car network can also call services such as network environment perception, artificial intelligence (AI) services, etc.

[0126] The functional granularity of the first network element can be determined based on the specific services provided, making the functional granularity of the first network element deployment more flexible and meeting different service requirements. The first network element can be terminal (group) granularity, service granularity or network-level granularity. For example:

[0127] (1) The first network element is at the terminal (group) granularity.

[0128] For example, the first network element only serves the following specific terminals (groups):

[0129] Home network terminal; or

[0130] local area network (LAN) terminal; or

[0131] Terminals in industrial scenarios.

[0132] (2) The first network element can be service-granular.

[0133] For example, the first network element provides services for terminals that perform specific services:

[0134] The first network element created by the application function (AF), such as a slice service.

[0135] (3) Network-level granularity:

[0136] For example, the first network element provides services to terminals in the following networks:

[0137] Large network services, such as MBB and voice services; or

[0138] Special network services, such as the Internet of Vehicles, the Internet of Things, satellite communication networks, etc.

[0139] The service triggering event received by the first network element may be any one or more service triggering events initiated by the terminal, initiated by another node in the network (for example, the fifth network element), internally initiated periodically, or initiated by an event. Specific examples may include, but are not limited to, the following:

[0140] The terminal initiation may be that the first network element receives a request message or an indication message of the terminal, such as a non-access stratum (NAS) message of the terminal, a session establishment request, a service request message, a registration request message, etc.

[0141] Other nodes in the network may initiate a service request message or control message received by the first network element from a network function, a fifth network element, or a management function in the operator-level network. For example, if the contract or service of the terminal expires, the management function in the operator-level network may notify the first network element to stop serving the terminal; or if the fifth network element needs to obtain the terminal's data, it may initiate a terminal data request message to the first network element; or if the air interface resources on the access network side change, the access network element may notify the first network element to change the terminal's session parameters, etc. The fifth network element and the first network element belong to different networks, such as different subnetworks, different network slices, different network domains, etc.

[0142] Internal periodic initiations can include periodic registration updates of terminals, terminal policy updates (such as session policies, access management policies, mobility management policies, etc.), network service policy updates (such as updates to the number of terminals that the network can accommodate, updates to the geographical locations served by the network, updates to the quality of service (QoS) parameters that the network can provide, etc.), etc.

[0143] Event-triggered initiation can be a service behavior triggered by certain events, such as triggering the update of access policy for the terminal when the terminal moves to a certain location.

[0144] After receiving any one or more of the above-mentioned service triggering events, the first network element can obtain service input data from the second network element. The second network element provides data storage services for the first network element and / or the third network element, which are retrieved by the first network element and / or the third network element. The data stored by the second network element can be terminal-level data, such as terminal subscription data, terminal policy information in the network, and terminal context data in the network (such as session context, mobility management-related context), etc.; it can also be a storage service for temporary files provided to the third network element, such as the user plane context maintained by the SMF, data analysis files maintained by the data analysis network element, etc.; it can also be service-level data, such as parameters of a certain application (such as QoS parameters, application server location information, address information, terminal list information, etc.). In existing communication systems, each third network element needs to maintain user plane context separately. Once any third network element fails, the user plane context maintained by the third network element may be lost. In this embodiment, a separate second network element provides data storage services for the first network element and / or the third network element, eliminating the need for the first network element and each third network element to separately maintain related service data, thereby improving storage efficiency and data security.

[0145] The second network element can be deployed separately based on the type of data. For example, the second network element that stores the terminal contract data can be centrally deployed by the operator; the terminal-specific data can be deployed nearby or separately on the terminal side; the data of the park in the industrial scenario can be deployed separately within the park; the terminal data of the home network can be deployed at home or in a nearby community, etc.

[0146] The second network element can also be co-deployed with the first network element. For example, the first network element serving a home network terminal can be co-deployed with the second network element in the home; or the same hardware or software can realize both functions (similar to a home network server or set-top box, etc.).

[0147] The service input data retrieved by the first network element and / or the third network element is data required for network services, such as obtaining session-related policies or providing a data network name (DNN) and / or slice information when creating a session. Exemplarily, the first network element obtains the service input data from the second network element based on the received service trigger event. The first network element may send an acquisition request to the second network element based on the received service trigger event, where the acquisition request is used to request the acquisition of the service input data. After receiving the acquisition request, the second network element sends an acquisition response to the first network element, where the acquisition response includes the service input data.

[0148] Furthermore, the second network element can also process the service input data to be sent to obtain processed user data, which can improve the security of the service input data transmission process. That is, the service input data provided by the second network element is processed user data. Exemplarily, the processed user data includes at least one of the following: encrypting the user's identification information in the user data or using a temporary identifier instead of the user's permanent identifier (subscription permanent identifier, SUIP) or international mobile subscriber identity (international mobile subscriber identity, IMSI), etc., removing the user identification information from the provided user data, and performing integrity protection on the user data (such as using encryption methods such as homomorphic encryption), etc. In the existing communication system, UDM / UDR does not perform security processing on the user contract data it provides, and each third network element can directly access the user contract data.

[0149] Illustratively, before sending the unprocessed service input data to at least one third network element, the first network element may also process the service input data in a similar manner as the second network element to obtain processed user data.

[0150] In order to reduce the signaling message overhead of carrying terminal data in messages and avoid frequent transmission of sensitive terminal data in the network, the second network element may also return a (temporary) service input data credential to the first network element. The service input data acquisition credential is a credential for obtaining the service input data, such as an identifier, key, or token. That is, after receiving any one or more of the above service triggering events, the first network element can obtain the service input data acquisition credential from the second network element, so that the third network element can subsequently obtain the corresponding data from the second network element based on the service input data credential.

[0151] Alternatively, the first network element may also allocate a (temporary) service input data voucher and inform the second network element, so that the third network element may subsequently obtain corresponding data from the second network element based on the service input data voucher.

[0152] The first network element obtains service input data from the second network element based on the received service trigger event. This acquisition can take two forms: one is on-demand data acquisition. For example, when executing access management services, it obtains terminal access-related contract data; when creating a session for a terminal, it obtains session-related contract data. The other is global acquisition. That is, when a terminal accesses the network or passes network authentication, the first network element obtains all relevant data about the terminal from the second network element, such as all the terminal's contract data. When executing a task later, the first network element selects the relevant contract information based on the obtained terminal contract to make subsequent service calls.

[0153] S502. The first network element sends a service request to at least one third network element.

[0154] Correspondingly, at least one third network element receives the service request.

[0155] The first network element requests at least one third network element to invoke a corresponding network service and provides service input data required for the service. Exemplarily, the first network element sends a service request to the at least one third network element, where the service request includes the service input data obtained by the first network element from the second network element.

[0156] Alternatively, the service request may include a service input data acquisition credential, and the at least one third network element may acquire the service input data from the second network element based on the service input data acquisition credential. The service input data may be unprocessed user data or processed user data.

[0157] Exemplarily, a service triggering event includes at least one of the following: a communication service request initiated by a terminal, a communication service request initiated by the fifth network element, a periodic communication service, and an event-triggered communication service. A service triggering event may be associated with one or more third network elements. For example, in a session creation scenario, the service triggering event is a session creation request initiated by the terminal, and the third network elements associated with the service triggering event include PCF, SMF, and UPF; in a registration scenario, the service triggering event is a registration request initiated by the terminal, and the third network elements associated with the service triggering event include PCF and AMF; in a business service scenario, the service triggering event is a business request initiated by the terminal, and the third network elements associated with the service triggering event include SMF and AMF. Then, the first network element sends a service request to at least one third network element associated with the service triggering event, and the service request includes the service input data obtained by the first network element from the second network element and the execution results of the service obtained from other third network elements in the at least one third network element. For example, in a session creation scenario, the service input data sent by the first network element to the SMF includes the session-related subscription data of the terminal obtained from the second network element and the session policy information obtained from the PCF. The first network element receives service feedback from at least one third network element respectively.

[0158] The third network element is used to provide network services. Depending on the content of the services provided, the third network element has a corresponding name. For example, in a 5G network, AMF provides access and mobility management services, SMF provides session management functions, and PCF provides user-related, session-related, access and management-related network policies. Exemplarily, at least one third network element can be the above-mentioned SMF, AMF, PCF, etc.

[0159] In this embodiment, the services provided by the third network element are not limited and can be network functions used in existing technologies or new functions defined in future networks, such as network functions providing computing services or data processing. The difference lies in the change in the logic used by the third network element to process service requests. For example, in existing session creation scenarios, after the SMF receives a session creation request from a terminal, it obtains session-related terminal subscription data from the UDM / UDR and interacts with other network elements to perform subsequent session creation. In this embodiment, however, the first network element can centrally process session creation requests, invoking the SMF, PCF, and UPF for session services. The SMF, PCF, and UPF are uncoupled or weakly coupled, thereby improving the flexibility of network deployment and management. Furthermore, the first network element can centrally obtain service input data from the second network element and send it to the relevant third network element. Alternatively, the first network element can obtain service input data credentials and send them to the relevant third network element, which then obtains the service input data from the second network element. The third network element cannot directly access the service input data, preventing frequent transmission of user privacy data within the network and improving data security.

[0160] Exemplarily, the first network element sending a service request to at least one third network element may be the first network element sending the service request to the at least one third network element based on the execution logic of the service. The execution logic of the service includes at least one of the following information: at least one third network element required to be invoked for each service, the scheduling order of the at least one third network element, the format of service input data corresponding to each third network element, the content of the service input data corresponding to each third network element, and information about each third network element (e.g., identification information and address information of the third network element).

[0161] Here, the execution logic of the service can correspond to a certain service provided by the network to the terminal, such as a connection service for establishing a terminal to a data network (DN) (called a PDU session connection service in 5G), a data storage service, a data analysis or prediction service, etc. Different services require different network functions to be called. For example, the connection service may need to call SMF, PCF, and UPF; the data storage service needs to call the data storage function; the data analysis or analysis service needs to call computing-related network functions (for example, the network data analysis function (NWDAF) in 5G), etc. The specific network functions that need to be called for each service, the order of calls, the input data format and content that each network function needs to provide, etc. can be called the execution logic of the service. The implementation form of the execution logic of the service can be a script, a piece of code, etc., which is pre-configured or configured to the first network element by a certain network function.

[0162] Exemplarily, the communication system shown in Figure 1 may also include a fourth network element. The fourth network element provides network function discovery and selection services for the first network element, which is similar to the NRF function in the existing 5G standard. The third network element that provides a single network service can register the capabilities, identification, address information, status information, network information, etc. of the third network element to the fourth network element. Exemplarily, the third network element can send a registration request to the fourth network element. Accordingly, the fourth network element receives the registration request. The registration request includes at least one of the following information: the capabilities, identification, address information, status information, and network information of the third network element. After receiving the registration request, the fourth network element saves the above at least one information and sends a registration response to at least one third network element.

[0163] The first network element can call the corresponding network function through the fourth network element based on the service execution logic. When the first network element needs to use a certain network function, it can initiate a corresponding network function service call request to the fourth network element. Based on the network function information it has learned and the request of the first network element, the fourth network element can select one or more third network elements that can provide services to the first network element, and feedback the address or identification information of the third network element to the first network element, which will then initiate subsequent service requests.

[0164] Therefore, the first network element sending a service request to at least one third network element may also be replaced by the first network element sending a scheduling request to a fourth network element. The fourth network element determines at least one third network element to schedule based on the received scheduling request. The fourth network element sends a scheduling response to the first network element. In response, the first network element receives the scheduling response. The scheduling response includes at least one of the following information about the at least one third network element to be scheduled: capabilities or provided network services, an identifier, address information, and status information of the at least one third network element.

[0165] Alternatively, the first network element sending a service request to at least one third network element may be replaced by the first network element sending a scheduling request to a fourth network element. The fourth network element determines at least one third network element to schedule based on the received scheduling request. The fourth network element sends a scheduling request to the at least one scheduled third network element. Exemplarily, the fourth network element may also send a scheduling response to the first network element.

[0166] Alternatively, the scheduling function can be statically or dynamically configured in the first network element. For example, network function information (such as identification information, address information, and status of the network function) can be preconfigured in the first network element. When the first network element needs to call a certain network function, it can determine the network function information to be called based on the preconfigured information. The fourth network element is optional and is represented by a dotted line in the figure.

[0167] The service input data can be processed user data. The third network element no longer obtains unprocessed user data. Instead, the first network element sends the processed user data to the third network element, which then provides the corresponding service. The data provided by the first network element or obtained by the third network element from the second network element is processed user data, i.e., desensitized data, which can avoid excessive exposure of the terminal's private data.

[0168] Exemplarily, if the service request includes a credential for obtaining service input data, each of the at least one third network element may further obtain the service input data from the second network element based on the credential. Specifically, the at least one third network element may send a retrieval request to the second network element based on the credential. After receiving the retrieval request, the second network element may send a retrieval response to the at least one third network element, where the retrieval response includes the service input data.

[0169] S503. Each third network element of the at least one third network element executes the requested service according to the service request.

[0170] A service request may involve one or more third network elements. After each third network element receives a service request from the first network element or a scheduling request from the fourth network element, it can execute the requested service based on the service input data carried in the service request. For example, the third network element can be an SMF, and the service request is a session establishment request initiated by the terminal. The SMF can generate a corresponding session context based on session-related parameters (DNN, network slice information), RAN side information accessed by the terminal (base station address information, port number, etc.), and session-related subscription data of the terminal obtained by the first network element from the second network element.

[0171] S504. Each third network element of the at least one third network element sends service feedback to the first network element.

[0172] Correspondingly, the first network element receives the service feedback.

[0173] The service feedback includes the execution result of the service.

[0174] Furthermore, after the third network element completes the service, it can also update the data in the second network element, such as updating the context of the terminal. Therefore, the service feedback can also include the update result of the service input data. The method can also include the following steps (indicated by dotted lines in the figure):

[0175] S505. The first network element sends a data synchronization request to the second network element.

[0176] Correspondingly, the second network element receives the data synchronization request.

[0177] The data synchronization request includes an update result of the service input data.

[0178] S506. The second network element sends a data synchronization response to the first network element.

[0179] As an alternative step to steps S504 to S506, the service feedback sent by each of the at least one third network element to the first network element may only include the execution result of the service, and each of the at least one third network element sends a data synchronization request to the second network element, and the data synchronization request includes the update result of the service input data; and after receiving the data synchronization request, the second network element updates the data and sends a data synchronization response to each third network element, thereby completing the data update.

[0180] As a result, the third network element can store this data in the second network element without having to maintain the terminal context for a long time, and can then call it when needed later. This allows the third network element to provide instant services without having to maintain the terminal context for a long period of time, improving service efficiency. Furthermore, if the third network element fails, the impact on the terminal data is minimized, and only other function instances need to be called, improving network robustness.

[0181] According to a communication method provided in an embodiment of the present application, a new core network architecture implemented by a serverless architecture is given, in which a first network element uniformly processes service requests and calls at least one third network element in the network. There is no coupling or weak coupling relationship between the third network elements, which improves the flexibility of network deployment and management.

[0182] The above embodiment describes a scheme for calling network services or data in a sub-network. The following embodiment describes how to call network services or data between different sub-networks:

[0183] FIG6 is a flow chart of another communication method provided in an embodiment of the present application. The method can be applied to the communication system shown in FIG1. ​​Exemplarily, the method may include the following steps:

[0184] S601. The fifth network element sends a service triggering event to the first network element.

[0185] Correspondingly, the first network element receives the service triggering event.

[0186] In this embodiment, the service triggering event comes from the fifth network element and includes a service request from the fifth network element.

[0187] The first network element and the fifth network element belong to different networks, such as different subnetworks, different network slices, different network domains, etc. The fifth network element is used to uniformly process business services in the network to which it belongs.

[0188] In one implementation, the first network element and the fifth network element may belong to different network slices. For example, the first network element belongs to network slice 1, and the fifth network element belongs to network slice 2.

[0189] In addition, the entire mobile network can be divided into two categories: operator-level networks and user-level networks. Operator-level networks can provide initial access authentication and authorization functions for user-level network access, access management (AM), charging functions (CHF), user-level network mutual discovery, and network control functions (NCF). User-level networks can provide differentiated network services based on terminal needs and network characteristics (for example, existing network slicing provides differentiated connection services).

[0190] The following are examples of user-level and carrier-level network architectures:

[0191] As shown in FIG7 , a schematic diagram of the architecture of a multi-level network provided in an embodiment of the present application is shown, which provides several sub-network (i.e., user-level network) deployment schemes:

[0192] (1) User-level network 1 may include complete network service functions, including a first network element, a second network element, a third network element, and a fourth network element. The fourth network element may be an NRF or an SCP. The first network element and the third network element, or the third network element and the third network element, may directly discover and interact with each other through the NRF or the SCP.

[0193] (2) User-level network 2, which includes the first network element, the second network element, the third network element, and the fourth network element. User-level network 2 adopts a service-oriented architecture, and each network element communicates with each other using the existing 5G network. For example, user-level network 2 can be an enterprise campus, where some third network elements are deployed within the enterprise to manage the network functions within the enterprise without using the operator's services; or the third network elements of the operator network can be borrowed.

[0194] (3) User-level network 3, which only includes the first network element and the second network element. The first network element serves as the execution node of the sub-network, processing user requests in the network and opening services to the outside world; the second network element can store private data in the sub-network, such as the terminal's contract, policy and other information in the sub-network. Based on this networking method, it can be ensured that the terminal data does not leave the network, ensuring the security of the terminal data. For example, the user-level network 3 can be an enterprise campus, and the second network element is deployed inside the enterprise. This networking method does not include a third network element, so it is necessary to call the third network element of the operator network or other sub-network to perform corresponding network services.

[0195] (4) User-level network 4, which only includes the first network element. That is, user-level network 4 can control the service processing logic of the sub-network through the first network element, but needs to use the third network element and the second network element of the operator network to perform specific services. It can be found that the deployment method based on user-level network 4 can make the sub-network functions very simple, and the first network element can even be deployed on the access network side. For example, user-level network 4 can be a home network.

[0196] The user-level network may have limited network capabilities. When services from other subnetworks or carrier-level networks are needed, services from other networks can be requested through service request calls between first network elements. Information about other networks or corresponding first network elements and supported network functions can be obtained by querying the NRF or other similar query servers.

[0197] A terminal can access multiple subnetworks (user-level networks / network slices) at the same time, and can have a separate identity in each subnetwork (for example, the terminal has a temporary identity / identification in each user-level network). The terminal can control the first network element in each subnetwork so that service calls or data sharing can be performed between different subnetworks. For example, in Figure 7, the terminal can access user-level network 1 and user-level network 3 at the same time. User-level network 1 corresponds to the public network (that is, it provides Internet connection, voice communication and other services), and user-level network 3 corresponds to the private network (such as a home network). The user can authorize user-level network 1 to obtain terminal data from user-level network 3, such as data on Internet behavior habits in the home network. Based on the design of the network architecture, the first network element 1 can obtain data information in user-level network 3 through the first network element 3. Similarly, if user-level network 3 needs to use the network function service in user-level network 1, the first network element 3 in user-level network 3 can also initiate a request for the corresponding network service to user-level network 1.

[0198] Based on the design concept of the above multi-level network architecture, operators can serve as network access service providers and network function service providers to provide services to different sub-networks. Within the sub-network, only an independent first network element (or an additional independent second network element) needs to be deployed to enjoy the operator's network services. Compared with existing technologies such as network slicing and private network implementation, it is easier to deploy and user data can be better protected (data only exists within the sub-network).

[0199] In another implementation, the first network element and the fifth network element may belong to different user-level networks.

[0200] In yet another implementation, the first network element belongs to a user-level network, and the fifth network element belongs to an operator-level network; or the first network element belongs to an operator-level network, and the fifth network element belongs to a user-level network.

[0201] The association between the first network element and the fifth network element can be configured locally via scripts. For example, if the fifth network element needs to use certain services of the first network element, the specific services and the corresponding first network element information (or the subnet information where the services reside) can be configured in the fifth network element. When a service triggers the fifth network element to call certain services, it will initiate a service request to the first network element based on the local configuration. Of course, the fifth network element can also obtain the services and the corresponding first network element information (or the subnet information where the services reside) through a query (for example, through an NRF or a server with query capabilities). A subnet can provide services specific to that subnet to other subnets, operator networks, or external networks (such as third-party application servers). These services include data services (sharing data within the subnet, including user behavior data and AI model data), computing services (providing computing power services to other networks or users), or other specialized network services. For example, AI models trained on a subnet can be made available to other networks. Some subnets may deploy their own computing servers and provide computing power services to other subnets. (The subnet where the first network element resides may have trained some AI models and made them available to other subnets.) For example, the fifth network element is located in a home network and needs to create a session, so it requests the first network element to create a session.

[0202] S602. After receiving the service triggering event, the first network element may refer to the process in the embodiment shown in FIG5 to execute the service request.

[0203] S603. The first network element sends service feedback to the fifth network element.

[0204] Correspondingly, the fifth network element receives the service feedback.

[0205] According to a communication method provided in an embodiment of the present application, a method for calling services between sub-networks is provided. The main corresponding scenario is that in addition to operator-level network services, sub-networks can also provide services to the outside (other sub-networks or outside the core network), such as data sharing services, computing services, etc. Based on the method of this embodiment, a more flexible business model can be provided for future networks. However, the existing communication system does not involve this multi-level network deployment architecture, but a unified network deployment architecture. The network deployment is not flexible enough and the development scale is large.

[0206] The above embodiment describes a solution for calling a network service or data in a sub-network or between sub-networks. The following describes how the first network element calls a network service or data in a specific communication scenario through an example:

[0207] As shown in Figure 8, a flow chart of a communication method in a session establishment scenario provided by an embodiment of the present application is provided. The third network element involved in the session establishment scenario includes: PCF, SMF and UPF. Exemplarily, the method may include the following steps:

[0208] S801. PCF, SMF, and UPF respectively register their capabilities with the fourth network element.

[0209] When PCF, SMF, and UPF register their capabilities, they carry at least one of the following information: PCF / SMF / UPF capabilities, identification, address information, status information, and network information to which they belong.

[0210] S802. The terminal sends a session establishment request to the first network element.

[0211] The session establishment request is used to request the establishment of a session. The session establishment request includes at least one of the following information: a terminal identifier, a session identifier, a data network name (DNN), and slice information.

[0212] S803a. After receiving the session establishment request, the first network element sends a subscription data acquisition request to the second network element.

[0213] The contract data acquisition request is used to request acquisition of session-related contract data of the terminal.

[0214] S803b. After receiving the subscription data acquisition request, the second network element sends a subscription data acquisition response to the first network element.

[0215] The contract data acquisition response includes the session-related contract data of the terminal.

[0216] In existing session creation scenarios, the RAN receives a session establishment request from a terminal and forwards it to the SMF. The SMF then obtains session-related terminal subscription data from the UDM / UDR. This means the SMF can directly access the terminal subscription data. The SMF then interacts with other network elements based on this subscription data to create subsequent sessions. This results in frequent transmission of user privacy data across the network, reducing security.

[0217] In this embodiment, the first network element uniformly obtains session-related contract data from the second network element and sends it to the SMF, while the SMF cannot directly access the terminal contract data related to the session, thereby avoiding frequent transmission of user privacy data in the network and improving data security.

[0218] S804a. The first network element sends a scheduling request to the fourth network element.

[0219] The scheduling request is used to obtain information of all third network elements related to the service from the fourth network element based on the service requested by the terminal.

[0220] Exemplarily, the scheduling request may include processing logic of the service of the first network element.

[0221] Alternatively, the first network element may send a scheduling request to the fourth network element multiple times based on the service processing logic.

[0222] S804b. After receiving the scheduling request, the fourth network element determines at least one third network element to be scheduled according to the scheduling request, and sends a scheduling response to the first network element.

[0223] The scheduling response includes at least one of the following information of the at least one scheduled third network element: capability, identification, address information, and status information of the at least one third network element.

[0224] For example, in the session establishment scenario, the fourth network element determines that the scheduled third network element includes a PCF and an SMF. The scheduling response includes the capabilities, identifiers, address information, and status information of the PCF and SMF that can provide services to the first network element.

[0225] For other services, the network elements that may be involved may be different.

[0226] S805a. The first network element sends a session policy request to the PCF.

[0227] The session policy request is used to request the PCF for the session policy of the session. The session policy request includes at least one of the following information: a DNN and network slice information. For example, the network slice information may be single network slice selection assistance information (S-NSSAI).

[0228] The first network element may also have acquired or stored the session policy of the session in advance. Therefore, this step is optional and is indicated by a dotted line in the figure.

[0229] S805b. After receiving the session policy request, the PCF sends a session policy response to the first network element.

[0230] After receiving the session policy request, the PCF generates a session policy based on the DNN and / or network slice information carried in the session policy request, and sends a session policy response to the first network element. The session policy response includes the above-mentioned session policy (SM policy).

[0231] The corresponding session policy request is optional, and this step may also be optional, as indicated by a dotted line in the figure.

[0232] S806. The first network element updates the session policy.

[0233] The update here can be understood as the first network element further modifying the session policy obtained from the PCF based on the terminal's session-related subscription data. For example, if the terminal's session-related subscription data allows a session bandwidth of 10 Mbps for the terminal, while the session policy allows a session bandwidth of 8 Mbps for the terminal, the first network element can update the session policy based on pre-defined criteria, either the terminal's session-related subscription data or the session policy obtained from the PCF. Alternatively, if the first network element has also configured some local policies, the session policy can be updated with the first network element's local policy as the highest priority.

[0234] The corresponding session policy request and session policy response are optional. This step may also be optional, as indicated by a dotted line in the figure.

[0235] S807. The first network element sends a session establishment request to the SMF.

[0236] The first network element invokes the session establishment service of the SMF and sends a session establishment request to the SMF. The session establishment request includes at least one of the following information: session policy information, session-related subscription data of the terminal, session-related parameters (DNN, network slice information), and RAN side information accessed by the terminal (base station address information, port number, etc.).

[0237] S808. After receiving the session establishment request, SMF performs user plane configuration on UPF.

[0238] In this embodiment, the SMF and UPF can maintain the existing coupling mode, that is, the SMF manages a specific UPF. The SMF generates session configuration information based on session policy information or the terminal's session-related subscription data and performs user plane configuration on the UPF. After completing the user plane configuration of the UPF, the SMF generates the corresponding session context.

[0239] S809.SMF sends a session establishment response to the first network element.

[0240] The SMF feeds back the generated session context to the first network element. That is, the session establishment response includes the session context.

[0241] In addition, the SMF may optionally send the user plane configuration information to the first network element. When the first network element needs to re-invoke a new SMF to modify the session, the user plane configuration information may be sent to the selected new SMF. In this case, the SMF and the re-invoked SMF may not be the same SMF.

[0242] In addition, the SMF may also store the generated user plane configuration information in the second network element, and then return an operation completion indication or identification information of the stored data (such as PDU session identification information or the identification of the user plane configuration information) to the first network element. Later, when the first network element selects a new SMF, the identification information of the user plane configuration information may be sent to the new SMF, which then obtains the user plane configuration information from the second network element and modifies the corresponding session parameters. As a result, the SMF does not need to maintain user-related context separately, but rather the second network element stores it uniformly. Even if the SMF fails, the user-related context will not be lost.

[0243] S810. The first network element updates the session context, and stores the updated session context in the second network element.

[0244] S811. The first network element sends user plane configuration information to the RAN.

[0245] The user plane configuration information includes at least one of the following information: UPF address information and QoS configuration information.

[0246] S812. The first network element sends a session establishment completion message to the terminal.

[0247] The session establishment completion message includes session-related parameters, such as uplink data packet QoS execution rules, etc.

[0248] In existing session creation scenarios, the terminal sends a session creation request to the SMF. After receiving the session creation request, the SMF obtains the terminal subscription data related to the session from the UDM / UDR and then performs subsequent session creation. In this embodiment, the interaction between the SMF and the PCF / UPF is reduced, and most of the execution logic is unified and handled by the first network element, improving the flexibility of network deployment and management.

[0249] As shown in Figure 9, a flow chart of a communication method in another session establishment scenario provided by an embodiment of the present application is provided. The third network element involved in the session establishment scenario includes: PCF, SMF and UPF. In this embodiment, PCF, SMF and UPF are decoupled from each other. Exemplarily, the method may include the following steps:

[0250] S901. PCF, SMF, and UPF respectively register their capabilities with the fourth network element.

[0251] For the specific implementation of this step, reference may be made to step S801 in the embodiment shown in FIG8 .

[0252] S902. The terminal sends a session establishment request to the first network element.

[0253] For the specific implementation of this step, reference may be made to step S802 in the embodiment shown in FIG8 .

[0254] S903a. After receiving the session establishment request, the first network element sends a subscription data acquisition request to the second network element.

[0255] For the specific implementation of this step, reference may be made to step S803a in the embodiment shown in FIG8 .

[0256] S903b: After receiving the subscription data acquisition request, the second network element sends a subscription data acquisition response to the first network element, wherein the subscription data acquisition response includes the session-related subscription data of the terminal.

[0257] For the specific implementation of this step, reference may be made to step S803b in the embodiment shown in FIG8 .

[0258] S904a. The first network element sends a scheduling request to the fourth network element.

[0259] For the specific implementation of this step, reference may be made to step S804a in the embodiment shown in FIG8 .

[0260] S904b. After receiving the scheduling request, the fourth network element determines at least one third network element to be scheduled based on the scheduling request and sends a scheduling response to the first network element. The scheduling response includes at least one of the following information about the at least one third network element to be scheduled: capability, identification, address information, and status information of the at least one third network element.

[0261] For the specific implementation of this step, reference may be made to step S804b in the embodiment shown in FIG8 .

[0262] S905a. The first network element sends a session policy request to the PCF, wherein the session policy request includes at least one of the following information: data network name DNN, network slice information.

[0263] For the specific implementation of this step, reference may be made to step S805a in the embodiment shown in FIG8 .

[0264] S905b. After receiving the session policy request, the PCF sends a session policy response to the first network element, wherein the session policy response includes a session policy generated based on the DNN and / or network slice information.

[0265] For the specific implementation of this step, reference may be made to step S805b in the embodiment shown in FIG8 .

[0266] S906. The first network element updates the session policy.

[0267] For the specific implementation of this step, reference may be made to step S806 in the embodiment shown in FIG8 .

[0268] S907. The first network element sends a session establishment request to the SMF.

[0269] For the specific implementation of this step, reference may be made to step S807 in the embodiment shown in FIG8 .

[0270] S908. After receiving the session establishment request, the SMF sends a session establishment response to the first network element.

[0271] In this embodiment, the SMF and UPF are independent of each other. The SMF completes session configuration based on the session policy, the terminal's session-related subscription data, RAN-side information, and other information, and sends the session management context, N2 information, and user plane configuration information to the first network element. That is, the session establishment response includes the session management context, N2 information, and user plane configuration information. The session configuration information may include at least one of the following: user plane path information (RAN address information, port information, DNN, slice information, etc.), data packet QoS enforcement rules, charging rules, and monitoring rules.

[0272] The SMF may also store the session management context, N2 information and user plane configuration information in the second network element, and only return an operation completion indication or identification information of the stored data to the first network element.

[0273] S909. The first network element sends a user plane resource request to the fourth network element.

[0274] The user plane resource request is used by the first network element to request user plane resources from the fourth network element based on user configuration information. The user plane resource request may include at least one of the following information: RAN side information, DNN, network slice information, QoS information (such as session bandwidth, rate guaranteed bandwidth, scheduling priority, etc.).

[0275] S910. After receiving the user plane resource request, the fourth network element sends a user plane resource response to the first network element.

[0276] The fourth network element feeds back to the first network element the UPF information that can execute the session, such as the address information of the UPF, based on the user plane resource request of the first network element.

[0277] S911. The first network element performs user plane configuration on the UPF.

[0278] The first network element performs user plane configuration on the UPF scheduled by the fourth network element based on the received user plane resource response, and carries user plane configuration information.

[0279] If the user plane also provides service functions, the first network element can send the configured user plane context (similar to the N4 session in 5G) to the UPF, and the UPF processes the terminal data packets based on the configuration information.

[0280] S912. The first network element updates the session context, and stores the updated session context in the second network element.

[0281] For the specific implementation of this step, reference may be made to step S810 in the embodiment shown in FIG8 .

[0282] S913. The first network element sends user plane configuration information to the RAN.

[0283] For the specific implementation of this step, reference may be made to step S811 in the embodiment shown in FIG8 .

[0284] S914. The first network element sends a session establishment completion message to the terminal.

[0285] For the specific implementation of this step, reference may be made to step S812 in the embodiment shown in FIG8 .

[0286] In existing session creation scenarios, the terminal sends a session creation request to the SMF. After receiving the session creation request, the SMF obtains the terminal subscription data related to the session from the UDM / UDR and then performs subsequent session creation. In this embodiment, however, there is no direct interaction between the SMF and the PCF / UPF. All execution logic is unified and handled by the first network element, improving the flexibility of network deployment and management.

[0287] The above embodiment shows how the first network element calls a network service or data in a session creation scenario. The following example shows how the first network element calls a network service or data in a terminal access scenario:

[0288] As shown in Figure 10, a flow chart of a communication method in a terminal registration scenario provided in an embodiment of the present application is provided. The third network element involved in the terminal registration scenario includes: PCF, AMF. Exemplarily, the method may include the following steps:

[0289] S1001. PCF and AMF respectively register their capabilities with the fourth network element.

[0290] When PCF and AMF register their capabilities, they carry at least one of the following information: PCF / AMF capabilities, identification, address information, status information, and network information.

[0291] S1002. The terminal sends a registration request to the first network element.

[0292] The registration request is used to request registration with the network. The registration request may include an identifier of the terminal.

[0293] S1003a. After receiving the registration request, the first network element sends an access authentication / subscription data acquisition request to the second network element.

[0294] The access authentication / subscription data acquisition request is used to request the acquisition of the terminal's access and / or mobility management related subscription data.

[0295] S1003b. After receiving the access authentication / subscription data acquisition request, the second network element sends an access authentication / subscription data acquisition response to the first network element.

[0296] The access authentication / contract data acquisition response includes the user's access and / or mobility management related contract data.

[0297] In existing terminal registration scenarios, the RAN receives a terminal's registration request and forwards it to the AMF / PCF. The AMF / PCF obtains access and / or mobility management-related subscription data from the UDM / UDR. Based on this access and / or mobility management-related subscription data, the AMF / PCF then interacts with other network elements to proceed with the subsequent registration process. This results in frequent transmission of user privacy data within the network, reducing security.

[0298] In this embodiment, the first network element uniformly obtains session-related subscription data from the second network element and sends it to the PCF, while the PCF cannot directly access access and / or mobility management-related subscription data, thereby avoiding frequent transmission of user privacy data in the network and improving data security.

[0299] S1004a. The first network element sends a scheduling request to the fourth network element.

[0300] The scheduling request is used to obtain information of all third network elements related to the service from the fourth network element based on the service requested by the terminal.

[0301] Exemplarily, the scheduling request may include processing logic of the service of the first network element.

[0302] Alternatively, the first network element may send a scheduling request to the fourth network element multiple times based on the service processing logic.

[0303] S1004b. After receiving the scheduling request, the fourth network element determines at least one third network element to be scheduled according to the scheduling request, and sends a scheduling response to the first network element.

[0304] The scheduling response includes at least one of the following information of the at least one scheduled third network element: capability, identification, address information, and status information of the at least one third network element.

[0305] For example, in the session establishment scenario, the fourth network element determines that the scheduled third network element includes a PCF and an AMF. The scheduling response includes the capabilities, identifiers, address information, and status information of the PCF and AMF that can provide services to the first network element.

[0306] S1005a. The first network element sends an access and / or mobility management policy request to the PCF.

[0307] The access and / or mobility management policy request is used to request the PCF to obtain the access and / or mobility management policy.

[0308] The first network element may also have acquired or stored the access and / or mobility management policy in advance. Therefore, this step is optional and is indicated by a dotted line in the figure.

[0309] S1005b. After receiving the access and / or mobility management policy request, the PCF sends an access and / or mobility management policy response to the first network element.

[0310] After receiving the access and / or mobility management policy request, the PCF generates an access and / or mobility management policy and sends the access and / or mobility management policy to the first network element.

[0311] The access and / or mobility management policy response includes an access and / or mobility management policy.

[0312] Corresponding to the above-mentioned access and / or mobility management policy request being optional, this step may also be optional, as indicated by a dotted line in the figure.

[0313] S1006. The first network element updates the access and / or mobility management policy.

[0314] The update here can be understood as the first network element further modifying the access and / or mobility management policy obtained from the PCF based on the access and / or mobility management related subscription data.

[0315] Corresponding to the above-mentioned access and / or mobility management policy request, access and / or mobility management policy response is optional, and this step may also be optional, which is indicated by a dotted line in the figure.

[0316] S1007a. The first network element sends an access and / or mobility management context creation request to the AMF.

[0317] The first network element invokes the access and / or mobility management service of the AMF and sends an access and / or mobility management context creation request to the AMF, wherein the access and / or mobility management context creation request is used to request the AMF to create an access and / or mobility management context.

[0318] For example, as mentioned above, in the future, the access and mobility management function network element may be divided into two network elements: the access management function network element and the mobility management function network element. The first network element can send an access management context creation request to the access management function network element and a mobility management context creation request to the mobility management function network element respectively.

[0319] S1107b.AMF sends an access and / or mobility management context creation response to the first network element.

[0320] After receiving the access and / or mobility management context creation request, the AMF creates an access and / or mobility management context, wherein the access and / or mobility management context creation response includes the access and / or mobility management context.

[0321] S1008. The first network element creates / stores an access and / or mobility management context in the second network element.

[0322] S1009. The first network element sends a registration response to the terminal.

[0323] The registration response is used to indicate that the terminal has been registered with the network.

[0324] In existing registration scenarios, the terminal sends a registration request to the AMF. After receiving the terminal's registration request, the AMF obtains access and / or mobility management-related subscription data from the UDM / UDR and then proceeds with the subsequent registration process. In this embodiment, the interaction between the AMF and the PCF is reduced, and most of the execution logic is unified and handled by the first network element, improving the flexibility of network deployment and management.

[0325] The above embodiments illustrate how the first network element calls a network service or data in a session creation scenario and a registration scenario. The following example illustrates how the first network element calls a network service or data in a service request scenario:

[0326] As shown in Figure 11, a flow chart of a communication method in a service request scenario provided by an embodiment of the present application is provided. The third network element involved in the service request scenario includes: SMF and AMF. Exemplarily, the method may include the following steps:

[0327] S1101.SMF and AMF respectively register their capabilities with the fourth network element.

[0328] When SMF and AMF register their capabilities, they carry at least one of the following information: SMF / AMF capabilities, identification, address information, status information, and network information.

[0329] S1102. The terminal sends a service request to the first network element.

[0330] The service request is used to request a connection to the network to obtain network services. The corresponding operation of the network element in the network is to change the terminal state from idle to connected, and then the suspended session of the terminal will be activated. Therefore, the process of this embodiment involves requesting the AMF to change the access and / or mobility management context of the terminal (terminal status update), and the SMF to update the PDU session of the terminal.

[0331] The service request includes at least one of the following information: terminal identification, session identification, DNN, and slice information.

[0332] S1103a. After receiving the service request, the first network element sends an access authentication / user context acquisition request to the second network element.

[0333] The access authentication / user context acquisition request is used to request acquisition of user context.

[0334] S1103b. After receiving the access authentication / user context acquisition request, the second network element sends an access authentication / user context acquisition response to the first network element.

[0335] The access authentication / user context acquisition response includes a mobility management context and a session management context.

[0336] In the existing business service scenario, after receiving the service request from the terminal, AMF obtains the user context from UDM / UDR, that is, AMF can directly access the user context. Then, AMF interacts with other network elements based on the user context to provide subsequent business services, causing the user's privacy data to be frequently transmitted in the network, reducing security.

[0337] In this embodiment, the first network element uniformly obtains the user context from the second network element and sends it to the AMF, and the AMF cannot directly access the user context, thereby avoiding frequent transmission of user privacy data in the network and improving data security.

[0338] S1104a. The first network element sends a scheduling request to the fourth network element.

[0339] The scheduling request is used to obtain information of all third network elements related to the service from the fourth network element based on the service requested by the terminal.

[0340] Exemplarily, the scheduling request may include processing logic of the service of the first network element.

[0341] Alternatively, the first network element may send a scheduling request to the fourth network element multiple times based on the service processing logic.

[0342] S1104b. After receiving the scheduling request, the fourth network element determines at least one third network element to be scheduled according to the scheduling request, and sends a scheduling response to the first network element.

[0343] The scheduling response includes at least one of the following information of the at least one scheduled third network element: capability, identification, address information, and status information of the at least one third network element.

[0344] For example, in this business service scenario, the fourth network element determines that the scheduled third network element includes AMF and SMF. The scheduling response includes the capabilities, identification, address information, and status information of the AMF and SMF that can provide services to the first network element.

[0345] S1105a. The first network element sends a user session update request to the SMF.

[0346] The user session update request is used to request the SMF to update the protocol data unit (PDU) session of the terminal. The user session update request includes a session management context obtained by the first network element from the second network element.

[0347] S1105b. After receiving the user session update request, the SMF sends a user session update response to the first network element.

[0348] After receiving the user session update request, the SMF updates the terminal's PDU session and, after completing the UPF's user plane configuration, updates the session management context. The user session update response indicates that the terminal's PDU session has been updated. The user session update response includes the updated session management context. The updated session management context includes user plane configuration information.

[0349] S1106. The first network element updates the session management context.

[0350] After receiving the updated session management context, the first network element stores it in the second network element.

[0351] S1107. The first network element sends user plane configuration information to the RAN.

[0352] The first network element sends the user plane configuration information included in the session management context to the RAN.

[0353] S1108a. The first network element sends an access and / or mobility management context update request to the AMF.

[0354] The first network element invokes the access and / or mobility management service of the AMF and sends an access and / or mobility management context update request to the AMF, wherein the access and / or mobility management context update request is used to request the AMF to update the access and / or mobility management context.

[0355] For example, as mentioned above, in the future, the access and mobility management function network element may be divided into two network elements: the access management function network element and the mobility management function network element. The first network element can send an access management context update request to the access management function network element and a mobility management context update request to the mobility management function network element respectively.

[0356] S1108b.AMF sends an access and / or mobility management context update response to the first network element.

[0357] After receiving the access and / or mobility management context update request, the AMF updates the access and / or mobility management context, wherein the access and / or mobility management context update response includes the updated access and / or mobility management context.

[0358] S1109. The first network element updates / stores the access and / or mobility management context.

[0359] S1110. The first network element sends a service response to the terminal.

[0360] The business response includes the business service result.

[0361] In existing service scenarios, the terminal sends a service request to the AMF. After receiving the service request from the terminal, the AMF obtains the user context from the UDM / UDR and then performs subsequent service processes. In this embodiment, the interaction between the AMF and SMF is reduced, and most of the execution logic is normalized and handled by the first network element, which improves the flexibility of network deployment and management.

[0362] It is understood that, in order to implement the functions in the above embodiments, each network element includes a hardware structure and / or software module corresponding to each function. Those skilled in the art should readily appreciate that, in conjunction with the various exemplary units and method steps described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or in a hardware-driven manner by computer software depends on the specific application scenario and design constraints of the technical solution.

[0363] Figures 12 and 13 are schematic diagrams of possible communication devices provided in embodiments of the present application. These communication devices can be used to implement the functions of each network element in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0364] As shown in Figure 12, the communication device 1200 includes a processing unit 1210 and a transceiver unit 1220. The communication device 1200 is used to implement the functions of each network element in the method embodiments shown in Figures 5 to 11 above.

[0365] When the communication device 1200 is used to implement the function of the first network element in the method embodiment shown in Figure 5: the transceiver unit 1220 is used to perform the operations of the first network element in S501, S502, S504~S506 in the embodiment shown in Figure 5; or when the communication device 1200 is used to implement the function of the first network element in the method embodiment shown in Figure 6: the transceiver unit 1220 is used to perform the operations of the first network element in S601~S603 in the embodiment shown in Figure 6.

[0366] When the communication device 1200 is used to implement the function of the second network element in the method embodiment shown in Figure 5: the transceiver unit 1220 is used to execute the operations of the second network element in S501, S504 to S506 in the embodiment shown in Figure 5; or when the communication device 1200 is used to implement the function of the second network element in the method embodiment shown in Figure 6: the transceiver unit 1220 is used to execute the operations of the second network element in S602 in the embodiment shown in Figure 6.

[0367] When the communication device 1200 is used to implement the function of the third network element in the method embodiment shown in Figure 5: the transceiver unit 1220 is used to execute the operations of the third network element in S502 and S504 in the embodiment shown in Figure 5; the processing unit 1210 is used to execute S503 in the embodiment shown in Figure 5; or when the communication device 1200 is used to implement the function of the third network element in the method embodiment shown in Figure 6: the transceiver unit 1220 is used to execute the operations of the third network element in S602 in the embodiment shown in Figure 6.

[0368] When the communication device 1200 is used to implement the function of the fourth network element in the method embodiment shown in Figure 8: the transceiver unit 1220 is used to perform the operation of the fourth network element in S801 in the embodiment shown in Figure 8; or when the communication device 1200 is used to implement the function of the fourth network element in the method embodiment shown in Figure 9: the transceiver unit 1220 is used to perform the operation of the fourth network element in S901 in the embodiment shown in Figure 9; or when the communication device 1200 is used to implement the function of the fourth network element in the method embodiment shown in Figure 10: the transceiver unit 1220 is used to perform the operation of the fourth network element in S1001 in the embodiment shown in Figure 10; or when the communication device 1200 is used to implement the function of the fourth network element in the method embodiment shown in Figure 11: the transceiver unit 1220 is used to perform the operation of the fourth network element in S1101 in the embodiment shown in Figure 11.

[0369] A more detailed description of the processing unit 1210 and the transceiver unit 1220 can be directly obtained by referring to the relevant descriptions in the method embodiments shown in Figures 5 to 11, and will not be repeated here.

[0370] As shown in Figure 13, communication device 1300 includes a processor 1310 and an interface circuit 1320. Processor 1310 and interface circuit 1320 are coupled to each other. It is understood that interface circuit 1320 can be a transceiver or an input / output interface. Optionally, communication device 1300 may also include a memory 1330 for storing instructions executed by processor 1310, input data required by processor 1310 to execute instructions, or data generated by processor 1310 after executing instructions.

[0371] When the communication device 1300 is used to implement the methods shown in FIG. 5 to FIG. 11 , the processor 1310 is used to implement the functions of the processing unit 1210 , and the interface circuit 1320 is used to implement the functions of the transceiver unit 1220 .

[0372] When the above-mentioned communication device is a chip applied to a first network element, the first network element chip implements the functions of the first network element in the above-mentioned method embodiment. The first network element chip receives information from other modules (such as a radio frequency module or antenna) in the first network element, and the information is sent to the first network element by the second network element, the third network element, or the fourth network element; or the first network element chip sends information to other modules (such as a radio frequency module or antenna) in the first network element, and the information is sent to the second network element, the third network element, or the fourth network element by the first network element.

[0373] When the above-mentioned communication device is a chip applied to a second network element, the second network element chip implements the functions of the second network element in the above-mentioned method embodiment. The second network element chip receives information from other modules (such as a radio frequency module or antenna) in the second network element, and the information is sent by the first network element or the third network element to the second network element; or the second network element chip sends information to other modules (such as a radio frequency module or antenna) in the second network element, and the information is sent by the second network element to the first network element or the third network element.

[0374] When the above-mentioned communication device is a chip applied to a third network element, the third network element chip implements the functions of the third network element in the above-mentioned method embodiment. The third network element chip receives information from other modules (such as a radio frequency module or antenna) in the third network element, and the information is sent to the third network element by the first network element, the second network element, or the fourth network element; or the third network element chip sends information to other modules (such as a radio frequency module or antenna) in the third network element, and the information is sent to the first network element, the second network element, or the fourth network element by the third network element.

[0375] When the above-mentioned communication device is a chip applied to a fourth network element, the fourth network element chip implements the functions of the fourth network element in the above-mentioned method embodiment. The fourth network element chip receives information from other modules (such as a radio frequency module or an antenna) in the fourth network element, and the information is sent by the first network element or the third network element to the fourth network element; or the fourth network element chip sends information to other modules (such as a radio frequency module or an antenna) in the fourth network element, and the information is sent by the fourth network element to the first network element or the third network element.

[0376] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0377] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a network device or a terminal device. Of course, the processor and the storage medium can also be present in a network device or a terminal device as discrete components.

[0378] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive.

[0379] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0380] In this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can 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 previous and next related objects are in an "or" relationship; in the formulas of this application, the character " / " indicates that the previous and next related objects are in a "division" relationship.

[0381] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

Claims

1. A communication method, characterized in that: The method comprises: The first network element obtains service input data or an acquisition credential of the service input data from the second network element according to the received service triggering event; The first network element sends a service request to at least one third network element, where the service request includes the service input data or an acquisition credential for the service input data; The first network element receives service feedback from the at least one third network element, where the service feedback includes an execution result of the service.

2. The method according to claim 1, characterized in that: The first network element is used to process different service requests in the network, and the second network element is used to provide data storage services for the first network element and / or the at least one third network element, and the at least one third network element is a network element that provides network functions; Among them, the at least one third network element includes: a session management function SMF network element, an access and mobility management function AMF network element, and a policy and control function PCF network element.

3. The method according to claim 1 or 2, characterized in that The first network element sending a service request to at least one third network element includes: The first network element sends the service request to the at least one third network element according to the execution logic of the service; Among them, the execution logic of the service includes at least one of the following information: at least one third network element that needs to be called for each service, the scheduling order of the at least one third network element, the format of the service input data corresponding to each third network element, and the content of the service input data corresponding to each third network element.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The first network element sends a scheduling request to a fourth network element, wherein the fourth network element is used to provide a network function discovery and selection service for the first network element; The first network element receives a scheduling response from the fourth network element, where the scheduling response includes at least one of the following information of the at least one third network element: capability, identification, address information, status information, and network information of the at least one third network element.

5. The method according to any one of claims 1 to 4, characterized in that The service feedback also includes the update result of the service input data; The method further comprises: The first network element sends a data synchronization request to the second network element, where the data synchronization request includes an update result of the service input data; The first network element receives a data synchronization response from the second network element.

6. The method according to any one of claims 1 to 5, characterized in that The service triggering event includes a service request from a fifth network element; The method further comprises: The first network element sends the service feedback to the fifth network element.

7. The method according to claim 6, characterized in that The first network element and the fifth network element belong to different networks; the different networks are user-level networks or operator networks, or different user-level networks, or different network slices.

8. The method according to any one of claims 1 to 7, characterized in that The service input data is processed user data.

9. The method according to any one of claims 1 to 7, characterized in that The service input data is unprocessed user data; the method further includes: The first network element processes the service input data to obtain processed user data.

10. The method according to claim 8 or 9, characterized in that The processed user data includes at least one of the following: encrypted user data, user data with user identification information removed, a temporary user identification, and an encrypted user identification.

11. The method according to any one of claims 6 to 10, characterized in that The service triggering event includes at least one of the following: a communication service request initiated by a terminal, a communication service request initiated by the fifth network element, a periodic communication service, and an event-triggered communication service; The first network element sending a service request to at least one third network element includes: the first network element sending the service request to the at least one third network element associated with the service triggering event, respectively, where the service request includes the service input data obtained by the first network element from the second network element and the execution result of the service obtained from other third network elements among the at least one third network element; The first network element receiving the service feedback from the at least one third network element includes: the first network element receiving the service feedback from the at least one third network element respectively.

12. The method according to any one of claims 1 to 11, characterized in that The service triggering event is a session establishment request, and the service input data includes session contract data; The first network element sending a service request to at least one third network element includes: The first network element sends a session policy request to the PCF, where the session policy request includes at least one of the following information: a data network name DNN and network slice information; The first network element receiving the service feedback from the at least one third network element includes: The first network receives a session policy response from the PCF, where the session policy response includes a session policy, where the session policy is generated based on the DNN and / or the network slice information.

13. The method according to claim 12, characterized in that The first network element sends a service request to at least one third network element, further comprising: The first network element sends a session establishment request to the SMF, where the session establishment request includes session policy information or session subscription information; The first network element receiving the service feedback from the at least one third network element further includes: The first network element receives a session establishment response from the SMF, where the session establishment response includes a session context.

14. A communication method, characterized in that: The method comprises: The second network element receives an acquisition request from the first network element, where the acquisition request is used to request to acquire service input data or an acquisition credential of the service input data, where the acquisition credential of the service input data is a credential for acquiring the service input data; The second network element sends an acquisition response to the first network element, where the acquisition response includes the service input data or an acquisition credential for the service input data.

15. The method according to claim 14, characterized in that The first network element is used to process different service requests in the network, and the second network element is used to provide data storage services for the first network element and / or at least one third network element, where the at least one third network element is a network element that provides network functions; Among them, the at least one third network element includes: a session management function SMF network element, an access and mobility management function AMF network element, and a policy and control function PCF network element.

16. The method according to claim 14 or 15, characterized in that The service input data is processed user data; The method further comprises: The second network element processes the service input data to obtain processed user data.

17. The method according to claim 16, characterized in that The processed user data includes at least one of the following: encrypted user data, user data with user identification information removed, a temporary user identification, and an encrypted user identification.

18. A communication method, characterized in that: The method comprises: The third network element receives a service request, where the service request includes service input data or a credential for obtaining the service input data; The third network element executes the requested service according to the service request.

19. The method according to claim 18, characterized in that The method further comprises: The third network element sends service feedback to the first network element, where the service feedback includes an execution result of the service.

20. The method according to claim 19, characterized in that The first network element is used to process different service requests in the network, and the third network element is a network element that provides network functions; Among them, the third network element includes any one of the following: session management function SMF network element, access and mobility management function AMF network element, policy and control function PCF network element.

21. The method according to claim 19 or 20, characterized in that The third network element receiving the service request includes: The third network element receives a service request from the first network element.

22. The method according to any one of claims 19 to 21, characterized in that The method further comprises: The third network element sends a registration request to the fourth network element, where the registration request includes at least one of the following information: capabilities, identification, address information, status information, and network information of the third network element, wherein the fourth network element is used to provide a network function discovery and selection service for the first network element; The third network element receives a registration response from the fourth network element.

23. The method according to claim 22, characterized in that The third network element receiving the service request includes: The third network element receives the service request from the fourth network element.

24. The method according to any one of claims 19 to 23, wherein: The service request includes a credential for obtaining the service input data, and the third network element receives the service request, including: The third network element sends an acquisition request to the second network element according to the acquisition credential, where the second network element is used to provide data storage services for the first network element and / or the third network element; The third network element receives an acquisition response from the second network element, where the acquisition response includes the service input data.

25. The method according to claim 24, characterized in that The service input data is processed user data.

26. The method according to claim 25, characterized in that The processed user data includes at least one of the following: encrypted user data, user data with user identification information removed, a temporary user identification, and an encrypted user identification.

27. The method according to any one of claims 18 to 26, characterized in that The service request includes the service input data obtained by the first network element from the second network element and the execution result of the service obtained from other third network elements among the at least one third network element.

28. The method according to any one of claims 20 to 27, characterized in that The third network element is a PCF network element, and the service input data includes session subscription data; The third network element receiving the service request includes: The third network element receives a session policy request, where the session policy request includes at least one of the following information: a data network name DNN, and network slice information; The third network element sending service feedback to the first network element includes: The third network element sends a session policy response to the first network element, where the session policy response includes a session policy, and the session policy is generated based on the DNN and / or the network slice information.

29. The method according to any one of claims 20 to 28, wherein The third network element is an SMF network element; The third network element receiving the service request includes: The third network element receives a session establishment request, where the session establishment request includes session policy information or session subscription information; The third network element sending service feedback to the first network element includes: The third network element sends a session establishment response to the first network element, where the session establishment response includes a session context.

30. A communication method, characterized in that: The method comprises: The fourth network element receives a registration request from at least one third network element, where the registration request includes at least one of the following information: capability, identification, address information, status information, and network information of the third network element; The fourth network element sends a registration response to the at least one third network element; The fourth network element receives a scheduling request from the first network element; The fourth network element determines, according to the scheduling request, at least one third network element to be scheduled; The fourth network element sends a scheduling response to the first network element, and the scheduling response includes at least one of the following information of at least one third network element scheduled: the capability, identification, address information, and status information of the at least one third network element; or the fourth network element sends the scheduling request to the at least one third network element scheduled.

31. The method according to claim 30, wherein The first network element is used to process different service requests in the network, the at least one third network element is a network element that provides network functions, and the fourth network element is used to provide network function discovery and selection services for the first network element; Among them, the at least one third network element includes: a session management function SMF network element, an access and mobility management function AMF network element, and a policy and control function PCF network element.

32. A communication device, characterized in that: The method comprises functions or units for executing the method according to any one of claims 1 to 31.

33. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other devices outside the communication device and transmit them to the processor, or send signals from the processor to other devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1 to 31 through logic circuits or execution code instructions.

34. A communication system, characterized in that Comprising a communication device as claimed in claim 32 or 33.

35. A chip, characterized in that: The chip is used to execute the method according to any one of claims 1 to 13, or to execute the method according to any one of claims 14 to 17, or to execute the method according to any one of claims 18 to 29, or to execute the method according to claim 30 or 31.

36. A chip module, characterized in that: The invention comprises a transceiver component and a chip, wherein the chip is used to execute the method according to any one of claims 1 to 13, or to execute the method according to any one of claims 14 to 17, or to execute the method according to any one of claims 18 to 29, or to execute the method according to claim 30 or 31.

37. A computer-readable storage medium, characterized in that The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, the method according to any one of claims 1 to 31 is implemented.

38. A computer program product which, when run on a computer, causes the method of any one of claims 1 to 31 to be performed.

Images