Service processing logic distribution method, network function and service processing equipment

Abstract

The invention relates to a service processing logic distribution method, a first NF and a service processing device. The method comprises the following steps: sending a first service processing logic to at least one service processing device; the first service processing logic is generated according to user context information acquired from the second NF.

Description

Technical Field

[0001] The present application relates to the field of communication technologies, and in particular, to a service processing logic distribution method, a network function, and a service processing device. Background Art

[0002] In the network architecture of the Fifth Generation Mobile Communication Technology (5G), a Network Function (NF) not only includes service processing logic but also includes context data related to services. The execution of the service processing logic depends on this context data stored locally in the NF. This service with the coupling of service processing logic and data provided by the NF is called a stateful service. The data of the stateful service is stored locally in a certain instance, and the requests of users must be sent to this instance for processing, which makes it difficult to share the load of a large number of user requests in the existing network among multiple instances. When an instance needs to be migrated due to planned (equipment update, on-orbit network elements with the periodic operation of the satellite) or unplanned (equipment failure) situations, it involves data migration and synchronization between instances, reducing the network operation and maintenance efficiency. Summary of the Invention

[0003] Based on this, in view of the above technical problems, it is necessary to provide a service processing logic distribution method, a network function, and a service processing device that can improve the network operation and maintenance efficiency.

[0004] In a first aspect, the present application provides a service processing logic distribution method, which is applied to a first Network Function (NF). The method includes:

[0005] Sending first service processing logic to at least one service processing device; the first service processing logic is generated according to user context information obtained from a second NF.

[0006] In one embodiment, the first NF includes any one of the following:

[0007] User Plane Function, Session Management Function, Computing Function, Data Function.

[0008] In one embodiment, the first NF and the second NF are the User Plane Function;

[0009] In one embodiment, the first NF and the second NF are the Session Management Function;

[0010] In one embodiment, the first NF is the Computing Function, and the second NF is the Data Function.

[0011] In one embodiment, the user context information includes at least one of the following:

[0012] Packet detection rule, forwarding action rule, quality of service implementation rule, usage reporting rule, caching action rule, user plane forwarding tunnel endpoint information.

[0013] In one embodiment, the first service processing logic includes at least one of the following:

[0014] Forwarding processing logic, charging processing logic, quality of service (QoS) control processing logic.

[0015] In one embodiment, the method further includes: generating, according to the user context information, first service processing logic supported by the at least one service processing device.

[0016] In one embodiment, if the at least one service processing device is an OpenFlow switch, the first service processing logic is a flow table entry supported by the OpenFlow protocol;

[0017] If the at least one service processing device is a P4 device, the first service processing logic is P4 code supported by the Runtime protocol;

[0018] If the at least one service processing device is an SRv6 device, the first service processing logic is an SRv6 policy and / or segment identifier (SID) supported by the BGP SR Policy protocol.

[0019] In one embodiment, it further includes:

[0020] If a migration indication is received, sending second service processing logic to the second service processing device;

[0021] The migration indication is used to indicate replacing a first service processing device with a second service processing device, where the first service processing device is a device among the at least one service processing device, and the second service processing device is a device outside the at least one service processing device.

[0022] In one embodiment, the migration indication includes an identifier of the first service processing device and an identifier of the second service processing device, and the identifier of the first service processing device is the same as the identifier of the second service processing device;

[0023] The second service processing logic is the first service processing logic.

[0024] In one embodiment, the migration instruction includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is the same as the identifier of the second service processing device;

[0025] If the network topology information corresponding to the second service processing device is different from the network topology information corresponding to the first service processing device, the second service processing logic is the service processing logic that supports the second service processing device generated according to the user context information.

[0026] In one embodiment, the migration instruction includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is different from the identifier of the second service processing device;

[0027] The second service processing logic is the service processing logic that supports the second service processing device generated according to the user context information.

[0028] In one embodiment, the migration instruction further includes the migration time;

[0029] If a migration instruction is received, sending the second service processing logic to the second service processing device includes:

[0030] If the migration instruction is received, before the migration time, send the second service processing logic to the second service processing device.

[0031] In a second aspect, the present application provides a method for distributing service processing logic, which is applied to a service processing device and includes: receiving the first service processing logic sent by the first NF; the first service processing logic is generated according to the user context information obtained from the second NF.

[0032] In a third aspect, the present application provides a first NF, including: a memory, a transceiver, and a processor;

[0033] The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations:

[0034] Send the first service processing logic to at least one service processing device; the first service processing logic is generated according to the user context information obtained from the second NF.

[0035] In a fourth aspect, the present application provides a service processing device, including: a memory, a transceiver, and a processor;

[0036] A memory for storing computer programs; a transceiver for transmitting and receiving data under the control of the processor; a processor for reading the computer programs in the memory and performing the following operations:

[0037] Receiving the first service processing logic sent by the first NF; the first service processing logic is generated according to the user context information obtained from the second NF.

[0038] In a fifth aspect, the present application provides a first NF, including:

[0039] A sending module for sending the first service processing logic to at least one service processing device; the first service processing logic is generated according to the user context information obtained from the second NF.

[0040] In a sixth aspect, the present application provides a service processing device, including:

[0041] A receiving module for receiving the first service processing logic sent by the first NF; the first service processing logic is generated according to the user context information obtained from the second NF.

[0042] In a seventh aspect, the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the method provided in the first aspect or any of its embodiments, or implements the method provided in the second aspect or any of its embodiments.

[0043] In an eighth aspect, the present application further provides a computer program product, including a computer program, and when the computer program is executed by a processor, it implements the method provided in the first aspect or any of its embodiments, or implements the method provided in the second aspect or any of its embodiments.

[0044] For the above service processing logic distribution method, network function, service processing device, storage medium and computer program product, the first NF sends the first service processing logic to at least one service processing device, where the first service processing logic is generated according to the user context information obtained from the second NF. Through this method, the user context information can be stored in the second NF, and the service processing logic can be distributed to the service processing device for execution, so that the user context information and the service processing logic can be separated, and at the same time, multiple equal service processing devices can process the user's service requests, realizing the decoupling of the user's service requests and the service processing device, thereby improving the network operation and maintenance efficiency. Description of the Drawings

[0045] To more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the following will briefly introduce the drawings required for use in the description of the embodiments or the related art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0046] Figure 1 It is a schematic diagram of the data packet processing flow in a UPF;

[0047] Figure 2 It is a schematic diagram of the network architecture of an SDN;

[0048] Figure 3 It is a schematic diagram of a service processing logic distribution method Figure 1 ;

[0049] Figure 4 It is a schematic diagram of a service processing logic distribution method Figure 2 ;

[0050] Figure 5 It is a schematic diagram of a network architecture Figure 1 ;

[0051] Figure 6 It is a schematic diagram of a network architecture Figure 2 ;

[0052] Figure 7 It is a schematic diagram of a network architecture Figure 3 ;

[0053] Figure 8 Based on the network architecture shown above Figure 6 It is a schematic diagram of a dynamic migration scenario Figure 1 ;

[0054] Figure 9 It is a schematic diagram of a service processing logic distribution method in a dynamic migration scenario;

[0055] Figure 10 Based on the network architecture shown above Figure 6 It is a schematic diagram in a dynamic migration scenario Figure 2 ;

[0056] Figure 11 Based on the network architecture shown above Figure 6 It is a schematic diagram in a dynamic migration scenario Figure 3 ;

[0057] Figure 12 It is a schematic diagram of the structure of the first NF provided by an embodiment;

[0058] Figure 13 It is a structural block diagram of the first NF in an embodiment. Detailed implementation manners

[0059] In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0060] To better illustrate the technical solution of the present application, the related technologies will be introduced first:

[0061] (1) Stateless service

