A method and system for implementing routing and forwarding control between an L-DN and a C-DN, an electronic device, and a storage medium

Abstract

The application discloses a method and system for realizing routing forwarding control between L-DN and C-DN, electronic equipment and a storage medium, and the method comprises the following steps: deploying a shunt between the L-DN and the C-DN, wherein the shunt comprises an uplink shunt and a downlink shunt; the uplink shunt and the downlink shunt are respectively used for identifying target flows in uplink and downlink and performing corresponding IP header replacement, so that the service traffic of the related UE can bypass the local application server in the L-DN, and the return service traffic from the L-DN can also reuse the PDU session path established between the UE and the central session anchor point. The technical scheme of the application can determine and forward the uplink and downlink target application traffic which needs to be bypassed while meeting the QoS (quality of service) requirement of the service of each user equipment in the case that there is no direct route between the L-DN and the C-DN.

Description

Technical Field

[0001] This invention belongs to the field of communication technology, and more specifically, relates to a method, system, electronic device, and storage medium for implementing routing and forwarding control between L-DN and C-DN. Background Technology

[0002] Currently, the support for traffic routing between L-DN (Local Data Network) and C-DN (Central Data Network) is as follows: Figure 1 As shown, L-DN is typically deployed at the operator's edge nodes, while C-DN is typically deployed in a national central data center or public cloud. In some scenarios, application traffic may need to be routed to edge nodes for processing. After initial processing, the application traffic ultimately needs further processing on the AS (Application Server) of the C-DN. Application-related UL (UpLink) traffic is first routed to the edge application server for local processing, and then further forwarded to the remote application server in the DN central area. Application-related DL (DownLink) traffic is first processed on the application server in the DN central area, then forwarded to the application server in the local EC (Edge Cloud) for local processing, and finally provided to the UE (User Equipment).

[0003] Because there is no direct route between the L-DN and C-DN, application traffic cannot be directly forwarded between the EAS (Edge Application Server) in the L-DN and the application server in the C-DN. Furthermore, the routes provided to any UE service traffic must meet the corresponding QoS (Quality of Service) requirements. Therefore, there is an urgent need for a method to enable UE service traffic to be bypassed and processed locally in the L-DN before being forwarded to the central C-DN application server (uplink) or forwarded to the UE (downlink) in the absence of a direct route between the L-DN and C-DN, while simultaneously meeting the QoS requirements of each UE service. Summary of the Invention

[0004] To address the shortcomings of existing technologies, this invention provides a method, system, electronic device, and storage medium for implementing routing and forwarding control between L-DN and C-DN. In the absence of a direct route between L-DN and C-DN, this method enables UE service traffic to be bypassed and processed locally in the L-DN before being forwarded to the central C-DN application server (uplink direction) or forwarded to the UE (downlink direction), while simultaneously meeting the QoS service quality requirements of each UE service.

[0005] The present invention adopts the following technical solution.

[0006] A first aspect of the present invention provides a method for implementing routing forwarding control between L-DN and C-DN, comprising:

[0007] A traffic splitter is deployed between the L-DN and C-DN. The traffic splitter includes an uplink traffic splitter and a downlink traffic splitter. The uplink traffic splitter and the downlink traffic splitter are used to identify the uplink target flow and the downlink target flow, respectively, and perform the corresponding IP header replacement. This allows the service traffic of the user equipment to bypass to the local application server in the L-DN. The service traffic returning from the L-DN can also reuse the PDU session path established between the user equipment and the central session anchor point. The central session anchor point is used as the anchor point for the user equipment IP address and connects to the C-DN.

[0008] Optionally, the splitter can be integrated into the local session anchor or as a standalone user plane function, where the local session anchor serves as the anchor point for the user equipment's local IP address and connects to the L-DN.

[0009] Optionally, a central application server is deployed in the C-DN, and a local edge application server is deployed in the L-DN. The data flow in the uplink direction includes:

[0010] The first data stream is the data stream sent by the user equipment to the uplink splitter. Its source address is the user equipment IP address and its destination address is the central application server IP address.

