Routing method, device and system for service flow

Abstract

The embodiment of the invention provides a service flow routing method, device and system, relates to the technical field of communication, and is used for continuously sending a service flow to a central DN after locally executing service chain control. The method comprises: a session management network element determining a routing rule, the routing rule being used for instructing a first offload entity to send a first service flow to a first functional entity and / or to send a second service flow to a second functional entity or an access device, the first service flow being a service flow to be subjected to first service chain control, and the second service flow being a service flow to be subjected to second service chain control; the second service flow is a service flow which has executed first service chain control; and in the session management process, the session management network element sends the routing rule to the first shunting entity.

Description

[0001] This application is a divisional application. The application number of the original application is 201980101714.2, and the original application date is November 8, 2019. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The embodiments of the present application relate to the field of communication technology, and in particular, to a method, device and system for routing a service flow. Background Art

[0003] The rapid development of mobile communications has promoted the emergence of various new services. In addition to traditional mobile broadband and the Internet of Things, mobile communications have spawned many application areas (such as augmented reality (AR) / virtual reality (VR), Internet of Vehicles, industrial control, Internet of Things (IOT), etc.). At the same time, it has also put forward higher requirements on network bandwidth, latency and other performance, further increasing the network load.

[0004] In order to provide users with better value-added services, traffic steering control is introduced. Traffic steering control means that the service flow is enhanced by a series of ordered service function network elements (SF). These SFs are located in the data network (DN). SFs can be functional network elements deployed by operators or by third parties.

[0005] like Figure 1 As shown, in a 4G network, a packet data network gateway (PGW) can perform traffic steering control on received service flows according to service chain policies. The specific process includes:

[0006] Step 1: The policy and charging rules function (PCRF) determines to activate service chain control for a service flow.

[0007] Step 2: PCRF sends the Policy and Charging Control (PCC) rules to the Policy and Charging Enforcement Function (PCEF). The PCC rules include: the identifier of the service flow and the identifier of the service chain policy. The PCEF is located in the PGW. The interface between the PGW and the PCRF is the Gx interface.

[0008] Step 3: PGW sends the service flow identified by the service flow identifier to each SF in the central DN according to the service chain policy to perform traffic steering control.

[0009] In 4G networks, traffic steering control is located between the PGW and the central DN. However, the PGW may be far away from the terminal. If the PGW sends the service flow to each SF to perform traffic steering control, a large delay may occur. Summary of the invention

[0010] The embodiments of the present application provide a method, device and system for transmitting a service flow, so as to enable the service flow to be continuously sent to a central DN after the service chain control is performed locally.

[0011] In order to achieve the above objectives, the present application provides the following technical solutions:

[0012] In a first aspect, an embodiment of the present application provides a method for routing a service flow, including: a session management network element determines a routing rule, the routing rule is used to instruct a first offload entity to send a first service flow to a first functional entity, and / or, to send a second service flow to a second functional entity or an access device, the first service flow is a service flow to be controlled by a first service chain, and the second service flow is a service flow that has been controlled by the first service chain. During the session management process, the session management network element sends the routing rule to the first offload entity.

[0013] The embodiment of the present application provides a method for routing a service flow, in which the session management network element determines a routing rule and sends the routing rule to a first diversion entity, so that the first diversion entity can perform corresponding forwarding actions on the service flow that complies with the routing rule according to the routing rule. For example, the first diversion entity can forward the first service flow recorded in the routing rule to the first functional entity. This is because the first service flow is usually a service flow to be controlled by the first service chain, so that the SF in the MEC platform corresponding to the first functional entity can perform the first service chain control on the first service flow. In addition, since the first functional entity is usually deployed at a location close to the terminal, the first service chain control can be performed on the first service flow as early as possible, such as video acceleration, firewall, and load balancing functions, so that the first service flow can be processed as early as possible, such as the firewall function, which can filter out invalid service flows as early as possible. Furthermore, in the embodiment of the present application, the first diversion entity can also send the second service flow recorded in the routing rule to the second functional entity or access device. This is because the second service flow is a service flow that has executed the first service chain control. In this way, the service flow can be sent back to the second functional entity after the first service chain control is executed.

[0014] In a possible implementation, the routing rule includes description information of the first service flow and information of the first functional entity associated with the description information of the first service flow, and / or description information of the second service flow and information of the second functional entity or access device associated with the description information of the second service flow. The description information includes source information of the first service flow or the second service flow. By indicating to the first diversion entity the description information of the first service flow sent to the first functional entity, it is convenient for the first diversion entity to send the received service flow to the first functional entity when determining that the description information of the received service flow is the same as the description information of the first service flow. By indicating to the first diversion entity the description information of the second service flow sent to the second functional entity, it is convenient for the first diversion entity to send the received service flow to the second functional entity or access device when determining that the description information of the received service flow is the same as the description information of the second service flow.

[0015] In a possible implementation, the routing rule includes any one or more of the following information: when the description information of the first service flow indicates that the first service flow comes from the access device or the second functional entity, the first shunt entity sends the first service flow to the first functional entity. Or, when the description information of the second service flow indicates that the second service flow comes from the first functional entity, the first shunt entity sends the second service flow to the access device or the second functional entity.

[0016] In a possible implementation, the routing rule is used to instruct the first shunt entity to send the first service flow from the second dedicated tunnel to the first functional entity, and / or to instruct the first shunt entity to send the second service flow from the first dedicated tunnel to the second functional entity. The second dedicated tunnel is located between the first shunt entity and the second functional entity. The first dedicated tunnel is located between the first shunt entity and the first functional entity. This facilitates the first shunt entity to determine that the service flow from a specific dedicated tunnel is sent to the corresponding functional entity.

[0017] In a possible implementation, the method provided by the embodiment of the present application further includes: the session management network element obtains one or more of the first dedicated tunnel information used to establish the first dedicated tunnel and the second dedicated tunnel information used to establish the second dedicated tunnel, so as to facilitate the subsequent establishment of one or more of the first dedicated tunnel and the second dedicated tunnel.

[0018] In a possible implementation, the method provided by the embodiment of the present application further includes: the session management network element sends the second dedicated tunnel information and the first forwarding rule to the second functional entity, and the first forwarding rule is used to instruct the second functional entity to transmit the first service flow to the first diversion entity through the second dedicated tunnel. By sending the first forwarding rule and the first dedicated tunnel information, the second functional entity can subsequently transmit the first service flow to be controlled by the service chain to be executed from the first dedicated tunnel to the first diversion entity.

[0019] In a possible implementation, the method provided by the embodiment of the present application further includes: the session management network element sends the first dedicated tunnel information and the second forwarding rule to the first functional entity, and the second forwarding rule is used to instruct the first functional entity to transmit the second service flow to the first diversion entity through the first dedicated tunnel. By sending the second forwarding rule and the first dedicated tunnel information, the first functional entity can subsequently transmit the second service flow that has executed service chain control to the first diversion entity through the first dedicated tunnel.

[0020] In a possible implementation, before the session management network element obtains one or more of the first dedicated tunnel information and the second dedicated tunnel information, the method provided in the embodiment of the present application also includes: the session management network element sends a first indication message to the first diversion entity, and the first indication message is used to indicate the first diversion entity to allocate one or more of the first dedicated tunnel information and the second dedicated tunnel information. Correspondingly, the session management network element obtains one or more of the first dedicated tunnel information and the second dedicated tunnel information, including: the session management network element receives one or more of the first dedicated tunnel information and the second dedicated tunnel information from the first diversion entity. That is, in addition to autonomously allocating one or more of the first dedicated tunnel information and the second dedicated tunnel information, the session management network element can also obtain one or more of the first dedicated tunnel information and the second dedicated tunnel information from the first diversion entity.

[0021] In a possible implementation, the first service flow is associated with the first identifier, and the routing rule is used to instruct the first shunt entity to send the service flow associated with the first identifier to the first functional entity. Alternatively, the second service flow is associated with the second identifier, and the routing rule is used to instruct the first shunt entity to send the service flow associated with the second identifier to the second functional entity.

[0022] In a possible implementation manner, the method provided by the embodiment of the present application also includes: the session management network element sends third indication information to the second functional entity, which is used to instruct the second functional entity to carry the first identifier in the message header of the first service flow.

[0023] In a possible implementation manner, the method provided by the embodiment of the present application also includes: the session management network element sends fourth indication information to the first functional entity, which is used to instruct the first functional entity to carry the second identifier in the message header of the second service flow.

[0024] In a possible implementation, the method provided by the embodiment of the present application also includes: the session management network element determines that the diversion entity changes from the first diversion entity to the second diversion entity. The session management network element sends a fifth indication information to the second diversion entity for instructing the second diversion entity to perform any one or more of the following steps: sending a third service flow originating from the first diversion entity to the access device; or, sending a fourth service flow originating from the second functional entity to the third functional entity corresponding to the second diversion entity. Among them, the third service flow has been executed service chain control or the third service flow is a service flow that has executed the first service chain control. The fourth service flow is a service flow to be executed by the first service chain control. In the case of a change in the diversion entity, the method can send the fourth service flow to the third functional entity to implement service chain control of the fourth service flow and send the first service flow that has executed service chain control to the access device by the second diversion entity.

[0025] In a possible implementation, the method provided by the embodiment of the present application also includes: the session management network element determines that the diversion entity changes from the first diversion entity to the second diversion entity. The session management network element sends a sixth indication message to the first diversion entity, and the sixth indication message is used to instruct the first diversion entity to send the fifth service flow from the second functional entity to the second diversion entity. The session management network element sends a seventh indication message to the second diversion entity, and the seventh indication message is used to instruct the second diversion entity to send the fifth service flow received by the second diversion entity to the third functional entity corresponding to the second diversion entity. The fifth service flow is a service flow to be controlled by the first service chain. The method can send the fifth service flow to the third functional entity when the diversion entity changes, so that the MEC platform corresponding to the third functional entity performs service chain control on the fifth service flow.

[0026] In a possible implementation manner, the routing rule is further used to instruct the first traffic distribution entity to send a sixth service flow to the access device or the second functional entity, where the sixth service flow is a service flow that does not require service chain control.

[0027] In a possible implementation manner, the routing rule includes description information of the sixth service flow and information of an access device or information of a second functional entity associated with the description information of the sixth service flow.

[0028] In a second aspect, an embodiment of the present application provides a method for transmitting a service flow, including: in a session management process of a session, a first shunt entity receives a routing rule from a session management network element, the routing rule is used to instruct the first shunt entity to send a first service flow to a first functional entity, and / or, to send a second service flow to a second functional entity or an access device, the first service flow is a service flow to be controlled by a first service chain, and the second service flow is a service flow that has been controlled by the first service chain. The first shunt entity transmits the target service flow received by the first shunt entity according to the routing rule.

[0029] In a possible implementation, the routing rule includes: description information of a first service flow and information of a first functional entity associated with the description information of the first service flow, and / or description information of a second service flow and information of a second functional entity or access device associated with the description information of the second service flow. The description information includes source information of the first service flow or the second service flow.

[0030] In a possible implementation, the first shunt entity transmits the target service flow received by the first shunt entity according to the routing rule, including: the description information of the target service flow is the same as the description information of the first service flow, and the first shunt entity sends the target service flow to the first functional entity. And / or, the description information of the target service flow is the same as the description information of the second service flow, and the first shunt entity sends the target service flow to the second functional entity or the access device.

[0031] In one possible implementation, the routing rules are used to instruct the first diversion entity to send a first service flow from a second dedicated tunnel to a first functional entity, and / or to instruct the first diversion entity to send a second service flow from the first dedicated tunnel to a second functional entity; wherein the second dedicated tunnel is located between the first diversion entity and the second functional entity, and the first dedicated tunnel is located between the first diversion entity and the first functional entity.

[0032] In one possible implementation, the first diversion entity transmits the target business flow received by the first diversion entity according to the routing rules, including: the target business flow originates from the second dedicated tunnel, and the first diversion entity sends the target business flow to the first functional entity; or, the target business flow originates from the first dedicated tunnel, and the first diversion entity sends the target business flow to the second functional entity.

[0033] In a possible implementation, the method provided in the embodiment of the present application further includes: the first diversion entity receives first indication information from the session management network element for indicating the first diversion entity to allocate one or more of the first dedicated tunnel information and the second dedicated tunnel information. The first dedicated tunnel information is used to establish the first dedicated tunnel. The second dedicated tunnel information is used to establish the second dedicated tunnel. The first diversion entity sends one or more of the first dedicated tunnel information and the second dedicated tunnel information to the session management network element.

[0034] In one possible implementation, the first business flow is associated with a first identifier, and the routing rule is used to instruct the first diversion entity to send the business flow associated with the first identifier to the first functional entity; or, the second business flow is associated with a second identifier, and the routing rule is used to instruct the first diversion entity to send the business flow associated with the second identifier to the second functional entity.

[0035] In one possible implementation, the first diversion entity transmits the target business flow received by the first diversion entity according to the routing rules, including: the business flow is associated with the first identifier, and the first diversion entity sends the target business flow to the first functional entity; or, the target business flow is associated with the second identifier, and the first diversion entity sends the target business flow to the second functional entity.

[0036] In a possible implementation manner, the routing rule is further used to instruct the first traffic distribution entity to send a third service flow to the access device or the second functional entity, where the third service flow is a service flow in the session that does not require service chain control.

[0037] In a possible implementation manner, the routing rule includes description information of the third service flow and information of an access device or information of a second functional entity associated with the description information of the third service flow.

[0038] In one possible implementation, the first diversion entity transmits the target service flow received by the first diversion entity according to the routing rules, including: if the description information of the target service flow is the same as the description information of the third service flow, the first diversion entity sends the target service flow to the access device or the second functional entity.

[0039] In a third aspect, an embodiment of the present application provides a method for transmitting a service flow, including: a session management network element obtains one or more of a first routing rule and a second routing rule, wherein the first routing rule is used to instruct a first functional entity to send a second service flow to a second functional entity through a dedicated tunnel between the first functional entity and the second functional entity. The second routing rule is used to instruct the second functional entity to send a first service flow to the first functional entity through a dedicated tunnel; wherein the first service flow is a service flow to be controlled by a first service chain, and the second service flow is a service flow that has been controlled by the first service chain; the session management network element sends the first routing rule to the first functional entity; and / or the session management network element sends the second routing rule to the second functional entity.

[0040] In a possible implementation, the method provided in the embodiment of the present application further includes: the session management network element obtains information for establishing a dedicated tunnel. The session management network element sends the information of the dedicated tunnel to the first functional entity or the second functional entity.

[0041] In a possible implementation, before the session management network element obtains the information for establishing the dedicated tunnel, the method provided in the embodiment of the present application further includes: the session management network element sends, to the first functional entity, first indication information for instructing the first functional entity to allocate information for establishing the dedicated tunnel. Or, the session management network element sends, to the second functional entity, second indication information for instructing the second functional entity to allocate information for establishing the dedicated tunnel.

[0042] In a fourth aspect, an embodiment of the present application provides a communication device, which can implement a method for routing a service flow described in the first aspect or any possible implementation of the first aspect, and thus can also achieve the beneficial effects of the first aspect or any possible implementation of the first aspect. The communication device can be a session management network element, or a device that can support a session management network element to implement the first aspect or any possible implementation of the first aspect. For example, a chip used in a session management network element. The communication device can implement the above method through software, hardware, or by executing corresponding software through hardware.

[0043] In one example, an embodiment of the present application provides a communication device, including: a processing unit, used to determine a routing rule, the routing rule is used to instruct a first diversion entity to send a first service flow to a first functional entity, and / or, to send a second service flow to a second functional entity or an access device, the first service flow is a service flow to be controlled by a first service chain, and the second service flow is a service flow that has already executed the first service chain control; during the session management process of a session, the communication unit is used to send the routing rule to the first diversion entity.

[0044] In a possible implementation, the routing rule includes description information of the first service flow and information of a first functional entity associated with the description information of the first service flow, and / or description information of the second service flow and information of a second functional entity or access device associated with the description information of the second service flow. The description information includes source information of the first service flow or the second service flow.

[0045] In one possible implementation, the routing rules include any one or more of the following information: when the description information of the first service flow indicates that the first service flow comes from the access device or the second functional entity, the first diversion entity sends the first service flow to the first functional entity; or, when the description information of the second service flow indicates that the second service flow comes from the first functional entity, the first diversion entity sends the second service flow to the access device or the second functional entity.

[0046] In a possible embodiment, the routing rule is used to instruct the first shunt entity to send the first service flow from the second dedicated tunnel to the first functional entity, and / or to instruct the first shunt entity to send the second service flow from the first dedicated tunnel to the second functional entity. The second dedicated tunnel is located between the first shunt entity and the second functional entity, and the first dedicated tunnel is located between the first shunt entity and the first functional entity.

[0047] In a possible implementation manner, the processing unit is further configured to obtain one or more of first dedicated tunnel information used to establish the first dedicated tunnel and second dedicated tunnel information used to establish the second dedicated tunnel.

[0048] In a possible implementation, the communication unit is further configured to send second dedicated tunnel information and a first forwarding rule to the second functional entity. The first forwarding rule is configured to instruct the second functional entity to transmit the first service flow to the first offload entity through the second dedicated tunnel.

[0049] In a possible implementation, the communication unit is further configured to send first dedicated tunnel information and a second forwarding rule to the first functional entity. The second forwarding rule is configured to instruct the first functional entity to transmit the second service flow to the first offload entity through the first dedicated tunnel.

[0050] In a possible implementation, before the processing unit is used to obtain one or more of the first dedicated tunnel information and the second dedicated tunnel information, the communication unit is further used to send first indication information to the first diversion entity, and the first indication information is used to instruct the first diversion entity to allocate one or more of the first dedicated tunnel information and the second dedicated tunnel information. The processing unit is specifically used to receive one or more of the first dedicated tunnel information and the second dedicated tunnel information from the first diversion entity through the communication unit.

[0051] In one possible implementation, the first business flow is associated with a first identifier, and the routing rule is used to instruct the first diversion entity to send the business flow associated with the first identifier to the first functional entity; or, the second business flow is associated with a second identifier, and the routing rule is used to instruct the first diversion entity to send the business flow associated with the second identifier to the second functional entity.

[0052] In a possible implementation, the communication unit is further used to send third indication information to the second functional entity, where the third indication information is used to instruct the second functional entity to carry the first identifier in a message header of the first service flow.

[0053] In a possible implementation, the communication unit is further used to send fourth indication information to the first functional entity, where the fourth indication information is used to instruct the first functional entity to carry the second identifier in a message header of the second service flow.

[0054] In a possible implementation, the processing unit is further used to determine that the diversion entity changes from the first diversion entity to the second diversion entity. The communication unit is also used to send fifth indication information to the second diversion entity, and the fifth indication information is used to instruct the second diversion entity to perform any one or more of the following steps: sending a third service flow originating from the first diversion entity to the access device; or, sending a fourth service flow originating from the second functional entity to the third functional entity corresponding to the second diversion entity. The third service flow has been executed service chain control or the third service flow is a service flow that has been executed first service chain control. The fourth service flow is a service flow to be executed first service chain control.

[0055] In a possible implementation, the processing unit is further used to determine that the diversion entity changes from the first diversion entity to the second diversion entity; the communication unit is further used to send sixth indication information to the first diversion entity. The sixth indication information is used to instruct the first diversion entity to send a fifth service flow from the second functional entity to the second diversion entity. The session management network element sends seventh indication information to the second diversion entity, and the seventh indication information is used to instruct the second diversion entity to send the fifth service flow received by the second diversion entity to the third functional entity corresponding to the second diversion entity. The fifth service flow is a service flow to be controlled by the first service chain.

[0056] In a possible implementation, the routing rule is further used to instruct the first traffic distribution entity to send a sixth service flow to the access device or the second functional entity, wherein the sixth service flow is a service flow that does not require service chain control.

[0057] In another example, an embodiment of the present application provides a communication device, which may be a session management network element or a chip in a session management network element. The communication device may include: a communication unit and a processing unit. When the communication device is a session management network element, the communication unit may be a communication interface. The communication device may also include a storage unit. The storage unit may be a memory. The storage unit is used to store computer program code, and the computer program code includes instructions. The processing unit may be a processor. The processing unit executes the instructions stored in the storage unit so that the session management network element implements a method for routing a service flow described in the first aspect or any possible implementation of the first aspect. When the communication device is a chip in a session management network element, the processing unit may be a processor, and the communication unit may be collectively referred to as a communication interface. For example, a communication interface may be an input / output interface, a pin or a circuit, etc. The processing unit executes the computer program code stored in the storage unit to enable the session management network element to implement a service flow routing method described in the first aspect or any possible implementation manner of the first aspect. The storage unit may be a storage unit within the chip (for example, a register, a cache, etc.), or may be a storage unit within the session management network element and located outside the chip (for example, a read-only memory, a random access memory, etc.).

[0058] Optionally, the processor, the communication interface and the memory are coupled to each other.

[0059] In a fifth aspect, an embodiment of the present application provides a communication device, which can implement a method for routing a service flow described in the second aspect or any possible implementation of the second aspect, and thus can also achieve the beneficial effects of the second aspect or any possible implementation of the second aspect. The communication device can be a first diversion entity, or a device that can support the first diversion entity to implement the second aspect or any possible implementation of the second aspect. For example, a chip used in the first diversion entity. The communication device can implement the above method through software, hardware, or by executing corresponding software through hardware.

[0060] In one example, an embodiment of the present application provides a communication device, comprising: in a session management process of a session, a communication unit is used to receive a routing rule from a session management network element. The routing rule is used to indicate that a first service flow is sent to a first functional entity, and / or that a second service flow is sent to a second functional entity or an access device, the first service flow is a service flow to be controlled by a first service chain, and the second service flow is a service flow that has been controlled by the first service chain. The communication unit is also used to transmit the target service flow received by the first diversion entity according to the routing rule.

