CN118828691A - Dual-domain private network diversion rule synchronization method, device, equipment, medium and product - Google Patents

Abstract

The application discloses a method, a device, equipment, a medium and a product for synchronizing a distribution rule of a dual-domain private network, wherein a session management function network element sends a PFD synchronous message to a user plane function network element, the PFD synchronous message comprises a PFD identifier of a target private network and PFD rule content, the PFD identifier comprises private network DNN information and private network slice identifier, and the PFD rule content comprises a distribution rule; the user plane functional network element determines a target distribution rule corresponding to the target private network from a stored distribution rule base based on the PFD identification; the user plane functional network element updates the target offload rules based on offload rules in the PFD rule content. According to the embodiment of the application, the shunting rule synchronization can be carried out through the PFD synchronization message of one node level aiming at different users signing the same private network, and compared with the traditional synchronization mode based on the session level message, the message quantity of the synchronous shunting rule among network elements is greatly reduced, and the consumption of equipment performance is reduced.

Description

Dual-domain private network diversion rule synchronization method, device, equipment, medium and product

Technical Field

The present application belongs to the field of communication technology, and in particular, relates to a dual-domain private network diversion rule synchronization method, device, equipment, medium and product.

Background Art

As the integration of 5G (5th Generation Mobile Communication Technology) and the industry market continues to deepen, the demand for 2B2C integrated private networks has increased significantly. The dual-domain private network solves the problems of traditional VPN access to the intranet, such as complicated operations, poor experience, and high risks, and provides users with on-demand direct intranet access experience, meeting the demands of various scenarios such as remote office, video conferencing, online classes, and access to the intranet to consult materials. The dual-domain private network refers to a network mode that can interconnect public networks and private networks. The public network, referred to as the public network, refers to a network that can be accessed in a public environment, such as the Internet. The private network, referred to as the private network, refers to a network that is only used in a specific environment, such as the data center of an Internet operator, the internal LAN of an enterprise, etc. Through this network mode, users can achieve the needs of secure access to the enterprise intranet and the Internet without changing the card or number. One of its main functions is seamless traffic diversion, which supports users to access the internal and external networks at will.

In the existing related technologies, the seamless diversion function of the dual-domain private network is mainly realized through the policy control function PCF network element, session management function SMF network element and user plane function UPF network element in the public network. When a user signs up for the seamless diversion service, the PCF network element transmits the diversion rules to the SMF network element based on the contract information. The SMF network element sends the diversion rules to the UPF network element. The UPF network element will establish a diversion rule base locally for matching the service messages of the seamless diversion users. In order to ensure the accuracy of the diversion rules in the diversion rule base, the diversion rules need to be synchronized between the SMF network element and the UPF network element.

In the existing related technologies, the SMF network element and the UPF network element mainly synchronize the diversion rules through session-level messages. This method requires the SMF network element and the UPF network element to exchange messages for each user respectively. In the diversion rule synchronization scenario with a large number of users, a large number of messages need to be exchanged between the SMF network element and the UPF network element, which leads to the consumption of network performance.

Summary of the invention

The embodiments of the present application provide a dual-domain private network diversion rule synchronization method, device, equipment, medium and product, which can reduce the amount of messages during diversion rule synchronization and reduce the consumption of equipment performance.

In a first aspect, an embodiment of the present application provides a dual-domain private network traffic diversion rule synchronization method, including:

The session management function network element sends a PFD synchronization message to the user plane function network element. The PFD synchronization message includes the PFD identifier and PFD rule content of the target private network. The PFD identifier includes the private network DNN information and the private network slice identifier. The PFD rule content includes the diversion rule.

The user plane functional network element determines a target diversion rule corresponding to the target private network from a stored diversion rule library based on the PFD identifier;

The user plane functional network element updates the target diversion rule based on the diversion rule in the PFD rule content.

In a second aspect, an embodiment of the present application provides a dual-domain private network diversion rule synchronization device, including: a session management function network element and a user plane function network element;