[0062] With the development of cloud computing technology reaching a certain level of maturity, it can better support the development and deployment of cloud-native applications. As the network moves towards cloud-native maturity, the business processing logic can be separated from the context data, and such a service is called a stateless service. Among them, cloud-native applications refer to application programs built on cloud computing platforms, which have high scalability, reliability, and flexibility and can better adapt to the cloud computing environment.

[0063] A stateless service means that the instance providing the service does not store the user's information (data) locally, and at the same time, multiple equal instances can provide the service. When the user's request arrives, the load balancing mechanism can randomly find an instance to complete the response to the request. No matter which instance is selected, the final response completed is the same.

[0064] The stateless service decouples the business processing logic and data, enabling the service to be flexibly expanded, quickly restored, and facilitating load balancing among multiple instances. This design is widely used in the Information Technology (IT) industry, but due to the characteristics of the Communications Technology (CT) industry itself, the stateless design is still in the exploratory stage currently.

[0065] (2) Hot standby between NFs

[0066] To ensure that the reliability of the system reaches 99.999%, a redundant backup mechanism for devices and links is usually adopted. In this way, the standby device can quickly take over in case of a failure to ensure the continuous and stable operation of the system. However, this method will also cause waste of resources, especially in the space-based network. Due to limitations such as power, energy consumption, and weight, the resources of satellites are limited, so it is more difficult to implement redundant backup on the satellite.

[0067] (3) Working principle of the User Plane Function (UPF) in the related technology

[0068] The architecture reference models of the Session Management Function (SMF) and the UPF in 5G Core Network (5GC) nodes are described in the standard protocol 3GPP TS23.501. The SMF and the UPF interact through the Packet Forwarding Control Protocol (PFCP) to establish / update / delete the PFCP session context, which is also called the N4 session context. Among them, in the 5G network, N4 refers to the reference point between the SMF and the UPF, and the packet forwarding scheme is responsible for implementation on the N4 reference point.

[0069] The SMF provides (i.e., adds, modifies, or deletes) Packet Detection Rules (PDRs), Forwarding Action Rules (FARs), QoS Enforcement Rules (QERs), Usage Reporting Rules (URRs), and Buffer Action Rules (BARs) for each PFCP session context to control the packet processing in the UPF function, such as packet forwarding, policy and charging control, lawful interception, etc.

[0070] In an exemplary embodiment, Figure 1 It is a schematic diagram of the packet processing flow in the UPF. As Figure 1 shown, the packet processing flow in the UPF includes the following steps:

[0071] 101. Packet in.

[0072] The UPF can receive the packet and perform data processing.

[0073] 102. PFCP Session look up.

[0074] Among them, PFCP Session look up means looking up the PFCP session corresponding to the packet in the UPF function to determine the status, parameters, and configuration of the PFCP session for packet control and management.

[0075] 103. PFCP session’s PDR look up.

[0076] Among all the PDRs configured for this PFCP session, find the first PDR that matches the incoming packet.

[0077] In some embodiments, start from the PDR with the highest priority and then continue in descending order of priority until a matching PDR is found. Only select the highest-priority PDR that matches the packet, that is, once a matching PDR is found, the UPF will stop looking for PDRs.

[0078] Among them, the matching PDR may contain the identifiers of multiple associated Multi-Access Rules (MARs), FARs, QERs, URRs, etc. These rules can control the packet processing in the UPF, such as packet forwarding, policy and charging control, lawful interception, etc.

[0079] 104. Packet output.

[0080] After the packet is processed in the UPF, the packet is output.

[0081] The PFCP session context (also referred to as user context information in this application) includes but is not limited to PDR, FAR, QER, URR, and BAR, etc. How the packets generated by the user accessing different services are forwarded, how to charge, and how to perform QoS control all depend on this user information. If the SMF selects UPF1 (which can refer to any UPF) when the user is activated, then all subsequent data streams of the user need to be forwarded through UPF1, and the update / deletion of the user's information needs to be sent to UPF1 for processing.

[0082] (IV) SDN technology

[0083] SDN is a new network architecture, and its main ideas are the separation of the control plane and the forwarding plane, the centralized control and scheduling of network resources, and the open programmable ability.

[0084] In an exemplary embodiment, Figure 2 For a schematic diagram of the network architecture of SDN. As Figure 2 shown, the network architecture of SDN is mainly divided into three-layer architecture: Application Layer, Control Layer, and Infrastructure Layer.

[0085] Among them, upper-layer applications run in the application layer, and different application logics in the application layer control the packet forwarding function of the device through the application management ability of the Application Programming Interface (API) opened by the control layer.

[0086] The control layer consists of SDN control software (commonly known as the SDN controller), which can communicate with forwarding devices through standardized protocols to achieve control over the infrastructure layer. It can communicate with the underlying network devices using the OpenFlow protocol. Among them, OpenFlow is a network protocol used to achieve network programmability and flexibility. The core idea of OpenFlow is to separate the control plane and data plane of network devices (such as switches and routers). By using the OpenFlow protocol, network administrators can program and control network devices through an external controller to achieve dynamic management and optimization of network traffic. The OpenFlow protocol defines a standardized interface, enabling network devices from different manufacturers to communicate with an external controller in the same way. The external controller can use the OpenFlow protocol to send instructions to network devices, such as changing forwarding rules, adding or deleting virtual networks, etc. The goal of OpenFlow is to achieve network automation and intelligence, improving network manageability and flexibility.

[0087] The infrastructure layer mainly consists of forwarding devices, which are physical switches in the network and achieve the forwarding function by forwarding network traffic to their destinations.

[0088] The above stateful UPF design is not conducive to load sharing among multiple instances for a large number of user requests and the dynamic migration of UPF, which will affect the operation and maintenance efficiency of the existing network. Especially in satellite networks, the problem of frequent migration caused by its high dynamicity is more prominent.

[0089] Based on stateless design and SDN design, this application splits user context information (data) and business processing logic, and provides a business processing logic distribution method, network function, and business processing device, thereby improving network operation and maintenance efficiency.

[0090] The business processing logic distribution method provided by the embodiments of this application can be implemented through the interaction between a network function (referred to as the first NF in this application) and at least one business processing device. In this method, the first NF can send the first business processing logic to at least one business processing device. Correspondingly, after each business processing device receives the first business processing logic, the business processing device can run the first business processing logic. Among them, the first business processing logic is generated based on the user context information obtained from the second NF, and the user context information is stored in the second NF.

[0091] In an exemplary embodiment, Figure 3 For the schematic of a business processing logic distribution method Figure 1 . Such as Figure 3As shown, this scenario includes: a first NF 301, a second NF 302, and two service processing devices, which are the service processing device 1 and the service processing device 2 in Figure 3 . Among them, the first NF 301 can generate first service processing logic according to the user context information stored in the second NF 302, and then can send the first service processing logic to the service processing device 1 and the service processing device 2.

[0092] In some embodiments, the user context information includes at least one of the following:

[0093] Packet detection rule, forwarding action rule, quality of service implementation rule, usage reporting rule, caching action rule, user plane forwarding tunnel endpoint information.

[0094] In some embodiments, the packet detection rule can define how to detect and identify the data packets transmitted in the network, and can include checking information such as the source address, destination address, and protocol type of the data packets to determine the nature and priority of the data packets.

[0095] In some embodiments, the forwarding action rule can define how the data packets should be processed in the network, and can include determining whether the data packets should be discarded, forwarded, or cached, and how to forward them, etc.

[0096] In some embodiments, the quality of service implementation rule can define how to guarantee the quality of service in the network, and can include determining the priority of the data packets, restricting the bandwidth of the data packets, implementing traffic control, etc., to ensure that the critical services in the network can obtain the required bandwidth and performance.

[0097] In some embodiments, the usage reporting rule can define how to report the usage of network resources to the network administrator or service provider, and can include collecting information about the number of data packets, bandwidth usage, traffic patterns, etc., and sending this information to the network administrator or service provider.