[0011] The second data stream is formed by the uplink splitter identifying the first data stream, replacing the source address of the first data stream with the user equipment's local IP address, and replacing the destination address of the first data stream with the local edge application server's IP address, and then sending the data stream to the local edge application server via the local session anchor.

[0012] The third data stream is the data stream sent from the local edge application server to the uplink splitter via the local session anchor point. Its source address is the IP address of the local edge application server, and its destination address is the local IP address of the user device.

[0013] The fourth data stream is the data stream formed by the uplink splitter after identifying the third data stream, replacing the source address of the third data stream with the user equipment IP address, and replacing the destination address of the third data stream with the central application server IP address, and then sending it to the central session anchor point.

[0014] The fifth data stream is the data stream sent from the central session anchor to the central application server. Its source address is the user device IP address, and its destination address is the central application server IP address.

[0015] Optionally, a central application server is deployed in the C-DN, and a local edge application server is deployed in the L-DN. The downlink data flow includes:

[0016] The first data stream is the data stream sent from the central application server to the central session anchor point. Its source address is the IP address of the central application server, and its destination address is the IP address of the user device.

[0017] The second data stream is the data stream sent from the central session anchor to the downlink splitter. Its source address is the IP address of the central application server and its destination address is the IP address of the user equipment.

[0018] The third data stream is the data stream that the downlink splitter identifies after the second data stream, replaces the source address of the second data stream with the user equipment IP address, and replaces the destination address with the local edge application server IP address; and sends it to the local edge application server through the local session anchor point.

[0019] The fourth data stream is the data stream sent from the local edge application server to the downlink splitter via the local session anchor. Its source address is the IP address of the local edge application server, and its destination address is the IP address of the user device.

[0020] The fifth data stream is a data stream formed by the downlink splitter identifying the fourth data stream, replacing its source address with the central application server's IP address, and sending it to the user equipment with the user equipment's IP address as the destination address.

[0021] Optionally, at the granularity of each quality of service flow of each user equipment service, the user equipment service traffic is transmitted through the PDU session of the user equipment established from the user equipment to the central session anchor point and processed and returned by the local edge application server, wherein one PDU session is bound to one user equipment.

[0022] Optionally, traffic from the user equipment to the local session anchor and traffic from the local session anchor to the central session anchor can be transmitted through the same PDU session.

[0023] Optionally, the session management function sends packet inspection rules and / or forwarding action rules to the flow splitter. The flow splitter identifies the target flow based on the packet inspection rules and performs the corresponding IP header replacement based on the forwarding action rules.

[0024] A second aspect of the present invention provides a system for implementing routing forwarding control between an L-DN and a C-DN, implementing the above-described method for implementing routing forwarding control between an L-DN and a C-DN, the system comprising:

[0025] User equipment;

[0026] The traffic splitter, deployed between the L-DN and C-DN, is used to identify the target flow and perform the corresponding IP header replacement, so that the service traffic of the user equipment can be bypassed to the local application server in the L-DN, and the service traffic returning from the L-DN can also reuse the PDU session path established between the user equipment and the central session anchor.

[0027] The central session anchor point serves as the anchor point for user equipment IP addresses and connects to the C-DN, in which a central application server is deployed.

[0028] The local session anchor point is used as the anchor point for the user equipment's local IP address and connects to the L-DN, in which the local edge application server is deployed;

[0029] The uplink traffic path is as follows: user equipment, uplink splitter, local session anchor, local edge application server, local session anchor, uplink splitter, central session anchor, central application server.

[0030] The downlink traffic path is as follows: central application server, central session anchor, downlink splitter, local session anchor, local edge application server, local session anchor, downlink splitter, and user equipment.

[0031] A third aspect of the present invention provides an electronic device, including a processor and a storage medium; wherein the storage medium is used to store instructions; and the processor is used to operate according to the instructions to execute the steps of the method described above for implementing routing forwarding control between L-DN and C-DN.