[0061] In a possible implementation, the routing rule includes description information of the first service flow and information of a first functional entity associated with the description information of the first service flow, and / or description information of the second service flow and information of a second functional entity or access device associated with the description information of the second service flow. The description information of the second service flow includes source information of the second service flow. The description information of the first service flow includes the source of the first service flow.

[0062] In one possible implementation, the description information of the target service flow is the same as the description information of the first service flow, and the communication unit is specifically used to send the target service flow to the first functional entity; and / or, the description information of the target service flow is the same as the description information of the second service flow, and the communication unit is specifically used to send the target service flow to the second functional entity or access device.

[0063] In a possible implementation, the routing rule is used to indicate that a first service flow from a second dedicated tunnel is sent to a first functional entity, and / or to indicate that a second service flow from a first dedicated tunnel is sent to a second functional entity. The second dedicated tunnel is located between the device and the second functional entity. The first dedicated tunnel is located between the device and the first functional entity.

[0064] In a possible implementation, the target service flow originates from the second dedicated tunnel, and the communication unit is specifically used to send the target service flow to the first functional entity. Or, the target service flow originates from the first dedicated tunnel, and the communication unit is specifically used to send the target service flow to the second functional entity.

[0065] In a possible implementation, the communication unit is further configured to receive first indication information from a session management network element for instructing the first offload entity to allocate one or more of the first dedicated tunnel information and the second dedicated tunnel information. The first dedicated tunnel information is used to establish the first dedicated tunnel. The second dedicated tunnel information is used to establish the second dedicated tunnel. The communication unit is further configured to send one or more of the first dedicated tunnel information and the second dedicated tunnel information to the session management network element.

[0066] In a possible implementation, the first service flow is associated with the first identifier, and the routing rule is used to indicate that the service flow associated with the first identifier is sent to the first functional entity. Alternatively, the second service flow is associated with the second identifier, and the routing rule is used to indicate that the service flow associated with the second identifier is sent to the second functional entity.

[0067] In a possible implementation, the target service flow is associated with a first identifier, and the communication unit is specifically used to send the target service flow to the first functional entity. Or, the target service flow is associated with a second identifier, and the communication unit is specifically used to send the target service flow to the second functional entity.

[0068] As another example, an embodiment of the present application provides a communication device, which may be a first diversion entity or a chip within the first diversion entity. The communication device may include: a communication unit and a processing unit. When the communication device is the first diversion entity, the communication unit may be a communication interface. The communication device may also include a storage unit. The storage unit may be a memory. The storage unit is used to store computer program code, and the computer program code includes instructions. The processing unit may be a processor. The processing unit executes the instructions stored in the storage unit so that the first diversion entity implements a method for routing a service flow described in the second aspect or any possible implementation of the second aspect. When the communication device is a chip within the first diversion entity, the processing unit may be a processor, and the communication unit may be collectively referred to as: a communication interface. For example, a communication interface may be an input / output interface, a pin or a circuit, etc. The processing unit executes the computer program code stored in the storage unit so that the first diversion entity implements a method for routing a service flow described in the second aspect or any possible implementation of the second aspect. The storage unit can be a storage unit within the chip (for example, a register, a cache, etc.) or a storage unit within the first diversion entity that is located outside the chip (for example, a read-only memory, a random access memory, etc.).

[0069] Optionally, the processor, the communication interface and the memory are coupled to each other.

[0070] In a sixth aspect, an embodiment of the present application provides a communication device, which can implement a method for routing a service flow described in the third aspect or any possible implementation of the third aspect, and thus can also achieve the beneficial effects of the third aspect or any possible implementation of the third aspect. The communication device can be a session management network element, or can be a device that can support a session management network element to implement the third aspect or any possible implementation of the third aspect. For example, a chip used in a session management network element. The communication device can implement the above method through software, hardware, or by executing corresponding software through hardware.

[0071] As an example, an embodiment of the present application provides a communication device, including: a processing unit, used to obtain one or more of a first routing rule and a second routing rule. The first routing rule is used to instruct the first functional entity to send a second service flow to the second functional entity through a dedicated tunnel between the first functional entity and the second functional entity. The second routing rule is used to instruct the second functional entity to send a first service flow to the first functional entity through a dedicated tunnel. The first service flow is a service flow to be controlled by a first service chain, and the second service flow is a service flow that has been controlled by the first service chain. A communication unit is used to send the first routing rule to the first functional entity; and / or a communication unit is used to send the second routing rule to the second functional entity.

[0072] In a possible implementation, the processing unit is further configured to obtain information for establishing a dedicated tunnel. The communication unit is further configured to send the information of the dedicated tunnel to the first functional entity or the second functional entity.

[0073] In a possible implementation, the processing unit is further configured to, before acquiring the information for establishing the dedicated tunnel, send to the first functional entity first indication information for instructing the first functional entity to allocate information for establishing the dedicated tunnel. Alternatively, the session management network element sends to the second functional entity second indication information for instructing the second functional entity to allocate information for establishing the dedicated tunnel.

[0074] In another example, an embodiment of the present application provides a communication device, which may be a session management network element or a chip in a session management network element. The communication device may include: a communication unit and a processing unit. When the communication device is a session management network element, the communication unit may be a communication interface. The communication device may also include a storage unit. The storage unit may be a memory. The storage unit is used to store computer program code, and the computer program code includes instructions. The processing unit may be a processor. The processing unit executes the instructions stored in the storage unit so that the session management network element implements a method for routing a service flow described in the third aspect or any possible implementation of the third aspect. When the communication device is a chip in a session management network element, the processing unit may be a processor, and the communication unit may be collectively referred to as a communication interface. For example, a communication interface may be an input / output interface, a pin or a circuit, etc. The processing unit executes the computer program code stored in the storage unit to enable the session management network element to implement a service flow routing method described in the third aspect or any possible implementation manner of the third aspect. The storage unit may be a storage unit within the chip (for example, a register, a cache, etc.), or may be a storage unit within the session management network element and located outside the chip (for example, a read-only memory, a random access memory, etc.).

[0075] Optionally, the processor, the communication interface and the memory are coupled to each other.

[0076] In the seventh aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instructions are stored. When the computer program or instructions are executed on a computer, the computer executes the method described in the first aspect or any possible implementation of the first aspect.

[0077] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instructions are stored. When the computer program or instructions are run on a computer, the computer executes the method described in the second aspect or any possible implementation of the second aspect.

[0078] In the ninth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instructions are stored. When the computer program or instructions are run on a computer, the computer executes the method described in the third aspect or any possible implementation of the third aspect.

[0079] In a tenth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in the first aspect or any possible implementation of the first aspect.

[0080] In an eleventh aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in the second aspect or any possible implementation of the second aspect.

[0081] In a twelfth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute a method as described in the third aspect or any possible implementation of the third aspect.

[0082] In a thirteenth aspect, an embodiment of the present application provides a communication device, which includes a processor and a storage medium, wherein the storage medium stores instructions, and when the instructions are executed by the processor, the method described in the first aspect or various possible implementation methods of the first aspect is implemented.

[0083] In a fourteenth aspect, an embodiment of the present application provides a communication device, which includes a processor and a storage medium, wherein the storage medium stores instructions, and when the instructions are executed by the processor, the method described in the second aspect or various possible implementation methods of the second aspect is implemented.

[0084] In a fifteenth aspect, an embodiment of the present application provides a communication device, which includes a processor and a storage medium, wherein the storage medium stores instructions, and when the instructions are executed by the processor, the method described in the third aspect or various possible implementation methods of the third aspect is implemented.

[0085] In the sixteenth aspect, an embodiment of the present application provides a communication device, comprising: at least one processor and a communication interface, at least one processor and the communication interface are interconnected through a line, at least one processor is coupled to a memory, the memory is used to store computer programs or instructions, and at least one processor is used to execute the computer program or instructions in the memory, so that the communication device executes the method described in the first aspect or various possible implementations of the first aspect.

[0086] In the seventeenth aspect, an embodiment of the present application provides a communication device, comprising: at least one processor and a communication interface, at least one processor and the communication interface are interconnected through a line, at least one processor is coupled to a memory, the memory is used to store computer programs or instructions, and at least one processor is used to execute the computer program or instructions in the memory, so that the communication device executes the method described in the second aspect or various possible implementations of the second aspect.

[0087] In the eighteenth aspect, an embodiment of the present application provides a communication device, comprising: at least one processor and a communication interface, at least one processor and the communication interface are interconnected through a line, at least one processor is coupled to a memory, the memory is used to store computer programs or instructions, and at least one processor is used to execute the computer program or instructions in the memory, so that the communication device executes the method described in the third aspect or various possible implementations of the third aspect.

[0088] In a possible implementation, the device described in any one of the sixteenth aspect, the seventeenth aspect, and the eighteenth aspect may also include: a memory.

[0089] In a nineteenth aspect, an embodiment of the present application provides a chip, the chip comprising at least one processor and a communication interface, the communication interface is coupled to the at least one processor, and the at least one processor is used to run a computer program or instruction to implement the method described in the first aspect or various possible implementations of the first aspect. The communication interface is used to communicate with other modules outside the chip.

[0090] In a twentieth aspect, an embodiment of the present application provides a chip, the chip comprising at least one processor and a communication interface, the communication interface is coupled to the at least one processor, and the at least one processor is used to run a computer program or instruction to implement the method described in the second aspect or various possible implementations of the second aspect. The communication interface is used to communicate with other modules outside the chip.

[0091] In a twenty-first aspect, an embodiment of the present application provides a chip, the chip comprising at least one processor and a communication interface, the communication interface is coupled to the at least one processor, and the at least one processor is used to run a computer program or instruction to implement the method described in the third aspect or various possible implementations of the third aspect. The communication interface is used to communicate with other modules outside the chip.

[0092] The chip provided in the embodiment of the present application may also include a memory, and the memory is used to store computer programs or instructions.

[0093] In aspect 22, an embodiment of the present application provides a communication device, which includes one or more modules for implementing the methods of the above-mentioned first aspect, second aspect, and third aspect, and the one or more modules may correspond to the steps of the methods of the above-mentioned first aspect, second aspect, and third aspect.

[0094] In the twenty-third aspect, an embodiment of the present application provides a communication device, comprising: at least one processor, at least one processor coupled to a memory, the memory being used to store computer programs or instructions, and at least one processor being used to execute the computer programs or instructions in the memory, so that the communication device executes the method described in the first aspect or various possible implementations of the first aspect.

[0095] In the twenty-fourth aspect, an embodiment of the present application provides a communication device, comprising: at least one processor, at least one processor coupled to a memory, the memory being used to store computer programs or instructions, and at least one processor being used to execute the computer programs or instructions in the memory, so that the communication device executes the method described in the second aspect or various possible implementations of the second aspect.

[0096] In the twenty-fifth aspect, an embodiment of the present application provides a communication device, comprising: at least one processor, at least one processor coupled to a memory, the memory being used to store computer programs or instructions, and at least one processor being used to execute the computer programs or instructions in the memory, so that the communication device executes the method described in the third aspect or various possible implementations of the third aspect.

[0097] In aspect twenty-six, an embodiment of the present application provides a communication system, which includes: a communication device described in aspect four or various possible implementations of the fourth aspect, and a communication device described in aspect five or various possible implementations of the fifth aspect.

[0098] In an optional implementation manner, the communication system may further include: a first functional entity, a second functional entity and an access device.

[0099] The specific steps executed by each communication device in the communication system can be referred to the description of the corresponding place, which will not be repeated here.

[0100] In the twenty-seventh aspect, an embodiment of the present application provides a communication system, which includes: a communication device described in the sixth aspect or various possible implementations of the sixth aspect.

[0101] In an optional implementation manner, the communication system may further include: a first functional entity, a second functional entity and an access device.

[0102] The specific steps executed by each communication device in the communication system can be referred to the description of the corresponding place, which will not be repeated here.

[0103] The beneficial effects of the second to twenty-seventh aspects of the present application and their various implementations can be referred to the analysis of the beneficial effects of the first aspect and its various implementations, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0104] Figure 1 A schematic diagram of a system architecture for performing service chain control on a service flow in the prior art provided in an embodiment of the present application;

[0105] Figure 2a to Figure 2f A schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0106] Figure 3a to Figure 3b A schematic diagram of a 5G architecture provided in an embodiment of the present application;

[0107] Figure 4 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0108] Figure 5 A schematic diagram of a business flow diversion scenario provided in an embodiment of the present application;

[0109] Figure 6 A flow diagram of a method for routing a service flow provided in an embodiment of the present application Figure 1 ;

[0110] Figure 7 Schematic diagram 2 of a flow chart of a method for routing a service flow provided in an embodiment of the present application;

[0111] Figure 8 Schematic diagram 3 of a flow chart of a method for routing a service flow provided in an embodiment of the present application;

[0112] Figure 9a to Figure 9b An architecture diagram of a traffic diversion entity that changes according to an embodiment of the present application;

[0113] Fig.10A flow diagram of a method for routing a service flow provided in an embodiment of the present application Figure 4 ;

[0114] Figures 11 to 17 A schematic diagram of a specific process of a method for routing a service flow provided in an embodiment of the present application;

[0115] Fig.18 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0116] Fig.19 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;

[0117] Fig. 20 A schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0118] In this application, “of”, “corresponding”, “relevant” and “corresponding” may sometimes be used interchangeably. It should be pointed out that when the distinction is not emphasized, the meanings they intend to express are the same.

[0119] In order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second" and the like are used to distinguish the same items or similar items with substantially the same functions and effects. For example, the first functional entity and the second functional entity are only used to distinguish different functional entities, and do not limit their order. Those skilled in the art can understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not necessarily limit them to be different.

[0120] It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0121] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0122] In the present application, "at least one" means one or more, and "plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0123] The system architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. It is known to those skilled in the art that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems. In the embodiments of the present application, the method provided is applied to an NR system or a 5G network as an example for explanation.

[0124] Before introducing the embodiments of the present application, the following are the relevant terms involved in the present application:

[0125] 1) Service chain control refers to: SF performs corresponding processing on service flows in the MEC platform or DN. For example, one or more of the following processing may be performed: firewall function, video acceleration processing function, and load balancing function.

[0126] 2) Local service chain control refers to the MEC platform corresponding to L-PSA (corresponding to the first functional entity) performing service chain control on the service flow.

[0127] 3) The service flow to be controlled by the first service chain may refer to the service flow that has not been processed by the SF in the MEC platform, or the service flow has not yet executed the local service chain control. However, the service flow may have been processed by the SF in the DN corresponding to the PSA (corresponding to the second functional entity), or may not have been processed by the SF in the DN corresponding to the PSA (corresponding to the second functional entity).

[0128] 4) The service flow that has executed the first service chain control may refer to the service flow that has been processed by the SF in the MEC platform.

[0129] 5) Uplink service flow refers to service flow from the terminal or access device 50 and with the destination address as the central DN. It should be noted that the destination address as the central DN means that the destination address is the address of the application server in the central DN, which corresponds to the service flow and provides the terminal with the corresponding application service.

[0130] 6) Downlink service flow refers to the service flow coming from the central DN and whose destination address is the terminal.

[0131] In order to effectively meet the high bandwidth and low latency requirements required by the rapid development of mobile Internet and Internet of Things and reduce network load, the European Telecommunication Standard Institute (ETSI) proposed mobile edge computing (MEC) technology in 2014. MEC is based on the 5G evolution architecture and is a technology that deeply integrates base stations with Internet services. The 3rd Generation Partnership Project (3GPP) has MEC-related projects in the radio access network (RAN) 3 and service and architecture (SA) 2 subgroups.

[0132] Based on the above description, Figure 2a A communication system to which a method for routing a service flow provided in an embodiment of the present application is applicable is shown. The communication system includes: a session management network element 10, a first diversion entity 20, a first functional entity 30, a second functional entity 40 and an access device 50.

[0133] The access device 50 can communicate with the session management network element 10 through the mobility management network element. The session management network element 10 communicates with the first offload entity 20, the first offload entity 20, the first function entity 30 and the second function entity 40.

[0134] In the embodiment of the present application, the first diversion entity 20 can divert certain service flows to local routes, or decide to divert service flows to remote routes.

[0135] The so-called local routing means that the first diversion entity 20 diverts the service flow to the first functional entity 30, and the first functional entity 30 transmits the service flow to the MEC platform that communicates with the first functional entity 30.

[0136] The so-called remote routing means that the first distribution entity 20 distributes the service flow to the second functional entity 40, and the second functional entity 40 transmits the service flow to a data network (eg, a central data network (centralDN)) that communicates with the second functional entity 30.

[0137] In order to realize the diversion of the above-mentioned service flow, the session management network element 10 can insert the first diversion entity 20 as a diversion point on the user plane path of the session. That is, the network element or entity corresponding to the first diversion entity 20 can be a network element with the function of diverting the service flow of the session. For example, the first diversion entity 20 can be an uplink classifier (ULCL) or a branching point network element (BP).

[0138] In an optional communication system, the communication system may also include: an MEC platform communicating with the first functional entity 30 and a central DN communicating with the second functional entity 40. The MEC platform includes one or more SFs (for example, SF1 and SF2). One or more SFs may be functional network elements deployed by an operator or a third party. SF may perform enhanced processing or filtering on service flows. For example: SF may be a network element with a firewall function, a network element with a video acceleration processing function, a network element with a load balancing function, etc. The central DN includes an application server (AS), and one or more SFs (for example, SF3 and SF4).

[0139] For example, one or more SFs deployed in the central DN may be network elements with load balancing or billing functions. Different SFs may have the same or different functions, which is not limited in the embodiments of the present application.

[0140] like Figure 2a As shown in the middle line 1 (representing uplink service flow 1) and line 2 (representing uplink service flow 2), uplink service flow 1 is a service flow that does not need to perform local service chain control, and uplink service flow 2 is a service flow that needs to perform local service chain control.

[0141] For example, the processing of the uplink service flow 1 by the first diversion entity 20 can be described as follows: the first diversion entity 20 sends the uplink service flow 1 to the second functional entity 40. The first diversion entity 20 sends the uplink service flow 2 to the first functional entity 30. Assume that the downlink service flow 1 does not need to perform local service chain control, and the downlink service flow 2 has performed local service chain control. The processing of the downlink service flow by the first diversion entity 20 can be described as follows: the first diversion entity 20 aggregates the downlink service flow 1 and the downlink service flow 2 into the N3 tunnel (i.e., the tunnel between the first diversion entity 20 and the access device 50) and sends them to the access device 50, which then sends them to the terminal.

[0142] like Figure 2a As shown, it is assumed that the uplink service flow 2 (marked by line 2) is processed by SF1 and SF2 on the MEC platform. The specific processing process is described as follows: the first functional entity 30 sends the uplink service flow 2 to SF1, and SF1 sends it back to the first functional entity 30 after processing. The first functional entity 30 then sends the uplink service flow 2 processed by SF1 to SF2, and SF2 sends it to the first functional entity 30 after processing; or SF1 sends it to SF2 after processing, and SF2 sends it back to the first functional entity 30 after processing the uplink service flow. After that, the first functional entity 30 sends the uplink service flow 2 that has executed the service chain control to the first diversion entity 20. The first diversion entity 20 sends the uplink service flow 2 to the second functional entity 40; or the uplink service flow 2 is sent to the second functional entity 40 after being processed by SF1 and SF2.

[0143] Furthermore, after the uplink service flow 2 is transmitted to the second functional entity 40, remote service chain control is to be performed, and the processing of the uplink service flow 2 in the central DN passes through SF3 and SF4. The processing of the uplink service flow 2 by the second functional entity 40 is similar to the processing of the uplink service flow 2 by the first functional entity 30. For example, the second functional entity 40 sends the uplink service flow 2 to SF3, and SF3 sends it back to the second functional entity 40 after processing. The second functional entity 40 then sends it to SF4, and SF4 sends it back to the second functional entity 40 after processing. The second functional entity 40 then sends it to the AS. Other possible processing processes are not described in detail in this embodiment.

[0144] It should be noted that: Figure 2a This is just an example and does not limit the specific sending method of traffic steering control. For example, in another implementation of traffic steering control, the second functional entity 40 sends the uplink service flow to SF3, which sends the uplink service flow to SF4 after processing, and which sends the uplink service flow to AS after processing.

[0145] In a possible implementation manner, the terminal accesses the communication system through the access device 50 .

[0146] In the embodiment of the present application, the terminals may be distributed throughout the wireless network, and each terminal may be static or mobile.

[0147] like Figure 2b As shown, Figure 2b Another communication system provided by an embodiment of the present application is shown. Figure 2a The communication systems shown differ in that: Figure 2a The first traffic distribution entity 20 and the first functional entity 30 are independently deployed, and Figure 2b The first diversion entity 20 and the first functional entity 30 are deployed in the same device, and the device can be called a combined network element. That is, the combined network element has both the function of diverting business flows and the function of sending business flows to be controlled by the first business chain to be executed to the MEC platform. When the first diversion entity 20 and the first functional entity 30 are located in the same device, the first diversion entity 20 and the first functional entity 30 can be independent modules or units in the combined network element. Alternatively, the function of sending business flows to be controlled by the first business chain to be executed to the MEC platform is integrated in the first diversion entity 20, that is, the first functional entity 30 is integrated in the first diversion entity 20.

[0148] Specifically, the combined network element has the following functions: sending the service flow that complies with rule 1 to the second functional entity 30, and sending the service flow that complies with rule 2 to the MEC platform. As for the specific contents of rule 1 and rule 2, reference can be made to the routing rules configured for the first diversion entity in the following embodiment.