[0098] In some embodiments, the caching action rule can define how to cache data in the network, and can include determining which data should be cached, the length of the caching time, how to update the cache, etc.

[0099] In some embodiments, the user plane forwarding tunnel endpoint information can define the tunnel endpoint information used when the user plane data is transmitted in the network, and can include determining the source and destination IP addresses of the tunnel, endpoint information, etc.

[0100] In some embodiments, the first service processing logic includes at least one of the following:

[0101] Forwarding processing logic, charging processing logic, quality of service QoS control processing logic.

[0102] In some embodiments, the above forwarding processing logic may refer to the logic for determining how to transfer data or messages from one node or system to another node or system. It involves operations such as selecting an appropriate path, determining the next-hop node, and processing the encapsulation and decapsulation of data packets to ensure that data can be transmitted in the correct order and along the correct path.

[0103] In some embodiments, the above billing processing logic may refer to the logic for calculating and managing the fees of communication services. It involves operations such as recording the usage of communication data, calculating fees according to billing policies and rates, generating billing reports, and handling billing disputes to ensure that communication service providers can accurately charge users for using the services.

[0104] In some embodiments, the above service quality QoS control processing logic may refer to the logic for managing and controlling the quality and performance of data transmission in a network. It involves defining and implementing QoS policies, allocating bandwidth resources, preferentially processing critical service traffic, and controlling parameters such as latency and packet loss rate to ensure that different applications and services in the network can obtain the required service levels and performance.

[0105] In an exemplary embodiment, Figure 4 is a schematic diagram of a method for distributing service processing logic Figure 2 , and the method includes:

[0106] 401. The first NF generates at least one first service processing logic supported by the service processing device according to the user context information.

[0107] Among them, when the service processing devices are different, their corresponding first service processing logics are also different. The above service processing device may be a programmable forwarding device.

[0108] The above first NF may obtain the stored user context information from the second NF and generate at least one first service processing logic supported by the service processing device based on the user context information.

[0109] Exemplarily, the above service processing device may be an OpenFlow switch, a P4 device, an SRv6 device, etc.

[0110] In some embodiments, if at least one service processing device is an OpenFlow switch, the first service processing logic is a flow table entry supported by the OpenFlow protocol.

[0111] An OpenFlow switch is a network device that supports the OpenFlow protocol and can accept instructions from an external controller through the OpenFlow protocol to achieve flexible control and management of network traffic.

[0112] The flow entries supported by the OpenFlow protocol include, but are not limited to, the following types of examples:

[0113] Match field: Used to describe the characteristics of the data packet, such as source address, destination address, protocol type, port number, etc.;

[0114] Action field: Used to specify the actions to be performed on the matched data packet, such as forwarding to a specified port, discarding the data packet, modifying the fields of the data packet, etc.;

[0115] Priority field: Used to determine the execution order of the flow entries. The flow entries with higher priority are executed first.

[0116] Counter field: Used to count information such as the number of matched data packets and the number of bytes;

[0117] Timeout field: Used to specify the survival time of the flow entry. After the timeout, the flow entry will be automatically deleted;

[0118] By using the above flow entries supported by the OpenFlow protocol, network traffic can be flexibly controlled, and automated and intelligent management of the network can be achieved.

[0119] In some embodiments, if the at least one service processing device is a P4 device, the first service processing logic is P4 code supported by the Runtime protocol.

[0120] The above P4 device is a network device that supports the P4 programming language. The forwarding behavior of the device can be defined by writing P4 code. The P4 programming language is a programming language used to define the behavior of the network data plane. It allows developers to describe the forwarding logic of network devices in a programming-like manner. Using the P4 programming language, developers can define matching rules, actions, and states to achieve flexible control and management of network traffic.

[0121] The above Runtime protocol is a protocol used to run P4 code on P4 devices. It defines the communication protocol between the device and the controller, allowing the controller to deploy P4 code to the device and monitor and control the forwarding behavior of the device in real time. By using P4 devices and the Runtime protocol, network administrators can flexibly define the forwarding behavior of network devices and achieve automated and intelligent management of the network. At the same time, the characteristics of the P4 programming language also enable network developers to develop and maintain network applications more easily.

[0122] In some embodiments, if at least one service processing device is an SRv6 device, the first service processing logic is an SRv6 policy and / or a segment identifier SID supported by the BGP SR Policy protocol.

[0123] The above SRv6 (Segment Routing IPv6) device is a network device that supports the SRv6 protocol and can perform traffic forwarding and path control in the network through the SRv6 protocol. SRv6 is a routing protocol based on IPv6. It uses IPv6 addresses as path identifiers and specifies the forwarding path of packets by inserting an SRv6 header into the packets. The SRv6 device can forward the packets to the specified destination according to the path information in the SRv6 header.

[0124] The above BGPSR Policy (BGPSegment Routing Policy) protocol is a protocol used to propagate SRv6 policies in the BGP protocol. It allows network administrators to publish SRv6 policies to the network through the BGP protocol so that other devices can understand and follow these policies. In the BGPSR Policy protocol, the supported SRv6 policies include path selection policies, traffic engineering policies, load balancing policies, etc. These policies can be implemented by defining different Segment Identifiers (SIDs). An SID is an identifier used to identify a path in the SRv6 protocol and can be divided into different types such as head node SID, intermediate node SID, and tail node SID. By using the SRv6 policies and SIDs supported by the BGPSR Policy protocol, the forwarding path of network traffic can be flexibly controlled to achieve network optimization and management.

[0125] 402. The first NF sends the first service processing logic to at least one service processing device.

[0126] Among them, after receiving the first service processing logic, each of the at least one service processing device can run the first service processing logic, so that the subsequent at least one service processing device can process the service data without difference and obtain the same processing effect.

[0127] The above service processing logic distribution method can store the user context information in the second NF and distribute the service processing logic to the service processing device for execution. In this way, the user context information and the service processing logic can be separated, and at the same time, the service requests of users can be processed by multiple equal service processing devices, realizing the decoupling of the service requests of users and the service processing devices, thereby improving the network operation and maintenance efficiency.

[0128] In some embodiments, the above first NF may include, but is not limited to, any one of the following:

[0129] User plane function, session management function, computing function, data function.

[0130] Among them, the difference between the above user plane function and the existing user plane function (UPF) in the related art is that the user plane function in this application is a new user plane function that separates the storage of user context information from the execution of service processing logic, which can be represented as NUPF in this application. The NUPF in this application is used to store user context information, and NUPF can support virtualization and Service Based Interface (SBI) interfaces; NUPF implements the N4 interface function in the existing 5GC.

[0131] The above session management function can be the existing session management function SMF or the network function corresponding to the session management function in the future network.

[0132] The above computing function and data function are network functions adapted to the future network architecture. The computing function can be represented as C-NF in this application, and the data function can be represented as D-NF in this application.

[0133] Among them, in the future network design, considering further separation of data and service logic and reducing the tight coupling between data and service processing, the above-mentioned separate data function is considered to be introduced into the network. This data function completes the overall management of various data and is open to other network functions through standard interfaces; among various data, there are static data and dynamic real-time data, such as user subscription data, user status data, network status data, connection data, resource utilization data, etc.

[0134] In the future network design, considering that a large amount of computing power is required for internal and external applications in the network and further convergence of computing and networking is needed, a separate computing function is considered to be introduced into the network. This computing function realizes the unified orchestration of computing and networking, formulates the best computing power service strategy, coordinates distributed multi-level computing power to complete the computing power tasks of internal and external applications in the network, and provides diversified computing power services.

[0135] In some embodiments, the first NF and the second NF may include but are not limited to the following situations:

[0136] Situation 1: The first NF and the second NF are NUPF;

[0137] Situation 2: The first NF and the second NF are session management functions;

[0138] Situation 3: The first NF is a computing function and the second NF is a data function.

[0139] For the above three exemplary situations, the network architectures applied by the service processing logic distribution method provided in the embodiments of the present disclosure will be different, which will be described separately below.