[0032] A fourth aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described above for implementing routing forwarding control between L-DN and C-DN.

[0033] Compared with the prior art, the beneficial effects of the present invention include at least the following:

[0034] This invention deploys a traffic splitter between the L-DN and C-DN. The splitter includes an uplink splitter and a downlink splitter. The uplink and downlink splitters are used to identify uplink and downlink target flows and perform corresponding IP header replacements, respectively. This allows the splitter to route traffic between the L-DN and C-DN using the existing PDU session path on the user plane path between the user equipment and the central session anchor. As a result, service traffic that has been bypassed by the L-DN can still use the same UE PDU session to go uplink to the C-DN or downlink to the UE. Thus, even when there is no direct route between the L-DN and C-DN, the invention can determine and forward uplink and downlink target application traffic while meeting the QoS service quality requirements of each UE service. Attached Figure Description

[0035] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Wherein:

[0036] Figure 1 This invention provides a schematic diagram of the routing support process between a local DN and a central DN for uplink / downlink traffic of a UE in a prior art. Figure 1 In the diagram, blue arrows represent uplink data flow from the user device client to the local edge application server, red arrows represent uplink data flow from the local edge application server to the central application server, magenta arrows represent downlink data flow from the central application server to the local edge application server, and green arrows represent downlink data flow from the local edge application server to the user device client.

[0037] Figure 2 This is a schematic diagram of the UL traffic guidance process in a method for implementing routing and forwarding control between L-DN and C-DN provided by the present invention; Figure 2 In the diagram, red arrows represent the first data flow from the user device to the splitter, the fourth data flow from the splitter to the central session anchor point, and the fifth data flow from the central session anchor point to the central application server, respectively. Purple arrows represent the second data flow from the splitter to the local edge application server via the local session anchor point, and blue arrows represent the third data flow from the local edge application server to the splitter via the local session anchor point. The source IPs of the data flows indicated by red arrows are all user device IPs, and the destination IPs are all central application server IPs. The source IPs of the data flows indicated by purple arrows are all user device local IPs, and the destination IPs are all local edge application server IPs. The source IPs of the data flows indicated by blue arrows are all local edge application server IPs, and the destination IPs are all user device local IPs.

[0038] Figure 3 This is a schematic diagram of the DL traffic processing flow in a method for implementing routing and forwarding control between L-DN and C-DN provided by the present invention. Figure 3 In the diagram, red arrows represent the first data flow from the central application service to the central session anchor, the second data flow from the central session anchor to the splitter, and the fifth data flow from the splitter to the user device, respectively. Purple arrows represent the fourth data flow from the local edge application server to the splitter via the local session anchor, and blue arrows represent the third data flow from the splitter to the local edge application server via the local session anchor. The source IPs of the data flows indicated by red arrows are all central application server IPs, and the destination IPs are all user IPs. The source IPs of the data flows indicated by purple arrows are all local application server IPs, and the destination IPs are all user device IPs. The source IPs of the data flows indicated by blue arrows are all user device IPs, and the destination IPs are all local application server IPs. Detailed Implementation

[0039] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of this invention. The embodiments described in this application are merely some embodiments of this invention, and not all embodiments. Based on the spirit of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the protection scope of this invention.

[0040] This invention provides a method for implementing routing forwarding control between L-DN and C-DN, comprising the following steps:

[0041] S1: Deploy a splitter between the L-DN and C-DN. The splitter includes an uplink splitter and a downlink splitter. The uplink splitter and downlink splitter are used to identify the uplink and downlink target flows and perform the corresponding IP header replacements, respectively.

[0042] Deploy an uplink / downlink splitter UL / DL CL (Classifier) ​​between the UE and the C-PSA (Central PDU Session Anchor) UPF (User Plane Function) to identify the target flow and perform relevant IP header replacements.

[0043] Specifically, the traffic splitter is deployed in advance by the operator at the service level. For example, according to the service agreement signed in advance with the application service provider, the corresponding local edge application server is deployed at the edge. At this time, the operator achieves local bypass of the corresponding traffic by issuing PDR (Packet Detection Rule) or FAR (Forwarding Action Rule). For example, for a video service of a certain application service provider, as long as the destination address is in the address range of this server, it will be bypassed to the edge server, that is, L-DN.