[0149] In one possible embodiment, combining Figure 2a ,like Figure 2c As shown, there is a second dedicated tunnel between the first diversion entity 20 and the second functional entity 40 in the embodiment of the present application. There is a first dedicated tunnel between the first diversion entity 20 and the first functional entity 30. Among them, the second dedicated tunnel is used to transmit the service flow to be controlled by the first service chain. The first dedicated tunnel is used to transmit the service flow that has been controlled by the first service chain. It should be noted that in the embodiment of the present application, only the first dedicated tunnel can be established, only the second dedicated tunnel can be established, or the first dedicated tunnel and the second dedicated tunnel can be established at the same time. Optionally, the first dedicated tunnel is used to transmit the uplink service flow, and the second dedicated tunnel is used to transmit the downlink service flow.

[0150] The dedicated tunnel in the embodiment of the present application may also be referred to as a dedicated connection. The dedicated tunnel may be used to transmit a service flow that has been controlled by the first service chain or a service flow to be controlled by the first service chain. Figure 2a to Figure 2fIn the communication system shown, in addition to the dedicated tunnels mentioned above, other tunnels or other connections may exist between various network elements.

[0151] In one possible embodiment, combining Figure 2b ,like Figure 2d As shown, there is a second dedicated tunnel between the jointly arranged network element and the second functional entity 40 in the embodiment of the present application.

[0152] like Figure 2e or Figure 2f As shown, Figure 2e or Figure 2f Another communication system provided by an embodiment of the present application is shown. Figure 2a-2d The difference is: Figure 2e There is a dedicated tunnel between the second functional entity 40 and the first functional entity 30. The first functional entity 30 can send the service flow that has executed the first service chain control to the second functional entity 40 through the dedicated tunnel. The second functional entity 40 can send the service flow to be executed by the first service chain control to the first functional entity 30 through the dedicated tunnel. Figure 2f The dedicated tunnel is located between the jointly-installed network element and the second functional entity 40 .

[0153] It should be noted that, in the embodiment of the present application, when the first traffic diversion entity 20 and the first functional entity 30 are located in the same device, since the first dedicated tunnel between the first traffic diversion entity 20 and the first functional entity 30 can be omitted, at this time, the second dedicated tunnel between the co-located network element and the second functional entity 40 can be regarded as a dedicated tunnel. In this case, the second dedicated tunnel can be used not only for the second functional entity 40 to send a service flow to be controlled by the first service chain, but also for the co-located network element to send a service flow that has been controlled by the first service chain to the second functional entity 40 on the second dedicated tunnel.

[0154] It should be noted that, in the case where there is a dedicated tunnel between the second functional entity 40 and the first functional entity 30, the first dedicated tunnel and the second dedicated tunnel may or may not exist, which is not limited in the embodiment of the present application.

[0155] In addition, in the embodiments of the present application Figure 2a-2f In the communication system shown, there may also be a third dedicated tunnel and / or a fourth dedicated tunnel between the first diversion entity 20 and the access device 50. The access device 50 may send an uplink service flow to be subject to service chain control to the first diversion entity 20 through the third dedicated tunnel or the existing tunnel between the access device 50 and the first diversion entity 20. The access device 50 may receive a downlink service flow for which service chain control has been executed and sent by the first diversion entity 20 through the fourth dedicated tunnel or the existing tunnel between the first diversion entity 20 and the access device 50.

[0156] Of course, in the case where the access device 50 and the first diversion entity 20 do not have a third dedicated tunnel, the access device 50 can send the service flow to be controlled by the first service chain to the first diversion entity 20 through the existing tunnel between the access device 50 and the first diversion entity 20. In the case where the access device 50 and the first diversion entity 20 do not have a fourth dedicated tunnel, the first diversion entity 20 can send the service flow on which the first service chain control has been executed to the first diversion entity 20 through the existing tunnel between the access device 50 and the first diversion entity 20.

[0157] For example, if the above communication diversion system is applied to a 5G network, Figure 3a or Figure 3b As shown, the network element or entity corresponding to the first diversion entity 20 may be an uplink classifier (UL CL) or a branching point (BP). The network element or entity corresponding to the session management network element 10 may be a session management function (SMF). The network element or entity corresponding to the first functional entity 30 may be a first user plane function (UPF) anchor (achor), which may also be referred to as a local PDU session anchor (L-PSA). The network element or entity corresponding to the second functional entity 40 may be a second user plane function (UPF) anchor (achor), which may also be referred to as a remote PDU session anchor (PSA). The access device 50 may be an access network (AN) device or a radio access network (RAN) device.

[0158] In addition, if Figure 3a or Figure 3bAs shown, the 5G network architecture may also include: access and mobility management function (AMF) network element, policy control function (PCF) network element, application function (AF) network element, data network (DN), authentication server function or authentication server function (AUSF) network element, unified data repository (UDR) ( Figure 3a or Figure 3b ), unified data management (UDM), etc., which are not specifically limited in the embodiments of the present application.

[0159] Among them, Figure 3a As shown, the terminal communicates with the AMF network element through the next generation network (Next generation, N1) interface (referred to as N1). The access device communicates with the AMF network element through the N2 interface (referred to as N2). The access device communicates with the ULCL / BP through the N3 interface (referred to as N3). The ULCL / BP communicates with the second UPF network element and the first UPF network element through the N9 interface. The first UPF network element communicates with the MEC platform through the N6 interface (referred to as N6). The second UPF network element communicates with the DN through the N6 interface (referred to as N6). Any two UPF network elements communicate through the N9 interface (referred to as N9). ULCL / BP communicates with the SMF network element through the N4 interface (referred to as N4). The AMF network element communicates with the SMF network element through the N11 interface (referred to as N11). The AMF network element communicates with the UDM network element through the N8 interface (referred to as N8). The SMF network element communicates with the PCF network element through the N7 interface (referred to as N7). The SMF network element communicates with the UDM network element through the N10 interface (referred to as N10). The AMF network element communicates with the AUSF network element through the N12 interface (referred to as N12). The AMF network element communicates with the NSSF network element through the N22 interface (referred to as N22). The AUSF network element communicates with the UDM network element through the N13 interface (referred to as N13). The UDM network element communicates with the UDR network element. The PCF network element communicates with the UDR network element. ULCL / BP can be implemented through UPF.

[0160] like Figure 3b The architecture based on service-oriented interface in 5G network architecture is shown. Figure 3a The difference is that in Figure 3bThe control plane network elements in 5GC can also interact using service-based interfaces. For example, AMF network elements, AUSF network elements, SMF network elements, UDM network elements, UDR network elements or PCF network elements interact using service-based interfaces. For example, the service-based interface provided by the AMF network element to the outside may be Namf. The service-based interface provided by the SMF network element to the outside may be Nsmf. The service-based interface provided by the UDM network element to the outside may be Nudm. The service-based interface provided by the UDR network element to the outside may be Nudr. The service-based interface provided by the PCF network element to the outside may be Npcf. It should be understood that Figure 3b For the description of the names of various service-oriented interfaces, please refer to the 5G system architecture diagram in the 23501 standard, which will not be repeated here.

[0161] It should be noted that Figure 3a or Figure 3b The interface name between the network elements in the example is just an example. In a specific implementation, the interface name may be other names, and the embodiments of the present application do not specifically limit this.

[0162] It should be noted that Figure 3a or Figure 3b The access device, AF network element, AMF network element, SMF network element, AUSF network element, UDM network element, UPF network element and PCF network element are just names, and the names do not limit the devices themselves. In 5G networks and other future networks, the network elements corresponding to the access devices, AF network elements, AMF network elements, SMF network elements, AUSF network elements, UDM network elements, UPF network elements and PCF network elements may also be other names, and the embodiments of the present application do not make specific limitations on this. For example, the UDM network element may also be replaced by a home subscriber server (HSS) or a user subscription database (USD) or a database entity, etc., which are uniformly explained here and will not be repeated later.

[0163] Figure 3a or Figure 3bThe terminal, (R)AN, UPF and DN are generally referred to as user-layer network function entities. The data traffic of the terminal can be transmitted through the protocol data unit (PDU) session (Session) established between the terminal and the DN, and the transmission will pass through the two network functions (entities) of (R)AN and UPF; while the other parts are called control-layer network functions and entities, which are mainly responsible for functions such as authentication and authorization, registration management, session management, mobility management and policy control, so as to realize reliable and stable transmission of user-layer traffic. The PDU session involved in the embodiments of the present application refers to an association between the UE and a Data Network that provides a PDU connectivity service between the terminal and the data network.

[0164] Figure 3a-Figure 3b This is the network architecture used in the embodiments of the present application. The functions of each part or network element involved in the network architecture in a 5G network are described below as an example.

[0165] like Figure 3a As shown, a session of the terminal has multiple anchor points (PDU session anchor). For example, the first UPF network element and the second UPF network element. For uplink service flow (UL data / traffic), BP / ULCL sends the received uplink service flow to different anchor points according to the forwarding rule; for downlink service flow (DL data / traffic), BP / ULCL sends the downlink service flow to the terminal according to the forwarding rule.

[0166] 1) The terminal may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication functions; it may also include a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a wireless modem, a handheld device (handheld), a laptop computer, a cordless phone or a wireless local loop (WLL) station, a machine type communication (MTC) terminal, a user equipment (UE), a mobile station (MS), a terminal device or a relay user device, etc. Among them, the relay user device may be, for example, a 5G residential gateway (RG). For the convenience of description, in this application, the above-mentioned devices are collectively referred to as terminals.

[0167] It should be understood that the terminals in the embodiments of the present application can be terminals in various vertical industry application fields such as IoT terminal devices, ports, smart factories, railway transportation, logistics, drones, and driverless cars. For example: mobile robots, automated guided vehicles (AGVs), driverless cars, control devices and sensors on trains, control devices and sensors deployed in factories, etc.

[0168] As an example, in the embodiment of the present application, the terminal can also be a wearable device. Wearable devices can also be called wearable smart devices, which are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring. The terminal can also be a sensor device used in factories.

[0169] (2) Access equipment is used to provide network access functions for authorized terminals in a specific area, and can use transmission tunnels of different qualities according to the level of the terminal, business requirements, etc. Access equipment can manage wireless resources, provide access services for terminal devices, and then complete the forwarding of control signals and terminal device data between the terminal device and the core network. Access equipment can also be understood as a base station in a traditional network. For example, it can be responsible for wireless resource management, quality of service (QoS) management, data compression and encryption, etc. on the air interface side.

[0170] An access device may be a device in a wireless network. An access device may also be referred to as a wireless access device or a network device. For example, a radio access network (RAN) node that connects a terminal to a wireless network. At present, some examples of access devices are: the Next Generation Node B (gNB) in the fifth generation (5G) system, a transmission reception point (TRP), an evolved Node B (eNB) in the LTE system, a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a base band unit (BBU), or a wireless fidelity (Wifi) access point (AP), etc. In a network structure, the network device may include a centralized unit (CU) node, a distributed unit (DU) node, or a RAN device including a CU node and a DU node. The access device may also be a wireless backhaul device, an in-vehicle device, a wearable device, a network device in a future 5G network, or a network device in a future evolved PLMN network. In a third generation (3G) system, it is called a NodeB, etc.

[0171] (3) Mobility management network element, which belongs to the core network element, is mainly responsible for signaling processing, such as access control, mobility management, attachment and detachment, and gateway selection. When the mobility management network element provides services for the terminal session, it will provide control plane storage resources for the session to store the session identifier, the SMF network element identifier associated with the session identifier, etc.

[0172] In the 5G communication system, the mobility management network element may be an AMF network element. In future communication systems, the mobility management network element may still be an AMF network element, or may have other names, which are not limited in this application.

[0173] (4) Session management network element, responsible for user plane network element selection, user plane network element redirection, Internet Protocol (IP) address allocation, bearer establishment, modification and release, and QoS control. Session management, terminal Internet Protocol (IP) address allocation and management, selection of endpoints that can manage user plane functions, policy control and charging function interfaces, and downlink data notification.

[0174] In a 5G communication system, the session management network element may be an SMF network element. In future communication systems, the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.

[0175] (5) User plane network elements are responsible for forwarding and receiving user data (e.g., service flows) in the terminal. User data can be received from the data network and transmitted to the terminal through the access device; the user plane network element can also receive user data from the terminal through the access device and forward it to the data network. The transmission resources and scheduling functions of the user plane network element that provide services to the terminal are managed and controlled by the session management network element.

[0176] In a 5G communication system, the user plane network element may be a UPF network element or a UPF module. In future communication systems, the user plane network element may still be a UPF network element or a UPF module, or may have other names, which are not limited in this application.

[0177] (6) The authentication server functional network element mainly provides authentication functions and supports authentication of 3GPP access and Non-3GPP access. For details, please refer to 3GPP TS 33.501.

[0178] In future communication systems, the authentication server function network element may still be an AUSF network element, or it may have other names, which is not limited in this application.

[0179] (7) NEF network element mainly supports the secure interaction between 3GPP network and third-party applications. NEF can safely expose network capabilities and events to third parties to enhance or improve the quality of application services. 3GPP network can also securely obtain relevant data from third parties to enhance the network's intelligent decision-making. At the same time, this network element supports the recovery of structured data from a unified database or the storage of structured data in a unified database.

[0180] (8) UDR network element is mainly responsible for storing structured data, including contract data and policy data, externally exposed structured data and application-related data.

[0181] (9) AF network element mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.

[0182] (10) Network storage element, used to maintain real-time information of all network function services in the network. NRF stores information of deployed network function (NF) components, such as the identification and network address of NF components, the identification of supported network slices, or information of data plane instances. NRF provides services such as registration and discovery of NF components to other NFs.

[0183] In future communication systems, the network storage network element may still be an NRF network element, or may have other names, which are not limited in this application.

[0184] It is understandable that the above-mentioned network elements or functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform).

[0185] (11) Data Network (DN) refers to the operator network that provides data transmission services to terminals, such as IMS (IP Multi-media Service) and the Internet.

[0186] The terminal accesses the data network by establishing a session (PDU session) from the terminal to the RAN to the UPF to the DN.

[0187] like Figure 4 As shown, Figure 4 The structure of the session management network element 10, the first offloading entity 20, the first functional entity 30 and the second functional entity 40 can be referred to in Figure 4 The communication device includes a processor 41, a communication line 44 and at least one communication interface ( Figure 4 The communication interface 43 is used as an example for illustration only).

[0188] Optionally, the communication device may further include a memory 42 .

[0189] The processor 41 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0190] The communication link 44 may include a pathway for transmitting information between the above-mentioned components.

[0191] The communication interface 43 uses any transceiver or other device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0192] The memory 42 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compressed optical disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may be independent and connected to the processor via a communication line 44. The memory may also be integrated with the processor.

[0193] The memory 42 is used to store computer execution instructions for executing the solution of the present application, and the execution is controlled by the processor 41. The processor 41 is used to execute the computer execution instructions stored in the memory 42, thereby realizing a method for routing a service flow provided in the following embodiment of the present application.

[0194] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

[0195] In a specific implementation, as an embodiment, the processor 41 may include one or more CPUs, such as Figure 4 CPU0 and CPU1 in.

[0196] In a specific implementation, as an embodiment, the communication device may include multiple processors, such as Figure 441 and processor 45 in the embodiment of the present invention. Each of these processors may be a single-CPU processor or a multi-CPU processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0197] like Figure 5 As shown in the figure, after the introduction of the MEC platform, ULCL / BP can divert the service flow to L-PSA, which then sends the service flow to the MEC platform, and the SF in the MEC platform performs traffic steering control. However, after the SF in the MEC platform performs traffic steering control on the service flow, how to send the processed service flow to the central DN is a technical problem that needs to be solved urgently. Figure 5 In order to solve the technical problem existing in the method described in the communication system shown in the figure, the session management network element 10 in the embodiment of the present application can configure the routing rules for the ULCL / BP, so that the ULCL / BP can send the service flow from the L-PSA and directed to the PSA described in the routing rules to the PSA according to the routing rules. Similarly, for the downlink service flow, the ULCL / BP sends the service flow from the access device or PSA and directed to the L-PSA to the L-PSA according to the routing rules.

[0198] In the embodiment of the present application, the specific structure of the execution subject of a method for routing a service flow is not particularly limited in the embodiment of the present application, as long as the program that records the code of the method for routing a service flow in the embodiment of the present application can be run to communicate according to the method for routing a service flow in the embodiment of the present application. For example, the execution subject of the method for routing a service flow provided in the embodiment of the present application may be a functional module that can call and execute a program in a session management network element, or a communication device applied to the session management network element, such as a chip. The execution subject of the method for routing a service flow provided in the embodiment of the present application may be a functional module that can call and execute a program in a first diversion entity, or a communication device applied to the first diversion entity, such as a chip. This application does not limit this. The execution subject of the method for routing a service flow provided in the embodiment of the present application may be a functional module that can call and execute a program in a first functional entity, or a communication device applied to the first functional entity, such as a chip. The execution subject of the method for routing a service flow provided in the embodiment of the present application may be a functional module that can call and execute a program in a second functional entity, or a communication device applied to the second functional entity, such as a chip. The following embodiments are described by taking as an example a session management network element, a first functional entity, a first traffic distribution entity, and a second functional entity as the execution subject of a service flow method.

[0199] It should be pointed out that the various embodiments of the present application can learn from or refer to each other. For example, the same or similar steps, method embodiments, device embodiments or system embodiments can refer to each other without limitation.

[0200] Combination Figure 2a to Figure 2d ,like Figure 6 As shown, an embodiment of the present application provides a method for routing a service flow, the method comprising:

[0201] Step 601: The session management network element 10 determines a routing rule. The routing rule is used to instruct the first traffic distribution entity 20 to send the first service flow to the first functional entity 30, and / or to send the second service flow to the second functional entity 40 or the access device 50. The first service flow is a service flow to be controlled by the first service chain, and the second service flow is a service flow that has been controlled by the first service chain. The first service chain control may correspond to the local service chain control.

[0202] It should be understood that the first service flow can represent one or more service flows in a session to be controlled by the first service chain, and the second service flow can represent one or more service flows in a session that have already been controlled by the first service chain, and it does not have an indicative meaning. The first service flow and the second service flow can be the same service flow or different service flows. For example, after the first service flow has completed the service chain control, it is the service flow that has been controlled by the first service chain. The first service flow and the second service flow can be service flows in the same session or in different sessions.

[0203] For example, the first service flow may represent service flow 1 and service flow 2 in the session. Service flow 1 and service flow 2 are both service flows to be controlled by the first service chain. The second service flow may represent service flow 1 and service flow 3 in the session. Service flow 1 and service flow 3 are both service flows that have been controlled by the first service chain.

[0204] It should be noted that in the embodiment of the present application, the first shunt entity 20 has the function of shunt the service flow. For the first shunt entity 20, it may not be necessary to determine whether the service flow has executed the service chain control or has not executed the service chain control. Or it may be determined that the service flow is a service flow to be executed with the first service chain control. Once the service flow received by the first shunt entity 20 meets the routing rules, the first shunt entity 20 can forward the service flow according to the routing rules.

[0205] The first service flow in the embodiment of the present application may be an uplink service flow from a terminal in a certain session, and the destination address of the uplink service flow is the central DN corresponding to the second functional entity 40. Or the first service flow may be a downlink service flow from the central DN corresponding to the second functional entity 40 in a certain session, and the destination address of the downlink service flow may be the terminal. When the first service flow is a downlink service flow from the central DN corresponding to the second functional entity 40 in a certain session, the downlink service flow may be controlled by the SF in the central DN corresponding to the second functional entity 40, but still needs to be controlled by the SF in the MEC platform corresponding to the first functional entity 30. Alternatively, the downlink service flow may not be controlled by the SF corresponding to the second functional entity 40, but may only be controlled by the SF in the MEC platform corresponding to the first functional entity 30. The SF in the central DN may be the same as or different from the SF in the MEC platform. The embodiment of the present application does not limit this.

[0206] The second service flow in the embodiment of the present application can be an uplink service flow in a certain session, or a downlink service flow in a certain session. If the second service flow is a downlink service flow, the downlink service flow may come from the second functional entity 40 or the first functional entity 30, then the routing rule is used to instruct the first shunt entity 20 to send the second service flow to the access device 50. If the second service flow is an uplink service flow, the uplink service flow may come from the access device 50 or the first functional entity 30, then the routing rule is used to instruct the first shunt entity 20 to send the second service flow to the second functional entity 40. As to whether the service flow is an uplink service flow or a downlink service flow, it can be identified in combination with its source address / destination address or source port / destination port number, and the embodiment of the present application does not limit this.

[0207] Step 602: During the session management process of the session, the session management network element 10 sends a routing rule to the first offload entity 20, so that the first offload entity 20 receives the routing rule from the session management network element 10 during the session management process of the session.

[0208] Exemplarily, the session management process may be a session establishment process, a session update (modification) process, or a session deletion process.

[0209] As a possible implementation manner, taking the session management process as a session establishment process as an example, step 602 can be specifically implemented in the following manner: the session management network element 10 sends an N4 session establishment request to the first offload entity 20, and the session establishment request carries a routing rule.

[0210] As another possible implementation manner, taking the session management process as a session establishment or session modification process as an example, step 602 can be specifically implemented in the following manner: the session management network element 10 sends an N4 session modification request to the first offload entity 20, and the session modification request carries a routing rule.

[0211] Of course, the routing rule may also carry a request message newly established in the session management process. Alternatively, the routing rule may also be sent by the session management network element 10 to the first diversion entity 20 in any process before the first diversion entity 20 diverts the first service flow or the second service flow, which is not limited in the embodiment of the present application. Alternatively, the session management network element 10 may send the routing rule to the first diversion entity 20 in other processes in which the session management network element 10 interacts with the first diversion entity 20.