[0140] In an exemplary embodiment, Figure 5 is a schematic diagram of a network architecture Figure 1 ; in the above case 1, the service processing logic distribution method provided in this application can be applied to Figure 5 the network architecture shown in the figure. This network architecture includes: SMF, NUPF, a controller, and service processing devices 1, 2, and 3. Among them, the controller can play a forwarding role in this network architecture. It should be noted that Figure 5 in this example, three service processing devices are used for illustration, and in actual applications, the number of service processing devices can be more or less.

[0141] Exemplarily, when the service processing logic distribution method is applied to Figure 5 the network architecture shown in the figure, the user context information is stored in an independent network function, and this independent network function can be the new user plane function NUPF. NUPF supports virtualization and the SBI interface; NUPF can implement the N4 interface function in 5GC to communicate with the SMF; NUPF can generate the first service processing logic supported by service processing devices 1, 2, and 3 according to the user context information, and send the first service processing logic to service processing devices 1, 2, and 3; when this first service processing logic runs on service processing devices 1, 2, and 3, the same processing effect can be obtained when service data enters any one of these service processing devices for processing.

[0142] In an exemplary embodiment, Figure 6 is a schematic diagram of a network architecture Figure 2 ; in the above case 2, the service processing logic distribution method provided in this application can be applied to Figure 6 the network architecture shown in the figure. This network architecture includes: SMF, a controller, and service processing devices 1, 2, and 3. Among them, the controller can play a forwarding role in this network architecture. It should be noted that Figure 6 in this example, three service processing devices are used for illustration, and in actual applications, the number of service processing devices can be more or less.

[0143] Exemplarily, when the service processing logic distribution method is applied to Figure 6When the network architecture shown is used, the user context information is stored in the SMF. The SMF generates the first service processing logic supported by Service Processing Device 1, Service Processing Device 2, and Service Processing Device 3 based on the user's data and distributes it to Service Processing Device 1, Service Processing Device 2, and Service Processing Device 3. When this first service processing logic runs on Service Processing Device 1, Service Processing Device 2, and Service Processing Device 3, when the user data packet enters any of these service processing devices, the same processing effect can be obtained according to the service processing logic.

[0144] The above Figure 6 The difference between the network architecture shown and the above Figure 5 shown network architecture is that the N4 interface / PFCP protocol processing becomes internal processing in the SMF, reducing the types and quantities of network functions and making the network architecture lightweight. Figure 6 The shown architecture is particularly suitable for the scenario of lightweighting the space-based network.

[0145] In an exemplary embodiment, Figure 7 is a schematic diagram of a network architecture Figure 3 ; in the above case 3, the service processing logic distribution method provided in this application can be applied to Figure 7 the network architecture shown. This network architecture is a schematic diagram of the evolution of the future network architecture. This network architecture includes: Data Function (D-NF), Access Function (R-NF), Computing Function (C-NF), a controller, and Service Processing Device 1, Service Processing Device 2, and Service Processing Device 3. Among them, the controller can play a forwarding role in this network architecture, and the controller communicates with D-NF, R-NF, and C-NF through the SBI interface. It should be noted that Figure 7 three service processing devices are taken as examples for illustration. In actual applications, the number of service processing devices can be more or less.

[0146] Exemplarily, when the service processing logic distribution method is applied to Figure 7 the network architecture shown, the user context information is stored in the D-NF to achieve unified storage, backup, and synchronization of future network data; the C-NF interacts with the D-NF. The C-NF obtains the user context information from the D-NF and generates the first service processing logic supported by the programmable forwarding device based on the user context information, and distributes this first service processing logic to Service Processing Device 1, Service Processing Device 2, and Service Processing Device 3; when this first service processing logic runs on Service Processing Device 1, Service Processing Device 2, and Service Processing Device 3, when the service data enters any of these service processing devices, it can be processed according to the first service processing logic and the same processing effect can be obtained.

[0147] In the above embodiments, after the first service processing logic is distributed to the service processing device, the service processing device can process the incoming service data, and during the processing, it can also support the dynamic migration of service data between different service processing devices, and the migration can be performed without backing up and synchronizing the user context information in advance, improving the network operation and maintenance efficiency and the user experience.

[0148] In an exemplary embodiment, Figure 8 Based on the above Figure 6 A schematic diagram of a dynamic migration scenario based on the shown network architecture Figure 1 . In this dynamic migration scenario, among service processing device 1, service processing device 2, and service processing device 3, service processing device 1 needs to be removed due to a fault.

[0149] In an exemplary embodiment, in Figure 8 The shown dynamic migration scenario, a service processing logic distribution method is provided, and this method may include but is not limited to the following steps:

[0150] Step 1: When the PDU session of the UE is activated, the SMF can determine the user plane forwarding path for the PDU session according to the UPF selection basis specified by the 3GPP protocol and the topological connection of the service processing device.

[0151] As Figure 8 shown, it is assumed that according to the shortest path algorithm, it can be determined that service processing device 1, service processing device 2, and service processing device 3 can all be used for service data packet forwarding.

[0152] Step 2: The SMF generates PFCP session context information (i.e., user context information) for the PDU session of the UE according to the local configuration or the Policy and Charging Control (PCC) dynamic rules.

[0153] The above user context information may include but is not limited to: one or more of PDR, FAR, QER, URR, BAR, and user plane forwarding tunnel endpoint information (Tunnel Endpoint ID, TEID).

[0154] Among them, the PCC dynamic rule is a mechanism for managing and controlling the use of network resources. It involves rules in terms of policy and charging, and can dynamically adjust the allocation and use of network resources according to different conditions and policies. In the 5G network, the PCC dynamic rule is used to determine how to allocate and manage network resources for each user equipment (UE)'s packet data unit (PDU) session. These rules can be based on various factors, such as the user's subscription information, service requirements, network conditions, etc., to achieve the effective utilization and charging management of network resources.

[0155] When the SMF receives a PDU session request from the UE, it generates corresponding PFCP session context information (i.e., the above-mentioned user context information) according to local configuration or PCC dynamic rules. This context information includes policies and charging rules related to the PDU session, which are used to guide network nodes on how to process and forward the data of this session. By using PCC dynamic rules, network operators can dynamically adjust policies and charging rules according to real-time network conditions and user needs, so as to optimize the allocation and use of network resources, provide a better user experience, and ensure the efficient operation of the network.

[0156] Step 3: The SMF generates the first service processing logic supported by the service processing device according to the user context information.

[0157] For example, when the service processing device is an SDN switch, the SMF generates flow table entries supported by the OpenFlow protocol; when the service processing device is a P4 device, the SMF generates P4 code adapted to the architecture of the service processing device supported by the Runtime protocol; when the service processing device is an SRv6 device, the SMF generates SRv6 Policy and / or SID supported by the BGP SR Policy protocol.

[0158] Step 4: The SMF simultaneously distributes the first service processing logic to service processing device 1, service processing device 2, and service processing device 3.

[0159] Among them, service processing device 1, service processing device 2, and service processing device 3 can process and forward service data packets according to the first service processing logic without obtaining user context information.

[0160] Step 5: When the load balancer receives the user's service data packet, it distributes the user's service data packet to service processing device 1, service processing device 2, and service processing device 3 according to the load balancing algorithm.

[0161] Since the service processing logics in service processing device 1, service processing device 2, and service processing device 3 among the three service processing devices are all the first service processing logic, the processing results of any service processing device for the service data packet are the same. Exemplarily, for example, if the first service processing logic is to perform a forwarding action on the data packet according to the flow table entry matching result, then when any service processing device encapsulates the GPRS Tunneling Protocol User Plane (GTP-U) header for the service data packet, the same source and destination IPs and tunnel endpoint information TEID will be added.