[0044] It should be noted that UL / DL CL can be integrated with the local PSA UPF or run as a standalone user plane function UPF.

[0045] S2: UL traffic forwarding processing.

[0046] Table 1 shows the IP replacement and forwarding operations performed at the UL / DL CL, i.e., the IP replacement and traffic rules configured on the UL / DL CL. (This is in conjunction with Table 1 and...) Figure 2 As shown, for UL traffic from the UE, such as Figure 2 The first and second data streams shown in the diagram, UL CL UPF replaces the source IP address (UE IP) with the UE's local IP address (UE IP2) and the destination IP address with the EAS IP address.

[0047] For UL traffic from EAS to central AS, such as Figure 2 In the third and fourth data streams shown, the source IP address (EAS IP) is replaced with the UE IP address, and the destination IP address is replaced with the AS IP address.

[0048] This invention utilizes the UE's local IP address UEIP2 in the second and third data streams of uplink traffic, with each UE's local IP corresponding to one UE. This helps the UL / DL CL UPF distinguish between uplink traffic (from EAS to AS) and downlink traffic (from EAS to UE). Downlink traffic will use the original UE IP as the destination IP address. This method solves the problem in existing technologies where the Local PSA UPF cannot determine whether application traffic originating from the local EAS and destined for the UE IP should be forwarded downlink to the UE or uplink to the C-PSA UPF.

[0049] The mapping between the UE's local IP address and the UE's IP address is maintained by the UL CL UPF. The UE's local IP address can be assigned by the local PSA UPF or the UL CL UPF itself.

[0050] After address translation, such as Figure 2 As shown in the second and third data streams, the EAS always generates a return traffic destination IP address using the source IP address of the received data packet. This eliminates the requirement for the EAS to know the AS IP address, a problem faced by existing technologies. Furthermore, it eliminates the need for the EAS to perform source IP address substitution operations that are typically not supported by the operating system / IP protocol stack.

[0051] S3: DL traffic forwarding processing.

[0052] like Figure 3 As shown, for downlink traffic redirection, the reverse operation will be performed by DL CL UPF. Specifically, this includes:

[0053] For DL ​​traffic from the central AS, such as Figure 3 The first and second data streams shown use IP as the source IP address and UE IP as the destination IP address.

[0054] The SMF (Session Management Function) sends the PDR / FAR to the DL CLUPF. The DL CLUPF identifies the second data stream in the downlink traffic according to the rules, and then performs the IP replacement specified in the FAR, that is, replacing the source IP address AS IP with the UE IP address and the destination IP address with the EAS IP address, as shown in the third data stream.

[0055] After address translation, the EAS responds to the request and generates DL traffic, which is sent to the UE via the fourth data stream, using the EAS IP as the source IP address and the UE IP as the destination IP address.

[0056] When DL CL UPF identifies the fourth data stream in the downlink traffic from EAS to UE, it replaces the source IP address (EAS IP) with the AS IP address, while keeping the destination IP address as the UE IP address, thus creating the fifth data stream.

[0057] For the downlink direction, this invention does not use the UE's local IP, thus avoiding confusion when the UL / DL CL processes the third data stream in the uplink traffic and the fourth data stream in the DL traffic.

[0058] Table 1. IP Replacement and Forwarding Operations Performed at UL / DL CL

[0059]

[0060] Furthermore, the traffic for each UE from the local DN / L-UPF to the central DN / C-UPF is transmitted through the UE's PDU (Packet Data Unit) session at the granularity of each UE's service.

[0061] It should be noted that granularity is the smallest distinguishable unit for network processing of service flows. Through PDU sessions, the network can distinguish the corresponding UEs. Through QoS flows in PDU sessions, the network can distinguish the corresponding service flows. Subsequent QoS guarantees and billing can be executed on a per UE or per QoS flow basis, thereby ensuring service quality control and policy and billing control.