[0212] Step 603: The first offload entity 20 processes the target service flow received by the first offload entity 20 according to the routing rule.

[0213] The embodiment of the present application provides a method for routing a service flow, in which the session management network element determines a routing rule and sends the routing rule to a first diversion entity, so that the first diversion entity can perform corresponding forwarding actions on the service flow that complies with the routing rule according to the routing rule. For example, the first diversion entity can forward the first service flow recorded in the routing rule to the first functional entity. This is because the first service flow is usually a service flow to be controlled by the first service chain, so that the SF in the MEC platform corresponding to the first functional entity can perform the first service chain control on the first service flow. In addition, since the first functional entity is usually deployed at a location close to the terminal, the first service chain control can be performed on the first service flow as early as possible, such as video acceleration, firewall, and load balancing functions, so that the first service flow can be processed as early as possible, such as the firewall function, which can filter out invalid service flows as early as possible. Furthermore, in the embodiment of the present application, the first diversion entity can also send the second service flow recorded in the routing rule to the second functional entity or access device. This is because the second service flow is a service flow that has executed the first service chain control. In this way, the service flow can be sent back to the second functional entity after the first service chain control is executed.

[0214] As a possible specific implementation manner, step 601 in the embodiment of the present application can be implemented in the following manner: the session management network element 10 determines the routing rule according to the policy information.

[0215] The policy information includes description information of the service flow to be controlled by the first service chain and description information of the service flow that has been controlled by the first service chain.

[0216] As another possible embodiment of the present application, the method provided in the embodiment of the present application may further include before step 601: the session management network element 10 obtains policy information (for example, PCC rules).

[0217] In one implementation, the policy information may be configured locally in the session management network element 10 .

[0218] In another implementation mode, the session management network element 10 obtains the policy information from the PCF network element, which is not limited in the embodiment of the present application.

[0219] For the specific manner in which the session management network element 10 obtains the policy information from the PCF network element, reference may be made to the description in steps 604 to 606.

[0220] As another possible embodiment of the present application, Figure 7 As shown, the method provided in the embodiment of the present application may further include, before step 601:

[0221] Step 604: The AF network element sends a first request message to the PCF network element, so that the PCF network element receives the first request message.

[0222] The first request message carries any one or more of the following information corresponding to one or more service flows: description information, terminal identifier, and service chain requirements.

[0223] The service chain requirement is used to indicate that the one or more service flows are service flows to be subject to the first service chain control, that is, the service flows are to be subject to local service chain control. Alternatively, the service chain requirement may also be used to indicate that the one or more service flows do not need to be subject to the first service chain control.

[0224] As a specific implementation, the first request message may be an AF request.

[0225] Step 605: The PCF network element generates PCC rules according to the AF request. The PCC rules include service chain information.

[0226] The service chain information may be a service chain policy identifier, which is an identifier pre-configured on the session management network element 10 and / or the PCF network element. Specifically, the session management network element may obtain the service chain policy corresponding to the identifier through the identifier, such as one or more SFs for executing the first service chain control on the service flow, and the execution order of the one or more SFs.

[0227] Step 606: The PCF network element sends the PCC rules to the session management network element 10, so that the session management network element 10 receives the PCC rules, which facilitates the session management network element 10 to determine routing rules according to the PCC rules.

[0228] In view of the fact that the routing rules in the embodiment of the present application can instruct the first offload entity 20 to send the first service flow to the first functional entity 30 and / or send the second service flow to the second functional entity 40 or the access device 50 in various forms, the following will be introduced respectively:

[0229] Example 1), the routing rule includes the description information of the first service flow and the information of the first functional entity 30 associated with the description information of the first service flow, and / or, the description information of the second service flow and the information of the second functional entity 40 or the access device 50 associated with the description information of the second service flow. The description information includes the source information of the first service flow or the second service flow.

[0230] In the embodiment of the present application, the description information may be referred to as a detection rule, and the functional entity to which the service flow corresponding to the description information is forwarded is referred to as a forwarding action. The forwarding action is used to indicate the processing logic of the service flow that meets the detection rule, that is, forwarding to the access device 50 or the first functional entity 30, or the second functional entity 40.

[0231] It should be noted that the detection rule may also be any one or more of the following: tunnel information, network instance, QoS Flow Identifier (QFI), application identifier, etc. The network instance may specifically be a virtual local area network (VLAN) identifier. In the embodiment of the present application, the service flow description information is recorded as SDF (service data flow) for illustration.

[0232] Exemplarily, the description information may include one or more of the terminal identifier, five-tuple information (e.g., IP five-tuple), triplet information (e.g., IP triplet), tunnel information, application identifier, data network name (DNN), or single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI). For example, the IP five-tuple includes the source IP address, source port number, destination IP address, destination port number, and transport layer protocol.

[0233] Exemplarily, the information of the second functional entity 40 may be an address of the second functional entity 40 , or an identifier of the second functional entity 40 , or a port number of the second functional entity 40 , or one or more combinations thereof.

[0234] Exemplarily, the information of the access device 50 may be an address of the access device 50 , or an identifier of the access device 50 , or a port number of the access device 50 , or one or more combinations thereof.

[0235] Exemplarily, the information of the first functional entity 30 may be an address of the first functional entity 30 , or an identifier of the first functional entity 30 , or a port number of the first functional entity 30 , or one or more combinations thereof.

[0236] Accordingly, step 603 in the embodiment of the present application can be implemented in the following manner: the description information of the target service flow is the same as the description information of the first service flow, and the first diversion entity 20 sends the target service flow to the first functional entity 30. And / or, the description information of the target service flow is the same as the description information of the second service flow, and the first diversion entity 20 sends the target service flow to the second functional entity 40 or the access device 50.

[0237] Considering the direction of the service flow, the description information corresponding to the upstream direction and the downstream direction of a service flow is different. For example, the specific contents of the IP quintuple corresponding to the upstream direction of service flow A and the IP quintuple corresponding to the downstream direction can refer to the description in Table 1.

[0238] For example, assume that the description information of the upstream service flow includes IP quintuple 1, corresponding to source IP address = IP1, source port number = port1, destination IP address = IP2, destination port number = port2, and transport layer protocol = UDP; the description information of the downstream service flow includes IP quintuple 2, corresponding to source IP address = IP2, source port number = port2, destination IP address = IP1, destination port number = port1, and transport layer protocol = UDP. The specific content of the routing rules in the embodiment of the present application is illustrated in the form of a table, as shown in Table 1:

[0239] Table 1 Specific content of routing rules

[0240]

[0241]

[0242] For example, if the target service flow is service flow C, its description information includes: IP quintuple 1, and the message header of the service flow C includes the information of the access device 50, that is, the service flow C originates from the access device 50, then the first diversion entity 20 forwards the service flow C to the first functional entity 30. The description information of the service flow C received by the first diversion entity 20 includes: IP quintuple 2, and the message header of the service flow C includes the information of the third functional entity 40, that is, the service flow C originates from the third functional entity 40, then the first diversion entity 20 forwards the service flow C to the first functional entity 30. Among them, the information of the access device 50 refers to the tunnel information of the first diversion entity 20 corresponding to the information of the access device 50; the information of the third functional entity 40 refers to the tunnel information of the first diversion entity 20 corresponding to the information of the third functional entity 40.

[0243] If the description information of the service flow C includes: IP quintuple 1, and the packet header of the service flow C includes the information of the first functional entity 30, that is, the service flow C originates from the first functional entity 30, then the first functional entity 30 sends the service flow C to the second functional entity 40. The information of the first functional entity 30 refers to the tunnel information of the first traffic distribution entity 20 corresponding to the first functional entity 30.

[0244] If the description information of the service flow C includes: IP quintuple 2, and the packet header of the service flow C includes the information of the first functional entity 30, that is, the service flow C originates from the first functional entity 30, then the first functional entity 30 sends the service flow C to the access device 50. The information of the first functional entity 30 refers to the tunnel information of the first diversion entity corresponding to the first functional entity 30.

[0245] In the embodiment of the present application, the first diversion entity 20 can determine the source of the service flow in the following manner: the first diversion entity 20 can determine the source of the service flow through the tunnel information in the message header of the service flow. For example, if the message header of the second service flow carries the tunnel information of the first diversion entity 20 corresponding to the first functional entity 30, that is, I-UPF tunnel information for L-PSA, the first diversion entity 20 can determine that the second service flow originates from the first functional entity 30. If the message header of the first service flow carries the tunnel information of the first diversion entity 20 corresponding to the second functional entity 40, that is, I-UPF tunnel information for PSA, the first diversion entity 20 can determine that the first service flow originates from the second functional entity 40. Similarly, if the message header of the first service flow carries the tunnel information of the first diversion entity 20 corresponding to the access device 50, that is, I-UPF tunnel information for RAN, the first diversion entity 20 can determine that the first service flow originates from the access device 50.

[0246] As a possible implementation: the routing rule includes any one or more of the following information: when the description information of the first service flow indicates that the first service flow comes from the access device 50 or the second functional entity 40, the first branch entity 20 sends the first service flow to the first functional entity 30. Or, when the description information of the second service flow indicates that the second service flow comes from the first functional entity 30, the first branch entity 20 sends the second service flow to the access device 50 or the second functional entity 40.

[0247] It should be noted that the above example takes the description information including five-tuple information as an example. Of course, in the actual process, the various contents of the description information can be decoupled or combined. For example, the description information may not include five-tuple information or three-tuple information. If the description information in the routing rule is QFI and forwarding action, the first diversion entity 20 can send the service flow carrying the specified QFI to the network element indicated by the forwarding action, that is, for the uplink service flow X and the downlink service flow Y of a certain terminal, if the uplink service flow X corresponds to the specified QFI and originates from the access device 50, the first diversion entity 20 sends the uplink service flow X to the second functional entity 40. If the downlink service flow Y corresponds to the specified QFI and originates from the second functional entity 40, the first diversion entity 20 sends the downlink service flow Y to the first functional entity 30. If the uplink service flow X corresponds to the specified QFI and originates from the first functional entity 30, the first diversion entity 20 sends the uplink service flow X to the second functional entity 40. If the downlink service flow Y corresponds to the specified QFI and originates from the first functional entity 30, the first traffic distribution entity 20 sends the downlink service flow Y to the access device 50. It can be understood that if the description information is a specified QFI, it means that both the downlink service flow and the uplink service flow corresponding to the specified QFI need to perform service chain control.

[0248] For the specific implementation of the description information being other description modes, such as network instance, tunnel information, and application identifier, reference can be made to the example of the description information being the identifier of the terminal, which will not be described in detail here.

[0249] It should be noted that Example 1 can be applied to Figure 2a to Figure 2d The communication system shown in any one of the above. That is, without the first dedicated tunnel and the second dedicated tunnel, for example Figure 2a or Figure 2b In the scenario shown, the session management network element 10 can configure the first offload entity 20 with description information of one or more first service flows forwarded to the first functional entity 30. And / or, the session management network element 10 can configure the first offload entity 20 with description information of one or more second service flows forwarded to the second functional entity 40 or the access device 50. In this case, the first offload entity 20 can send the first service flow to the first functional entity 30 through the remaining tunnels except the first dedicated tunnel between the first offload entity 20 and the first functional entity 30. The first offload entity 20 can send the second service flow to the second functional entity 30 through the remaining tunnels except the second dedicated tunnel between the first offload entity 20 and the second functional entity 40.

[0250] Of course, on the basis of having the first dedicated tunnel and the second dedicated tunnel, for example Figure 2c or Figure 2dIn the scenario shown, the session management network element 10 can still configure the first offload entity 20 with description information of one or more first service flows forwarded to the first functional entity 30. And / or, the session management network element 10 configures the first offload entity 20 with description information of one or more second service flows forwarded to the second functional entity 40 or the access device 50.

[0251] Example 2), combined Figure 2c or Figure 2d The routing rule is used to instruct the first shunt entity 20 to send the first service flow from the second dedicated tunnel to the first functional entity 30, and / or to instruct the first shunt entity 20 to send the second service flow from the first dedicated tunnel to the second functional entity 40. The second dedicated tunnel is located between the first shunt entity 20 and the second functional entity 40. The first dedicated tunnel is located between the first shunt entity 20 and the first functional entity 30. The first dedicated tunnel is used to transmit the service flow that has executed the first service chain control. The second dedicated tunnel is used to transmit the service flow to be executed by the first service chain control.

[0252] Accordingly, step 603 in the embodiment of the present application can be implemented as follows: the target service flow originates from the first dedicated tunnel, and the first diversion entity 20 sends the target service flow to the first functional entity 30. Alternatively, the target service flow originates from the second dedicated tunnel, and the first diversion entity 20 sends the target service flow to the second functional entity 40.

[0253] As a specific implementation, the first traffic distribution entity 20 may determine whether the target service flow originates from the first dedicated tunnel or the second dedicated tunnel according to the tunnel information carried in the packet header of the target service flow.

[0254] For example, if the packet header of the target service flow carries the first dedicated tunnel information, the target service flow originates from the first dedicated tunnel. If the packet header of the target service flow carries the second dedicated tunnel information, the target service flow originates from the second dedicated tunnel.

[0255] It should be noted that, in the embodiment of the present application, the first dedicated tunnel and the second dedicated tunnel may coexist, or one of the two may exist. Figure 2c The scenario shown may have a first dedicated tunnel and a second dedicated tunnel, or may have a first dedicated tunnel but not a second dedicated tunnel, or may have a second dedicated tunnel but not a first dedicated tunnel.

[0256] It should be understood that Example 2 can be applicable to scenarios with a second dedicated tunnel and / or a first dedicated tunnel. In the embodiment of the present application, one or more of the first dedicated tunnel information and the second dedicated tunnel information can be allocated by the session management network element 10. Of course, the first dedicated tunnel information can also be allocated by the UPF network element, that is, the first diversion entity 20 allocates it to the first functional entity 30, and the second dedicated tunnel information can also be allocated by the UPF network element, that is, the first diversion entity 20 allocates it to the second functional entity 40, and the embodiment of the present application does not limit this.

[0257] In the case where the first dedicated tunnel information and / or the second dedicated tunnel information is allocated by the first offloading entity 20, as shown in FIG. Figure 7 As shown, the method provided in the embodiment of the present application may further include before step 601: the session management network element 10 obtains one or more of the first dedicated tunnel information and the second dedicated tunnel information.

[0258] In one implementation manner, the session management network element 10 may autonomously obtain one or more of the first dedicated tunnel information and the second dedicated tunnel information.

[0259] As a possible implementation, the session management network element 10 may determine to obtain one or more of the first dedicated tunnel information and the second dedicated tunnel information according to the PCC rule. For example, in addition to the service flow description information, the PCC rule also includes indication information. The indication information is used to indicate that the first service chain control is performed on a certain service flow in the uplink direction. Or the indication information is used to indicate that the first service chain control is performed on a certain service flow in the downlink direction. Or the indication information indicates that a certain service flow is to perform the first service chain control not only in the uplink direction, but also in the downlink direction.

[0260] Optionally, the indication information in the PCC rule is derived from step 604, that is, the first request message sent by the AF to the PCF also includes indication information. Thus, the session management network element 10 determines to obtain one or more of the first dedicated tunnel information and the second dedicated tunnel information according to the indication information.

[0261] In another manner, the session management network element 10 may obtain one or more of the first dedicated tunnel information and the second dedicated tunnel information from the first offload entity 20. For the implementation manner in which the session management network element 10 obtains one or more of the first dedicated tunnel information and the second dedicated tunnel information from the first offload entity 20, reference may be made to the description in the following steps 607 to 609.

[0262] Step 607: The session management network element 10 sends first indication information to the first diversion entity 20, so that the first diversion entity 20 receives the first indication information from the session management network element 10. The first indication information is used to instruct the first diversion entity 20 to allocate one or more of the first dedicated tunnel information and the second dedicated tunnel information. Alternatively, the first indication information is used to instruct the first diversion entity 20 to establish one or more of the first dedicated tunnel and the second dedicated tunnel, so that the first diversion entity 20 can determine to allocate one or more of the first dedicated tunnel information and the second dedicated tunnel information.

[0263] for Figure 2d In the scenario shown, the first indication information is used to instruct the first offload entity 20 to allocate second dedicated tunnel information, or the first indication information is used to instruct the first offload entity 20 to establish a second dedicated tunnel.

[0264] for Figure 2c In the scenario shown, the first indication information may be used to instruct the first offload entity 20 to allocate the second dedicated tunnel information, or the first indication information may be used to instruct the first offload entity 20 to establish the second dedicated tunnel.

[0265] for Figure 2c In the scenario shown, the first indication information may be used to instruct the first offload entity 20 to allocate first dedicated tunnel information, or the first indication information may be used to instruct the first offload entity 20 to establish a first dedicated tunnel.

[0266] for Figure 2c In the scenario shown, the first indication information may be used to instruct the first offload entity 20 to allocate the first dedicated tunnel information and the second dedicated tunnel information, or the first indication information may be used to instruct the first offload entity 20 to establish the first dedicated tunnel and the second dedicated tunnel.

[0267] Exemplarily, the session management network element 10 may send the first indication information to the first diversion entity 20 during the session management process. Alternatively, the session management network element 10 may send the first indication information to the first diversion entity 20 in other processes that interact with the first diversion entity 20 other than the session management process. For example, taking the session management process as a session establishment process as an example, step 607 may be implemented in the following manner: the session management network element 10 sends an N4 session establishment request to the first diversion entity 20. The N4 session establishment request carries the first indication information. Of course, the N4 session establishment request may also be replaced by an N4 session modification request.

[0268] Step 608 : The first traffic distribution entity 20 sends one or more of the first dedicated tunnel information and the second dedicated tunnel information to the session management network element 10 .

[0269] Exemplarily, the first traffic distribution entity 20 may send one or more of the first dedicated tunnel information and the second dedicated tunnel information to the session management network element 10 in a session management response process or other processes of interacting with the session management network element 10 .

[0270] For example, the first offload entity 20 may send an N4 session establishment response message to the session management network element 10 , where the session establishment response message includes one or more of the first dedicated tunnel information and the second dedicated tunnel information.

[0271] Therefore, as a possible embodiment, Figure 7 As shown, the method provided in the embodiment of the present application further includes, after step 608:

[0272] Step 609 : The session management network element 10 receives one or more of the first dedicated tunnel information and the second dedicated tunnel information from the first offload entity 20 .

[0273] The first dedicated tunnel information is used to establish a first dedicated tunnel, and may specifically be tunnel information of the first offload entity 20 corresponding to the first functional entity 30. The second dedicated tunnel information is used to establish a second dedicated tunnel, and may specifically be tunnel information of the first offload entity 20 corresponding to the second functional entity 40.

[0274] As an implementation, the first dedicated tunnel and the second dedicated tunnel are unidirectional tunnels. The first dedicated tunnel refers to the downlink tunnel between the first functional entity 30 and the first diversion entity 20, that is, when the first functional entity 30 sends a service flow to the first diversion entity 20 through the first dedicated tunnel, the message header of the service flow carries the first dedicated tunnel information. The second dedicated tunnel refers to the downlink tunnel between the second functional entity 40 and the second diversion entity 20, that is, when the second functional entity 40 sends a service flow to the first diversion entity 20 through the second dedicated tunnel, the message header of the service flow carries the second dedicated tunnel information.

[0275] It should be noted that, in the scenario where the second dedicated tunnel and / or the first dedicated tunnel is allocated by the session management network element 10, step 607 and step 608 can be replaced by: the session management network element 10 sends one or more of the first dedicated tunnel information and the second dedicated tunnel information to the first diversion entity 20. The first diversion entity 20 returns a response to the session management network element 10. At this time, step 609 can be omitted.

[0276] In the scenario with the second dedicated tunnel and / or the first dedicated tunnel, the session management network element 10 may also instruct the second functional entity 40 or the first functional entity 30 to send the service flow using the dedicated tunnel. For the specific implementation manner in which the session management network element 10 instructs the second functional entity 40 or the first functional entity 30 to send the service flow using the dedicated tunnel, reference may be made to steps 610 and 611.

[0277] As a possible embodiment, Figure 7 As shown, the method provided in the embodiment of the present application also includes:

[0278] Step 610: The session management network element 10 sends the second dedicated tunnel information and the first forwarding rule to the second functional entity 40, so that the second functional entity 40 receives the second dedicated tunnel information and the first forwarding rule.

[0279] The first forwarding rule is used to instruct the second functional entity 40 to transmit the first service flow to the first traffic distribution entity 20 through the second dedicated tunnel.

[0280] By executing step 610, the second functional entity 40 carries the second dedicated tunnel information in the message header of the service flow to be controlled by the first service chain. In the subsequent service flow transmission process, the first traffic distribution entity 20 can send the service flow carrying the second dedicated tunnel information in the message header to the first functional entity 30.

[0281] Exemplarily, the session management network element 10 may send the second dedicated tunnel information and the first forwarding rule to the second functional entity 40 during the session management process.

[0282] Step 611: The session management network element 10 sends the first dedicated tunnel information and the second forwarding rule to the first functional entity 30, so that the first functional entity 30 receives the first dedicated tunnel information and the second forwarding rule. The second forwarding rule is used to instruct the first functional entity to transmit the second service flow to the first offload entity through the first dedicated tunnel.

[0283] Exemplarily, the session management network element 10 may send the first dedicated tunnel information and the second forwarding rule to the second functional entity 40 during the session management process.

[0284] By executing step 611, the first functional entity 30 carries the first dedicated tunnel information in the message header of the service flow that has executed the first service chain control. In the subsequent service flow transmission process, the first traffic distribution entity 20 can send the service flow carrying the first dedicated tunnel information in the message header to the second functional entity 30.