[0162] At this time, Figure 8The data network (DN) therein can receive the service data packets processed by service processing device 1, service processing device 2, and service processing device 3, and the DN can sort the received processed service data packets.

[0163] The above GTP-U header encapsulation is a protocol header encapsulation method for transmitting user data in a mobile communication network. The GTP-U header is used to transmit user data in a mobile communication network. It is part of the GPRS Tunneling Protocol (GTP) and is used to establish a tunnel between the mobile core network and the radio access network to ensure reliable and secure data transmission. When a service data packet needs to be transmitted through a mobile communication network, it is encapsulated with a GTP-U header. The GTP-U header contains some important information, such as tunnel identification, protocol version, data type, sequence number, etc. This information helps to correctly route and process service data packets in the network. The process of encapsulating the GTP-U header involves adding the GTP-U header in front of the original service data packet and adding appropriate padding at the end of the service data packet to meet the protocol requirements. In this way, the encapsulated service data packet can be transmitted in the mobile communication network and be decapsulated at the receiving end to extract the original service data packet.

[0164] Among them, the above load balancing can be a network function within the radio access network (RAN) or a network function in the core network. When the load balancing is a network function within the RAN, the RAN can distribute service data packets to different connected service processing devices.

[0165] Step 6: When service processing device 1 is removed due to a fault, the load balancing distributes the service data packets to service processing device 2 and service processing device 3 according to the load balancing algorithm.

[0166] When service processing device 1 is removed due to a fault, service processing device 1 can no longer continue to process service data packets. At this time, the service data packets can be distributed by selecting a device from service processing device 2 and service processing device 3 based on the load balancing algorithm.

[0167] At this time, Figure 8 the DN therein can receive the service data packets processed by service processing device 2 and service processing device 3, and the DN can sort the received processed service data packets.

[0168] The above load balancing algorithm is a method for distributing load between multiple devices or resources to achieve more efficient resource utilization and better performance. Exemplarily, the following are several example load balancing algorithms:

[0169] Round Robin: Requests are sequentially and cyclically assigned to each available device. Each device receives one request in sequence, then the next device, and so on.

[0170] Weighted Round Robin: Requests are assigned based on the weights of the devices. The weights can be set according to the processing capabilities, performance, or other factors of the devices. Devices with higher weights will receive more requests.

[0171] Random: A random available device is selected to process the request. This can be achieved through a random number generator or other random algorithms.

[0172] Weighted Random: Similar to Weighted Round Robin, but uses random selection to determine which device to assign the request to.

[0173] Least Connections: Requests are assigned to the device with the fewest active connections currently. This helps balance the load among devices because devices with fewer connections may have more available resources to handle new requests.

[0174] Hashing: Calculate a hash value based on certain attributes of the request (such as URL, source IP address, etc.), and assign the request to the device that matches the hash value.

[0175] It should be noted that the above Figure 8 is based on Figure 6 the network architecture shown, and is a dynamic migration scenario. However, for the above Figure 5 or Figure 7 network architectures, the same dynamic migration scenario can also be achieved. And for the dynamic migration scenarios implemented for the above Figure 5 or Figure 7 network architectures, a service processing logic distribution method similar to the one shown in the above Figure 8 dynamic migration scenario can also be achieved, which will not be elaborated here.

[0176] In an exemplary embodiment, Figure 9 is a schematic diagram of a service processing logic distribution method in a dynamic migration scenario. The method includes:

[0177] 901. The first NF generates at least one first service processing logic supported by the service processing devices according to the user context information.

[0178] 902. The first NF sends the first service processing logic to at least one service processing device.

[0179] For the descriptions of steps 901 and 902, reference may be made to the above descriptions of steps 401 and 402, which will not be elaborated here.

[0180] 903. The first NF receives a migration instruction.

[0181] The migration instruction is used to indicate replacing the first service processing device with the second service processing device. The first service processing device is a device among at least one service processing device, and the second service processing device is a device outside at least one service processing device.

[0182] Exemplarily, in a satellite network, satellite 1 carrying the first service processing device is about to fly out of the user's service area, and satellite 1' carrying the second service processing device is about to fly into the user's service area to take over the work. The ground operation and control system can calculate in advance the identifiers of the first service processing device and the second service processing device according to network operation information (such as ephemeris information, network topology, satellite service capabilities, etc.). The ground operation and control system can send a migration instruction to the SMF, carrying the identifiers of the first service processing device and the second service processing device, the migration time, etc.

[0183] In the embodiments of the present application, the sender of the migration instruction is not limited. In some embodiments, the above migration instruction may be a migration instruction input by a network administrator, or the migration instruction may be a migration instruction sent by the ground operation and control system.

[0184] 904. The first NF sends the second service processing logic to the second service processing device.

[0185] In some embodiments, the migration instruction includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is the same as the identifier of the second service processing device; the second service processing logic is the first service processing logic.

[0186] When the identifier of the first service processing device is the same as the identifier of the second service processing device, and the network topology information corresponding to the second service processing device is the same as the network topology information corresponding to the first service processing device, after replacing the first service processing device with the second service processing device, the second service processing device is equivalent to the original first service processing device. At this time, the first service processing logic running in the previous first service processing device can still be used. Therefore, the first NF can directly send the previously generated first service processing logic to the second service processing device without generating new service processing logic for the second service processing device.

[0187] In some embodiments, the migration indication includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is the same as the identifier of the second service processing device; if the network topology information corresponding to the second service processing device is different from the network topology information corresponding to the first service processing device, after replacing the first service processing device with the second service processing device, the second service processing device is not equivalent to the original first service processing device. At this time, the first NF needs to generate a new second service processing logic for the second service processing device. The second service processing logic is a service processing logic that supports the second service processing device generated according to the user context information. Here, when generating the service processing logic that supports the second service processing device, the network topology information corresponding to the second service processing device can be considered.

[0188] Exemplarily, the network topology information corresponding to the above service processing device may be the port number through which the service processing device accesses the network.

[0189] In some embodiments, the migration indication includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is different from the identifier of the second service processing device; the second service processing logic is a service processing logic that supports the second service processing device generated according to the user context information.

[0190] When the identifier of the first service processing device is different from the identifier of the second service processing device, after replacing the first service processing device with the second service processing device, the second service processing device is equivalent to a new service processing device added to the network topology. At this time, the first service processing logic running in the previous first service processing device cannot be used. Therefore, the first NF can generate a new second service processing logic for the second service processing device. The second service processing logic is a service processing logic that supports the second service processing device generated according to the user context information.

[0191] In some embodiments, the migration indication further includes the migration time; if a migration indication is received, then before the migration time, the second service processing logic is sent to the second service processing device.

[0192] Sending the second service processing logic to the second service processing device before the migration time can ensure that before migrating the service data packet to the second service processing device, the second service processing device has already run the second service processing logic, ensuring that the processing of the service data packet after migration will not be interrupted and ensuring the continuity of service processing.

[0193] In an exemplary embodiment, Figure 10 For the above Figure 6 shown network architecture as the basis for a schematic diagram in a dynamic migration scenario Figure 2In this dynamic migration scenario, the service processing device 1 fails and disconnects, and is replaced by the service processing device 1'.

[0194] In some embodiments, in the Figure 10 dynamic migration scenario shown, a service processing logic distribution method is provided, which may include but is not limited to the following steps:

[0195] Step a: The SMF generates PFCP session context information (i.e., user context information) for the PDU session of the UE according to local configuration or Policy and Charging Control (PCC) dynamic rules.

[0196] Step b: The SMF generates the first service processing logic supported by the service processing device according to the user context information.

[0197] For the descriptions of steps a and b above, reference may be made to the relevant descriptions of steps 1, 2, and 3 above, which will not be elaborated here.

[0198] Step c: When the load balancer receives the user's service data packet, it distributes the user's service data packet to the service processing device 1.

[0199] At this time Figure 10 the DN shown will receive the service data packet processed by the service processing device 1.