The session management function network element is used to send a PFD synchronization message to the user plane function network element. The PFD synchronization message includes the PFD identifier and PFD rule content of the target private network. The PFD identifier includes the private network DNN information and the private network slice identifier. The PFD rule content includes the diversion rule.

A user plane function network element, used to determine a target diversion rule corresponding to a target private network from a stored diversion rule library based on a PFD identifier;

The user plane functional network element is further used to update the target diversion rule based on the diversion rule in the PFD rule content.

In a third aspect, an embodiment of the present application provides an electronic device, the electronic device comprising: a processor and a memory storing computer program instructions;

When the processor executes the computer program instructions, the dual-domain private network traffic diversion rule synchronization method of the first aspect is implemented.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, a dual-domain private network diversion rule synchronization method as in the first aspect is implemented.

In a fifth aspect, an embodiment of the present application provides a computer program product. When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the dual-domain private network diversion rule synchronization method as in the first aspect.

The dual-domain private network diversion rule synchronization method, apparatus, equipment, medium and product of the embodiment of the present application are that the session management function network element sends a PFD synchronization message to the user plane function network element, the PFD synchronization message includes the PFD identifier and PFD rule content of the target private network, the PFD identifier includes the private network DNN information and the private network slice identifier, and the PFD rule content includes the diversion rule; the user plane function network element determines the target diversion rule corresponding to the target private network from the stored diversion rule library based on the PFD identifier; the user plane function network element updates the target diversion rule based on the diversion rule in the PFD rule content. According to the embodiment of the present application, for different users who have signed contracts for the same private network, the diversion rule synchronization can be performed through a node-level PFD synchronization message. Compared with the traditional synchronization method based on session-level messages, the amount of messages for synchronizing diversion rules between network elements is greatly reduced, the consumption of equipment performance is reduced, and the risk of core network signaling storms is reduced.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solution of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

FIG1 is a schematic diagram showing the principle of a dual-domain private network seamless traffic diversion function provided in an embodiment of the present application;

FIG2 is a flow chart of a dual-domain private network diversion rule synchronization method provided in an embodiment of the present application;

FIG3 is a flow chart of a dual-domain private network traffic diversion rule synchronization method provided by another embodiment of the present application;

FIG4 is a flow chart of a method for synchronizing dual-domain private network traffic diversion rules provided by another embodiment of the present application;

FIG5 is a block diagram of a dual-domain private network diversion rule synchronization device provided in an embodiment of the present application;

FIG. 6 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.

It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

First, the professional terms involved in the embodiments of the present application are explained:

UE: User Equipment.

PCF: Policy Control Function, refers to policy control function.

SMF: Session Management Function, refers to session management function.

UPF: User Plane Function, refers to user plane function.

RAN: Radio Access Network, refers to wireless access network.

AMF: Access and Mobility Management Function, access mobility management.

DNN: Data Network name, which has the same concept as 4G APN, i.e., access point name.

NSSAI: Network Slice Selection Assistance Information--Network Slice Selection Assistance Information, Network Slice Selection Assistance Information, hereinafter referred to as slice identification.

PFCP: Packet Forwarding Control Protocol, packet forwarding control protocol.

PFD: packet Flow Descriptions, packet flow description.

Refer to Figure 1, which is a functional principle diagram of the senseless diversion of the dual-domain private network. As shown in Figure 1, it includes the Internet, the enterprise intranet, PCF1, the public network session management function network element SMF1, the public network user plane function network element UPF1, the private network session management function network element SMF2, the private network user plane function network element UPF2 and the access mobility management AMF1. Among them, the private network session management function network element SMF2, the private network user plane function network element and the enterprise intranet are located inside the enterprise's campus, and the Internet, PCF1, the public network session management function network element SMF1, the public network user plane function network element UPF1, and the access mobility management AMF1 can be located outside the enterprise's campus.