[0062] Furthermore, traffic from the UE to the Local PSA UPF (Local Session Anchor Point) and traffic from the Local PSA UPF to the C-PSA UPF (Central Session Anchor Point) are both transmitted through the same PDU session. For example... Figure 2 As shown, the source IP address of the first, fourth, and fifth data streams in the uplink should always be the UE IP address, while the destination IP address should always be the AS IP address. This ensures service consistency.

[0063] In this invention, the flow returned from L-DN processing and the original flow (i.e., the PDU session request initiated by the UE to the central session anchor point) still use the same UE's PDU session. That is, whether it's the uplink first, fourth, or fifth data flow, or the downlink first, second, or fifth data flow, their source and destination addresses remain the same. This ensures they are still within the same UE PDU session, thus guaranteeing consistent QoS. This invention allows service traffic that has undergone L-DN bypass processing to still use the same UE PDU session for uplink to C-DN or downlink to the UE, thereby ensuring that consistent service QoS requirements are met.

[0064] This invention also provides a system for implementing routing forwarding control between L-DN and C-DN, running the above-described method for implementing routing forwarding control between L-DN and C-DN, the system comprising:

[0065] User equipment;

[0066] The traffic splitter, deployed between the L-DN and C-DN, is used to identify the target flow and perform the corresponding IP header replacement, so that the service traffic of the user equipment can be bypassed to the local application server in the L-DN, and the service traffic returning from the L-DN can also reuse the PDU session path established between the user equipment and the central session anchor.

[0067] The central session anchor point serves as the anchor point for user equipment IP addresses and connects to the C-DN, in which a central application server is deployed.

[0068] The local session anchor point is used as the anchor point for the user equipment's local IP address and connects to the L-DN, in which the local edge application server is deployed;

[0069] The uplink traffic path is as follows: user equipment, uplink splitter, local session anchor, local edge application server, local session anchor, uplink splitter, central session anchor, central application server.

[0070] The downlink traffic path is as follows: central application server, central session anchor, downlink splitter, local session anchor, local edge application server, local session anchor, downlink splitter, and user equipment.

[0071] Regarding the system in the above embodiments, the specific manner in which each unit performs operations has been described in detail in the embodiments related to the method, and will not be elaborated here.

[0072] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when loaded onto the processor, implements the above-described method for routing and forwarding control between L-DN and C-DN.

[0073] The present invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method for routing and forwarding control between L-DN and C-DN.

[0074] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0075] This disclosure can be a system, method, and / or computer program product. A computer program product may include a computer-readable storage medium having computer-readable program instructions loaded thereon for causing a processor to implement various aspects of this disclosure.

[0076] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example—but not limited to—electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination of the foregoing. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

[0077] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0078] Computer program instructions used to perform the operations of this disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing the status information of the computer-readable program instructions to implement various aspects of this disclosure.

[0079] All parts not covered in this invention are the same as or can be implemented using existing technologies.

[0080] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the specific implementation of the present invention. Any modifications or equivalent substitutions that do not depart from the spirit and scope of the present invention should be covered within the protection scope of the claims of the present invention.

Claims

1. A method for implementing routing forwarding control between L-DN and C-DN, characterized in that, include: A traffic splitter is deployed between the L-DN and C-DN. The traffic splitter includes an uplink traffic splitter and a downlink traffic splitter. The uplink traffic splitter and the downlink traffic splitter are used to identify the uplink target flow and the downlink target flow, respectively, and perform the corresponding IP header replacement. This allows the service traffic of the user equipment to bypass to the local application server in the L-DN. The service traffic returning from the L-DN can also reuse the PDU session path established between the user equipment and the central session anchor point. The central session anchor point is used as the anchor point for the user equipment IP address and connects to the C-DN.

2. The method according to claim 1, characterized in that, The splitter can be integrated into the local session anchor or used as a standalone user plane function, where the local session anchor serves as the anchor point for the user equipment's local IP address and connects to the L-DN.