[0200] Step d: When the service processing device 1 fails and disconnects and is replaced by the service processing device 1', and the identifiers of the service processing device 1 and the service processing device 1' are the same, the SMF issues the second service processing logic to the service processing device 1'.

[0201] When the service processing device 1 fails and disconnects and is replaced by the service processing device 1', the service processing device 1' can be connected to the network. After the controller senses the change in the network topology, it can notify the SMF so that the SMF automatically issues the second service processing logic to the new device.

[0202] In some embodiments, when the port numbers of the service processing device 1' and the service processing device 1 accessing the network topology are the same, the second service processing logic issued by the SMF to the service processing device 1' can be the first service processing logic that has been generated before; when the port numbers of the service processing device 1' and the service processing device 1 accessing the network topology are different, the second service processing logic issued can be the new service processing logic generated to support the service processing device 1' to ensure normal data forwarding.

[0203] Step e: When the load balancer receives the user's service data packet, it distributes the user's service data packet to the service processing device 1'.

[0204] At this time Figure 10 The DN shown will receive the service data packet processed by the service processing device 1'.

[0205] When the identifiers of the service processing device 1 and the service processing device 1' are the same, the service data packet of the user is migrated to the new service processing device 1' for processing, and the processing effect is the same as that of the old service processing device 1. For example, when performing a forwarding action on the data packet according to the flow table entry matching result and encapsulating the GTP-U header for the service data packet, the same IP and TEID are added.

[0206] In an exemplary embodiment, in this Figure 10 Another service processing logic distribution method in the dynamic migration scenario shown may include but is not limited to the following steps:

[0207] Step A: The SMF generates PFCP session context information (i.e., user context information) for the PDU session of the UE according to the local configuration or the Policy and Charging Control (PCC) dynamic rules.

[0208] Step B: The SMF generates the first service processing logic supported by the service processing device according to the user context information.

[0209] For the descriptions of the above steps A and B, reference may be made to the relevant descriptions of the above steps 1, 2, and 3, which will not be elaborated here.

[0210] Step C: When the load balancer receives the service data packet of the user, it distributes the service data packet of the user to the service processing device 1.

[0211] At this time Figure 10 The DN shown will receive the service data packet processed by the service processing device 1.

[0212] Step D: When the service processing device 1 needs to be replaced by the service processing device 1' and the identifiers of the service processing device 1 and the service processing device 1' are different, the SMF generates the second service processing logic supported by the service processing device 1'.

[0213] Exemplarily, in a satellite network, satellite 1 carrying service processing device 1 is about to fly out of the user's service area, and satellite 1' carrying service processing device 1' is about to fly into the user's service area to take over the work. At this time, service processing device 1 needs to be replaced by service processing device 1'. The ground operation and control system will calculate in advance the identifiers of service processing device 1 and service processing device 1' based on network operation information (such as ephemeris information, network topology, satellite service capabilities, etc.), and the ground operation and control system can send a UPF migration instruction to the SMF, carrying the identifiers of service processing device 1 and service processing device 1', the migration time, etc.

[0214] When the identifiers of service processing device 1 and service processing device 1' are different, it indicates that service processing device 1' is a newly added device, and the first service processing logic generated previously is not suitable for the current service processing device 1'. The SMF can, according to the migration instruction, regenerate the second service processing logic that supports service processing device 1' and send it to service processing device 1'.

[0215] Step E: The SMF sends the second service processing logic to service processing device 1'.

[0216] Step F: When the load balancer receives the user's service data packet, it distributes the user's service data packet to service processing device 1'.

[0217] At this time Figure 10 the shown DN will receive the service data packet processed by service processing device 1'.

[0218] Since the second service processing logic has been sent to service processing device 1', the user's service data packet is migrated to service processing device 1' for processing, which can ensure that the service data processing will not be interrupted and the processing effect is consistent, ensuring that the service data processing will not be affected by the replacement of the service processing device.

[0219] It should be noted that the above Figure 10 shown is a dynamic migration scenario based on the Figure 6 shown network architecture. For the above Figure 5 or Figure 7 network architecture, the same dynamic migration scenario can also be realized, and for the dynamic migration scenario realized by the above Figure 5 or Figure 7 network architecture, a service processing logic distribution method similar to the service processing logic distribution method in the above Figure 10 shown dynamic migration scenario can also be realized, which will not be elaborated here.

[0220] In an exemplary embodiment, Figure 11 for the above Figure 6Schematic diagram in a dynamic migration scenario based on the network architecture shown Figure 3 As Figure 11 shown, the service processing device in this network architecture is an SRv6 device, and in this dynamic migration scenario, SRv6 device 1 needs to be replaced with SRv6 device 1'. Both SRv6 device 1 and SRv6 device 1' include Qos control and traffic statistics functions for performing Qos control and traffic statistics during the process of processing service data packets.

[0221] In an exemplary embodiment, taking the service processing device as an SRv6 device as an example, in the dynamic migration scenario shown Figure 11 a service processing logic distribution method is provided. This method may include but is not limited to the following steps:

[0222] Step G: The SMF generates PFCP session context information (i.e., user context information) for the PDU session of the UE according to local configuration or PCC dynamic rules.

[0223] Step H: The SMF generates the first service processing logic supported by SRv6 device 1 according to the user context information and distributes it to SRv6 device 1.

[0224] At this time Figure 11 the shown DN will receive the service data packets processed by SRv6 device 1.

[0225] Step I: When SRv6 device 1 receives the service data packets of the user, it executes the corresponding first service processing logic on the service data packets.

[0226] Step J: When SRv6 device 1 needs to be replaced with SRv6 device 1', the SMF distributes the second service processing logic to SRv6 device 1'.

[0227] Among them, the second service processing logic supports SRv6 device 1' and has the same processing logic as the first service processing logic.

[0228] For example, in a satellite network, satellite 1 carrying SRv6 device 1 is about to fly out of the service area of the user, and satellite 1' carrying SRv6 device 1' is about to fly into the service area of the user to take over the work. The ground operation and control system can calculate the identifiers of SRv6 device 1 and SRv6 device 1' based on network operation information (such as ephemeris information, network topology, satellite service capabilities, etc.). The ground operation and control system sends a UPF migration instruction to the SMF, carrying the identifiers of SRv6 device 1 and SRv6 device 1', the migration time, etc. The SMF issues the service processing logic for SRv6 device 1' according to the UPF migration instruction (without the need to transmit the information of the PFCP session context). Among them, the SMF can update the SRv6 Policy information according to the UPF migration instruction, modify the SID of SRv6 device 1 in the original SRv6 Policy SID List to the SID of SRv6 device 1', and issue the SRv6 Policy information to SRv6 device 1', that is, the above-mentioned second service processing logic for SRv6 device 1'.

[0229] Step K, when SRv6 device 1' receives the service data packet of the user, it executes the corresponding second service processing logic on the service data packet.

[0230] At this time Figure 11 the shown DN will receive the service data packet processed by SRv6 device 1'.

[0231] In the above embodiments, it can be ensured that the service data packets of the user are migrated to SRv6 device 1' for processing, which is consistent with the processing effect of SRv6 device 1, ensuring that the processing of service data will not be affected by the replacement of the service processing device.

[0232] It should be noted that the above Figure 11 shown is a dynamic migration scenario taking the service processing device as an SRv6 device as an example. When the service processing device is other devices (such as P4 devices), there can also be similar dynamic migration scenarios, and the service processing logic distribution method in these similar dynamic migration scenarios can be implemented, which will not be elaborated here.

[0233] It should be understood that although the steps in the flowcharts involved in the above-described embodiments are sequentially shown according to the indications of the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear indication in this document, the execution of these steps has no strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-described embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same moment, but can be executed at different moments, and the execution order of these steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or steps or stages in other steps.