When a user signs a contract for a seamless traffic diversion service with the enterprise intranet, PCF1 transmits the diversion rules to the SMF1 network element through the N7 interface based on the contract information. The diversion rules can include information such as the specified URL (i.e., service URL, which can be in the form of an IP address format, FQDN full domain name, etc.), private network BPN, and private network slices. SMF1 sends the diversion rules to the public network UPF1 through the N4 interface. When the user equipment UE accesses the service of the enterprise intranet it has signed through the wireless access network RAN, UPF1 triggers the detection and reports it to SMF1. SMF1 triggers the establishment of a private network DNN session and selects SMF2 as the anchor SMF of the private network session. SMF2 selects the specified private network UPF2 to connect to the enterprise intranet, so that the data packets used by the user equipment to access the private network can be smoothly sent to the enterprise intranet.

The service URL in each diversion rule usually needs to support multiple FQDN domain names + 100 IP addresses, for example, 300, and the total length is usually limited to 5000 bytes. Each session can usually send up to 5 diversion rules, so all service URLs sent by each session can support a maximum size of 5*5K bytes. After the diversion rules sent by each session are sent to UPF1 through the N4 interface, UPF1 will establish a dynamic DPI rule base based on the service URL locally, that is, the diversion rule base, which is used to match the user service messages for seamless diversion. UPF1 and SMF1 need to synchronize the diversion rules to maintain and dynamically update the diversion rule base on UPF1.

The existing traffic diversion rule synchronization solution between SMF1 and UPF1 is mainly acquired and synchronized through the session level message of the N4 interface. The traffic diversion rule synchronization between SMF1 and UPF1 can include the following two situations:

The first case is when the enterprise changes the service URL in the diversion rule, SMF1 actively sends the diversion rule to UPF1.

The second situation is that UPF1 sends a request to SMF1 for obtaining diversion rules, and SMF1 sends the diversion rules to UPF1 in response to the request.

In view of the above two situations, the existing synchronization scheme has the following problems:

For the first case, when the enterprise changes the service URL in the diversion rule, SMF1 will send a PFCP Session Modification Request message to UPF1 for each user signed up by the enterprise to push updates to all user sessions signed up by this enterprise. When the number of users signed up by the current enterprise is relatively large, this active push update at the session level will trigger a large number of N4 message interactions, causing a large consumption of device performance.

For the second case, the PFCP Session Report request message that UPF1 sends to SMF1 to obtain the diversion rules is also based on the session level. UPF1 needs to send a session report request message to SMF1 for each user. When the number of user sessions accessed on UPF1 is relatively large, such as 100,000 users accessing the current UPF1, a large number of session-level N4 message interactions for diversion rule synchronization will be caused, which will cause a great consumption of device performance.

If such session messages carry a large number of service URLs, the consumption of device performance in the above two situations will be further amplified.

In view of this, the embodiments of the present application optimize the above-mentioned problems and propose a dual-domain private network diversion rule synchronization method, device, equipment, medium and product. A method for updating and maintaining diversion rules on UPF through PFD node-level messages. When the diversion rules corresponding to different sessions, that is, users, are the same, the diversion rules of different sessions can be synchronized through a node-level message, which can greatly reduce the consumption of device performance.

The following first describes the dual-domain private network diversion rule synchronization method provided in an embodiment of the present application.

The dual-domain private network diversion rule synchronization method provided in the embodiment of the present application can be applied to the dual-domain private network scenario.

Referring to FIG. 2 , a flow chart of a dual-domain private network traffic diversion rule synchronization method provided in an embodiment of the present application is shown. As shown in FIG. 2 , the method may include the following steps S21-S23, which are described below respectively:

S21. The session management function network element sends a PFD synchronization message to the user plane function network element. The PFD synchronization message includes the PFD identifier and PFD rule content of the target private network. The PFD identifier includes the private network DNN information and the private network slice identifier. The PFD rule content includes the diversion rule.

In this embodiment, the session management function network element and the user plane function network element are both network elements in the public network. Taking Figure 1 as an example, the session management function network element corresponds to SMF1, and the user plane function network element corresponds to UPF1. For ease of description, the session management function network element is referred to as SMF and the user plane function network element is referred to as UPF.

In this embodiment, the message type of the PFD synchronization message is a PFCP PFD Management message, that is, a PFD management message using the PFCP protocol. The PFCP PFD Management message is a node-level management message defined in the 3GPP protocol.