[0285] It should be noted that in Example 2, when the first functional entity 30 and the first traffic diversion entity 20 are co-located, step 611 can be omitted. At this time, the routing rule is used to instruct the co-located network element to send the uplink service flow received through the traffic steering control to the second functional entity 40, and / or to instruct the co-located network element to send the downlink service flow received from the second dedicated tunnel, that is, the downlink service flow with the second dedicated tunnel information in the packet header to the MEC platform, so that the SF in the MEC platform performs traffic steering control.

[0286] Example 3), the first service flow is associated with the first identifier, and the routing rule is used to instruct the first diversion entity 20 to send the service flow associated with the first identifier to the first functional entity 30. Or, the second service flow is associated with the second identifier, and the routing rule is used to instruct the first diversion entity 20 to send the service flow associated with the second identifier to the second functional entity 40 or the access device 50.

[0287] Exemplarily, the first identifier is used to indicate that the service flow originates from the second functional entity 40 or the access device 50 , that is, the first identifier may indicate that the first service flow originating from the second functional entity 40 or the access device 50 is sent to the first functional entity 30 through the first diversion entity 30 .

[0288] Exemplarily, the second identifier is used to indicate that the service flow originates from the first functional entity 30. That is, the second identifier may indicate that the second service flow originating from the first functional entity 30 is sent to the second functional entity 40 through the first traffic distribution entity 20.

[0289] Specifically, whether the service flow carrying the second identifier is sent to the second functional entity 40 or to the access device 50 can be determined in combination with the description information of the service flow, such as the destination address or the destination port, or whether the service flow is an uplink service flow or a downlink service flow. For example, if the service flow D carries the second identifier, and the service flow D is an uplink service flow or the destination address of the service flow D points to the second functional entity 40, the first diversion entity 20 can send the service flow D to the second functional entity 40. If the service flow D carries the second identifier, and the service flow D is a downlink service flow or the destination address of the service flow D points to the terminal, the first diversion entity 20 can send the service flow D to the access device 50.

[0290] In a possible implementation manner, the second service flow is associated with the second identifier, and the routing rule is used to instruct the first offload entity 20 to send the service flow associated with the second identifier to the second functional entity 40.

[0291] Correspondingly, such as Figure 8As shown, step 603 in the embodiment of the present application can be implemented in the following manner: the target business flow is associated with the first identifier, and the first diversion entity 20 sends the target business flow to the first functional entity 30; or, the target business flow is associated with the second identifier, and the first diversion entity 20 sends the target business flow to the second functional entity 40.

[0292] That is, in Example 3, the session management network element 10 can instruct the first offload entity 20 through the routing rule to send the service flow carrying the first identifier to the first functional entity 30, and to send the service flow carrying the second identifier to the second functional entity 40. That is, for the first offload entity 20, it can regard the service flow carrying the first identifier as the first service flow, and regard the service flow carrying the second identifier as the second service flow.

[0293] When the first diversion entity 20 determines whether to forward the service flow to the first functional entity 30 or the second functional entity 40 based on the first identifier or the second identifier carried in the service flow, the method provided in the embodiment of the present application may further include: the first functional entity 30 carries the first identifier in the message header of the service flow that has executed the first service chain control. The second functional entity 40 carries the second identifier in the message header of the service flow to be controlled by the first service chain.

[0294] In one implementation manner, the first functional entity 30 or the second functional entity 40 may autonomously determine to carry an identifier in a message header of the service flow.

[0295] In another implementation, the session management network element 10 may instruct to carry an identifier in the message header of the service flow. For the specific process of the first functional entity 30 or the second functional entity 40 carrying an identifier in the message header of the service flow, refer to the description in the following steps 612-613.

[0296] As a possible embodiment, Figure 8 As shown, the method provided in the embodiment of the present application may further include, before step 603:

[0297] Step 612: The session management network element 10 sends third indication information to the second functional entity 40, so that the second functional entity 40 receives the third indication information from the session management network element 10. The third indication information is used to instruct the second functional entity 40 to carry the first identifier in the packet header of the first service flow.

[0298] In a possible implementation, the third indication information may be implemented by a forwarding rule. For example, the session management network element 10 sends a forwarding rule to the second functional entity 40, and the forwarding rule is used to instruct the second functional entity 40 to process the message of the first service flow as follows: add a first identifier to the message header.

[0299] Exemplarily, the session management network element 10 may send the third indication information to the second functional entity 40 during the session management process, or send the third indication information to the second functional entity 40 during other interactions with the second functional entity 40 outside the session management process.

[0300] Specifically, for the second functional entity 40, after receiving the third indication information, when the first service flow does not need to perform service chain control in the central DN, the second functional entity 40 carries the first identifier in the message header of the first service flow to be controlled by the first service chain, and sends it to the first diversion entity 20. When the first service flow needs to be controlled by the SF in the central DN, the second functional entity 40 adds the first identifier to the message header of the first service flow that has been controlled by the SF in the central DN and still needs to be controlled by the first service chain, and sends it to the first diversion entity 20. In other words, the second functional entity processes the message of the first service flow to be controlled by the first service chain as follows according to the third indication information in step 612: adding the first identifier to the message header.

[0301] For example, the message header of the service flow may be a General Packet Radio Service Technology Tunnel Protocol-User Plane Message Header (General Packet Radio Service, GPRS) tunnel protocol-user plane, GTP-Uheader).

[0302] For example, take the service flow C to be controlled by the first service chain as an example. Assuming that the uplink service flow of the service flow C is represented by SDF (service data flow) 1 and the downlink service flow is represented by SDF2, the processing logic of the second functional entity 40 for the service flow C is shown in Table 2 or Table 3 below:

[0303] Table 2

[0304]

[0305] Table 3

[0306]

[0307] Step 613: The session management network element 10 sends fourth indication information to the first functional entity 30, so that the first functional entity 30 receives the fourth indication information from the session management network element 10. The fourth indication information is used to instruct the first functional entity 30 to carry the second identifier in the packet header of the second service flow.

[0308] In a possible implementation, the fourth indication information may be implemented by a forwarding rule. For example, the session management network element 10 sends a forwarding rule to the first functional entity 30, and the forwarding rule is used to instruct the first functional entity 30 to process the message of the second service flow as follows: add a second identifier in the message header.

[0309] For example, still taking service flow C as an example, the processing logic of service flow C by the first functional entity 30 is shown in Table 4 below:

[0310] Table 4

[0311]

[0312]

[0313] It should be noted that in Example 3, when the first functional entity 30 and the first diversion entity 20 are co-installed, the first functional entity 30 in step 613 can be replaced by the co-installed network element. At this time, the routing rule can be used to instruct the co-installed network element to send the service flow associated with the first identifier to the MEC platform so that the SF in the MEC platform can execute the first service chain control; and / or the routing rule is used to instruct the co-installed network element to send the service flow that has executed the first service chain control to the second functional entity 40. Among them, how to mark that a certain service flow has been executed by the SF in the MEC platform to execute the first service chain control is not limited in the embodiment of the present application. For example, it can be implemented in the following way: the second functional entity 40 records the description information of the service flow, and when the second functional entity receives the description information of the service flow from the MEC platform again, the second functional entity 40 considers that the service flow is a service flow that has executed the first service chain control.

[0314] In actual process, there may be a scenario where the first offload entity 20 and the first functional entity 30 change, for example, the terminal moves out of the service area of ​​the first offload entity 20. Figure 9a or Figure 9b As shown, the session management network element 10 determines that the diversion entity changes from the first diversion entity 20 to the second diversion entity 60. Among them, the second diversion entity 60 corresponds to the third functional entity 70. The third functional entity 70 corresponds to the MEC platform. Therefore, in this scenario, the downlink service flow can be implemented through the following steps 614 and 615, or, steps 614, 616, and 617 to perform the first service chain control.

[0315] Combination Figure 9a ,like Figure 7 or Figure 8 As shown, as another embodiment of the present application, the method provided in the embodiment of the present application may also include:

[0316] Step 614 : The session management network element 10 determines that the traffic diversion entity is changed from the first traffic diversion entity 20 to the second traffic diversion entity 60 .

[0317] For example, the session management network element 10 determines to change the offload entity from the first offload entity 20 to the second offload entity 60 according to the location of the terminal. In other words, the session management network element 10 determines that the terminal has moved out of the service area of ​​the first offload entity 20.

[0318] Step 615: The session management network element 10 sends fifth indication information to the second offload entity 60, so that the second offload entity 60 receives the fifth indication information. The fifth indication information is used to instruct the second offload entity 60 to perform any one or more of the following steps:

[0319] Send the third service flow from the first offload entity 20 to the access device 50; or send the fourth service flow from the second function entity 40 to the third function entity 70 corresponding to the second offload entity 60. The third service flow is a service flow that has been controlled by the first service chain. The fourth service flow is a service flow to be controlled by the first service chain.

[0320] Furthermore, the fifth indication information is also used to instruct the second offload entity 60 not to send the third service flow originating from the first offload entity 20 to the third functional entity 70 .

[0321] In a possible implementation, the fifth indication information may specifically be a forwarding rule. That is, the session management network element 10 sends a forwarding rule to the second diversion entity 60, where the forwarding rule is used to instruct the second diversion entity 60 to send the third service flow from the first diversion entity 20 to the access device 50; and / or, to send the fourth service flow from the second functional entity 40 to the third functional entity 70.

[0322] Correspondingly, after receiving the fifth indication information, the second offload entity 60 may determine to send the third service flow to the access device 50 , or send the fourth service flow to the third function entity 70 corresponding to the second offload entity 50 .

[0323] Specifically, the fifth indication information can be implemented through a forwarding rule. For example, the session management network element 10 sends a forwarding rule to the second diversion entity 60, and the forwarding rule includes the description information of the third service flow and the information of the access device 50 corresponding to the description information of the third service flow, and / or includes the description information of the fourth service flow and the information of the third functional entity 70 corresponding to the description information of the fourth service flow.

[0324] It should be noted that in step 614-step 615, the SF in the MEC platform corresponding to the first functional entity 30 performs the first service chain control on the third service flow. Afterwards, the first functional entity 30 sends the third service flow that has executed the first service chain control to the first diversion entity 20, and the first diversion entity 20 forwards it to the second diversion entity 60. For the third service flow received by the second diversion entity 60 from the first diversion entity 20, the third service flow can be forwarded to the access device 50 according to the fifth indication information in step 615 (that is, the second diversion entity 60 does not need to send the third service flow to the third functional entity 70). For the fourth service flow received by the second diversion entity 60 from the second functional entity 40, the second diversion entity 60 sends the fourth service flow to the third functional entity 70 corresponding to the second diversion entity 60 according to the fifth indication information in step 615, and the third functional entity 70 sends the fourth service flow to the MEC platform corresponding to the third functional entity to perform the first service chain control.

[0325] It should be noted that the method provided in the embodiment of the present application may also include: the session management network element 10 sends indication information to the first offload entity 20, where the indication information is used to instruct the first offload entity 20 to send the third service flow from the second functional entity 40 to the second offload entity 60.

[0326] Further, the session management network element 10 sends, to the second functional entity 40 , indication information for instructing the second functional entity 40 to send the fourth service flow to the second offload entity 60 .

[0327] Combination Figure 9b ,like Figure 7 or Figure 8 As shown, as another embodiment of the present application, the method provided in the embodiment of the present application may further include, after step 614:

[0328] Step 616: The session management network element 10 sends sixth indication information to the first offload entity 20 or the second functional entity 40, so that the first offload entity 20 receives the sixth indication information. The sixth indication information is used to instruct the first offload entity 20 or the second functional entity 40 to send a fifth service flow to the second offload entity 60. The fifth service flow is a service flow to be controlled by the first service chain.

[0329] Step 617: The session management network element 10 sends seventh indication information to the second diversion entity 60, so that the second diversion entity 60 receives the seventh indication information. The seventh indication information is used to instruct the second diversion entity 60 to send the fifth service flow to the third functional entity 70 corresponding to the second diversion entity 60. The fifth service flow comes from the second functional entity 40 or from the first diversion entity 20.

[0330] exist Figure 9a or Figure 9b In the scenario shown, when the offload entity changes from the first offload entity 20 to the second offload entity 60, the session management network element 10 may also send information of the second offload entity 60 to the first offload entity 20 and the second functional entity 40, such as tunnel information of the second offload entity 60, including the tunnel endpoint identifier and address of the second offload entity 40. This part is the prior art, and the embodiments of the present application will not be repeated here.

[0331] In summary, Figure 9a The second shunt entity 60 can send the fourth service flow from the second functional entity 40 to the third functional entity 70 corresponding to the second shunt entity 60, so that the MEC platform corresponding to the third functional entity 70 performs service chain control. After the MEC platform corresponding to the third functional entity 70 performs service chain control on the fourth service flow, the second shunt entity 60 sends the fourth service flow to the access device 50. However, for the third service flow from the first shunt entity 20, the second shunt entity 60 can forward the third service flow to the access device 50. That is, in Figure 9a In the example, for the third service flow, the second traffic distribution entity 60 does not need to forward it to the third functional entity 70. This is because the third service flow has been service chain controlled at the MEC platform corresponding to the first functional entity 30.

[0332] exist Figure 9b In the scenario shown, taking the fifth business flow as business flow a originating from the first diversion entity 20 or business flow b originating from the second functional entity 40 as an example, the second diversion entity 60 sends the fifth business flow to the third functional entity 70, so that the MEC platform corresponding to the third functional entity 70 performs business chain control.

[0333] Figure 9a or Figure 9b It is only an example of the path of the SF that performs service chain control on the MEC platform or central DN and does not have an indicative meaning.

[0334] Combination Figure 2e or Figure 2f ,like Fig.10 As shown, the embodiment of the present application provides a method for transmitting a service flow, including:

[0335] Step 1001: The session management network element 10 determines one or more of a first routing rule and a second routing rule, wherein the first routing rule is used to instruct the first functional entity 30 to send a second service flow to the second functional entity 40 through a dedicated tunnel between the first functional entity 30 and the second functional entity 40. The second routing rule is used to instruct the second functional entity 40 to send a first service flow to the first functional entity 30 through a dedicated tunnel. The first service flow is a service flow to be controlled by a first service chain, and the second service flow is a service flow that has been controlled by the first service chain.

[0336] In addition, the first routing rule is also used to instruct the first functional entity 30 to perform the first service chain control on the first service flow received from the dedicated tunnel. That is, the first routing rule is also used to instruct the first functional entity 30 to send the first service flow from the dedicated tunnel to the MEC platform.

[0337] Specifically, the specific implementation of step 1001 can refer to the specific implementation of step 601, and the embodiments of the present application will not be repeated here.

[0338] Step 1002: The session management network element 10 sends a first routing rule to the first functional entity 30, so that the first functional entity 30 receives the first routing rule.

[0339] Exemplarily, the session management network element 10 may send the first routing rule to the first functional entity 30 during the session management process.

[0340] Step 1003: The first functional entity 30 processes the second service flow according to the first routing rule.

[0341] For example, as a specific implementation of step 1003, the first functional entity 30 carries the dedicated tunnel information of the second functional entity 40 corresponding to the first functional entity 30, that is, specific PSA tunnel information for L-PSA, in the packet header of the second service flow according to the first routing rule.

[0342] For example, take the service flow C to be controlled by the local service chain as an example. Assuming that the uplink service flow of service flow C is represented by SDF1 and the downlink service flow is represented by SDF2, the specific content of the first routing rule can be shown in Table 5:

[0343] Table 5

[0344]

[0345]

[0346] Step 1004: The session management network element 10 sends the second routing rule to the second functional entity 40, so that the second functional entity 40 receives the second routing rule.

[0347] Exemplarily, the session management network element 10 may send the second routing rule to the second functional entity 40 during the session management process.

[0348] Step 1005: The second functional entity 40 processes the first service flow according to the second routing rule.

[0349] For example, as a specific implementation of step 1005, the second functional entity 40 carries the dedicated tunnel information of the first functional entity 30 corresponding to the second functional entity 40, that is, specific L-PSA tunnel information for PSA, in the packet header of the first service flow according to the second routing rule.

[0350] For example, take the service flow C to be controlled by the local service chain as an example. It is assumed that the uplink service flow of the service flow C is represented by SDF1, and the downlink service flow is represented by SDF2.

[0351] Scenario 1: Service flow C does not require central DN for service chain control. The specific content of the second routing rule, that is, the processing of service flow C by the second functional entity 40 according to the second routing rule, can be shown in Table 6.1; the specific content of the first routing rule, that is, the processing of service flow C by the first functional entity 30 according to the first routing rule, can be shown in Table 6.2:

[0352] Table 6.1 Second routing rules

[0353]

[0354] Table 6.2 First routing rules

[0355]

[0356] Scenario 2: Service flow C needs to perform service chain control in the central DN. The specific content of the second routing rule can be as shown in Table 7:

[0357] Table 7

[0358]

[0359] The embodiment of the present application provides a method for routing a service flow, in which the session management network element instructs the first functional entity 30 through the first routing rule to send the service flow (for example, the second service flow) that has executed the first service chain control to the second functional entity 40 through the dedicated tunnel, or the session management network element 10 instructs the second functional entity 40 through the second routing rule to send the first service flow to be controlled by the service chain to the first functional entity 30 using the dedicated tunnel. By using the dedicated tunnel established between the first functional entity 30 and the second functional entity 40, the first functional entity 30 can determine that the first service flow is a service flow to be controlled by the first service chain, and then send the first service flow to the MEC platform to execute the first service chain control. This method can avoid the first diversion entity 20 from transferring the service flow interacting between the first functional entity 30 and the second functional entity 40, and simplify the processing logic of the first diversion entity 20 for the service flow.

[0360] In a possible embodiment, Fig.10 As shown, the method provided in the embodiment of the present application further includes before step 1001:

[0361] Step 1006: The session management network element 10 sends first indication information to the first functional entity 30, so that the first functional entity 30 receives the first indication information from the session management network element 10. The first indication information is used to instruct the first functional entity 30 to allocate information for establishing a dedicated tunnel.

[0362] Exemplarily, the information allocated by the first functional entity 30 for establishing a dedicated tunnel is dedicated tunnel information of the first functional entity 30 corresponding to the second functional entity 40. For example, the dedicated tunnel information of the first functional entity 30 corresponding to the second functional entity 40 may include a tunnel endpoint identifier and an address of the first functional entity 30. For example, the dedicated tunnel information of the first functional entity 30 corresponding to the second functional entity 40 may be specific L-PSA tunnel information for PSA in the following embodiments.

[0363] Step 1007: The session management network element 10 sends second indication information to the second functional entity 40, where the second indication information is used to instruct the second functional entity 40 to allocate information for establishing a dedicated tunnel.

[0364] It should be noted that, either step 1006 or step 1007 can exist, or they can coexist.

[0365] Exemplarily, the information allocated by the second functional entity 40 for establishing a dedicated tunnel is dedicated tunnel information of the second functional entity 40 corresponding to the first functional entity 30. For example, the dedicated tunnel information of the second functional entity 40 corresponding to the first functional entity 30 may include a tunnel endpoint identifier and an address of the second functional entity 40. For example, the tunnel information of the second functional entity 40 corresponding to the first functional entity 30 may be specific PSA tunnel information for L-PSA in the following embodiments.

[0366] Step 1008 : The second functional entity 40 and / or the first functional entity 30 sends information of the dedicated tunnel to the session management network element 10 .

[0367] The dedicated tunnel information includes at least one of the following: dedicated tunnel information of the second functional entity 40 corresponding to the first functional entity 30, and dedicated tunnel information of the first functional entity 30 corresponding to the second functional entity 40. In a possible implementation, the dedicated tunnel information sent by the second functional entity 40 to the session management network element 10 is the dedicated tunnel information of the second functional entity 40 corresponding to the first functional entity 30, and the dedicated tunnel information sent by the first functional entity 30 to the session management network element 10 is the dedicated tunnel information of the first functional entity 30 corresponding to the second functional entity 40.

[0368] It should be noted that there is no execution order between step 1007 and step 1008.

[0369] Step 1009: The session management network element 10 obtains information for establishing a dedicated tunnel.

[0370] Exemplarily, the information used to establish the dedicated tunnel may be information of the dedicated tunnel.

[0371] Step 1010 : The session management network element 10 sends corresponding dedicated tunnel information to the first functional entity 30 and / or the second functional entity 40 .

[0372] In a possible implementation, the corresponding dedicated tunnel information sent by the session management network element 10 to the first functional entity 30 is the dedicated tunnel information of the second functional entity 40 corresponding to the first functional entity 30. The corresponding dedicated tunnel information sent by the session management network element 10 to the second functional entity 40 is the dedicated tunnel information of the first functional entity 30 corresponding to the second functional entity 40.

[0373] It should be noted that when the information used to establish a dedicated tunnel is independently acquired by the session management network element 10, for example, the session management network element 10 allocates the dedicated tunnel information, steps 1006 to 1008 in the embodiment of the present application can be omitted.

[0374] It should be noted that if there is also a third dedicated tunnel between the first functional entity 30 and the access device 50, the first traffic diversion entity 20 can be omitted. For the downlink service flow that has been controlled by the first service chain on the MEC platform, the first functional entity 30 can send it to the access device 50 through the third dedicated tunnel. For the uplink service flow from the access device 50 to be controlled by the first service chain, the access device 50 can also send it to the first functional entity 30 through the third dedicated tunnel. In addition, when combined with Figure 2b describe Fig.10 In the method shown, the first functional entity 30 can be replaced by a combined network element.

[0375] like Fig.11 As shown, Fig.11 Taking the session management network element 10 as the SMF network element, the first offload entity 20 as the I-UPF network element, the first functional entity 30 as the L-PSA, the second functional entity 40 as the PSA, and the access device 50 as the RAN as an example, the specific process of a routing method for a service flow in an embodiment of the present application is described in detail, and the method includes:

[0376] Step 1101: The AF network element sends an AF request to the PCF network element, so that the PCF network element receives the AF request, wherein the AF request carries description information of the service flow, service chain requirements, and terminal identification.

[0377] It can be understood that, before step 1101, the transmission path of the uplink service flow and the downlink service flow of the terminal is: terminal<-RAN<--PSA<-central DN.

[0378] The traffic description information is used to indicate the traffic flow targeted by the AFrequest, and can be specifically represented by an IP quintuple or an IP triplet, etc. The terminal identifier can be the IP of the terminal, the SUPI of the terminal, etc.

[0379] The service chain requirement is used to indicate whether the service flow determined by the description information of the service flow performs local service chain control, or to indicate whether the service flow determined by the description information of the service flow performs service chain control by the SF in the MEC platform corresponding to the L-PSA.

[0380] That is, through step 1101, the AF network element provides the PCF network element with description information of the service flow for which local service chain control is to be performed.

[0381] Step 1102: The PCF network element generates PCC rules according to the AF request. The PCC rules include service chain information. The service chain information may be a service chain policy identifier.

[0382] Step 1103: The PCF network element triggers the session policy modification process and sends PCC rules to the SMF network element.

[0383] In terms of service-oriented interface operations, step 1103 can be described as the PCF network element calling the Npcf_SMPolicyControl_UpdateNotify request service to notify the SMF network element of the PCC rules.

[0384] Step 1104: The SMF network element decides to insert I-UPF and L-PSA into the session according to PCC rules.

[0385] Among them, I-UPF acts as a diversion point, sending part of the terminal's service flow to L-PSA and the other part to PSA.

[0386] Step 1105: The SMF network element selects L-PSA.

[0387] The specific implementation of step 1105 can refer to the existing technology, and this embodiment of the present application will not be elaborated on it.

[0388] Step 1106: The SMF network element sends an N4 session establishment request to the L-PSA, so that the L-PSA receives the N4 session establishment request.

[0389] Step 1107: L-PSA sends an N4 session establishment response to the SMF network element, so that the SMF network element receives the N4 session establishment response, wherein the N4 session establishment response carries L-PSA tunnel information.

[0390] It should be understood that the SMF network element obtains the tunnel information of the L-PSA through steps 1106 and 1107. The SMF network element then sends the L-PSA tunnel information to other user plane network elements, such as the I-UPF, to establish a tunnel connection between the I-UPF and the L-PSA.

[0391] It should be noted that L-PSA tunnel information can also be allocated by SMF network elements. The above only takes L-PSA allocation of L-PSA tunnel information as an example. When L-PSA tunnel information is allocated by SMF network elements, the SMF network element sends L-PSA tunnel information to L-PSA in the N4 session establishment request. Similarly, when tunnel information allocation is involved in subsequent steps, it can be allocated by SMF network elements, L-PSA, I-UPF or PSA.

[0392] Step 1108: The SMF network element sends an N4 session establishment request to the I-UPF network element, so that the I-UPF network element receives the N4 session establishment request, wherein the N4 session establishment request carries RAN tunnel information, PSA tunnel information, and L-PSA tunnel information.

[0393] The purpose of step 1108 in the embodiment of the present application is to establish a user plane connection, that is, to transmit the tunnel information of the two endpoints (i.e., network elements) on the user plane connection to the other end. For example, endpoint A obtains the tunnel information of endpoint B, and endpoint B obtains the tunnel information of endpoint A, so that the user plane connection between endpoint A and endpoint B is successfully established. This establishment process is all implemented through the control plane network element, i.e., the SMF network element.

[0394] Among them, RAN tunnel information is used to establish a tunnel between the I-UPF network element and the RAN. After that, the message header of the service flow sent by the I-UPF network element to the RAN can carry the RAN tunnel information. That is, when the I-UPF receives a service flow to be sent to the RAN, it can send it to the RAN. In other words, the tunnel between the I-UPF and the RAN is successfully established.

[0395] L-PSA tunnel information is used to establish a tunnel between the I-UPF network element and the L-PSA. After that, the message header of the service flow sent by the I-UPF network element to the L-PSA can carry the L-PSA tunnel information. That is, when the I-UPF receives the service flow sent to the L-PSA, it can send it to the L-PSA. In other words, the tunnel between the I-UPF and the L-PSA is successfully established.

[0396] PSA tunnel information is used to establish a tunnel between the I-UPF network element and the PSA. After that, the message header of the service flow sent by the I-UPF network element to the PSA can carry the PSA tunnel information. That is, when the I-UPF receives the service flow sent to the PSA, it can send it to the PSA. In other words, the tunnel between the I-UPF and the PSA is successfully established.

[0397] Step 1109: The I-UPF network element returns an N4 session establishment response to the SMF network element, so that the SMF network element receives the N4 session establishment response. The N4 session establishment response carries I-UPF tunnel information for PSA and I-UPF tunnel information for L-PSA.

[0398] Among them, I-UPF tunnel information for PSA is the tunnel information corresponding to PSA allocated by I-UPF. When the SMF network element sends this information to PSA, that is, when PSA obtains I-UPF tunnel information for PSA, the tunnel between PSA and I-UPF is successfully established. After that, the message header of the service flow sent by PSA to I-UPF can carry I-UPF tunnel information for PSA, that is, I-UPF can determine that the service flow comes from PSA according to the I-UPF tunnel information for PSA carried in the message header of the service flow.

[0399] Among them, I-UPF tunnel information for L-PSA is the tunnel information corresponding to L-PSA allocated by I-UPF. When the SMF network element sends the I-UPF tunnel information for L-PSA to L-PSA, that is, when L-PSA obtains the I-UPF tunnel information for L-PSA, the tunnel between L-PSA and I-UPF is successfully established. After that, the message header of the service flow sent by L-PSA to I-UPF can carry I-UPF tunnel information for L-PSA, that is, I-UPF can determine that the service flow comes from L-PSA based on the I-UPF tunnel information for L-PSA carried in the message header of the service flow.

[0400] Step 1110: The SMF network element sends an N4 session modification request to the I-UPF, so that the I-UPF receives the N4 session modification request. The N4 session modification request carries a routing rule. The routing rule includes a detection rule and a forwarding rule. The detection rule includes a service flow identifier and a service flow source. The forwarding action is used to indicate the processing logic of the service flow that meets the detection rule, that is, forwarding to the RAN, or L-PSA, or PSA.

[0401] Exemplarily, assuming that a certain service flow needs to perform local service chain control or has performed local service chain control, the routing rule is used to instruct the I-UPF to perform any one or more of the following steps on the service flow, wherein the uplink direction of the service flow is referred to as an uplink service flow in this embodiment of the application; the downlink direction is referred to as a downlink service flow in this embodiment of the application:

[0402] - The uplink service flow received from the RAN, that is, the service flow carrying the I-UPF tunnel information for RAN in the packet header, is sent to the L-PSA.

[0403] -The uplink service flow received from L-PSA, that is, the service flow carrying I-UPF tunnelinformation for L-PSA in the message header, is sent to PSA.

[0404] - The downlink service flow received from PSA, that is, the service flow carrying I-UPF tunnel information for PSA in the message header, is sent to L-PSA.

[0405] - The downlink service flow received from L-PSA, that is, the service flow carrying I-UPF tunnelinformation for L-PSA in the packet header, is sent to RAN.

[0406] For example, take service flow C as a service flow to be executed or to be executed for local traffic steering control (uplink service flow is represented by SDF1, and downlink service flow is represented by SDF2) as an example for explanation, then the routing rules are specifically shown in Table 8:

[0407] Table 8

[0408]

[0409] Step 1111. I-UPF sends an N4 session modification response to the SMF network element so that the SMF network element receives the N4 session modification response.

[0410] It should be noted that Fig.11Taking sending routing rules to I-UPF in N4 session modification request as an example, of course, the SMF network element can also send routing rules in N4 session establishment request, that is, carry routing rules in step 1110. If the routing rules are carried in the N4 session establishment request, steps 1110-1111 can be omitted. In other words, step 1110 can be merged with step 1108, and step 1111 can be merged with step 1109.

[0411] Step 1112: The SMF network element sends an N4 session modification request to the PSA, so that the PSA receives the N4 session modification request, wherein the session modification request carries the I-UPF tunnel information for the PSA and the first forwarding rule.

[0412] The first forwarding rule is used to instruct the PSA to send the downlink service flow to be controlled by the local service chain to the I-UPF. Specifically, the PSA carries the I-UPF tunnel information for the PSA in the packet header of the downlink service flow.

[0413] It should be noted that, when the service flow requires the central DN to also perform service chain control, the first forwarding rule is used to instruct the PSA to send the downlink service flow that has been controlled by the central DN to the I-UPF. That is, the downlink service flow from the PSA to be controlled by the local service chain may be controlled by the central DN or not.

[0414] Step 1113, PSA sends an N4 session modification response to the SMF network element, so that the SMF network element receives the N4 session modification response of PSA. The N4 session modification response is used to indicate that the I-UPF tunnel information for PSA and the first forwarding rule have been successfully received, or the N4 session modification response carries response indication information indicating the successful reception of the I-UPF tunnel information for PSA and the first forwarding rule.

[0415] Step 1114: SMF sends an N4 session modification request to L-PSA, so that L-PSA receives the N4 session modification request, wherein the N4 session modification request carries the second forwarding rule and I-UPF tunnel information for L-PSA.

[0416] The second forwarding rule is used to instruct L-PSA to send the uplink service flow that has executed local service chain control or the downlink service flow that has executed local service chain control to I-UPF. That is, L-PSA can carry I-UPF tunnelinformation for L-PSA in the message header of the uplink service flow that has executed local service chain control or the downlink service flow that has executed local service chain control.

[0417] Step 1115. L-PSA sends an N4 session modification response to the SMF network element so that the SMF network element receives the N4 session modification response.

[0418] The N4 session modification response is used to indicate that the I-UPF tunnel information for L-PSA and the second forwarding rule have been successfully received, or the N4 session modification response carries response indication information indicating the successful reception of the I-UPF tunnel information for L-PSA and the second forwarding rule.

[0419] like Fig.12 As shown, Fig.12 Another method for routing a service flow in an embodiment of the present application is shown. Fig.12 The embodiment shown is Fig.11 The difference of the embodiment shown is that the I-UPF and L-PSA are located in the same network element, that is, Fig.11 The I-UPF and L-PSA are replaced by a jointly set network element.

[0420] Step 1201 to step 1205 are the same as the above steps 1101 to step 1105.

[0421] In this embodiment, the I-UPF and L-PSA selected by SM are the same network element, that is, the I-UPF and L-PSA are jointly configured.

[0422] Step 1206: The SMF network element sends an N4 session establishment request to the jointly-established network element so that the jointly-established network element receives the N4 session establishment request.

[0423] Step 1207: The co-located network element sends an N4 session establishment response to the SMF network element, so that the SMF network element receives the N4 session establishment response of the L-PSA. The N4 session management response carries I-UPF tunnel information for PSA and I-UPF tunnel information for RAN.

[0424] Step 1208: The SMF network element sends an N4 session modification request to the co-located network element, so that the co-located network element receives the N4 session modification request. The N4 session modification request carries routing rules. The routing rules include detection rules and forwarding rules. The detection rules include service flow identifiers and service flow sources. The forwarding action is used to indicate the processing logic for service flows that meet the detection rules, i.e., forwarding to the RAN or PSA.

[0425] The forwarding rule is used to instruct the co-located network element to perform one or more of the following steps on the service flow to be or have been subject to local service chain control:

[0426] The received uplink service flow for which local service chain control has been performed is sent to PSA.

[0427] For the uplink service flow received from the RAN (i.e., the message header carries the I-UPF tunnel information for RAN), local service chain control is performed.

[0428] Local service chain control is performed for downlink service flows received from PSA (i.e., the message header carries I-UPF tunnel information for PSA).

[0429] The received downlink service flow for which local service chain control has been executed is sent to the RAN.

[0430] For example, take the service flow C that is to be executed or has executed the local service chain control as an example. Assuming that the uplink service flow of service flow C is represented by SDF1 and the downlink service flow is represented by SDF2, the routing rules are as shown in Table 9.1:

[0431] Table 9.1

[0432]

[0433] It should be noted that in the embodiment of the present application, instructing the co-located network element to perform local service chain control may refer to instructing the co-located network element to send the service flow that needs to perform service chain control to the MEC platform, and the SF in the MEC platform performs local service chain control on the service flow. That is, in the co-located scenario, if the routing rule instructs the co-located network element to perform local service chain control, it can be understood as instructing the co-located network element to send the service flow to the MEC platform so that the SF in the MEC platform can perform local service chain control.

[0434] Step 1209, the combined network element sends an N4 session modification response to the SMF network element, so that the SMF network element receives the N4 session modification response.

[0435] It should be noted that Fig.12Taking sending routing rules to the co-located network element in the N4 session modification request as an example, of course, the SMF network element can also send routing rules to the co-located network element in the N4 session establishment request, that is, in step 1206, the SMF sends routing rules to the co-located network element. If the routing rules are carried in the N4 session establishment request, steps 1208-1209 can be omitted.

[0436] Step 1210 - Step 1211 are the same as step 1112 and step 1113, and the embodiments of the present application will not be repeated here.

[0437] like Fig.13 As shown, Fig.13 Another specific implementation of a service flow routing method provided in an embodiment of the present application is shown, and the method includes:

[0438] Step 1301 to step 1307 are the same as step 1101 to step 1107, and the embodiment of the present application will not be repeated here.

[0439] Step 1308: The SMF network element sends an N4 session establishment request to the I-UPF, so that the I-UPF network element receives the N4 session establishment request, wherein the N4 session establishment request carries the first indication information, RAN tunnel information, PSA tunnel information, and L-PSA tunnel information.

[0440] The first indication information is used to instruct the I-UPF to allocate dedicated tunnel information to establish a first dedicated tunnel between the I-UPF and the L-PSA, and a second dedicated tunnel between the I-UPF and the PSA.

[0441] Other parameter information is known in the prior art, such as RAN tunnel information, PSA tunnel information, and L-PSA tunnel information, and will not be described in detail in the present invention.

[0442] Step 1309: The I-UPF allocates specific I-UPF tunnel information for L-PSA and specific I-UPF tunnel information for PSA according to the first indication information.

[0443] The specific I-UPF tunnel information for PSA is the second dedicated tunnel information. The specific I-UPF tunnel information for L-PSA is the first dedicated tunnel information.

[0444] Step 1310, the I-UPF returns an N4 session establishment response to the SMF network element, so that the SMF network element receives the N4 session establishment response. The N4 session establishment response carries I-UPF tunnel information for L-PSA, I-UPF tunnel information for PSA, I-UPF tunnel information for RAN, and specific I-UPF tunnel information for L-PSA, specific I-UPF tunnel information for PSA.

[0445] It should be noted that, for the scenario where I-UPF and L-PSA are co-installed, for the convenience of description, the present invention refers to the network element after I-UPF and L-PSA are co-installed as I-UPF: I-UPF (i.e., the co-installed network element) allocates specific I-UPF tunnelinformation for PSA, and returns an N4 session establishment response to the SMF network element. At this time, the N4 session establishment response carries I-UPF tunnel information for PSA, I-UPF tunnel information for RAN, and specific I-UPF tunnel information for PSA. Since I-UPF and L-PSA are co-installed, I-UPF may not allocate the following information: I-UPF tunnel information for L-PSA, specific I-UPF tunnel information for L-PSA.

[0446] Step 1311: The SMF network element sends an N4 session modification request to the I-UPF, so that the I-UPF receives the N4 session modification request, wherein the N4 session modification request carries a routing rule.

[0447] The routing rule is used to instruct the I-UPF to perform the following processing on the service flow to be subject to service chain control or the service flow that has already been subject to the first service chain control:

[0448] - The service flow received from the first dedicated tunnel (i.e., the dedicated tunnel between the I-UPF and the L-PSA, i.e., the message header carries specific I-UPF tunnel info for L-PSA) is sent to the PSA.

[0449] - The service flow received from the second dedicated tunnel (i.e., the dedicated tunnel between the I-UPF and the PSA, i.e., the message header carries specific I-UPF tunnel info for PSA) is sent to the L-PSA.

[0450] Step 1312, I-UPF sends an N4 session modification response to the SMF network element so that the SMF network element receives the N4 session modification response.

[0451] It should be noted that Fig.13 Taking sending routing rules to I-UPF in N4 session modification request as an example, of course, the SMF network element can also send routing rules in N4 session establishment request, that is, SMF sends routing rules to I-UPF in step 1310. If the routing rules are carried in the N4 session establishment request, step 1311 can be omitted.

[0452] It should be noted that, for the scenario where the I-UPF and the L-PSA are co-located, the forwarding rule is used to instruct the I-UPF (ie, the co-located network element) to perform one or more of the following steps on the service flow to be executed or having executed the first service chain control:

[0453] -Receive uplink traffic flows that have executed local traffic steering control and send them to PSA.

[0454] -When receiving the downlink service flow from the second dedicated tunnel (i.e., the dedicated tunnel between I-UPF and PSA), that is, when the message header carries specific I-UPF tunnel info for PSA, it is sent to the MEC platform to perform local trafficsteering control.

[0455] For example, taking the service flow C (the uplink service flow is represented by SDF1 and the downlink service flow is represented by SDF2) that is to be executed or has executed local traffic steering control as an example, the I-UPF describes its processing logic as shown in Table 9.2 below:

[0456] Table 9.2

[0457]

[0458] Step 1313: The SMF network element sends an N4 session modification request to the PSA, so that the PSA receives the N4 session modification request, wherein the N4 session modification request carries the first forwarding rule, specific I-UPF tunnel information for PSA, and I-UPF tunnel information for PSA in sequence.

[0459] Among them, the first forwarding rule is used to instruct the PSA to send the downlink service flow to be controlled by the local service chain to the I-UPF through the second dedicated tunnel between the PSA and the I-UPF. Alternatively, it can also be understood that the first forwarding rule is used to instruct the PSA to carry specific I-UPF tunnelinformation for PSA in the message header of the downlink service flow to be controlled by the local service chain.

[0460] For example, take the service flow C that is to be controlled by the local service chain or has been controlled by the local service chain as an example. Assuming that the uplink service flow of the service flow C is represented by SDF1 and the downlink service flow is represented by SDF2, the processing logic of the PSA for the service flow C is as follows:

[0461] When service flow C does not need service chain control in the central DN, the specific content of the first forwarding rule can refer to Table 10:

[0462] Table 10

[0463]

[0464] When service flow C needs to be service chain controlled in the central DN, the specific content of the first forwarding rule can be referred to Table 11:

[0465] Table 11

[0466]

[0467] Step 1314: PSA returns an N4 session modification response to the SMF network element so that the network element receives the N4 session modification response.

[0468] Step 1315: The SMF network element sends an N4 session modification request to the L-PSA, so that the L-PSA receives the N4 session modification request, wherein the N4 session modification request carries the second forwarding rule, I-UPF tunnel information for L-PSA, and specific I-UPF tunnel information for L-PSA.

[0469] The second forwarding rule is used to instruct the L-PSA to send the uplink service flow that has been controlled by the local service chain to the I-UPF through the first dedicated tunnel between the L-PSA and the I-UPF. In other words, the second forwarding rule is used to instruct the L-PSA to carry specific I-UPF tunnelinformation for L-PSA in the message header of the uplink service flow that has been controlled by the local service chain.

[0470] For example, for a service flow C (an uplink service flow is represented by SDF1 and a downlink service flow is represented by SDF2) that is to be or has been subjected to local traffic steering control, the L-PSA describes its processing logic as shown in Table 12 below:

[0471] Table 12

[0472]

[0473] For SDF1 that has performed local service chain control, L-PSA sends SDF1 to I-UPF through the first dedicated tunnel between L-PSA and I-UPF. In other words, the GTP-U header encapsulated by L-PSA for SDF1 contains specific I-UPF tunnel information for L-PSA.

[0474] Step 1316: L-PSA returns an N4 session modification response to the SMF network element so that the SMF network element receives the N4 session modification response.

[0475] It should be noted that, for the scenario where I-UPF and L-PSA are co-installed, step 1315 and step 1316 can be omitted.

[0476] Combination Figure 2e or Figure 2f ,like Fig.14 As shown, Fig.14 Another method for routing a service flow of the present invention is provided. Fig.13 The embodiment shown differs in that Fig.14 In the embodiment shown, a dedicated tunnel is established between the L-PSA and the PSA. Fig.13 In the embodiment shown, the transmission of the service flow between L-PSA and PSA needs to be realized through I-UPF transfer. The method includes:

[0477] Step 1401 to step 1405 are the same as step 1101 to step 1105, and the embodiment of the present application will not be repeated here.

[0478] Step 1406: The SMF network element sends an N4 session establishment request to the L-PSA, so that the L-PSA receives the N4 session establishment request. The N4 session establishment request carries first indication information. The first indication information is used to instruct the L-PSA to allocate dedicated tunnel information, that is, to allocate specific L-PSA tunnel information for PSA. The dedicated tunnel information is used to establish a dedicated tunnel connection between the PSA and the L-PSA.

[0479] Step 1407: L-PSA allocates dedicated tunnel information according to the first indication information.

[0480] Step 1408: L-PSA returns an N4 session establishment response to the SMF network element, so that the SMF network element receives the N4 session establishment response, wherein the N4 session establishment response carries L-PSA tunnel information and specific L-PSA tunnel information for PSA.

[0481] The L-PSA tunnel information is used to establish a tunnel connection between the I-UPF and the L-PSA. This parameter is a prior art and will not be described in detail in the present invention.