3. The method according to claim 1, characterized in that, A central application server is deployed in the C-DN, and local edge application servers are deployed in the L-DN. The uplink data flow includes: The first data stream is the data stream sent by the user equipment to the uplink splitter. Its source address is the user equipment IP address and its destination address is the central application server IP address. The second data stream is formed by the uplink splitter identifying the first data stream, replacing the source address of the first data stream with the local IP address of the user equipment, and replacing the destination address of the first data stream with the IP address of the local edge application server. The data stream is then sent to the local edge application server via the local session anchor. The third data stream is the data stream sent from the local edge application server to the uplink splitter via the local session anchor point. Its source address is the IP address of the local edge application server, and its destination address is the local IP address of the user device. The fourth data stream is the data stream formed by the uplink splitter after identifying the third data stream, replacing the source address of the third data stream with the user equipment IP address, and replacing the destination address of the third data stream with the central application server IP address, and then sending it to the central session anchor point. The fifth data stream is the data stream sent from the central session anchor to the central application server. Its source address is the user device IP address, and its destination address is the central application server IP address.

4. The method according to claim 1, characterized in that, A central application server is deployed in the C-DN, and local edge application servers are deployed in the L-DN. The downlink data flow includes: The first data stream is the data stream sent from the central application server to the central session anchor point. Its source address is the IP address of the central application server, and its destination address is the IP address of the user device. The second data stream is the data stream sent from the central session anchor to the downlink splitter. Its source address is the IP address of the central application server and its destination address is the IP address of the user equipment. The third data stream is the data stream that the downlink splitter identifies after the second data stream, replaces the source address of the second data stream with the user equipment IP address, and replaces the destination address with the local edge application server IP address; and sends it to the local edge application server through the local session anchor point. The fourth data stream is the data stream sent from the local edge application server to the downlink splitter via the local session anchor. Its source address is the IP address of the local edge application server, and its destination address is the IP address of the user device. The fifth data stream is a data stream formed by the downlink splitter identifying the fourth data stream, replacing its source address with the central application server's IP address, and sending it to the user equipment with the user equipment's IP address as the destination address.

5. The method according to claim 1, characterized in that, At the granularity of each quality of service flow of each user device service, the user device service traffic is transmitted through the PDU session established from the user device to the central session anchor point and processed and returned by the local edge application server. Here, one PDU session is bound to one user device.

6. The method according to claim 1, characterized in that, Traffic from user equipment to the local session anchor and traffic from the local session anchor to the central session anchor are transmitted through the same PDU session.

7. The method according to claim 1, characterized in that, The session management function sends packet inspection rules and / or forwarding action rules to the flow splitter. The flow splitter identifies the target flow based on the packet inspection rules and performs the corresponding IP header replacement based on the forwarding action rules.

8. A system for implementing routing forwarding control between L-DN and C-DN, comprising the method according to any one of claims 1-7, characterized in that, The system includes: User equipment; The traffic splitter, deployed between the L-DN and C-DN, is used to identify the target flow and perform corresponding IP header replacement, so that the service traffic of the user equipment can be bypassed to the local application server in the L-DN, and the service traffic returning from the L-DN can also reuse the PDU session path established between the user equipment and the central session anchor. The central session anchor point serves as the anchor point for user equipment IP addresses and connects to the C-DN, in which a central application server is deployed. The local session anchor point is used as the anchor point for the user equipment's local IP address and connects to the L-DN, in which the local edge application server is deployed; The uplink traffic path is as follows: user equipment, uplink splitter, local session anchor, local edge application server, local session anchor, uplink splitter, central session anchor, central application server. The downlink traffic path is as follows: central application server, central session anchor, downlink splitter, local session anchor, local edge application server, local session anchor, downlink splitter, and user equipment.

9. An electronic device, comprising a processor and a storage medium; characterized in that: The storage medium is used to store instructions; The processor is configured to operate according to the instructions to perform the steps of the method according to any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements the steps of the method described in any one of claims 1-7.

Images