The PFD synchronization message includes the PFD identifier and PFD rule content of the target private network. The target private network can include any private network in the dual-domain private network scenario. Among them, the PFD identifier is the unique identifier of the target private network created based on the private network DNN information and private network slice identifier of the target private network. The PFD rule content is the diversion rule created based on the network access information of the target private network, that is, the service URL.

The construction method of the PFD identifier includes but is not limited to service DNN+service NSSAI=PFD ID, where service DNN refers to private network DNN information, service NSSAI refers to the private network slice identifier, and PFD ID refers to the PFD identifier.

The service URL of the target private network can include four formats: IPv4 address or address segment, IPv6 address or address segment, FQDN, and URL. According to the definition of PFD Contents in the 3GPP protocol, that is, the content of PFD rules, PFD rule content supports three formats: Flow Description, URL, and Domain Name. Therefore, the PFD rule content in the PFD synchronization message can fully support several formats of the current service URL.

In this way, UPF can create dynamic diversion rules for the target private network based on the PFD synchronization message sent by SMF, accurately identify the traffic of the target private network and complete subsequent diversion.

S22. The user plane function network element determines a target diversion rule corresponding to the target private network from a stored diversion rule library based on the PFD identifier.

In this embodiment, a diversion rule library is stored on the UPF, and the diversion rule library includes diversion rules for each private network in the dual-domain private network scenario. After the UPF receives the PFD synchronization message sent by the SMF, it can parse the PFD synchronization message to obtain the PFD identifier and PFD rule content of the target private network contained therein. It can be seen from the foregoing content that the PFD identifier is constructed based on the private network DNN information and private network slice identifier of the target private network, and the private network DNN information and private network slice identifier are used to identify private network users. Therefore, the UPF can identify the target private network based on the private network DNN information and private network slice identifier of the target private network. Based on this, the UPF can determine the target diversion rule corresponding to the target private network from the stored diversion rule library based on the acquired PFD identifier.

S23. The user plane functional network element updates the target diversion rule based on the network access information in the PFD rule content.

In this embodiment, the PFD rule content of the target private network includes the diversion rules of the target private network. Based on this, after UPF determines the target diversion rules from the diversion rule library, it can update the target diversion rules based on the PFD rule content to achieve synchronization of the diversion rules of the target private network, thereby facilitating accurate identification of the target private network traffic and completing subsequent diversion.

In some embodiments of the present application, the PFD rule content of the target private network may include the full diversion rule of the target private network. Based on this, the user plane function network element updates the target diversion rule based on the diversion rule in the PFD rule content, which may include the following steps:

Delete the target diversion rule from the diversion rule library;

The diversion rules in the PFD rule content are stored in the diversion rule library as diversion rules corresponding to the target private network.

In this way, the diversion rules corresponding to the target private network in the diversion rule library can be completely replaced, thereby improving the accuracy of the updated diversion rules.

In some embodiments of the present application, considering that when the session management function network element sends a PFD synchronization message to the user plane function network element, the diversion rule of the target private network may not have changed, when the user plane function network element updates the target diversion rule based on the diversion rule in the PFD rule content, before deleting the target diversion rule from the diversion rule library, the following steps may be performed:

The diversion rule in the PFD rule content is compared with the target diversion rule to determine whether the diversion rule in the PFD rule content is consistent with the target diversion rule.

Accordingly, deleting the target diversion rule from the diversion rule library may include:

When the diversion rule in the PFD rule content is inconsistent with the target diversion rule, the target diversion rule is deleted from the diversion rule library.

When the diversion rules in the PFD rule content are consistent with the target diversion rules, there is no need to update the target diversion rules, and thus there is no need to delete the target diversion rules from the diversion rule library.

In this way, the replacement of diversion rules of the target private network whose diversion rules have not changed can be reduced, thereby reducing the consumption of device performance.