[0482] Step 1409: The SMF network element sends an N4 session establishment request to the I-UPF, so that the SMF network element receives the N4 session establishment request, wherein the N4 session establishment request carries RAN tunnel information, PSA tunnel information, and L-PSA tunnel information.

[0483] Step 1410: The I-UPF sends an N4 session establishment response to the SMF network element, so that the SMF network element receives the N4 session establishment response from the I-UPF. The N4 session establishment response carries I-UPF tunnel information for PSA and I-UPF tunnel information for L-PSA.

[0484] Step 1411, the SMF network element sends an N4 session modification request to the PSA, so that the PSA receives the N4 session modification request. The N4 session modification request carries the first forwarding rule, the second indication information, specific L-PSA tunnel information for PSA, and I-UPF tunnel information for PSA.

[0485] The first forwarding rule is used to instruct the PSA to send the downlink service flow to be controlled by the service chain to the L-PSA through a dedicated tunnel, that is, the message header carries specific L-PSA tunnel information for PSA. The second indication information is used to instruct the PSA to allocate dedicated tunnel information, that is, to instruct the PSA to allocate specific PSA tunnel information for L-PSA. The dedicated tunnel information is sent to the L-PSA through the SMF to establish a dedicated tunnel connection between the L-PSA and the PSA.

[0486] In a possible implementation manner, the second indication information and the first forwarding rule have the same parameters, that is, the second indication information is implemented by the first forwarding rule.

[0487] For specific examples, please refer to Table 10, which will not be described in detail here.

[0488] Step 1412: PSA allocates dedicated tunnel information, i.e., specific PSA tunnel information for L-PSA, according to the second indication information, for establishing dedicated tunnel information between L-PSA and PSA. The dedicated tunnel information between L-PSA and PSA is used by PSA to identify that the service flow originates from L-PSA, i.e., the service flow carrying the dedicated tunnel information indicates that the service flow originates from PSA.

[0489] Step 1413, PSA returns an N4 session modification response to the SMF network element, so that the SMF network element receives the N4 session modification response. The N4 session modification response carries the specific PSA tunnel information for L-PSA allocated by PSA according to the second indication information.

[0490] Step 1414: The SMF network element sends an N4 session modification request to the L-PSA, so that the L-PSA receives the N4 session modification request, wherein the N4 session modification request carries the second forwarding rule, specific PSA tunnel information for L-PSA, and I-UPF tunnel information for L-PSA.

[0491] Among them, the second forwarding rule is used to instruct L-PSA to send the uplink service flow that has executed local service chain control to PSA through a dedicated tunnel, that is, the message header of the uplink service flow that has executed local service chain control carries specific PSA tunnel information for L-PSA. In addition, the second forwarding rule can also instruct L-PSA to send the downlink service flow received from the dedicated tunnel to the MEC platform, and the MEC platform performs local service chain control on the downlink service flow, that is, the message header of the downlink service flow carries specific L-PSA tunnel information for PSA. Among them, I-UPF tunnel information for L-PSA is used to establish a tunnel between L-PSA and I-UPF, that is, the message header of the service flow sent by L-PSA to I-UPF carries I-UPF tunnel information for L-PSA.

[0492] Step 1415: PSA returns an N4 session modification response to the SMF network element.

[0493] like Fig.15 As shown, Fig.15 The specific implementation of another service flow routing method provided in an embodiment of the present application is shown, and the method includes:

[0494] Step 1501 - Step 1505 are the same as Step 1101 - Step 1105.

[0495] Step 1506: The SMF network element sends an N4 session establishment request to the I-UPF, so that the I-UPF receives the N4 session establishment request, wherein the N4 session establishment request carries the L-PSA tunnel information.

[0496] Step 1507, I-UPF sends an N4 session establishment response to the SMF network element, so that the SMF network element receives the N4 session establishment response of the I-UPF network element. The N4 session establishment response carries I-UPF tunnel information for PSA, I-UPF tunnel information for L-PSA, and I-UPF tunnel information for RAN. I-UPF tunnel information for PSA is used to establish a tunnel between PSA and I-UPF; I-UPF tunnel information for L-PSA is used to establish a tunnel between L-PSA and I-UPF; I-UPF tunnel information for RAN is used to establish a tunnel between RAN and I-UPF.

[0497] Step 1508: The SMF network element sends an N4 session modification request to the I-UPF, so that the I-UPF receives the N4 session modification request. The N4 session modification request carries a routing rule. The routing rule is used to instruct the I-UPF to perform the following processing on the service flow that is to be executed or has executed local service chain control:

[0498] - For uplink service flows received from RAN, they are sent to L-PSA.

[0499] - For the received uplink service flow with flag, send it to PSA. And / or, this rule can also be described as: for the received service flow with flag from L-PSA, send it to PSA.

[0500] - For the received downlink service flow with flag, send it to L-PSA. And / or, this rule can also be described as: for the received service flow with flag from PSA, send it to L-PSA.

[0501] In addition, the routing rule is also used to instruct the I-UPF to send the received downlink service flow to the RAN.

[0502] The I-UPF determines the source of the service flow based on the following information:

[0503] If the packet header of the service flow carries I-UPF tunnel information for RAN, the uplink service flow originates from the RAN.

[0504] If the packet header of the service flow carries I-UPF tunnel information for L-PSA, the uplink service flow originates from L-PSA.

[0505] If the packet header of the service flow carries I-UPF tunnel information for PSA, the downlink service flow comes from PSA.

[0506] If the packet header of the service flow carries I-UPF tunnel information for L-PSA, the downlink service flow comes from L-PSA.

[0507] For example, assume that the service flow C to be controlled by the first service chain is represented by SDF1 for the uplink service flow and SDF2 for the downlink service flow. The routing rules on the I-UPF are shown in Table 13 below:

[0508] Table 13

[0509]

[0510]

[0511] Step 1509, I-UPF sends an N4 session modification response to the SMF network element so that the SMF network element receives the N4 session modification response.

[0512] It should be noted that if the N4 session establishment request sent by the SMF network element to the I-UPF carries routing rules, that is, carries routing rules in step 1506, then steps 1508 and 1509 can be omitted. Or step 1508 does not carry routing rules.

[0513] Step 1510: The SMF network element sends an N4 session modification request to the PSA, so that the PSA receives the N4 session modification request, wherein the N4 session modification request carries the first forwarding rule and the I-UPF tunnel information for the PSA.

[0514] The first forwarding rule is used to instruct the PSA to perform the following processing on the service flow to be controlled by the local service chain:

[0515] -When the service flow to be controlled by local service chain does not need to be controlled by service chain in the central DN, the PSA adds a flag to the message header of the service flow to be controlled by local service chain and sends it to the I-UPF.

[0516] -When the service flow to be subject to local service chain control needs to be subject to service chain control in the central DN, the PSA adds a flag to the message header of the downlink service flow that has been subject to service chain control by the central DN and is subject to service chain control, and sends it to the I-UPF.

[0517] Step 1511, PSA returns the N4 session modification response to the SMF network element, so that the SMF network element receives the N4 session modification response.

[0518] Step 1512: The SMF network element sends an N4 session modification request to the L-PSA, so that the L-PSA receives the N4 session modification request, wherein the N4 session modification request carries the second forwarding rule and the I-UPF tunnel information for the L-PSA.

[0519] The second forwarding rule is used to instruct the L-PSA to perform the following processing on the service flow that has executed the local service chain control:

[0520] -For the received service flow that has executed local service chain control, add a flag to the message header and send it to I-UPF.

[0521] Step 1513, L-PSA returns the N4 session modification response to the SMF network element, so that the SMF network element receives the N4 session modification response.

[0522] Combination Figure 9a ,like Fig.16 As shown, Fig.16 In the example, the first split entity 20 is a source I-UPF, the second split entity 60 is a target I-UPF, the third functional entity 70 is L-PSA2, and the first functional entity 30 is L-PSA1. The method includes:

[0523] Step 1601, the SMF network element determines to change I-UPF and L-PSA.

[0524] Before step 1601, the terminal has established a session, and the user plane connection 1 corresponding to the session is: terminal→RAN→source I-UPF→L-PSA1→local service chain control→L-PSA1→PSA; the user plane connection 2 is: terminal→RAN→source I-UPF→PSA.

[0525] Step 1602: The SMF network element selects the target L-PSA, namely L-PSA2.

[0526] For example: When the terminal moves, SMF selects L-PSA2 according to the terminal location.

[0527] Step 1603: The SMF network element sends an N4 session establishment request to L-PSA2 so that L-PSA2 receives the N4 session establishment request.

[0528] Step 1604: L-PSA2 sends an N4 session establishment response to the SMF network element, so that the SMF network element receives the N4 session establishment response from L-PSA2, wherein the N4 session establishment response carries L-PSA2 tunnel information.

[0529] Among them, L-PSA2 tunnel information is the tunnel information allocated by L-PSA2.

[0530] Step 1605: The SMF network element selects a target I-UPF and establishes a forwarding tunnel between the target I-UPF and the source I-UPF.

[0531] The specific step 1605 can be implemented in the following manner: the SMF network element sends an N4 session establishment request to the target I-UPF, so that the target I-UPF receives the N4 session establishment request. The N4 session establishment request carries L-PSA2 tunnel information, RAN tunnel information, and PSA tunnel information.

[0532] It should be understood that an uplink tunnel between the target I-UPF and L-PSA2 can be established through the L-PSA2 tunnel information. For example, when the target I-UPF sends a service flow to L-PSA2, such as a downlink service flow or an uplink service flow, the L-PSA2 tunnel information is carried in the message header of the service flow.

[0533] A downlink tunnel between the target I-UPF and the RAN can be established through the RAN tunnel information. For example, when the target I-UPF sends a downlink service flow to the RAN, the RAN tunnel information is carried in the packet header of the downlink service flow.

[0534] The uplink tunnel between the target I-UPF and the PSA can be established through the PSA tunnel information. For example, when the target I-UPF sends an uplink service flow to the PSA, the PSA tunnel information is carried in the packet header of the uplink service flow.

[0535] Afterwards, the target I-UPF returns an N4 session establishment response to the SMF network element, so that the SMF network element receives the N4 session establishment response. The N4 session establishment response carries target I-UPF tunnel information for L-PSA1, target I-UPF tunnel information for source I-UPF, and target I-UPF tunnelinformation for L-PSA2.

[0536] The target I-UPF tunnel information for L-PSA1 is used to establish a downlink tunnel between the target I-UPF and L-PSA1, so that the message header of the service flow sent by L-PSA1 to the target I-UPF can carry the target I-UPF tunnel information for L-PSA1.

[0537] The target I-UPF tunnel information for source I-UPF is used to establish a downlink tunnel between the source I-UPF and the target I-UPF, so that the message header of the service flow sent by the source I-UPF to the target I-UPF can carry the target I-UPF tunnel information for source I-UPF.

[0538] The target I-UPF tunnel information for L-PSA2 is used to establish a downlink tunnel between L-PSA2 and the target I-UPF, so that the message header of the service flow sent by L-PSA2 to the target I-UPF can carry the target I-UPF tunnel information for L-PSA2.

[0539] Step 1606: The SMF network element sends an N4 session modification request to the source I-UPF, so that the source I-UPF receives the N4 session modification request, wherein the N4 session modification request carries target I-UPF tunnel information for source I-UPF.

[0540] Step 1607, source I-UPF returns an N4 session modification response to the SMF network element, so that the SMF network element receives the N4 session modification response.

[0541] Optionally, the N4 session modification response carries source I-UPF tunnel information for target I-UPF. The source I-UPF tunnel information for target I-UPF is used to establish an uplink tunnel between the source I-UPF and the target I-UPF, so that the message header of the service flow sent by the target I-UPF to the source I-UPF can carry the source I-UPF tunnel information for target I-UPF.

[0542] Step 1608: The SMF network element sends an N4 session modification request to the target I-UPF so that the target I-UPF receives the N4 session modification request.

[0543] The N4 session modification request carries source I-UPF tunnel information for target I-UPF and forwarding rules.

[0544] The forwarding rule is used to instruct the target I-UPF to process the service flow to be controlled by the local service chain as follows: when the service flow is received from the source I-UPF (i.e., from the forwarding tunnel between the source I-UPF and the target I-UPF, i.e., the message header carries the target I-UPF tunnel information for the source I-UPF), it does not need to be sent to the L-PSA2, but can be sent to the RAN. The forwarding rule is also used to instruct the target I-UPF to process the service flow to be controlled by the local service chain as follows: when the service flow is received from the PSA (i.e., the message header carries the target I-UPF tunnel information for PSA), send the L-PSA2.

[0545] It should be noted that the forwarding rule can also be understood as a kind of indication information.

[0546] Step 1609, target I-UPF returns an N4 session modification response to the SMF network element.

[0547] Step 1610: The SMF network element updates the downlink user plane information of the PSA. Specifically, the SMF sends an N4 session modification request to the PSA, carrying the target I-UPF tunnel information for the PSA. The PSA returns an N4 session modification response.

[0548] Step 1611: The SMF network element sends an N4 session modification request to L-PSA2, so that L-PSA2 receives the N4 session modification request, wherein the N4 session modification request carries target I-UPF tunnel information for L-PSA2.

[0549] Step 1612: L-PSA2 returns an N4 session modification response to the SMF network element.

[0550] At this point, the transmission path of the downlink service flow to be controlled by the local service chain is:

[0551] (1) Downstream service flow path 1

[0552] PSA→target I-UPF→L-PSA2→traffic steering control→L-PSA2→targetI-UPF→RAN→terminal.

[0553] (2) Downstream service flow path 2

[0554] PSA→source I-UPF→L-PSA1→traffic steering control→L-PSA1→sourceI-UPF→target I-UPF→RAN→terminal.

[0555] In the downlink service flow path 2, the target I-UPF forwards the service flow from the source I-UPF to the RAN. That is, there is no need to send the service chain to the L-PSA2 so that the L-PSA2 can perform local service chain control.

[0556] Step 1613: The SMF network element updates the uplink user plane information of the RAN. Specifically, the SMF network element sends an N2 request to the RAN through the AMF network element, carrying the target I-UPF tunnel information for the RAN. The RAN returns an N2 response.

[0557] In summary, Fig.16Although the I-UPF changes from source I-UPF to target I-UPF, since PSA may still send the downlink service flow C (the downlink service flow C is the service flow to be controlled by the first service chain) to the source I-UPF (for example, downlink service flow path 1), when the source I-UPF receives the downlink service flow C from PSA, it can still send the downlink service flow C to L-PSA1, so that the MEC platform corresponding to L-PSA1 can perform service chain control on the downlink service flow C. After the downlink service flow C has completed the service chain control, the source I-UPF sends the downlink service flow C that has completed the service chain control to the target I-UPF, and then sends it back to the RAN.

[0558] like Fig.17 As shown, Fig.17 Another method for routing a service flow provided by an embodiment of the present application is shown. Fig.16 The difference is that in Fig.17 In the example, the target I-UPF sends the downlink service flow to L-PSA2, so that the MEC corresponding to L-PSA2 can perform traffic steering control on the service flow. The source I-UPF can forward the downlink service flow from PSA to the target I-UPF, and there is no need to forward the downlink service flow from PSA to L-PSA1, so that the MEC corresponding to L-PSA1 can perform traffic steering control on the service flow.

[0559] Step 1701 to step 1704 are the same as step 1601 to step 1604.

[0560] Step 1705: The SMF network element sends an N4 session modification request to the source I-UPF, so that the source I-UPF receives the N4 session modification request, wherein the N4 session modification request carries target I-UPF tunnel information for source I-UPF and forwarding rules.

[0561] Among them, the forwarding rule is used to instruct the source I-UPF to perform the following processing on the service flow to be controlled by the local service chain: when receiving the downlink service flow from the PSA, the source I-UPF sends the downlink service flow to the target I-UPF, that is, the downlink service flow is sent to the target I-UPF through the forwarding tunnel between the source I-UPF and the target I-UPF, that is, the packet header of the downlink service flow is encapsulated with the target I-UPF tunnel information for the source I-UPF.

[0562] It can be understood that the forwarding rules in step 1705 include detection rules and forwarding actions. Among them, the detection rules include description information of the service flow to be controlled by the local service chain. The forwarding action is used to indicate that the service flow determined by the description information of the service flow to be controlled by the local service chain is forwarded to the target I-UPF. For the source I-UPF, it does not need to determine whether the downlink service flow from the PSA is the service flow to be controlled by the local service chain. Once the source I-UPF determines that the downlink service flow from the PSA is received, it forwards the downlink service flow from the PSA to the target I-UPF.

[0563] Step 1706: The source I-UPF returns an N4 session modification response to the SMF network element, so that the SMF network element receives the N4 session modification response. Optionally, the N4 session modification response carries source I-UPF tunnel information for target I-UPF.

[0564] Step 1707: The SMF network element sends an N4 session modification request to the target I-UPF, so that the target I-UPF receives the N4 session modification request, wherein the N4 session modification request carries source I-UPF tunnel infoinformation for target I-UPF and forwarding rules.

[0565] Among them, the forwarding rule is used to instruct the target I-UPF to perform the following processing on the service flow to be controlled by the local service chain: whether the service flow is received from the source I-UPF (that is, from the forwarding tunnel between the source I-UPF and the target I-UPF, that is, the message header carries the target I-UPF tunnel information for the source I-UPF) or from the PSA (that is, the message header carries the target I-UPF tunnel information for the PSA), it is sent to L-PSA2.

[0566] Step 1708, the target I-UPF returns an N4 session modification response to the SMF network element.

[0567] It can be understood that the forwarding rules in step 1707 include detection rules and forwarding actions. Among them, the detection rules include description information of the service flow to be controlled by the local service chain. The forwarding action is used to indicate that the service flow determined by the description information of the service flow to be controlled by the local service chain is forwarded to L-PSA2. For the target I-UPF, it is not necessary to determine whether the downlink service flow from the PSA or the downlink service flow from the source I-UPF is the service flow to be controlled by the local service chain. Once the target I-UPF determines that the description information of the downlink service flow received from the PSA or the source I-UPF exists in the detection rule, the downlink service flow is forwarded to L-PSA2.

[0568] In an embodiment of the present application, when the service flow needs to be controlled not only by the MEC but also by the central DN, how to send service chain information, such as the service flow policy identifier.

[0569] Idea 1: After receiving the service chain policy information from the PCF network element, the SMF network element sends service chain information 1 to the L-PSA and sends service chain information 2 to the PSA. Specifically, the SMF network element decides to send service chain information 1 to the L-PSA and send service chain information 2 to the PSA based on the DNAI and service chain policy information.

[0570] For example, the service chain policy corresponds to the upstream direction of service flow C, that is, SDF1, which is processed by SF1, SF2, SF3, and SF4; the downstream direction is processed by SF3, SF4, SF5, and SF2. SF1 and SF2 are located on the MEC platform, and L-PSA can access the MEC platform. SF3 and SF4 are located in the central DN, and PSA can access the central DN.

[0571] Therefore, the service chain information 1 sent by the SMF network element to L-PSA is (the above behavior is used as an example only): SDF1 needs to be processed by SF1 and SF2; the service chain information 2 sent to PSA is: SDF1 needs to be processed by SF3 and SF4.

[0572] Idea 2: After receiving the service chain policy information from the PCF network element, the SMF network element sends the service chain information to the L-PSA or sends the service chain information to the PSA. That is, the SMF network element sends the corresponding service chain information to the L-PSA and PSA respectively. For example: Taking the above example as an example, in the uplink direction: the SMF network element sends the service chain information to the L-PSA, and the service chain information indicates that SDF1 needs to be processed by SF1, SF2, SF3, and SF4. In the downlink direction: the SMF network element sends the service chain information to the PSA, and the service chain information indicates that SDF2 needs to be processed by SF3, SF4, SF5, and SF2.

[0573] The above mainly introduces the scheme of the embodiment of the present application from the perspective of the interaction between various network elements. It can be understood that in order to realize the above functions, each network element, such as the session management network element, the first diversion entity, the first functional entity and the second functional entity, includes a hardware structure and / or software module corresponding to each function. It should be easy for those skilled in the art to realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed in this document, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0574] The embodiment of the present application can divide the functional units according to the session management network element, the first diversion entity, the first functional entity and the second functional entity according to the above method example. For example, each functional unit can be divided according to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units. It should be noted that the division of units in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0575] Combined with the above Figures 6 to 17 , the method of the embodiment of the present application is explained, and the communication device for executing the above method provided by the embodiment of the present application is described below. Those skilled in the art can understand that the method and the device can be combined and referenced with each other, and the communication device provided by the embodiment of the present application can execute the steps performed by the session management network element and the first diversion entity in the above communication method.

[0576] In the case of an integrated unit, Fig.18 A communication device involved in the above embodiment is shown, and the communication device may include: a communication unit 102 and a processing unit 101.

[0577] In one example, the communication device is a session management network element, or a chip used in a session management network element. In this case, the processing unit 101 is used to support the communication device to execute the above-mentioned embodiment. Figure 6 Executed by the session management element Figure 6 The communication unit 102 is used to support the communication device to perform Figure 6 The sending action performed by the session management network element in step 602.

[0578] In a possible embodiment, the communication unit 102 is further used to support the communication device to execute the action received by the session management network element in step 606 of the above embodiment, the action sent by the session management network element in (step 607, step 610, step 611, step 612, step 613, step 616, step 617), the action received by the session management network element in step 608 or step 609, and step 611. The processing unit 101 is further used to support the communication device to execute the action processed by the session management network element in step 609 and step 614 of the above embodiment.

[0579] In another example, the communication device is a first shunt entity, or a chip used in the first shunt entity. In this case, the communication unit 102 is used to support the communication device to perform the action received by the first shunt entity in step 602 of the above embodiment. The processing unit 101 is used to support the communication device to perform the action processed by the first shunt entity in step 603 of the above embodiment.