[0234] Based on the same inventive concept, an embodiment of the present application also provides a first NF and a service processing device for implementing the service processing logic distribution method involved above. The implementation solutions provided by the first NF and the service processing device for solving problems are similar to the implementation solutions recorded in the above method. Therefore, the specific limitations in one or more of the following first NF and service processing device embodiments can refer to the limitations on the service processing logic distribution method in the above text, and will not be elaborated here.

[0235] Exemplarily, Figure 12 FIG. 8 is a schematic structural diagram of a first NF provided for an embodiment. The NF includes: a memory 1201, a transceiver 1202, and a processor 1203, wherein the memory 1201, the transceiver 1202, and the processor 1203 are connected through a bus interface.

[0236] The memory 1201 is used to store a computer program; the transceiver 1202 is used to transmit and receive data under the control of the processor 1203; the processor 1203 is used to read the computer program in the memory 1201 and perform the following operations:

[0237] Send a first service processing logic to at least one service processing device; the first service processing logic is generated according to the user context information obtained from the second NF.

[0238] In one embodiment, the first NF includes any one of the following:

[0239] User plane function, session management function, computing function, data function.

[0240] In one embodiment, the first NF and the second NF are the user plane functions;

[0241] In one embodiment, the first NF and the second NF are the session management functions;

[0242] In one embodiment, the first NF is the computing function and the second NF is the data function.

[0243] In one embodiment, the user context information includes at least one of the following:

[0244] Packet detection rule, forwarding action rule, quality of service implementation rule, usage reporting rule, caching action rule, user plane forwarding tunnel endpoint information.

[0245] In one embodiment, the first service processing logic includes at least one of the following:

[0246] Forwarding processing logic, charging processing logic, quality of service (QoS) control processing logic.

[0247] In one embodiment, the method further includes: generating, according to the user context information, first service processing logic supported by the at least one service processing device.

[0248] In one embodiment, if the at least one service processing device is an OpenFlow switch, the first service processing logic is a flow table entry supported by the OpenFlow protocol;

[0249] If the at least one service processing device is a P4 device, the first service processing logic is P4 code supported by the Runtime protocol;

[0250] If the at least one service processing device is an SRv6 device, the first service processing logic is an SRv6 policy and / or segment identifier (SID) supported by the BGP SR Policy protocol.

[0251] In one embodiment, it further includes:

[0252] If a migration indication is received, sending second service processing logic to the second service processing device;

[0253] The migration indication is used to indicate replacing a first service processing device with a second service processing device, where the first service processing device is a device among the at least one service processing device, and the second service processing device is a device outside the at least one service processing device.

[0254] In one embodiment, the migration indication includes an identifier of the first service processing device and an identifier of the second service processing device, and the identifier of the first service processing device is the same as the identifier of the second service processing device;

[0255] The second service processing logic is the first service processing logic.

[0256] In one embodiment, the migration indication includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is the same as the identifier of the second service processing device;

[0257] If the network topology information corresponding to the second service processing device is different from the network topology information corresponding to the first service processing device, the second service processing logic is the service processing logic that supports the second service processing device generated according to the user context information.

[0258] In one embodiment, the migration indication includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is different from the identifier of the second service processing device;

[0259] The second service processing logic is the service processing logic that supports the second service processing device generated according to the user context information.

[0260] In one embodiment, the migration indication further includes the migration time;

[0261] Sending the second service processing logic to the second service processing device if the migration indication is received includes:

[0262] If the migration indication is received, the second service processing logic is sent to the second service processing device before the migration time.

[0263] Those skilled in the art can understand that Figure 12 the structure shown in is only a block diagram of some structures related to the solution of the present application, and does not constitute a limitation on the first NF to which the solution of the present application is applied. The specific first NF may include more or fewer components than those shown in the figure, or combine some components, or have a different component layout.

[0264] A service processing device provided in an embodiment of the present application further includes: a memory, a transceiver, and a processor, where the memory, the transceiver, and the processor are connected through a bus interface.

[0265] The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations:

[0266] Receive the first service processing logic sent by the first NF; the first service processing logic is generated according to the user context information obtained from the second NF.

[0267] In some embodiments, the processor is further configured to read the computer program in the memory and execute the method performed by the service processing device in the foregoing method embodiments.

[0268] In an exemplary embodiment, as Figure 13 shown, a structural block diagram of a first NF is provided. The first NF includes:

[0269] A sending module 1301, configured to send first service processing logic to at least one service processing device; the first service processing logic is generated according to user context information obtained from a second NF.

[0270] In one of the embodiments, the first NF includes any one of the following:

[0271] User plane function, session management function, computing function, data function.

[0272] In one of the embodiments, the first NF and the second NF are the user plane functions;

[0273] In one of the embodiments, the first NF and the second NF are the session management functions;

[0274] In one of the embodiments, the first NF is the computing function and the second NF is the data function.

[0275] In one of the embodiments, the user context information includes at least one of the following:

[0276] Packet detection rules, forwarding action rules, quality of service implementation rules, usage reporting rules, caching action rules, user plane forwarding tunnel endpoint information.

[0277] In one of the embodiments, the first service processing logic includes at least one of the following:

[0278] Forwarding processing logic, charging processing logic, quality of service (QoS) control processing logic.

[0279] In one of the embodiments, the first NF further includes: a generating module 1302, configured to generate the first service processing logic supported by the at least one service processing device according to the user context information.

[0280] In one of the embodiments, if the at least one service processing device is an OpenFlow switch, the first service processing logic is a flow table entry supported by the OpenFlow protocol;

[0281] If the at least one service processing device is a P4 device, the first service processing logic is P4 code supported by the Runtime protocol;

[0282] If the at least one service processing device is an SRv6 device, the first service processing logic is an SRv6 policy and / or a Segment Identifier (SID) supported by the BGP SR Policy protocol.

[0283] In one embodiment, the sending module 1301 is further configured to:

[0284] If a migration instruction is received, send the second service processing logic to the second service processing device;

[0285] The migration instruction is used to indicate replacing the first service processing device with the second service processing device, where the first service processing device is a device among the at least one service processing device, and the second service processing device is a device outside the at least one service processing device.

[0286] In one embodiment, the migration instruction includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is the same as the identifier of the second service processing device;

[0287] The second service processing logic is the first service processing logic.

[0288] In one embodiment, the migration instruction includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is the same as the identifier of the second service processing device;

[0289] If the network topology information corresponding to the second service processing device is different from the network topology information corresponding to the first service processing device, the second service processing logic is service processing logic that supports the second service processing device generated according to the user context information.

[0290] In one embodiment, the migration instruction includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is different from the identifier of the second service processing device;

[0291] The second service processing logic is service processing logic that supports the second service processing device generated according to the user context information.

[0292] In one embodiment, the migration instruction further includes a migration time;

[0293] If a migration instruction is received, send second service processing logic to the second service processing device, including:

[0294] If the migration instruction is received, before the migration moment, send the second service processing logic to the second service processing device.

[0295] In one embodiment, the present application provides a service processing device, which includes:

[0296] A receiving module, configured to receive first service processing logic sent by a first NF; the first service processing logic is generated according to user context information obtained from a second NF.

[0297] The above-mentioned first NF and each module in the service processing device are only for exemplary illustration. In practice, there may be more or fewer modules. The above-mentioned each module can be implemented in whole or in part through software, hardware and their combination. The above-mentioned each module can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory of the computer device in the form of software, so as to facilitate the processor to call and execute the operations corresponding to the above-mentioned each module.

[0298] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0299] Send first service processing logic to at least one service processing device; the first service processing logic is generated according to user context information obtained from a second NF.

[0300] In some embodiments, when the computer program is executed by a processor, it can also implement each process related to the first NF in the above method embodiments.

[0301] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0302] Receive first service processing logic sent by a first NF; the first service processing logic is generated according to user context information obtained from a second NF.

[0303] In some embodiments, when the computer program is executed by a processor, it can also implement each process related to the service processing device in the above method embodiments.