The dual-domain private network diversion rule synchronization method provided in this embodiment is that the session management function network element sends a PFD synchronization message to the user plane function network element, the PFD synchronization message includes the PFD identifier and PFD rule content of the target private network, the PFD identifier includes the private network DNN information and the private network slice identifier, and the PFD rule content includes the diversion rule; the user plane function network element determines the target diversion rule corresponding to the target private network from the stored diversion rule library based on the PFD identifier; the user plane function network element updates the target diversion rule based on the diversion rule in the PFD rule content. According to the embodiment of the present application, for different users who have signed contracts for the same private network, the diversion rule synchronization can be performed through a node-level PFD synchronization message. Compared with the traditional synchronization method based on session-level messages, the amount of messages for synchronizing diversion rules between network elements is greatly reduced, the consumption of equipment performance is reduced, and the risk of core network signaling storms is reduced.

In some embodiments, referring to FIG. 3 , before the above step S21, the following steps may be performed:

S31. The session management function network element determines whether there is a private network whose diversion rules have changed;

S32. When the session management function network element determines that there is a private network with a changed diversion rule, the private network with a changed diversion rule is used as the target private network;

S33. The session management function network element generates a PFD synchronization message of the target private network based on the DNN information of the target private network, the private network slice identifier and the changed diversion rules.

In this embodiment, when SMF determines that there is a private network whose diversion rules have changed in the dual-domain private network scenario, it can actively send a PFD synchronization message of the private network to UPF to synchronize the diversion rules.

For each private network, its corresponding traffic diversion rules are closely related to its network access information, that is, the service URL. When the service URL changes, its corresponding traffic diversion rules will also change accordingly. Among them, changes to the service URL include but are not limited to addition, deletion, modification, etc.

In some embodiments of the present application, one enterprise may correspond to one private network. For example, a private network B corresponding to an enterprise A may be used to change the service URL of private network B on the PCF according to actual needs, such as adding a new service URL. After enterprise A changes the service URL of private network B, the PCF may transmit the diversion rules corresponding to private network B to the SMF based on the changed content. After the SMF receives the diversion rules sent by the PCF, it may determine that the diversion rules of private network B have been changed, and thus use private network B as the target private network.

After determining the target private network, the PFD identifier of the target private network is generated based on the private network DNN information and private network slice identifier of the target private network, and the PFD rule content of the target private network is generated based on the changed diversion rules of the target private network. The PFD identifier and PFD rule content of the target private network are combined into a PFD synchronization message. Then, the SMF can send the PFD synchronization message to the UPF.

In this way, after the diversion rules of the private network are changed, SMF can actively synchronize the diversion rules for the private network with UPF to ensure the accuracy of the diversion rules stored in UPF.

In some embodiments, referring to FIG. 4 , before the above step S21, the following steps S41-S43 may be performed first, which are described below:

S41. The session management function network element determines whether a request message sent by the user plane function network element is received, where the request message is used to request to obtain a diversion rule.

In this embodiment, when determining that diversion rule synchronization is required, UPF can send a request message for requesting to obtain diversion rules to SMF to instruct SMF to synchronize diversion rules. Therefore, SMF can determine whether it is necessary to synchronize diversion rules with UPF by determining whether the request message sent by UPF is received.

In some embodiments of the present application, the UPF may send a request message to the SMF when any diversion rule stored thereon is lost. For example, the UPF may actively send a request message to the SMF for obtaining the diversion rule when the diversion rule stored thereon is lost due to aging, abnormal deletion, restart, etc.

S42. When the session management function network element determines that it has received the request message sent by the user plane function network element, the session management function network element determines the target private network based on the request message.

In some embodiments of the present application, after receiving the request message sent by UPF, SMF may send a response message to UPF to inform UPF that it has received the request message. Among them, the message types of the request message and the response message may both be Node Report messages. For example, when the diversion rules stored on UPF are lost due to aging, abnormal deletion, restart, etc., UPF may actively send a Node Report Request message to SMF for requesting to obtain the diversion rules. After SMF receives the Node Report Request message from UPF, it responds to UPF with a Node Report Response message.

When the SMF receives the request message sent by the UPF, it can generate a corresponding PFD synchronization message based on the request message. When generating the PFD synchronization message, the target private network is first determined based on the request message.