[0580] In a possible embodiment, the communication unit 102 is further used for the communication device to execute the action of receiving by the first offload entity in step 607 and the action of receiving by the first offload entity in step 608 in the above embodiment.

[0581] In another example, the communication device is a session management network element, or a chip used in a session management network element. The communication unit 102 is used to support the communication device to perform the action sent by the session management network element in step 1002 of the above embodiment. The processing unit 101 is used to support the communication device to perform the action processed by the session management network element in step 1001 of the above embodiment.

[0582] In a possible embodiment, the communication unit 102 is further used for the communication device to perform the action sent by the session management network element in step 1004, step 1006, step 1007, and step 1010 in the above embodiment. The communication unit 102 is also used to support the communication device to perform the action received by the session management network element in step 1009. Or the processing unit 101 is used to support the communication device to perform the action of autonomously obtaining information for establishing a dedicated tunnel by the session management network element in step 1009.

[0583] In the case of an integrated unit, Fig.19 A possible logical structure diagram of the communication device involved in the above embodiment is shown. The communication device includes: a processing module 112 and a communication module 113. The processing module 112 is used to control and manage the actions of the communication device. For example, the processing module 112 is used to execute the steps of information / data processing in the communication device. The communication module 113 is used to support the communication device to send or receive information / data.

[0584] In a possible embodiment, the communication device may further include a storage module 111 for storing program codes and data of the communication device.

[0585] In one example, the communication device is a session management network element, or a chip used in a session management network element. In this case, the processing module 112 is used to support the communication device to execute the above-mentioned embodiment. Figure 6 Executed by the session management element Figure 6 The communication module 113 is used to support the communication device to perform Figure 6 The sending action performed by the session management network element in step 602.

[0586] In a possible embodiment, the communication module 113 is further used to support the communication device to execute the action received by the session management network element in step 606 of the above embodiment, the action sent by the session management network element in (step 607, step 610, step 611, step 612, step 613, step 616, step 617), the action received by the session management network element in step 608 or step 609, and step 611. The processing module 112 is further used to support the communication device to execute the action processed by the session management network element in step 609 and step 614 of the above embodiment.

[0587] In another example, the communication device is a first shunt entity, or a chip used in the first shunt entity. In this case, the communication module 113 is used to support the communication device to perform the action received by the first shunt entity in step 602 of the above embodiment. The processing module 112 is used to support the communication device to perform the action processed by the first shunt entity in step 603 of the above embodiment.

[0588] In a possible embodiment, the communication module 113 is further used by the communication device to execute the action of receiving by the first offload entity in step 607 and the action of receiving by the first offload entity in step 608 in the above embodiment.

[0589] In another example, the communication device is a session management network element, or a chip used in a session management network element. The communication module 113 is used to support the communication device to perform the action sent by the session management network element in step 1002 of the above embodiment. The processing module 112 is used to support the communication device to perform the action processed by the session management network element in step 1001 of the above embodiment.

[0590] In a possible embodiment, the communication module 113 is also used for the communication device to perform the action sent by the session management network element in step 1004, step 1006, step 1007, and step 1010 in the above embodiment. The communication module 113 is also used to support the communication device to perform the action received by the session management network element in step 1009. Or the processing module 112 is used to support the communication device to perform the action of autonomously obtaining information for establishing a dedicated tunnel by the session management network element in step 1009.

[0591] Among them, the processing module 112 can be a processor or a controller, for example, a central processing unit, a general processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements a computing function, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, etc. The communication module 113 can be a transceiver, a transceiver circuit or a communication interface, etc. The storage module 111 can be a memory.

[0592] When the processing module 112 is the processor 41 or the processor 45, the communication module 113 is the communication interface 43, and the storage module 111 is the memory 42, the communication device involved in the present application can be Figure 4 The communication device shown.

[0593] Fig. 201 is a schematic diagram of the structure of a chip 150 provided in an embodiment of the present application. The chip 150 includes one or more than two (including two) processors 1510 and a communication interface 1530 .

[0594] Optionally, the chip 150 further includes a memory 1540, which may include a read-only memory and a random access memory, and provides operation instructions and data to the processor 1510. A portion of the memory 1540 may also include a non-volatile random access memory (NVRAM).

[0595] In some embodiments, the memory 1540 stores the following elements, execution modules or data structures, or a subset thereof, or an extended set thereof.

[0596] In the embodiment of the present application, the corresponding operation is performed by calling the operation instruction stored in the memory 1540 (the operation instruction may be stored in the operating system).

[0597] In a possible implementation manner, the structures of chips used by the session management network element and the first traffic distribution entity are similar, and different devices may use different chips to implement their respective functions.

[0598] The processor 1510 controls the processing operation of any one of the session management network element and the first traffic distribution entity. The processor 1510 may also be called a central processing unit (CPU).

[0599] The memory 1540 may include a read-only memory and a random access memory, and provides instructions and data to the processor 1510. A portion of the memory 1540 may also include an NVRAM. For example, in an application, the memory 1540, the communication interface 1530, and the memory 1540 are coupled together via a bus system 1520, wherein the bus system 1520 may include a power bus, a control bus, and a status signal bus in addition to a data bus. However, for the sake of clarity, in Fig. 20 Various buses are labeled as bus system 1520.

[0600] The method disclosed in the above embodiment of the present application can be applied to the processor 1510, or implemented by the processor 1510. The processor 1510 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the processor 1510. The above processor 1510 can be a general-purpose processor, a digital signal processor (digital signal processing, DSP), an ASIC, a field-programmable gate array (field-programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to execute, or the hardware and software modules in the decoding processor can be executed. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 1540, and the processor 1510 reads the information in the memory 1540 and completes the steps of the above method in combination with its hardware.

[0601] In one possible implementation, the communication interface 1530 is used to execute Figure 6-Figure 17 The steps of receiving and sending by the session management network element and the first traffic distribution entity in the embodiment shown. The processor 1510 is configured to execute Figure 6-Figure 17 The processing steps of the session management network element and the first traffic distribution entity in the illustrated embodiment.

[0602] The above communication unit may be a communication interface of the device, used to receive signals from other devices. For example, when the device is implemented in a chip, the communication unit is a communication interface of the chip used to receive or send signals from other chips or devices.

[0603] In one aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium, and when the instructions are executed, the following is implemented: Figure 6 -Figure 9, Figure 11-Figure 17 The function of the session management network element in the network.

[0604] In one aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium, and when the instructions are executed, the following is implemented: Fig.10 The function of the session management network element in the network.

[0605] On the other hand, a computer-readable storage medium is provided, in which instructions are stored. When the instructions are executed, the following is achieved: Figure 6-Figure 17 The function of the first diversion entity in.

[0606] In one aspect, a computer program product is provided, wherein the computer program product includes instructions, and when the instructions are executed, the following are implemented: Figure 6-Figure 17 The function of the session management network element in the network.

[0607] In another aspect, a computer program product comprising instructions is provided. The computer program product comprises instructions. When the instructions are executed, the following are implemented: Figure 6-Figure 17 The function of the first diversion entity in.

[0608] In one aspect, a chip is provided, which is applied to a network management network element, and the chip includes at least one processor and a communication interface, wherein the communication interface is coupled to the at least one processor, and the processor is used to run instructions to implement the following Figure 6-Figure 17 The function of the session management network element in the network.

[0609] In another aspect, a chip is provided, which is applied to a Donor node, and includes at least one processor and a communication interface, wherein the communication interface is coupled to the at least one processor, and the processor is used to run instructions to implement the following Figure 6-Figure 17 The function of the first diversion entity in.

[0610] The embodiment of the present application provides a communication system, which includes: a session management network element and a first traffic distribution entity. The session management network element is used to perform Figure 6-Figure 17 Any one of the steps performed by the session management network element, the first offloading entity is used to perform Figure 6-Figure 17 Any one of the steps performed by the first branching entity.

[0611] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device or other programmable device. The computer program or instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instruction may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired or wireless means. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, for example, a floppy disk, a hard disk, a tape; it may also be an optical medium, for example, a digital video disc (DVD); it may also be a semiconductor medium, for example, a solid state drive (SSD).

[0612] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art may understand and implement other changes to the disclosed embodiments by viewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "one" or "an" does not exclude multiple situations. A single processor or other unit may implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0613] Although the present application has been described in conjunction with specific features and embodiments thereof, it is obvious that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely exemplary illustrations of the present application as defined by the appended claims, and are deemed to have covered any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for routing a service flow, characterized in that: include: The session management network element acquires one or more of a first routing rule and a second routing rule, where the first routing rule is used to instruct the first functional entity to send a second service flow to the second functional entity through a dedicated tunnel between the first functional entity and the second functional entity; The second routing rule is used to instruct the second functional entity to send a first service flow to the first functional entity through a dedicated tunnel; wherein the first service flow is a service flow that has not yet been processed by a service function SF network element in a mobile edge computing MEC platform, and the second service flow is a service flow that has been processed by the SF network element in the MEC platform; the first functional entity is used to communicate with the MEC platform, and the second functional entity is used to communicate with a data network; The session management network element sends the first routing rule to the first functional entity; and / or the session management network element sends the second routing rule to the second functional entity.

2. The method according to claim 1, characterized in that The first routing rule is also used to instruct the first functional entity to send the first service flow received from the dedicated tunnel to the MEC platform.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: The session management network element acquires first information and / or second information, where the first information and / or the second information is information used to establish a dedicated tunnel; The session management network element sends the first information to the first functional entity, and / or the session management network element sends the second information to the second functional entity.

4. The method according to claim 3, characterized in that Before the session management network element obtains information for establishing a dedicated tunnel, the method further includes: The session management network element sends first indication information to the first functional entity, where the first indication information is used to instruct the first functional entity to allocate the first information; And / or, the session management network element sends second indication information to the second functional entity, where the second indication information is used to instruct the second functional entity to allocate the second information.

5. The method according to claim 4, characterized in that The first information allocated by the first functional entity is dedicated tunnel information of the first functional entity corresponding to the second functional entity; The second information allocated by the second functional entity is dedicated tunnel information of the second functional entity corresponding to the first functional entity.

6. A method for routing a service flow, characterized in that: include: In the session management process, the first functional entity receives a first routing rule from a session management network element, where the first routing rule is used to instruct the first functional entity to send a second service flow to the second functional entity through a dedicated tunnel between the first functional entity and the second functional entity; The first functional entity processes the second service flow according to the first routing rule; Alternatively, during the session management process, the second functional entity receives a second routing rule from the session management network element, where the second routing rule is used to instruct the second functional entity to send the first service flow to the first functional entity through a dedicated tunnel; The second functional entity processes the first service flow according to the second routing rule; The first service flow is a service flow that has not yet been processed by a service function SF network element in a mobile edge computing MEC platform, and the second service flow is a service flow that has been processed by the SF network element in the MEC platform; The first functional entity is used to communicate with the MEC platform, and the second functional entity is used to communicate with the data network.

7. The method according to claim 6, characterized in that The first routing rule is also used to instruct the first functional entity to send the first service flow received from the dedicated tunnel to the MEC platform.

8. The method according to claim 6 or 7, characterized in that: The method further comprises: The first functional entity receives first information from the session management network element, where the first information is used to establish information of the dedicated tunnel; And / or, the second functional entity receives second information from the session management network element, where the second information is used to establish information of the dedicated tunnel.

9. The method according to claim 8, characterized in that Before receiving the information for establishing the dedicated tunnel, the method further includes: The first functional entity receives first indication information from the session management network element, where the first indication information is used to instruct the first functional entity to allocate the first information; Or, the second functional entity receives second indication information from the session management network element, and the sending is used to instruct the second functional entity to allocate the second information.

10. The method according to claim 9, characterized in that The first information allocated by the first functional entity is dedicated tunnel information of the first functional entity corresponding to the second functional entity; The second information allocated by the second functional entity is dedicated tunnel information of the second functional entity corresponding to the first functional entity.

11. A method for routing a service flow, characterized in that: include: The session management network element determines a routing rule, where the routing rule is used to instruct the first offload entity to send the first service flow to the first functional entity, and / or to send the second service flow to the second functional entity or the access device, where the first service flow is a service flow to be controlled by a first service chain, and the second service flow is a service flow that has been controlled by the first service chain; During the session management process, the session management network element sends the routing rule to the first offload entity.

12. The method according to claim 11, characterized in that The routing rules include: description information of the first business flow and information of the first functional entity associated with the description information of the first business flow, and / or description information of the second business flow and information of the second functional entity or access device associated with the description information of the second business flow; wherein the description information includes source information of the first business flow or source information of the second business flow.

13. The method according to claim 12, characterized in that The routing rules include any one or more of the following information: When the description information of the first service flow indicates that the first service flow comes from the access device or the second functional entity, the first traffic distribution entity sends the first service flow to the first functional entity; or, When the description information of the second service flow indicates that the second service flow comes from the first functional entity, the first traffic distribution entity sends the second service flow to the access device or the second functional entity.

14. A method for routing a service flow, characterized in that: include: In the session management process, the first traffic distribution entity receives a routing rule from the session management network element, where the routing rule is used to instruct the first traffic distribution entity to send a first service flow to a first functional entity, and / or to send a second service flow to a second functional entity or an access device, where the first service flow is a service flow to be controlled by a first service chain, and the second service flow is a service flow that has been controlled by the first service chain; The first offloading entity transmits the target service flow received by the first offloading entity according to the routing rule.

15. The method according to claim 14, characterized in that The routing rules include: description information of the first service flow and information of the first functional entity associated with the description information of the first service flow, and / or description information of the second service flow and information of the second functional entity or access device associated with the description information of the second service flow; wherein the description information includes source information of the first service flow or the second service flow.

16. The method according to claim 15, characterized in that The first offloading entity transmits the target service flow received by the first offloading entity according to the routing rule, including: The description information of the target service flow is the same as the description information of the first service flow, and the first traffic distribution entity sends the target service flow to the first functional entity; and / or, The description information of the target service flow is the same as the description information of the second service flow, and the first traffic distribution entity sends the target service flow to the second functional entity or the access device.

17. A communication device, characterized in that: include: a processing unit, configured to obtain one or more of a first routing rule and a second routing rule, wherein the first routing rule is configured to instruct the first functional entity to send a second service flow to the second functional entity through a dedicated tunnel between the first functional entity and the second functional entity; The second routing rule is used to instruct the second functional entity to send a first service flow to the first functional entity through a dedicated tunnel; wherein the first service flow is a service flow that has not yet been processed by a service function SF network element in a mobile edge computing MEC platform, and the second service flow is a service flow that has been processed by the SF network element in the MEC platform; the first functional entity is used to communicate with the MEC platform, and the second functional entity is used to communicate with a data network; A communication unit, configured to send the first routing rule to the first functional entity; and / or the session management network element to send the second routing rule to the second functional entity.

18. The communication device according to claim 17, characterized in that: The first routing rule is also used to instruct the first functional entity to send the first service flow received from the dedicated tunnel to the MEC platform.

19. The communication device according to claim 17 or 18, characterized in that: The processing unit is further used to obtain first information and / or second information, where the first information and / or the second information is information used to establish a dedicated tunnel; The communication unit is further configured to send the first information to the first functional entity, and / or the session management network element sends the second information to the second functional entity.

20. The communication device according to claim 19, characterized in that Before obtaining information for establishing a dedicated tunnel, The communication unit is further used to send first indication information to the first functional entity, where the first indication information is used to instruct the first functional entity to allocate the first information; Alternatively, the communication unit is further used to send second indication information to the second functional entity, where the second indication information is used to instruct the second functional entity to allocate the second information.

21. The communication device according to claim 20, characterized in that: The first information allocated by the first functional entity is dedicated tunnel information of the first functional entity corresponding to the second functional entity; The second information allocated by the second functional entity is dedicated tunnel information of the second functional entity corresponding to the first functional entity.

22. A communication device, characterized in that: include: a communication unit, configured to receive a first routing rule from a session management network element during a session management process, wherein the first routing rule is used to instruct the first functional entity to send a second service flow to the second functional entity through a dedicated tunnel between the first functional entity and the second functional entity; a processing unit, configured to process the second service flow according to the first routing rule; Alternatively, the communication unit is configured to receive a second routing rule from a session management network element during a session management process, wherein the second routing rule is configured to instruct the second functional entity to send a first service flow to the first functional entity through a dedicated tunnel; a processing unit, configured to process the first service flow according to the second routing rule; The first service flow is a service flow that has not yet been processed by a service function SF network element in a mobile edge computing MEC platform, and the second service flow is a service flow that has been processed by the SF network element in the MEC platform; The first functional entity is used to communicate with the MEC platform, and the second functional entity is used to communicate with the data network.

23. The communication device according to claim 22, characterized in that The first routing rule is also used to instruct the first functional entity to send the first service flow received from the dedicated tunnel to the MEC platform.

24. The communication device according to claim 22 or 23, characterized in that: The communication unit is further configured to receive first information from the session management network element, where the first information is used to establish information of the dedicated tunnel; Alternatively, the communication unit is further used to receive second information from the session management network element, where the second information is used to establish information of the dedicated tunnel.

25. The communication device according to claim 24, characterized in that Before receiving information for establishing a dedicated tunnel, The communication unit is further used to receive first indication information from the session management network element, where the first indication information is used to instruct the first functional entity to allocate the first information; Or, the communication unit is further used to receive second indication information from the session management network element, and the sending is used to instruct the second functional entity to allocate the second information.

26. The communication device according to claim 25, characterized in that The first information allocated by the first functional entity is dedicated tunnel information of the first functional entity corresponding to the second functional entity; The second information allocated by the second functional entity is dedicated tunnel information of the second functional entity corresponding to the first functional entity.

27. A communication device, characterized in that: include: a processing unit, configured to determine a routing rule, wherein the routing rule is used to instruct the first traffic distribution entity to send a first service flow to a first functional entity, and / or to send a second service flow to a second functional entity or an access device, wherein the first service flow is a service flow to be controlled by a first service chain, and the second service flow is a service flow that has been controlled by the first service chain; During the session management process, the communication unit is used to send the routing rule to the first offloading entity.

28. The device according to claim 27, characterized in that The routing rules include description information of the first service flow and information of the first functional entity associated with the description information of the first service flow, and / or description information of the second service flow and information of the second functional entity or access device associated with the description information of the second service flow; wherein the description information includes source information of the first service flow or the second service flow.

29. The device according to claim 28, characterized in that The routing rules include any one or more of the following information: When the description information of the first service flow indicates that the first service flow comes from the access device or the second functional entity, the first traffic distribution entity sends the first service flow to the first functional entity; or, When the description information of the second service flow indicates that the second service flow comes from the first functional entity, the first traffic distribution entity sends the second service flow to the access device or the second functional entity.

30. A communication device, characterized in that: include: In the session management process, the communication unit is used to receive a routing rule from a session management network element, where the routing rule is used to instruct to send a first service flow to a first functional entity, and / or to send a second service flow to a second functional entity or an access device, where the first service flow is a service flow to be controlled by a first service chain, and the second service flow is a service flow that has been controlled by the first service chain; The communication unit is further configured to transmit the target service flow received by the first distribution entity according to the routing rule.

31. The device according to claim 30, characterized in that The routing rules include description information of the first service flow and information of the first functional entity associated with the description information of the first service flow, and / or description information of the second service flow and information of the second functional entity or access device associated with the description information of the second service flow; wherein the description information includes source information of the first service flow or the second service flow.

32. The device according to claim 31, characterized in that The description information of the target service flow is the same as the description information of the first service flow, and the communication unit is specifically used for the first distribution entity to send the target service flow to the first functional entity; and / or, The description information of the target service flow is the same as the description information of the second service flow, and the communication unit is specifically used to send the target service flow to the second functional entity or the access device.

33. A computer-readable storage medium, characterized in that: The readable storage medium stores instructions, which, when executed, implement the method according to any one of claims 1 to 5, or the method according to any one of claims 6 to 10, or the method according to any one of claims 11 to 13, or the method according to any one of claims 14 to 16.

34. A chip, characterized in that: The chip includes a processor and a communication interface, which is coupled to the processor. The processor is used to run a computer program or instructions to implement the method described in any one of claims 1 to 5, or the method described in any one of claims 6 to 10, or the method described in any one of claims 11 to 13, or the method described in any one of claims 14 to 16. The communication interface is used to communicate with other modules outside the chip.

35. A communication device, characterized in that: include: A processor and a communication interface, wherein the communication interface is used to perform the operation of sending and receiving messages in the session management network element in the method according to any one of claims 1 to 5 or any one of claims 11 to 13; the processor runs instructions to perform the operation of processing or controlling in the session management network element in the method according to any one of claims 1 to 5 or any one of claims 11 to 13; or, The communication interface is used to perform the operation of sending and receiving messages in the first functional entity or the second functional entity in the method according to any one of claims 6 to 10; the processor runs instructions to perform the operation of processing or controlling in the first functional entity or the second functional entity in the method according to any one of claims 6 to 10; or, The communication interface is used to perform the operation of sending and receiving messages in the first diversion entity in the method described in any one of claims 14-16; the processor runs instructions to perform the operation of processing or controlling in the first diversion entity in the method described in any one of claims 14-16.

36. A communication system, characterized in that: The system comprises: the communication device according to any one of claims 17-21, and the communication device according to any one of claims 22-26; or, the system comprises: the communication device according to any one of claims 27-29, and the communication device according to any one of claims 30-32.

37. A computer program product comprising: The method comprises computer instructions, which, when executed on a communication device, cause the communication device to execute the method according to any one of claims 1 to 5, or execute the method according to any one of claims 6 to 10, or execute the method according to any one of claims 11 to 13, or execute the method according to any one of claims 14 to 16.

Images