[0304] In one embodiment, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the following steps are implemented:

[0305] Send the first service processing logic to at least one service processing device; the first service processing logic is generated according to the user context information obtained from the second NF.

[0306] In some embodiments, when the computer program is executed by a processor, it may also perform each process involved in the first NF in the above method embodiments.

[0307] In one embodiment, a computer program product is provided, including a computer program, which when executed by a processor, implements the following steps:

[0308] Receive the first service processing logic sent by the first NF; the first service processing logic is generated according to the user context information obtained from the second NF.

[0309] In some embodiments, when the computer program is executed by a processor, it may also perform each process involved in the service processing device in the above method embodiments.

[0310] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data that have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with relevant regulations.

[0311] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memories. Non-volatile memories can include read-only memory (ROM), magnetic tapes, floppy disks, flash memories, optical memories, high-density embedded non-volatile memories, resistive random access memories (ReRAM), magnetoresistive random access memories (MRAM), ferroelectric random access memories (FRAM), phase change memories (PCM), graphene memories, etc. Volatile memories can include random access memory (RAM) or external cache memories, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in the present application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in the present application can be general-purpose processors, central processors, graphics processors, digital signal processors, programmable logic devices, data processing logics based on quantum computing, etc., without limitation.

[0312] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope described in this specification.

[0313] The above-described embodiments merely represent several implementation manners of the present application. The description thereof is relatively specific and detailed, but it should not be construed as a limitation on the patent scope of the present application. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims

1. A method for distributing service processing logic, characterized in that, Applied to the first network function NF, the method includes: Sending first service processing logic to at least one service processing device; the first service processing logic is generated according to user context information obtained from a second NF.

2. The method according to claim 1, characterized in that, The first NF includes any one of the following: User plane function, session management function, computing function, data function.

3. The method according to claim 2, characterized in that, The first NF and the second NF are the user plane functions; Or, The first NF and the second NF are the session management functions; Or, The first NF is the computing function, and the second NF is the data function.

4. The method according to claim 1, characterized in that, The user context information includes at least one of the following: Packet detection rule, forwarding action rule, quality of service implementation rule, usage reporting rule, caching action rule, user plane forwarding tunnel endpoint information.

5. The method according to claim 1, characterized in that, The first service processing logic includes at least one of the following: Forwarding processing logic, charging processing logic, quality of service (QoS) control processing logic.

6. The method according to claim 1, characterized in that, The method further includes: Generating first service processing logic supported by the at least one service processing device according to the user context information.

7. The method according to claim 6, characterized in that, If the at least one service processing device is an OpenFlow switch, the first service processing logic is a flow table entry supported by the OpenFlow protocol; If the at least one service processing device is a P4 device, the first service processing logic is P4 code supported by the Runtime protocol; If the at least one service processing device is an SRv6 device, the first service processing logic is an SRv6 policy and / or segment identifier (SID) supported by the BGP SR Policy protocol.

8. The method according to any one of claims 1 to 7, characterized in that, It further includes: If a migration indication is received, sending second service processing logic to the second service processing device; The migration indication is used to indicate replacing a first service processing device with a second service processing device, where the first service processing device is a device among the at least one service processing device, and the second service processing device is a device outside the at least one service processing device.

9. The method according to claim 8, characterized in that, The migration indication includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is the same as the identifier of the second service processing device; The second service processing logic is the first service processing logic.

10. The method according to claim 8, characterized in that, The migration indication includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is the same as the identifier of the second service processing device; If the network topology information corresponding to the second service processing device is different from the network topology information corresponding to the first service processing device, the second service processing logic is service processing logic generated according to the user context information and supporting the second service processing device.

11. The method according to claim 8, characterized in that, The migration indication includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is different from the identifier of the second service processing device; The second service processing logic is the service processing logic that is generated based on the user context information and supports the second service processing device.

12. The method according to claim 8, characterized in that, The migration instruction further includes a migration time. If a migration instruction is received, sending the second service processing logic to the second service processing device includes: If the migration instruction is received, before the migration time, send the second service processing logic to the second service processing device.

13. A service processing logic distribution method, characterized in that Applied to a service processing device, it includes: Receiving the first service processing logic sent by the first NF; the first service processing logic is generated based on the user context information obtained from the second NF.

14. A first NF, characterized in that It includes: A memory, a transceiver, and a processor; The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor. The processor is used to read the computer programs in the memory and perform the following operations: Send the first service processing logic to at least one service processing device; the first service processing logic is generated based on the user context information obtained from the second NF.

15. The first NF according to claim 14, characterized in that The first NF includes any one of the following: User plane function, session management function, computing function, data function.

16. The first NF according to claim 15, characterized in that The first NF and the second NF are the user plane functions; Or, The first NF and the second NF are the session management functions; Or, The first NF is the computing function, and the second NF is the data function.

17. The first NF according to claim 14, characterized in that The user context information includes at least one of the following: Packet detection rule, forwarding action rule, quality of service implementation rule, usage reporting rule, caching action rule, user plane forwarding tunnel endpoint information.

18. The first NF according to claim 14, characterized in that The first service processing logic includes at least one of the following: Forwarding processing logic, charging processing logic, quality of service (QoS) control processing logic.

19. The first NF according to claim 14, characterized in that The processor is further used to read the computer programs in the memory and perform the following operations: Generate the first service processing logic supported by the at least one service processing device according to the user context information.

20. The first NF according to claim 19, characterized in that If the at least one service processing device is an OpenFlow switch, the first service processing logic is a flow table entry supported by the OpenFlow protocol. If the at least one service processing device is a P4 device, the first service processing logic is P4 code supported by the Runtime protocol. If the at least one service processing device is an SRv6 device, the first service processing logic is an SRv6 policy and / or segment identifier (SID) supported by the BGP SR Policy protocol.

21. The first NF according to any one of claims 14 to 20, characterized in that The processor is further used to read the computer programs in the memory and perform the following operations: If a migration instruction is received, send the second service processing logic to the second service processing device. The migration instruction is used to indicate replacing the first service processing device with the second service processing device. The first service processing device is a device among the at least one service processing device, and the second service processing device is a device outside the at least one service processing device.

22. The first NF according to claim 21, characterized in that The migration instruction includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is the same as the identifier of the second service processing device; The second service processing logic is the first service processing logic.

23. The first NF according to claim 21, wherein, The migration instruction includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is the same as the identifier of the second service processing device; If the network topology information corresponding to the second service processing device is different from the network topology information corresponding to the first service processing device, the second service processing logic is the service processing logic that supports the second service processing device generated according to the user context information.

24. The first NF according to claim 21, wherein, The migration instruction includes the identifier of the first service processing device and the identifier of the second service processing device, and the identifier of the first service processing device is different from the identifier of the second service processing device; The second service processing logic is the service processing logic that supports the second service processing device generated according to the user context information.

25. The first NF according to claim 21, wherein, The migration instruction further includes the migration time; The processor is further configured to read the computer program in the memory and perform the following operations: If the migration instruction is received, before the migration time, send the second service processing logic to the second service processing device.

26. A service processing device, wherein, Comprising: A memory, a transceiver, and a processor; The memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; The processor is used to read the computer program in the memory and perform the following operations: Receive the first service processing logic sent by the first NF; the first service processing logic is generated according to the user context information obtained from the second NF.

27. A first NF, wherein, The first NF includes: A sending module, configured to send the first service processing logic to at least one service processing device; the first service processing logic is generated according to the user context information obtained from the second NF.

28. A service processing device, wherein, The service processing device includes: A receiving module, configured to receive the first service processing logic sent by the first NF; the first service processing logic is generated according to the user context information obtained from the second NF.

29. A computer-readable storage medium having a computer program stored thereon, wherein, When the computer program is executed by the processor, it implements the steps of the method according to any one of claims 1 to 13.

Images