In some embodiments of the present application, the request message sent by the UPF may carry a PFD identifier. Based on this, when determining the target private network based on the request message, the following steps may be adopted:

Determine whether the request message contains a PFD identifier;

When the request message includes a PFD identifier, the private network corresponding to the PFD identifier included in the request message is used as the target private network;

When the request message does not contain the PFD identifier, all private networks are regarded as target private networks.

Among them, all private networks refer to all private networks in the dual-domain private network scenario.

In this way, when the request message contains the PFD identifier, the diversion rule synchronization of the private network corresponding to the PFD identifier can be performed, so that the diversion rule synchronization of the specified private network can be achieved in a targeted manner; and when the request message does not contain the PFD identifier, the lost diversion rules can be synchronized to the UPF in time by synchronizing the diversion rules of all private networks.

S43. The session management function network element generates a PFD synchronization message of the target private network based on the private network DNN information, private network slice identifier and diversion rules of the target private network.

In some embodiments of the present application, SMF can generate a PFD synchronization message for each target private network respectively. For each target private network, SMF can generate a PFD identifier of the target private network based on the DNN information and the private network slice identifier of the target private network, generate the PFD rule content of the target private network based on the diversion rule of the target private network, and combine the PFD identifier and PFD rule content of the target private network to obtain the PFD synchronization message corresponding to the target private network.

Through the above method, SMF can synchronize the diversion rules with UPF when UPF sends a request message.

In some embodiments, after completing the update of the diversion rules corresponding to the target private network, the UPF may send a PFD response message to the SMF in response to the PFD synchronization message to inform the SMF that the diversion rule synchronization has been successfully completed. The message type of the PFD response message is also a PFCP PFD Management message. For example, when the SMF determines that there is a private network in which the diversion rules have been changed and/or determines that a request message sent by the UPF has been received, the SMF sends a PFCP PFD Management Request message to the UPF to synchronize the diversion rules with the UPF. After the synchronization is completed, the UPF may send a PFCP PFD Management Response message to the SMF in response to the PFCP PFD Management Request message to inform the SMF that the synchronization is complete.

Based on the dual-domain private network traffic diversion rule synchronization method provided in the above embodiment, the present application also provides a specific implementation of the dual-domain private network traffic diversion rule synchronization device. Please refer to the following embodiment.

5 , a dual-domain private network diversion rule synchronization device 500 provided in an embodiment of the present application includes at least: a session management function network element 501 and a user plane function network element 502;

The session management function network element 501 is used to send a PFD synchronization message to the user plane function network element 502. The PFD synchronization message includes the PFD identifier and PFD rule content of the target private network. The PFD identifier includes the private network DNN information and the private network slice identifier. The PFD rule content includes the diversion rule.

The user plane function network element 502 is used to determine a target diversion rule corresponding to the target private network from the stored diversion rule library based on the PFD identifier;

The user plane function network element 502 is further configured to update the target diversion rule based on the diversion rule in the PFD rule content.

The dual-domain private network diversion rule synchronization device of the embodiment of the present application is configured such that the session management function network element sends a PFD synchronization message to the user plane function network element, the PFD synchronization message includes the PFD identifier and PFD rule content of the target private network, the PFD identifier includes the private network DNN information and the private network slice identifier, and the PFD rule content includes the diversion rule; the user plane function network element determines the target diversion rule corresponding to the target private network from the stored diversion rule library based on the PFD identifier; the user plane function network element updates the target diversion rule based on the diversion rule in the PFD rule content. According to the embodiment of the present application, for different users who have signed contracts for the same private network, diversion rule synchronization can be performed through a node-level PFD synchronization message. Compared with the traditional synchronization method based on session-level messages, the amount of messages for synchronizing diversion rules between network elements is greatly reduced, the consumption of equipment performance is reduced, and the risk of core network signaling storms is reduced.

In some embodiments, the session management function network element 501 is further configured to:

Before sending the PFD synchronization message to the user plane function network element 502, determine whether there is a private network whose diversion rules have been changed;

When it is determined that there is a private network whose diversion rules have been changed, the private network whose diversion rules have been changed is used as the target private network;

Generate the PFD synchronization message of the target private network based on the DNN information of the target private network, the private network slice identifier and the changed diversion rules.

In some embodiments, the session management function network element 501 is further configured to:

Before sending the PFD synchronization message to the user plane function network element 502, determining whether a request message sent by the user plane function network element is received, the request message is used to request to obtain the diversion rule;

In the case of determining that a request message sent by the user plane function network element is received, determining a target private network based on the request message;

A PFD synchronization message of the target private network is generated based on the private network DNN information, private network slice identifier and diversion rules of the target private network.

In some embodiments, the session management function network element 501 is further configured to:

Determine whether the request message contains a PFD identifier;

When the request message includes a PFD identifier, the private network corresponding to the PFD identifier included in the request message is used as the target private network;

When the request message does not contain the PFD identifier, all private networks are regarded as target private networks.

In some embodiments, the user plane function network element 502 is further configured to:

In the event that any diversion rule stored thereon is lost, a request message is sent to the session management function network element 501 .

In some embodiments, the PFD rule content of the target private network includes a full traffic diversion rule of the target private network, and the user plane function network element 50 is used to:

Delete the target diversion rule from the diversion rule library;

The diversion rules in the PFD rule content are stored in the diversion rule library as diversion rules corresponding to the target private network.

In some embodiments, the user plane function network element 502 is further configured to:

Before deleting the target diversion rule from the diversion rule library, the diversion rule in the PFD rule content is compared with the target diversion rule to determine whether the diversion rule in the PFD rule content is consistent with the target diversion rule;

When the diversion rule in the PFD rule content is inconsistent with the target diversion rule, the target diversion rule is deleted from the diversion rule library.

The dual-domain private network diversion rule synchronization device provided in the embodiment of the present application can implement each process implemented by the method embodiments of Figures 2 to 4. To avoid repetition, they will not be described here.

FIG6 shows a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application.

The electronic device 600 may include a processor 601 and a memory 602 storing computer program instructions.

Specifically, the processor 601 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

The memory 602 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 602 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, the memory 602 may include a removable or non-removable (or fixed) medium. In appropriate cases, the memory 602 may be inside or outside the integrated gateway disaster recovery device. In a specific embodiment, the memory 602 is a non-volatile solid-state memory. The memory 602 may include a read-only memory (ROM), a random access memory (RAM), a disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical, or other physical/tangible memory storage device. Therefore, typically, the memory 602 includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it can perform the operations described in any one of the dual-domain private network diversion rule synchronization methods in the above-mentioned embodiments.

The processor 601 implements any one of the dual-domain private network traffic diversion rule synchronization methods in the above embodiments by reading and executing computer program instructions stored in the memory 602.

In one example, the electronic device 600 may further include a communication interface 603 and a bus 610. As shown in Fig. 6, the processor 601, the memory 602, and the communication interface 603 are connected via the bus 610 and communicate with each other.

The communication interface 603 is mainly used to implement communication between various modules, devices, units and/or equipment in the embodiments of the present application.

Bus 610 includes hardware, software or both, and the parts of online data flow billing equipment are coupled to each other. For example, but not limitation, bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industrial standard architecture (EISA) bus, front-end bus (FSB), hypertransport (HT) interconnection, industrial standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In appropriate cases, bus 610 may include one or more buses. Although the present application embodiment describes and shows a specific bus, the present application considers any suitable bus or interconnection.

In addition, in combination with the dual-domain private network traffic diversion rule synchronization method in the above embodiment, the embodiment of the present application can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when the computer program instructions are executed by the processor, any dual-domain private network traffic diversion rule synchronization method in the above embodiment is implemented.

It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.

The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.

Aspects of the present disclosure are described above with reference to the flowchart and/or block diagram of the method, device (system) and computer program product according to the embodiment of the present disclosure. It should be understood that each box in the flowchart and/or block diagram and the combination of each box in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function/action specified in one or more boxes of the flowchart and/or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and/or flowchart and the combination of boxes in the block diagram and/or flowchart can also be implemented by dedicated hardware that performs a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

The above is only a specific implementation of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.

Claims (11)

1. A dual-domain private network diversion rule synchronization method, characterized by comprising: The session management function network element sends a PFD synchronization message to the user plane function network element, wherein the PFD synchronization message includes the PFD identifier and PFD rule content of the target private network, wherein the PFD identifier includes the private network DNN information and the private network slice identifier, and the PFD rule content includes the diversion rule; The user plane function network element determines a target diversion rule corresponding to the target private network from a stored diversion rule library based on the PFD identifier; The user plane function network element updates the target diversion rule based on the diversion rule in the PFD rule content. 2. The method according to claim 1, characterized in that before the session management function network element sends the PFD synchronization message to the user plane function network element, the method further comprises: The session management function network element determines whether there is a private network whose diversion rules have been changed; When the session management function network element determines that there is a private network whose diversion rule has been changed, the private network whose diversion rule has been changed is used as the target private network; The session management function network element generates a PFD synchronization message of the target private network based on the DNN information of the target private network, the private network slice identifier and the changed diversion rules. 3. The method according to claim 1, characterized in that before the session management function network element sends the PFD synchronization message to the user plane function network element, the method further comprises: The session management function network element determines whether a request message sent by the user plane function network element is received, where the request message is used to request to obtain a diversion rule; The session management function network element determines the target private network based on the request message when determining that the request message sent by the user plane function network element is received; The session management function network element generates a PFD synchronization message of the target private network based on the private network DNN information, private network slice identifier and diversion rules of the target private network. 4. The method according to claim 3, characterized in that the determining the target private network based on the request message comprises: Determine whether the request message contains a PFD identifier; In the case where the request message includes a PFD identifier, taking the private network corresponding to the PFD identifier included in the request message as the target private network; When the request message does not include a PFD identifier, all private networks are taken as target private networks. 5. The method according to claim 3 or 4, characterized in that the method further comprises: The user plane function network element sends the request message to the session management function network element when any diversion rule stored therein is lost. 6. The method according to claim 1, wherein the PFD rule content of the target private network includes a full diversion rule of the target private network, and the user plane function network element updates the target diversion rule based on the diversion rule in the PFD rule content, comprising: Deleting the target diversion rule from the diversion rule library; The diversion rules in the PFD rule content are stored in the diversion rule library as diversion rules corresponding to the target private network. 7. The method according to claim 6, characterized in that before deleting the target diversion rule from the diversion rule library, the method further comprises: The user plane function network element compares the diversion rule in the PFD rule content with the target diversion rule to determine whether the diversion rule in the PFD rule content is consistent with the target diversion rule; The deleting the target diversion rule from the diversion rule library includes: When the diversion rule in the PFD rule content is inconsistent with the target diversion rule, the target diversion rule is deleted from the diversion rule library. 8. A dual-domain private network diversion rule synchronization device, characterized by comprising: a session management function network element and a user plane function network element; The session management function network element is used to send a PFD synchronization message to the user plane function network element, wherein the PFD synchronization message includes a PFD identifier and PFD rule content of a target private network, wherein the PFD identifier includes private network DNN information and a private network slice identifier, and the PFD rule content includes a diversion rule; The user plane function network element is used to determine a target diversion rule corresponding to the target private network from a stored diversion rule library based on the PFD identifier; The user plane function network element is further used to update the target diversion rule based on the diversion rule in the PFD rule content. 9. An electronic device, characterized in that the electronic device comprises: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the dual-domain private network diversion rule synchronization method as described in any one of claims 1-7 is implemented. 10. A computer-readable storage medium, characterized in that computer program instructions are stored on the computer-readable storage medium, and when the computer program instructions are executed by a processor, the dual-domain private network diversion rule synchronization method according to any one of claims 1 to 7 is implemented. 11. A computer program product, characterized in that when the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the dual-domain private network diversion rule synchronization method as described in any one of claims 1-7.