WO2021088018A1 - 一种业务流的路由方法、装置及系统 - Google Patents

一种业务流的路由方法、装置及系统 Download PDF

Info

Publication number
WO2021088018A1
WO2021088018A1 PCT/CN2019/116803 CN2019116803W WO2021088018A1 WO 2021088018 A1 WO2021088018 A1 WO 2021088018A1 CN 2019116803 W CN2019116803 W CN 2019116803W WO 2021088018 A1 WO2021088018 A1 WO 2021088018A1
Authority
WO
WIPO (PCT)
Prior art keywords
service flow
entity
information
functional entity
network element
Prior art date
Application number
PCT/CN2019/116803
Other languages
English (en)
French (fr)
Inventor
李永翠
雷骜
倪慧
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2019/116803 priority Critical patent/WO2021088018A1/zh
Priority to EP19952041.2A priority patent/EP4044666A4/en
Priority to CN201980101714.2A priority patent/CN114631350B/zh
Publication of WO2021088018A1 publication Critical patent/WO2021088018A1/zh
Priority to US17/738,782 priority patent/US11963032B2/en
Priority to US18/616,049 priority patent/US20240236755A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/12—Shortest path evaluation
    • H04L45/121—Shortest path evaluation by minimising delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/308—Route determination based on user's profile, e.g. premium users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/20—Traffic policing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2483—Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H04W28/0236—Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a method, device, and system for routing service flows.
  • AR augmented reality
  • VR virtual reality
  • IOT Internet of Things
  • Service chain control refers to that the service flow is enhanced by a series of orderly service function network elements (SF). Among them, these SFs are located in a data network (DN).
  • DN data network
  • the SF can be a functional network element deployed by an operator or a functional network element deployed by a third party.
  • a packet data network gateway can perform traffic steering control on the received service flow according to a service chain strategy.
  • the specific process includes:
  • Step 1 The policy and charging rules function (PCRF) determines the activation of the service chain control for the service flow.
  • PCF policy and charging rules function
  • Step 2 The PCRF sends a policy and charging control (PCC) rule to a policy and charging enforcement function (PCEF).
  • PCC rules include: the identification of the business flow and the identification of the business chain strategy.
  • PCEF is located in PGW.
  • the interface between the PGW and the PCRF is the Gx interface.
  • Step 3 the PGW sends the service flow determined by the service flow identifier to each SF in the central DN to perform traffic steering control.
  • traffic steering control is located between the PGW and the central DN. However, the location of the PGW may be far away from the terminal. If the PGW sends the service flow to each SF for traffic steering control, a large delay may occur.
  • the embodiments of the present application provide a method, device, and system for transmitting a service flow, so as to realize that the service flow continues to be sent to the central DN after the service chain control is executed locally.
  • an embodiment of the present application provides a service flow routing method, including: a session management network element determines a routing rule, the routing rule is used to instruct a first offloading entity to send the first service flow to a first functional entity, and /Or, send the second service flow to the second functional entity or the access device, the first service flow is the service flow to be controlled by the first service chain, and the second service flow is the service flow for which the first service chain control has been executed .
  • the session management network element sends routing rules to the first offloading entity.
  • the embodiment of the present application provides a routing method for a service flow.
  • a session management network element determines routing rules, and sends the routing rules to a first offloading entity, so that the first offloading entity can match the routing rules according to the routing rules.
  • the service flow performs the corresponding forwarding action.
  • the first offloading entity may 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 controlled by the first service chain to be executed, which can be controlled by the first function.
  • the SF in the MEC platform corresponding to the entity performs the first service chain control on the first service flow.
  • the first service chain control such as video acceleration, firewall, and load balancing functions, can be performed on the first service stream as soon as possible, so that the first service stream can be obtained as soon as possible. Processing, such as the firewall function, can filter out invalid business flows as early as possible.
  • the first offloading entity in the embodiment of the present application may also send the second service flow recorded in the routing rule to the second functional entity or the 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 first service chain control can be performed on the service flow and then sent back to the second functional entity.
  • the routing rule includes the description information of the first service flow and the information of the first functional entity associated with the description information of the first service flow, and/or the description information of the second service flow and the first service flow. 2. Information of the second functional entity or information of the access device associated with the description information of the service flow. Wherein, the description information includes source information of the first service flow or the second service flow.
  • the first offloading entity By instructing the first offloading entity to send the description information of the second service flow to the second functional entity, it is convenient for the first offloading entity to determine that the received description information of the service flow is the same as the description information of the second service flow.
  • the received service flow is sent to the second functional entity or the access device.
  • 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 offload entity The first functional entity sends the first service flow. Or, when the description information of the second service flow indicates that the second service flow comes from the first functional entity, the first offload entity sends the second service flow to the access device or the second functional entity.
  • the routing rule is used to instruct the first offloading entity to send the first service flow from the second dedicated tunnel to the first functional entity, and/or to instruct the first offloading entity to send to the second functional entity
  • the second traffic flow from the first dedicated tunnel is located between the first offloading entity and the second functional entity.
  • the first dedicated tunnel is located between the first offloading entity and the first functional entity. This facilitates the first offloading entity to determine to send the service flow from the specific dedicated tunnel to the corresponding functional entity.
  • the method provided in the embodiment of the present application further includes: the session management network element obtains the first dedicated tunnel information used to establish the first dedicated tunnel and the second dedicated tunnel used to establish the second dedicated tunnel One or more of the information. It is convenient to subsequently establish one or more of the first dedicated tunnel and the second dedicated tunnel.
  • the method provided in 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, where the first forwarding rule is used to indicate the second function
  • the entity transmits the first service flow to the first offloading entity through the second dedicated tunnel.
  • the second functional entity can subsequently transmit the first service flow to be controlled by the service chain from the first dedicated tunnel to the first offloading entity.
  • the method provided in 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
  • the functional entity transmits the second service flow to the first offloading entity through the first dedicated tunnel.
  • the first functional entity can subsequently transmit the second service flow for which the service chain control has been executed to the first offloading entity through the first dedicated tunnel.
  • the method provided in the embodiment of the present application further includes: the session management network element sends the first dedicated tunnel information to the first dedicated tunnel information.
  • An offload entity sends first indication information, where the first indication information is used to instruct the first offload entity to allocate one or more of the first dedicated tunnel information and the second dedicated tunnel information.
  • acquiring one or more of the first dedicated tunnel information and the second dedicated tunnel information by the session management network element includes: the session management network element receiving the first dedicated tunnel information and the second dedicated tunnel information from the first offload entity One or more of. That is, the session management network element can independently allocate one or more of the first dedicated tunnel information and the second dedicated tunnel information, and can also obtain the first dedicated tunnel information and the second dedicated tunnel information from the first offloading entity. One or more of.
  • the first service flow is associated with the first identifier, and the routing rule is used to instruct the first offloading entity to send the service flow associated with the first identifier to the first functional entity.
  • the second service flow is associated with the second identifier, and the routing rule is used to instruct the first offload entity to send the service flow associated with the second identifier to the second functional entity.
  • the method provided in the embodiment of the present application further includes: the session management network element sends to the second functional entity to instruct the second functional entity to carry the first identifier in the header of the first service flow The third instruction information.
  • the method provided in the embodiment of the present application further includes: the session management network element sends to the first functional entity to instruct the first functional entity to carry the second identifier in the header of the second service flow The fourth instruction information.
  • the method provided in the embodiment of the present application further includes: the session management network element determines that the offload entity is changed from the first offload entity to the second offload entity.
  • the session management network element sends to the second offload entity fifth indication information for instructing the second offload entity to perform any one or more of the following steps: sending the third service flow originating from the first offload entity to the access device; Or, sending the fourth service flow originating from the second functional entity to the third functional entity corresponding to the second offloading entity.
  • the third service flow has been subjected to service chain control or the third service flow is a service flow for which the first service chain control has been executed.
  • the fourth service flow is the service flow for which the first service chain control is to be executed.
  • This method can send the fourth service stream to the third functional entity when the offload entity changes, so as to realize the service chain control of the fourth service stream and transfer the first service stream that has been controlled by the service chain from the first service stream to the third functional entity.
  • the two-distribution entity sends to the access device.
  • the method provided in the embodiment of the present application further includes: the session management network element determines that the offload entity is changed from the first offload entity to the second offload entity.
  • the session management network element sends sixth indication information to the first offload entity, where the sixth indication information is used to instruct the first offload entity to send the fifth service flow from the second functional entity to the second offload entity.
  • the session management network element sends seventh indication information to the second offload entity, where the seventh indication information is used to instruct the second offload entity to send the fifth service flow received by the second offload entity to a third functional entity corresponding to the second offload entity.
  • the fifth service flow is the service flow for which the first service chain control is to be executed. This method can send the fifth service flow to the third functional entity when the offload entity changes, so that the MEC platform corresponding to the third functional entity performs service chain control on the fifth service flow.
  • the routing rule is also used to instruct the first offload entity to send a sixth service flow to the access device or the second functional entity, and the sixth service flow is a service flow that does not need to perform service chain control.
  • the routing rule includes the information of the access device or the information of the second functional entity associated with the description information of the sixth service flow and the description information of the sixth service flow.
  • a service flow transmission method includes: in the session management process of the session, a first offload entity receives a routing rule from a session management network element, and the routing rule is used to indicate the first offload
  • the entity sends the first service flow to the first functional entity, and/or sends the second service flow to the second functional entity or the access device.
  • the first service flow is the service flow to be controlled by the first service chain.
  • the second business flow is the business flow that has executed the first business chain control.
  • the first offload entity transmits the target service flow received by the first offload entity according to the routing rule.
  • 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 The information of the second functional entity or the information of the 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.
  • the first offloading entity transmits the target service flow received by the first offloading entity according to the routing rules, including: the description information of the target service flow is the same as the description information of the first service flow, and the first offloading entity The 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 offload entity sends the target service flow to the second functional entity or the access device.
  • the routing rule is used to instruct the first offloading entity to send the first service flow from the second dedicated tunnel to the first functional entity, and/or to instruct the first offloading entity to send to the second functional entity
  • the first offload entity transmits the target service flow received by the first offload entity according to the routing rule, including: the target service flow originates from the second dedicated tunnel, and the first offload entity sends the target service flow To the first functional entity; or, the target service flow originates from the first dedicated tunnel, and the first offloading entity sends the target service flow to the second functional entity.
  • the method provided in the embodiment of the present application further includes: the first offloading entity receives from the session management network element for instructing the first offloading entity to allocate the first dedicated tunnel information and the second dedicated tunnel information One or more of the first indication 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 offloading entity sends one or more of the first dedicated tunnel information and the second dedicated tunnel information to the session management network element.
  • the first service flow is associated with the first identifier
  • the routing rule is used to instruct the first offloading entity to send the service flow associated with the first identifier to the first functional entity; or, the second service flow Associated with the second identifier, the routing rule is used to instruct the first offload entity to send the service flow associated with the second identifier to the second functional entity.
  • the first offload entity transmits the target service flow received by the first offload entity according to the routing rule, including: the service flow is associated with the first identifier, and the first offload entity sends the target to the first functional entity Business flow; or, the target business flow is associated with the second identifier, and the first offloading entity sends the target business flow to the second functional entity.
  • the routing rule is also used to instruct the first offloading entity to send a third service flow to the access device or the second functional entity.
  • the third service flow is a service that does not need to perform service chain control in the session. flow.
  • the routing rule includes the description information of the third service flow and the information of the access device or the information of the second functional entity associated with the description information of the third service flow.
  • the first offload entity transmits the target service flow received by the first offload entity according to the routing rules, including: the description information of the target service flow is the same as the description information of the third service flow, then the first The offloading entity sends the target service flow to the access device or the second functional entity.
  • an embodiment of the present application provides a service flow transmission method, including: a session management network element obtains one or more of a first routing rule and a second routing rule, the first routing rule is used to indicate a first function The entity sends the second service flow to the second functional entity through the 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 the first service flow to the first functional entity through a dedicated tunnel; where the first service flow is the service flow to be executed under the control of the first service chain, and the second service flow is executed The service flow 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.
  • 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.
  • the method provided in the embodiment of the present application further includes: the session management network element sends to the first functional entity indicating the first functional entity Allocate the first indication information of the information used to establish 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 a dedicated tunnel.
  • an embodiment of the present application provides a communication device, which can implement the service flow routing method described in the first aspect or any one of the possible implementations of the first aspect, and therefore can also Achieve the beneficial effects of the first aspect or any one of the possible implementation manners of the first aspect.
  • the communication device of this type may be a session management network element, or may be a device that can support the session management network element to implement the first aspect or any one of the possible implementation manners of the first aspect. For example, it is applied to a chip in a session management network element.
  • This kind of communication device can implement the above method through software, hardware, or through hardware executing corresponding software.
  • an embodiment of the present application provides a communication device, including: a processing unit, configured to determine routing rules, where the routing rules are used to instruct a first offload entity to send a first service flow to a first functional entity, and/or, Send the second service flow to the second functional entity or the access device, the first service flow is the service flow to be controlled by the first service chain, and the second service flow is the service flow for which the first service chain control has been executed;
  • the communication unit is used to send routing rules to the first offload entity.
  • the routing rule includes the description information of the first service flow and the information of the first functional entity associated with the description information of the first service flow, and/or the description information of the second service flow and the first service flow. 2. Information of the second functional entity or information of the access device associated with the description information of the service flow. Wherein, the description information includes source information of the first service flow or the second service flow.
  • 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 offload entity The first functional entity sends the first service flow; or, when the description information of the second service flow indicates that the second service flow comes from the first functional entity, the first offload entity sends the second service flow to the access device or the second functional entity.
  • the routing rule is used to instruct the first offloading entity to send the first service flow from the second dedicated tunnel to the first functional entity, and/or to instruct the first offloading entity to send to the second functional entity
  • the second traffic flow from the first dedicated tunnel is located between the first offloading entity and the second functional entity
  • the first dedicated tunnel is located between the first offloading entity and the first functional entity.
  • the processing unit is further configured to obtain 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.
  • the communication unit is further configured to send the second dedicated tunnel information and the first forwarding rule to the second functional entity.
  • the first forwarding rule is used to instruct the second functional entity to transmit the first service flow to the first offloading entity through the second dedicated tunnel.
  • the communication unit is further configured to send the first dedicated tunnel information and the second forwarding rule to the first functional entity.
  • the second forwarding rule is used to instruct the first functional entity to transmit the second service flow to the first offloading entity through the first dedicated tunnel.
  • the communication unit is further configured to send the first indication information to the first offload entity
  • the first indication information is used to instruct the first offload entity to allocate one or more of the first dedicated tunnel information and the second dedicated tunnel information.
  • the processing unit is specifically configured to receive one or more of the first dedicated tunnel information and the second dedicated tunnel information from the first offload entity through the communication unit.
  • the first service flow is associated with the first identifier
  • the routing rule is used to instruct the first offloading entity to send the service flow associated with the first identifier to the first functional entity; or, the second service flow Associated with the second identifier, the routing rule is used to instruct the first offload entity to send the service flow associated with the second identifier to the second functional entity.
  • the communication unit is further configured 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 service flow in the header of the first service flow.
  • the third indication information is used to instruct the second functional entity to carry the first service flow in the header of the first service flow.
  • the communication unit is further configured to send fourth indication information to the first functional entity, and the fourth indication information is used to instruct the first functional entity to carry the second logo.
  • the processing unit is further configured to determine that the shunt entity changes from the first shunt entity to the second shunt entity.
  • the communication unit is further configured to send fifth indication information to the second offload entity, where the fifth instruction information is used to instruct the second offload entity to perform any one or more of the following steps: send the source from the first offload entity to the access device Or, send the fourth service flow from the second functional entity to the third functional entity corresponding to the second offload entity.
  • the third service flow has been subjected to service chain control or the third service flow is a service flow for which the first service chain control has been executed.
  • the fourth service flow is the service flow for which the first service chain control is to be executed.
  • the processing unit is further configured to determine that the offload entity changes from the first offload entity to the second offload entity; the communication unit is further configured to send sixth indication information to the first offload entity.
  • the sixth indication information is used to instruct the first offload entity to send the fifth service flow from the second functional entity to the second offload entity.
  • the session management network element sends seventh indication information to the second offload entity, where the seventh indication information is used to instruct the second offload entity to send the fifth service flow received by the second offload entity to a third functional entity corresponding to the second offload entity.
  • the fifth service flow is the service flow for which the first service chain control is to be executed.
  • the routing rule is further used to instruct the first offload entity to send the sixth service flow to the access device or the second functional entity.
  • the sixth service flow is a service flow that does not need to perform service chain control.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a session management network element or a chip in the session management network element.
  • the communication device may include: a communication unit and a processing unit.
  • 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 the service flow routing method described in the first aspect or any one of the possible implementation manners of the first aspect.
  • the processing unit may be a processor, and the communication unit may be collectively referred to as a communication interface.
  • the communication interface may be an input/output interface, pin or circuit, and so on.
  • the processing unit executes the computer program code stored in the storage unit, so that the session management network element implements the service flow routing method described in the first aspect or any one of the possible implementations of the first aspect, the storage unit It may be a storage unit (for example, register, cache, etc.) in the chip, or a storage unit (for example, read-only memory, random access memory, etc.) located outside the chip in the session management network element.
  • the processor, the communication interface and the memory are coupled with each other.
  • the embodiments of the present application provide a communication device, which can implement the service flow routing method described in the second aspect or any one of the possible implementations of the second aspect, so the second aspect can also be implemented. Aspect or the beneficial effects in any possible implementation manner of the second aspect.
  • the communication device of this type may be a first offload entity, or a device that can support the first offload entity to implement the second aspect or any one of the possible implementation manners of the second aspect. For example, it is applied to the chip in the first shunt entity.
  • This kind of communication device can implement the above method through software, hardware, or through hardware executing corresponding software.
  • an embodiment of the present application provides a communication device, including: in a session management process of a session, a communication unit is configured to receive routing rules from a session management network element.
  • the routing rule is used to instruct 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, the first service flow is the first service chain control to be executed
  • the second business flow is the business flow that has been controlled by the first business chain.
  • the communication unit is further configured to transmit the target service flow received by the first offloading entity according to the routing rule.
  • the routing rule includes the description information of the first service flow and the information of the first functional entity associated with the description information of the first service flow, and/or the description information of the second service flow and the first service flow. 2. Information of the second functional entity or information of the access device associated with the description information of the service flow. Wherein, 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.
  • 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 of the target service flow
  • the information 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.
  • the routing rule is used to instruct to send the first service flow from the second dedicated tunnel to the first functional entity, and/or to instruct to send the second service flow from the first dedicated tunnel to the second functional entity.
  • business flow wherein, 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.
  • the target service flow originates from the second dedicated tunnel, and the communication unit is specifically configured to send the target service flow to the first functional entity.
  • 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.
  • the communication unit is further configured to receive the first dedicated tunnel information from the 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. Instructions. Wherein, 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.
  • the first service flow is associated with the first identifier, and the routing rule is used to instruct to send the service flow associated with the first identifier to the first functional entity.
  • the second service flow is associated with the second identifier, and the routing rule is used to instruct to send the service flow associated with the second identifier to the second functional entity.
  • the target service flow is associated with the first identifier, and the communication unit is specifically configured to send the target service flow to the first functional entity.
  • the target service flow is associated with the second identifier, and the communication unit is specifically configured to send the target service flow to the second functional entity.
  • an embodiment of the present application provides a communication device.
  • the device may be a first offload entity or a chip in the first offload entity.
  • the communication device may include: a communication unit and a processing unit.
  • 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 offload entity implements the service flow routing method described in the second aspect or any one of the possible implementation manners of the second aspect.
  • the processing unit may be a processor, and the communication unit may be collectively referred to as a communication interface.
  • the communication interface may be an input/output interface, pin or circuit, and so on.
  • the processing unit executes the computer program code stored in the storage unit, so that the first offloading entity implements the service flow routing method described in the second aspect or any one of the possible implementations of the second aspect, the storage unit It may be a storage unit (for example, a register, a cache, etc.) in the chip, or a storage unit (for example, a read-only memory, a random access memory, etc.) located outside the chip in the first shunt entity.
  • the processor, the communication interface and the memory are coupled with each other.
  • the embodiments of the present application provide a communication device, which can implement the service flow routing method described in the third aspect or any one of the possible implementation manners of the third aspect, so the third aspect can also be implemented. Aspect or the beneficial effects in any possible implementation manner of the third aspect.
  • the communication device of this type may be a session management network element, or may be a device that can support the session management network element to implement the third aspect or any one of the possible implementation manners of the third aspect. For example, it is applied to a chip in a session management network element.
  • This kind of communication device can implement the above method through software, hardware, or through hardware executing corresponding software.
  • an embodiment of the present application provides a communication device, including: a processing unit, configured 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 the 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 the first service flow to the first functional entity through the dedicated tunnel.
  • the first service flow is a service flow for which the first service chain control is to be executed
  • the second service flow is a service flow for which the first service chain control has been executed.
  • the communication unit is configured to send the first routing rule to the first functional entity; and/or the communication unit is configured to send the second routing rule to the second functional entity.
  • the processing unit is also used to obtain information for establishing a dedicated tunnel.
  • the communication unit is also used to send information about the dedicated tunnel to the first functional entity or the second functional entity.
  • the processing unit is further configured to obtain information for establishing a dedicated tunnel
  • the communication unit is further configured to send to the first functional entity an instruction to instruct the first functional entity to allocate for establishing a dedicated tunnel.
  • the first indication of the information 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 a dedicated tunnel.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a session management network element or a chip in the session management network element.
  • the communication device may include: a communication unit and a processing unit.
  • 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 the service flow routing method described in the third aspect or any one of the possible implementation manners of the third aspect.
  • the processing unit may be a processor, and the communication unit may be collectively referred to as a communication interface.
  • the communication interface may be an input/output interface, pin or circuit, and so on.
  • the processing unit executes the computer program code stored in the storage unit to enable the session management network element to implement the service flow routing method described in the third aspect or any one of the possible implementations of the third aspect, the storage unit It may be a storage unit (for example, register, cache, etc.) in the chip, or a storage unit (for example, read-only memory, random access memory, etc.) located outside the chip in the session management network element.
  • the processor, the communication interface and the memory are coupled with each other.
  • the embodiments of the present application provide a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program or instruction.
  • the computer program or instruction runs on a computer, the computer executes the first aspect, or The method described in any one of the possible implementations of the first aspect.
  • an embodiment of the present application provides a computer-readable storage medium in which a computer program or instruction is stored.
  • the computer program or instruction runs on a computer, the computer can execute the second aspect, or The method described in any possible implementation of the second aspect.
  • the embodiments of the present application provide a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program or instruction.
  • the computer program or instruction runs on the computer, the computer can execute the third aspect, or The method described in any of the possible implementations of the third aspect.
  • embodiments of the present application provide a computer program product including instructions, which when the instructions run on a computer, cause the computer to execute the method described in the first aspect or any one of the possible implementations of the first aspect.
  • an embodiment of the present application provides a computer program product including instructions.
  • the instructions run on a computer, the computer executes the method described in the second aspect or any one of the possible implementations of the second aspect. .
  • the embodiments of the present application provide a computer program product including instructions.
  • the instructions run on a computer, the computer executes the method described in the third aspect or any one of the possible implementations of the third aspect. .
  • an embodiment of the present application provides a communication device.
  • the communication device includes a processor and a storage medium.
  • the storage medium stores instructions. When the instructions are executed by the processor, they implement various aspects such as the first aspect or the first aspect. Possible implementations are described in the method.
  • an embodiment of the present application provides a communication device.
  • the communication device includes a processor and a storage medium.
  • the storage medium stores instructions. When the instructions are executed by the processor, they can implement various aspects such as the second aspect or the second aspect. Possible implementations are described in the method.
  • an embodiment of the present application provides a communication device that includes a processor and a storage medium.
  • the storage medium stores instructions.
  • the instructions When executed by the processor, they can implement various aspects such as the third aspect or the third aspect. Possible implementations are described in the method.
  • an embodiment of the present application provides a communication device, including: at least one processor and a communication interface, at least one processor and the communication interface are interconnected through a wire, at least one processor is coupled with a memory, and the memory is used to store a computer program Or instructions, at least one processor is used to execute the computer program or instructions in the memory, so that the communication device executes the first aspect or the methods described in various possible implementation manners of the first aspect.
  • an embodiment of the present application provides a communication device, including: at least one processor and a communication interface, at least one processor and the communication interface are interconnected by a wire, at least one processor is coupled with a memory, and the memory is used to store a computer program Or instructions, at least one processor is used to execute the computer program or instructions in the memory, so that the communication device executes the second aspect or the methods described in the various possible implementation manners of the second aspect.
  • an embodiment of the present application provides a communication device, including: at least one processor and a communication interface, at least one processor and the communication interface are interconnected through a wire, at least one processor is coupled with a memory, and the memory is used to store a computer program Or instructions, at least one processor is used to execute the computer program or instructions in the memory, so that the communication device executes the third aspect or the methods described in the various possible implementation manners of the third aspect.
  • the device described in any one of the sixteenth aspect, the seventeenth aspect, and the eighteenth aspect may further include: a memory.
  • an embodiment of the present application provides a chip.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor.
  • the at least one processor is used to run a computer program or instruction to implement the first aspect. Or the methods described in the various possible implementations of the first aspect.
  • the communication interface is used to communicate with other modules outside the chip.
  • an embodiment of the present application provides a chip that includes at least one processor and a communication interface, the communication interface is coupled to at least one processor, and the at least one processor is used to run computer programs or instructions to implement the second aspect Or the methods described in the various possible implementations of the second aspect.
  • the communication interface is used to communicate with other modules outside the chip.
  • an embodiment of the present application provides a chip.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor.
  • the at least one processor is used to run a computer program or instruction to implement the third Aspect or the methods described in the various possible implementations of the third aspect.
  • the communication interface is used to communicate with other modules outside the chip.
  • the chip provided in the embodiment of the present application may further include a memory, and the memory is used to store computer programs or instructions.
  • an embodiment of the present application provides a communication device.
  • the communication device includes one or more modules for implementing the methods of the first, second, and third aspects.
  • the one or more The module may correspond to the steps of the method of the first aspect, the second aspect, and the third aspect described above.
  • an embodiment of the present application provides a communication device, including: at least one processor, at least one processor coupled with a memory, the memory is used to store computer programs or instructions, and at least one processor is used to execute the The computer program or instruction causes the communication device to execute the method described in the first aspect or various possible implementation manners of the first aspect.
  • an embodiment of the present application provides a communication device, including: at least one processor, at least one processor is coupled with a memory, the memory is used to store computer programs or instructions, and at least one processor is used to execute the The computer program or instruction causes the communication device to execute the method described in the second aspect or various possible implementation manners of the second aspect.
  • an embodiment of the present application provides a communication device, including: at least one processor, at least one processor coupled with a memory, the memory is used to store computer programs or instructions, and at least one processor is used to execute the The computer program or instruction causes the communication device to execute the method described in the third aspect or various possible implementation manners of the third aspect.
  • an embodiment of the present application provides a communication system, which includes: the communication device described in the fourth aspect or various possible implementation manners of the fourth aspect, and the fifth aspect or the fifth aspect The communication device described in the various possible implementations.
  • the communication system may further include: a first functional entity, a second functional entity, and an access device.
  • an embodiment of the present application provides a communication system, and the communication system includes: the communication device described in the sixth aspect or various possible implementation manners of the sixth aspect.
  • the communication system may further include: a first functional entity, a second functional entity, and an access device.
  • FIG. 1 is a schematic diagram of a system architecture for performing service chain control on a service flow in the prior art according to an embodiment of the application;
  • FIGS. 2a to 2f are schematic diagrams of the architecture of a communication system provided by an embodiment of this application.
  • 3a to 3b are schematic diagrams of a 5G architecture provided by an embodiment of this application.
  • FIG. 4 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 5 is a schematic diagram of a service flow offloading scenario provided by an embodiment of the application.
  • FIG. 6 is a first flowchart of a method for routing a service flow according to an embodiment of the application
  • FIG. 7 is a second schematic flowchart of a service flow routing method provided by an embodiment of this application.
  • FIG. 8 is a third schematic flowchart of a service flow routing method provided by an embodiment of this application.
  • Figures 9a to 9b are structural diagrams of a shunt entity that is changed according to an embodiment of the application.
  • FIG. 10 is a fourth flowchart of a service flow routing method provided by an embodiment of this application.
  • 11 to 17 are schematic diagrams of specific processes of a service flow routing method provided by embodiments of this application.
  • FIG. 18 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 19 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • FIG. 20 is a schematic structural diagram of a chip provided by an embodiment of the application.
  • words such as “first” and “second” are used to distinguish the same items or similar items that have substantially the same function and effect.
  • the first functional entity and the second functional entity are only for distinguishing different functional entities, and the order of their order is not limited.
  • words such as “first” and “second” do not limit the quantity and execution order, and words such as “first” and “second” do not limit the difference.
  • At least one refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • the following at least one item (a)” or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • Service chain control refers to: the SF performs corresponding processing on the service flow in the MEC platform or DN. For example, one or more of the following processes are executed: firewall function, video acceleration processing function, load balancing function.
  • Local service chain control means that the MEC platform corresponding to L-PSA (corresponding to the first functional entity) performs service chain control on the service flow.
  • the service flow for which the first service chain control is to be executed may mean that the service flow 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 not processed by the SF in the DN corresponding to the PSA (corresponding to the second functional entity).
  • the service flow for which the first service chain control has been executed may mean that the service flow has been processed by the SF in the MEC platform.
  • Uplink service flow refers to the service flow from the terminal or access device 50, and the destination address is the central DN. It should be noted that the destination address being the central DN means that the destination address is the address of the application server in the central DN, and the application server corresponds to the service flow and provides corresponding application services for the terminal.
  • Downlink service flow refers to the service flow from the center DN and whose destination address is the terminal.
  • MEC European Telecommunication Standard Institute
  • 5G evolution architecture is a technology that deeply integrates base stations and Internet services.
  • 3GPP 3rd Generation Partnership Project
  • SA service and architecture
  • FIG. 2a shows a communication system to which a service flow routing method provided by an embodiment of the present application is applicable.
  • the communication system includes: a session management network element 10, a first offloading entity 20, a first functional entity 30, The second functional entity 40 and the access device 50.
  • 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 offloading entity 20, the first offloading entity 20, the first functional entity 30, and the second functional entity 40.
  • the first offloading entity 20 may offload certain service flows to a local route, or decide to offload service flows to a remote route.
  • the so-called local routing means that the first offloading entity 20 offloads 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.
  • the data network communicating with the second functional entity 30 for example, the central data network ( central DN)
  • the session management network element 10 may insert the first distribution entity 20 as a distribution point in the user plane path of the session. That is, the network element or entity corresponding to the first offloading entity 20 may be a network element that offloads the service flow of the session.
  • the first offloading entity 20 may be an uplink classifier (ULCL) or a branch point network element (BP, Branching point).
  • ULCL uplink classifier
  • BP branch point network element
  • the communication system may further include: an MEC platform communicating with the first functional entity 30 and a central DN 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 functional network elements deployed by a third party.
  • SF can enhance or filter the service flow.
  • SF can 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 (application server, AS) and one or more SFs (for example, SF3 and SF4).
  • one or more SFs deployed in the central DN may be network elements with load balancing or charging functions.
  • the functions of different SFs may be the same or different, which is not limited in the embodiment of the present application.
  • the uplink service flow 1 is a service flow that does not need to perform local service chain control.
  • Upstream service flow 2 is a service flow that needs to perform local service chain control.
  • the processing of the uplink service flow 1 by the first offloading entity 20 can be described as: the first offloading entity 20 sends the uplink service flow 1 to the second functional entity 40.
  • the first offloading entity 20 sends the uplink service flow 2 to the first functional entity 30.
  • downlink service flow 1 does not need to perform local service chain control, and downlink service flow 2 has already performed local service chain control.
  • the processing of the downlink service flow by the first offloading entity 20 can be described as: the first offloading entity 20 aggregates the downlink service flow 1 and the downlink service flow 2 into the N3 tunnel (that is, the tunnel between the first offloading entity 20 and the access device 50). ) Is sent to the access device 50, and then sent to the terminal by the access device 50.
  • the upstream service flow 2 (identified by line 2) is processed on the MEC platform through SF1 and SF2.
  • the specific processing process is described as follows: the first functional entity 30 sends the upstream service flow 2 to SF1, and after SF1 is processed, it sends back to the first functional entity 30, and the first functional entity 30 sends the upstream service flow 2 processed by SF1 to SF1.
  • SF2 is processed and then sent to the first functional entity 30; or SF1 is processed and then sent to SF2, SF2 processes the upstream traffic flow and then sends it back to the first functional entity 30, after which the first functional entity 30 will have executed
  • the uplink service flow 2 controlled by the service chain is sent to the first offloading entity 20.
  • the first offloading entity 20 sends the uplink service flow 2 to the second functional entity 40; or the uplink service flow 2 is processed by SF1 and SF2 before being sent to the second functional entity 40.
  • the processing of the uplink service flow 2 in the central DN passes through SF3 and SF4.
  • the processing procedure of the second functional entity 40 on the uplink service flow 2 is similar to the processing of the first functional entity 30 on the uplink service flow 2.
  • the second functional entity 40 sends the uplink service flow 2 to SF3, and then sends back to the second functional entity 40 after SF3 is processed.
  • the second functional entity 40 sends it to SF4, and after SF4 is processed, it sends back to the second functional entity 40.
  • the second functional entity 40 sends it to the AS.
  • Other possible processing procedures will not be repeated in this embodiment.
  • Fig. 2a is only an example, and does not limit the specific transmission method of traffic steering control.
  • the second functional entity 40 sends the uplink service flow to SF3, after SF3 is processed, it is sent to SF4, and after SF4 is processed, it is sent to the AS.
  • the terminal accesses the communication system through the access device 50.
  • the terminals may be distributed in the entire wireless network, and each terminal may be static or mobile.
  • Fig. 2b shows another communication system provided by an embodiment of the present application.
  • the difference between this communication system and the communication system shown in Fig. 2a lies in: in Fig. 2a, the first offload entity 20 and the first The functional entity 30 is independently deployed.
  • the first offloading entity 20 and the first functional entity 30 are deployed in the same device, which may be referred to as a co-located network element. That is, the co-located network element has both the function of offloading the service flow and the function of sending the service flow controlled by the first service chain to the MEC platform.
  • the first offload entity 20 and the first functional entity 30 may be independent modules or units in the co-located network element.
  • the first offload entity 20 integrates a function of sending the service flow to be controlled by the first service chain to the MEC platform, that is, the first offload entity 20 integrates the first functional entity 30.
  • the co-located network element has the following functions: sending the service flow conforming to rule 1 to the second functional entity 30, and flowing the service conforming to rule 2 to the MEC platform.
  • the specific content of rule 1 and rule 2 refer to the routing rule configured by the first offloading entity in the following embodiment.
  • FIG. 2c there is a second dedicated tunnel between the first offloading entity 20 and the second functional entity 40 in the embodiment of the present application.
  • 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 for which the first service chain control has been executed.
  • only the first dedicated tunnel may be established, or only the second dedicated tunnel may be established, or the first dedicated tunnel and the second dedicated tunnel may be established at the same time.
  • the first dedicated tunnel is used to transmit the uplink service flow
  • the second dedicated tunnel is used to transmit the downlink service flow.
  • 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 the service flow for which the first service chain control has been executed or the service flow for which the first service chain control is to be executed.
  • other tunnels or other connections may exist between each network element in addition to the above-mentioned dedicated tunnels.
  • FIG. 2d there is a second dedicated tunnel between the co-located network element and the second functional entity 40 in the embodiment of the present application.
  • Fig. 2e or Fig. 2f shows another communication system provided by an embodiment of the present application.
  • the difference between this communication system and FIGS. 2a-2d is that there is a dedicated tunnel between the second functional entity 40 and the first functional entity 30 in FIG. 2e.
  • the first functional entity 30 may send the service flow for which the first service chain control has been performed to the second functional entity 40 through a dedicated tunnel.
  • the second functional entity 40 may send to the first functional entity 30 a service flow to be controlled by the first service chain through a dedicated tunnel.
  • the dedicated tunnel is located between the co-located network element and the second functional entity 40.
  • the second dedicated tunnel between the co-located network element and the second functional entity 40 can be regarded as a dedicated tunnel.
  • the second dedicated tunnel can not only be used by the second functional entity 40 to send the service flow to be controlled by the first service chain, but also can be used by the co-located network element to transmit to the second function on the second dedicated tunnel.
  • the entity 40 sends the service flow for which the first service chain control has been performed.
  • the first dedicated tunnel and the second dedicated tunnel may or may not exist.
  • the embodiment of the application does not limit this.
  • the access device 50 may send an uplink service flow to be executed service chain control to the first offload entity 20 through a third dedicated tunnel or an existing tunnel between the access device 50 and the first offload entity 20.
  • the access device 50 may receive the downlink service flow sent by the first offloading entity 20 that has executed the service chain control through the fourth dedicated tunnel or the existing tunnel between the first offloading entity 20 and the access device 50.
  • the access device 50 can send the waiting to the first offloading entity 20 through the existing tunnel with the first offloading entity 20.
  • the first offloading entity 20 may send to the first offloading entity 20 the first offloading entity 20 through the existing tunnel with the access device 50.
  • the network element or entity corresponding to the first offload entity 20 may be an uplink classifier (UL CL) or branch. Point (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 plan function (UPF) anchor (achor), and may also be referred to as a local session anchor (Local PDU session anchor, L-PSA) .
  • UPF user plan function
  • L-PSA local session anchor
  • the network element or entity corresponding to the second functional entity 40 may be a second user plan function (UPF) anchor (achor), or may be called a remote session anchor (remote PDU session anchor, abbreviated as PSA) ).
  • the access device 50 may be an access network (access network, AN) device or a radio access network (radio access network, RAN) device.
  • the 5G network architecture may also include: access and mobility management function (AMF) network elements, policy control function (PCF) network elements, Application function (AF) network element, data network (DN), authentication server function or authentication server function (authentication server function, AUSF) network element, unified database (Unified Data Repository, UDR) ( Figure 3a) Or not shown in FIG. 3b), unified data management (Unified Data Management, UDM), etc., which are not specifically limited in the embodiment of the present application.
  • AMF access and mobility management function
  • PCF policy control function
  • AF Application function
  • DN data network
  • authentication server function or authentication server function authentication server function
  • AUSF authentication server function
  • UDM Unified Data Management
  • the terminal communicates with the AMF network element through the Next Generation Network (N1) interface (N1 for short).
  • the access device communicates with the AMF network element through the N2 interface (N2 for short).
  • the access device communicates with ULCL/BP through the N3 interface (N3 for short).
  • 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 (N6 for short).
  • the second UPF network element communicates with the DN through an N6 interface (N6 for short). Any two UPF network elements communicate through an N9 interface (N9 for short).
  • the ULCL/BP communicates with SMF network elements through the N4 interface (N4 for short).
  • the AMF network element communicates with the SMF network element through the N11 interface (N11 for short).
  • the AMF network element communicates with the UDM network element through the N8 interface (N8 for short).
  • the SMF network element communicates with the PCF network element through the N7 interface (N7 for short).
  • the SMF network element communicates with the UDM network element through the N10 interface (N10 for short).
  • the AMF network element communicates with the AUSF network element through the N12 interface (N12 for short).
  • the AMF network element communicates with the NSSF network element through the N22 interface (N22 for short).
  • the AUSF network element communicates with the UDM network element through the N13 interface (N13 for short).
  • 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.
  • Fig. 3b shows an architecture based on a service-oriented interface in a 5G network architecture.
  • the difference between this architecture and Fig. 3a is that the control plane network elements in the 5GC in Fig. 3b can also interact with a service-oriented interface.
  • AMF network elements, AUSF network elements, SMF network elements, UDM network elements, UDR network elements, or PCF network elements interact with each other using service-oriented interfaces.
  • the service-oriented interface provided by the AMF network element to the outside may be Namf.
  • the service-oriented interface provided by the SMF network element to the outside may be Nsmf.
  • the service-oriented interface provided by the UDM network element to the outside may be Nudm.
  • the service-oriented interface provided by the UDR network element to the outside may be Nudr.
  • the service-oriented interface provided by the PCF network element to the outside may be Npcf. It should be understood that the relevant description of the names of various service-oriented interfaces in FIG. 3b can refer to the 5G system architecture (5G system architecture) diagram in the 23501 standard, which will not be repeated here.
  • the name of the interface between the network elements in FIG. 3a or FIG. 3b is only an example, and the name of the interface may be other names in a specific implementation, which is not specifically limited in the embodiment of the present application.
  • 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 in Figure 3a or Figure 3b are just one name.
  • the equipment itself does not constitute a limitation.
  • the network elements corresponding to the access equipment, AF network elements, AMF network elements, SMF network elements, AUSF network elements, UDM network elements, UPF network elements, and PCF network elements can also be other The name of this application does not specifically limit this.
  • the UDM network element may also be replaced with a user home server (home subscriber server, HSS) or user subscription database (user subscription database, USD) or a database entity, etc., which will be uniformly explained here and will not be repeated in the following .
  • HSS home subscriber server
  • USD user subscription database
  • the terminal, (R)AN, UPF, and DN in Figure 3a or Figure 3b are generally called user layer network functional entities.
  • the data traffic of the terminal can pass through the protocol data unit (PDU) established between the terminal and the DN.
  • Session Session
  • Session is transmitted, and the transmission will pass through two network functions (entities) (R)AN and UPF; and the other parts are called control layer network functions and entities, which are mainly responsible for authentication and authentication, registration management, Functions such as session management, mobility management, and policy control enable reliable and stable transmission of user-level traffic.
  • the PDU session involved in the embodiments of this application refers to a connection (association between the UE and a Data Network that provides a PDU connectivity service) between the terminal and the data network to provide a PDU connection service.
  • FIGS 3a-3b are network architectures applied to embodiments of the present application. The functions of the various parts involved in the network architecture or the network elements in the 5G network are described below as examples.
  • one session of the terminal has multiple anchor points (PDU session anchors).
  • PDU session anchors For example, the first UPF network element and the second UPF network element.
  • BP/ULCL For uplink service flow (UL data/traffic), BP/ULCL sends the received uplink service flow to different anchor points according to forwarding rules; for downlink service flow (DL data/traffic), BP/ULCL sends downlink traffic according to forwarding rules.
  • the service flow is sent to the terminal.
  • Terminals can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to wireless modems with wireless communication functions; they can also include subscriber units and cellular phones.
  • cellular phone smart phone (smart phone), wireless data card, personal digital assistant (personal digital assistant, PDA) computer, tablet computer, wireless modem (modem), handheld device (handheld), laptop computer (laptop) computer), cordless phone or wireless local loop (wireless local loop, WLL), machine type communication (MTC) terminal, user equipment (UE), mobile station (mobile station, MS), terminal device (terminal device) or relay user equipment, etc.
  • the relay user equipment may be, for example, a 5G residential gateway (RG).
  • RG 5G residential gateway
  • the terminals in the embodiments of the present application may be terminals in various vertical industry application fields such as Internet of Things terminal equipment, ports, smart factories, railway transportation, logistics, drones, and unmanned vehicles.
  • Mobile Robot Mobile Robot
  • AGV Automated Guided Vehicle
  • driverless cars control equipment and sensors on trains
  • control equipment and sensors Sensors deployed in factories, etc.
  • the terminal may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for using wearable technology to intelligently design everyday wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones.
  • the terminal can also be a sensor device used in a factory.
  • the access device is used to provide network access functions for authorized terminals in a specific area, and can use transmission tunnels of different quality according to the level of the terminal and service requirements.
  • Access equipment can manage wireless resources, provide access services for terminal equipment, and then complete the forwarding of control signals and terminal equipment data between the terminal equipment and the core network.
  • the access equipment can also be understood as a base station in a traditional network. For example, it can be responsible for functions such as radio resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • QoS quality of service
  • the access device can be a device in a wireless network.
  • Access equipment may also be referred to as wireless access equipment or network equipment.
  • the terminal is connected to the radio access network (RAN) node of the wireless network.
  • some examples of access devices are: The Next Generation Node B (gNB) in the fifth generation (5G) system, the transmission reception point (TRP), and the LTE system Evolved Node B (evolved Node B, eNB), radio network controller (RNC), Node B (Node B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (BBU), or wireless fidelity (wireless fidelity, Wifi) access point (access point, AP) etc.
  • 5G Fifth Generation Node B
  • TRP transmission reception point
  • LTE LTE system
  • Evolved Node B evolved Node B
  • RNC
  • the network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node.
  • the access device can also be a wireless backhaul device, a vehicle-mounted device, a wearable device, and a network device in a future 5G network or a network device in a future evolved PLMN network.
  • 3G Third generation
  • Node B Node B
  • Mobility management network element which belongs to the core network network element, is mainly responsible for the signaling processing part, such as: access control, mobility management, attachment and detachment, gateway selection and other functions.
  • the mobile management network element When the mobile management network element provides services for the session of the terminal, it will provide storage resources of the control plane for the session to store the session identifier, the SMF network element identifier associated with the session identifier, and so on.
  • the mobility management network element may be an AMF network element.
  • the mobility management network element may still be an AMF network element, or may also have other names, which is not limited in this application.
  • the session management network element is 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 end points that can manage user plane functions, policy control and charging function interfaces, and downlink data notifications.
  • IP internet protocol
  • IP terminal Internet protocol
  • the session management network element may be an SMF network element.
  • the session management network element may still be an SMF network element, or may also have other names, which is not limited in this application.
  • the user plane network element is responsible for forwarding and receiving user data (for example, service flow) 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 forwarded to the data network.
  • the transmission resources and scheduling functions of the user plane network element that provide services for the terminal are managed and controlled by the session management network element.
  • the user plane network element may be a UPF network element or a UPF module.
  • the user plane network element may still be a UPF network element or a UPF module, or may also have other names, which is not limited by this application.
  • the network element with the authentication server function mainly provides authentication functions and supports authentication of 3GPP access and Non-3GPP access.
  • 3GPP TS 33.501 3GPP TS 33.501.
  • the authentication server function network element may still be an AUSF network element, or may also have other names, which is not limited in this application.
  • NEF network elements mainly support the secure interaction between 3GPP networks and third-party applications. NEF can safely expose network capabilities and events to third parties to strengthen or improve application service quality. 3GPP networks can also safely follow the third party. The three parties obtain relevant data to enhance the intelligent decision-making of the network; at the same time, the network element supports the restoration of structured data from the unified database or the storage of structured data in the unified database.
  • UDR network element is mainly responsible for storing structured data.
  • the stored content includes contract data and policy data, structured data exposed to the outside, and application-related data.
  • the 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 third-party services to the network side.
  • NRF Network storage network element, used to maintain real-time information of all network function services in the network.
  • NRF stores the information of deployed network function (NF) components, such as NF component identification and network address, supported network slice identification, or data plane instance information, etc.
  • NF network function
  • the network storage network element may still be an NRF network element, or may also have other names, which is not limited by this application.
  • network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • Data Network refers to an operator network that provides data transmission services for terminals, such as IMS (IP Multi-media Service, IP multimedia service), Internet, etc.
  • IMS IP Multi-media Service, IP multimedia service
  • Internet etc.
  • the terminal accesses the data network by establishing a session (PDU session) from the terminal to the RAN to the UPF to the DN.
  • PDU session a session from the terminal to the RAN to the UPF to the DN.
  • FIG. 4 shows a schematic diagram of the hardware structure of a communication device in an embodiment of the present application.
  • 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 may refer to the structure shown in FIG. 4.
  • the communication device includes a processor 41, a communication line 44, and at least one communication interface (in FIG. 4, the communication interface 43 is included as an example for illustration).
  • the communication device may further include a memory 42.
  • the processor 41 can be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs for controlling the execution of the program of this application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 44 may include a path to transmit information between the aforementioned components.
  • the communication interface 43 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 42 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disc storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • the memory can exist independently and is connected to the processor through the communication line 44. The memory can also be integrated with the processor.
  • the memory 42 is used to store computer execution instructions for executing the solution of the application, and the processor 41 controls the execution.
  • the processor 41 is configured to execute computer-executable instructions stored in the memory 42 to implement a service flow routing method provided in the following embodiments of the present application.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
  • the processor 41 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 4.
  • the communication device may include multiple processors, such as the processor 41 and the processor 45 in FIG. 4.
  • processors can be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • the session management network element 10 in the embodiment of the present application can configure routing rules for ULCL/BP, so that ULCL/BP can add routing rules according to the routing rules.
  • the description is derived from the L-PSA, and the PSA is sent to the service flow of the PSA.
  • ULCL/BP sends the service flow originating from the access device or PSA and directed to the L-PSA to the L-PSA according to the routing rules.
  • the specific structure of the executive body of a service flow routing method is not particularly limited in the embodiment of the present application, as long as the code of a service flow routing method of the embodiment of the present application can be recorded by running
  • the procedure of the communication can be carried out by using a service flow routing method according to an embodiment of the present application.
  • the execution subject of a service flow routing method provided by the embodiment of the present application may be a functional module in the session management network element that can call and execute the program, or a communication device applied to the session management network element, for example, chip.
  • the execution subject of the service flow routing method provided by the embodiment of the present application may be a functional module in the first offload entity that can call and execute the program, or a communication device, such as a chip, applied to the first offload entity.
  • the execution subject of the service flow routing method provided by the embodiment of the present application may be a functional module in the first functional entity that can call and execute the program, or a communication device, such as a chip, applied to the first functional entity.
  • the execution subject of the service flow routing method provided by the embodiment of the present application may be a functional module in the second functional entity that can call and execute the program, or a communication device, such as a chip, applied to the second functional entity.
  • the following embodiments describe an example in which the execution subject of a service flow method is a session management network element, a first functional entity, a first offloading entity, and a second functional entity.
  • an embodiment of the present application provides a service flow routing method, which includes:
  • Step 601 The session management network element 10 determines a routing rule.
  • the routing rule is used to instruct the first offloading 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 for which the first service chain control is to be executed
  • the second service flow is a service flow for which the first service chain control has been executed.
  • the first service chain control may correspond to the above-mentioned local service chain control.
  • the first service flow may represent one or more service flows controlled by the first service chain to be executed in a certain session
  • the second service flow may represent one or more first service flows that have been executed in a certain session.
  • the business flow controlled by the business chain does not have an indicative meaning.
  • the first service flow and the second service flow may be the same service flow or different service flows. For example, after the first business flow has executed the business chain control, it is the business flow for which the first business chain control has been executed.
  • the first service flow and the second service flow may be service flows in the same session, or may be service flows in different sessions.
  • 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 for which the first service chain control is to be executed.
  • the second service flow may represent service flow 1 and service flow 3 in the session, and both service flow 1 and service flow 3 are service flows for which the control of the first service chain has been executed.
  • the first offloading entity 20 in the embodiment of the present application has the function of offloading the service flow.
  • it may not need to determine that the service flow has executed service chain control or has not executed the service. Chain control. Or it is determined that the service flow is the service flow to be controlled by the first service chain.
  • the first offloading entity 20 can forward the service flow according to the routing rule.
  • 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.
  • 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 in this case, the destination address of the downlink service flow may be a terminal.
  • the downlink service flow can be controlled by the SF in the central DN corresponding to the second functional entity 40 through service chain control.
  • the SF in the MEC platform corresponding to the first functional entity 30 still needs to perform service chain control.
  • the downlink service flow may not be controlled by the SF corresponding to the second functional entity 40, but only by the SF in the MEC platform corresponding to the first functional entity 30.
  • the SF in the center DN and the SF in the MEC platform can be the same or different. The embodiment of the application does not limit this.
  • the second service flow in the embodiment of the present application may be an uplink service flow in a certain session, or may be 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, and the routing rule is used to instruct the first offload entity 20 to send the second service flow To access device 50. If the second service flow is an upstream service flow, the upstream service flow may come from the hunger-relieving device 50 or the first functional entity 30, and the routing rule is used to instruct the first offloading entity 20 to send the second service flow To the second functional entity 40. As for 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, which is not limited in the embodiment of the present application.
  • Step 602 During the session management process of the session, the session management network element 10 sends routing rules to the first offloading entity 20, so that the first offloading entity 20 receives the routing rules from the session management network element 10 during the session management process of the session .
  • the session management process may be a session establishment process or a session update (modification) process or a session deletion process.
  • 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 is Carry routing rules.
  • 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 offloading entity 20, and The session modification request carries routing rules.
  • the routing rule can also carry a request message newly established in the session management process.
  • the routing rule may also be sent by the session management network element 10 to the first offloading entity 20 in any process before the first offloading entity 20 implements offloading the first service flow or the second service flow. This is the case in this embodiment of the application.
  • the session management network element 10 may send the routing rule to the first offloading entity 20 in other processes in which the session management network element 10 and the first offloading entity 20 interact.
  • Step 603 The first offloading entity 20 processes the target service flow received by the first offloading entity 20 according to the routing rule.
  • the embodiment of the present application provides a routing method for a service flow.
  • a session management network element determines routing rules, and sends the routing rules to a first offloading entity, so that the first offloading entity can match the routing rules according to the routing rules.
  • the service flow performs the corresponding forwarding action.
  • the first offloading entity may 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 controlled by the first service chain to be executed, which can be controlled by the first function.
  • the SF in the MEC platform corresponding to the entity performs the first service chain control on the first service flow.
  • the first service chain control such as video acceleration, firewall, and load balancing functions, can be performed on the first service stream as soon as possible, so that the first service stream can be obtained as soon as possible. Processing, such as the firewall function, can filter out invalid business flows as early as possible.
  • the first offloading entity in the embodiment of the present application may also send the second service flow recorded in the routing rule to the second functional entity or the 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 first service chain control can be performed on the service flow and then sent back to the second functional entity.
  • step 601 in the embodiment of the present application may be implemented in the following manner: the session management network element 10 determines the routing rule according to the policy information.
  • the policy information includes the description information of the service flow for which the first service chain control is to be executed, and the description information of the service flow for which the first service chain control has been executed.
  • the method provided in the embodiment of the present application may further include: the session management network element 10 obtains policy information (for example, PCC rules).
  • policy information for example, PCC rules
  • the policy information may be configured locally in the session management network element 10.
  • the session management network element 10 obtains policy information from the PCF network element, which is not limited in the embodiment of the present application.
  • step 604 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 step 604 to step 606.
  • the method provided in the embodiment of the present application may further include before step 601:
  • 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.
  • the first request message carries any one or more of the following information corresponding to one or more service flows: description information, terminal identification, and service chain requirements.
  • the service chain requirement is used to indicate that the one or more service flows are the service flows to be controlled by the first service chain, that is, the service flows are to be controlled by the local service chain.
  • the service chain requirement may also be used to indicate that the one or more service flows do not need to perform the first service chain control.
  • the first request message may be AF request.
  • Step 605 The PCF network element generates PCC rules according to the AF request.
  • PCC rules contain business chain information.
  • the service chain information may be a service chain policy identifier
  • the service chain policy identifier is an identifier pre-configured on the session management network element 10 and/or the PCF network element.
  • the session management network element can obtain the service chain strategy corresponding to the identifier through the identifier, such as one or more SFs that perform the first service chain control on the service flow, and the execution sequence of the one or more SFs.
  • Step 606 The PCF network element sends PCC rules to the session management network element 10, so that the session management network element 10 receives the PCC rules. In this way, it is convenient for the session management network element 10 to determine the routing rules according to the PCC rules.
  • routing rules in the embodiments of the present application can instruct the first offloading entity 20 to send the first service flow to the first functional entity 30 in various forms, and/or to send the second service flow to the second functional entity 40 or Access equipment 50.
  • the following will be introduced separately:
  • 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 service flow.
  • the description information includes source information of the first service flow or the second service flow.
  • 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.
  • the detection rule can also be any one or more of the following: tunnel information, network instance, quality of service flow identifier (QoS Flow Identifier, QFI), application identifier, and so on.
  • the network instance may specifically be a virtual local area network (Virtual Local Area Network, VLAN) identifier.
  • the service flow description information is recorded as SDF (service data flow) as an example for description.
  • the description information may include the identification of the terminal, quintuple information (for example, IP quintuple), triplet information (for example, IP triplet), tunnel information, application identification, and data network name (data network name). name, DNN), or one or more of Single Network Slice Selection Assistance Information (S-NSSAI).
  • the IP 5-tuple includes source IP address, source port number, destination IP address, destination port number, and transport layer protocol.
  • the information of the second functional entity 40 may be one or more combinations of the address of the second functional entity 40, or the identification of the second functional entity 40, or the port number of the second functional entity 40.
  • the information of the access device 50 may be one or more combinations of the address of the access device 50, or the identification of the access device 50, or the port number of the access device 50.
  • the information of the first functional entity 30 may be one or more combinations of the address of the first functional entity 30, or the identification of the first functional entity 30, or the port number of the first functional entity 30.
  • 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 offloading 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 offloading entity 20 sends the target service flow to the second functional entity 40 or the access device 50.
  • the description information corresponding to the uplink direction and the downlink direction of a service flow is different.
  • the specific content of the IP quintuple corresponding to the uplink direction of service flow A and the IP quintuple corresponding to the downlink direction can be found in Table 1. description of.
  • Table 1 The specific content of the routing rules in the embodiment of the present application is shown in the form of a table, as shown in Table 1:
  • the target service flow is service flow C
  • its description information includes: IP quintuple 1
  • the 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
  • the first offloading 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 offloading entity 20 includes: IP quintuple 2
  • the header of the service flow C includes the information of the third functional entity 40, that is, the service flow C is derived from the third function Entity 40, the first offloading entity 20 forwards the service flow C to the first functional entity 30.
  • the information of the access device 50 refers to the tunnel information of the first offloading entity 20 corresponding to the information of the access device 50; the information of the third functional entity 40 refers to the second information corresponding to the information of the third functional entity 40 The tunnel information of a shunt entity 20.
  • the description information of the service flow C includes: IP quintuple 1
  • the 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 function The 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 offload entity 20 corresponding to the first functional entity 30.
  • the description information of the service flow C includes: IP quintuple 2
  • the 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 function The 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 offload entity corresponding to the first functional entity 30.
  • the first offload entity 20 may determine the source of the service flow in the following manner: the first offload entity 20 may determine the source of the service flow through tunnel information in the header of the service flow. For example, if the packet header of the second service flow carries the tunnel information of the first offload entity 20 corresponding to the first functional entity 30, that is, I-UPF tunnel information for L-PSA, the first offload entity 20 can determine the second The service flow originates from the first functional entity 30. If the header of the first service flow carries the tunnel information of the first offload entity 20 corresponding to the second functional entity 40, that is, I-UPF tunnel information for PSA, the first offload entity 20 can determine the first service flow From the second functional entity 40. Similarly, the header of the first service flow carries the tunnel information of the first offload entity 20 corresponding to the access device 50, that is, I-UPF tunnel information for RAN, and the first offload entity 20 can determine the first service flow From the access device 50.
  • 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 offload entity 20 The first service flow is sent 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 offloading entity 20 sends the second service flow to the access device 50 or the second functional entity 40.
  • the above example takes the description information including quintuple information as an example.
  • the various contents of the description information can be decoupled or combined.
  • the description information may not include quintuple information or triplet information.
  • the first offloading entity 20 may send the service flow carrying the specified QFI to the forwarding
  • the network element indicated by the 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 designated QFI and originates from the access device 50, the first offloading entity 20 will uplink The service flow X is sent to the second functional entity 40.
  • the first offloading entity 20 sends the downlink service flow Y to the first functional entity 30. If the uplink service flow X corresponds to the designated QFI and originates from the first functional entity 30, the first offloading entity 20 sends the uplink service flow X to the second functional entity 40. If the downlink service flow Y corresponds to the designated QFI and originates from the first functional entity 30, the first offloading entity 20 sends the downlink service flow Y to the access device 50. It is understandable that if the description information is a designated QFI, it means that both the downstream service flow and the upstream service flow corresponding to the designated QFI need to perform service chain control.
  • description information to be other description methods, such as network instance, tunnel information, and application identification
  • the specific implementation can refer to the example where the description information is the identification of the terminal, which will not be repeated here.
  • Example 1 can be applied to the communication system shown in any one of FIGS. 2a to 2d. That is, on the basis of not having the first dedicated tunnel and the second dedicated tunnel, such as the scenario shown in FIG. 2a or FIG. 2b, the session management network element 10 may configure the first offload entity 20 to forward to the first functional entity 30. Descriptive information of one or more first service flows. And/or, the session management network element 10 configures the first offloading entity 20 with description information of one or more second service flows that are forwarded to the second functional entity 40 or the access device 50. In this case, the first offloading entity 20 may send the first service flow to the first functional entity 30 through the remaining tunnels with the first functional entity 30 except for the first dedicated tunnel. The first offloading entity 20 may send the second service flow to the second functional entity 30 through the remaining tunnels with the second functional entity 40 except for the second dedicated tunnel.
  • the session management network element 10 can still configure the first offload entity 20 to forward to the first functional entity 30. Descriptive information of one or more first service flows. And/or, the session management network element 10 configures the first offloading entity 20 with description information of one or more second service flows that are forwarded to the second functional entity 40 or the access device 50.
  • Example 2 With reference to Figure 2c or Figure 2d, the routing rule is used to instruct the first offloading 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 offloading entity 20 to send
  • the second functional entity 40 sends the second service flow from the first dedicated tunnel.
  • 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 offloading entity 20 and the first functional entity 30.
  • the first dedicated tunnel is used to transmit the service flow for which the first service chain control has been executed.
  • the second dedicated tunnel is used to transmit the service flow to be controlled by the first service chain.
  • 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 offloading entity 20 sends the target service flow to the first functional entity 30. Or, the target service flow originates from the second dedicated tunnel, and the first offloading entity 20 sends the target service flow to the second functional entity 40.
  • the first offloading 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 header of the target service flow.
  • the target service flow originates from the first dedicated tunnel.
  • the message header of the target service flow carries the second dedicated tunnel information, and the target service flow originates from the second dedicated tunnel.
  • first dedicated tunnel and the second dedicated tunnel in the embodiment of the present application may coexist, or one of the two may exist.
  • Example 2 may be applicable to a scenario with a second dedicated tunnel and/or a first dedicated tunnel.
  • One or more of the first dedicated tunnel information and the second dedicated tunnel information in the embodiment of the present application may be allocated by the session management network element 10.
  • the first dedicated tunnel information can also be allocated by the UPF network element, that is, the first offload entity 20 is allocated 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 offload entity 20 is allocated by the second functional entity 40, which is not limited in the embodiment of the present application.
  • the method provided by the embodiment of the present application may further include: session management network element before step 601 10 Acquire one or more of the first dedicated tunnel information and the second dedicated tunnel information.
  • the session management network element 10 can independently acquire one or more of the first dedicated tunnel information and the second dedicated tunnel information.
  • the session management network element 10 may determine to acquire one or more of the first dedicated tunnel information and the second dedicated tunnel information according to the PCC rule.
  • the PCC rule also contains indication information.
  • the indication information is used to indicate that the first service chain control is performed in the uplink direction for a certain service flow.
  • the indication information is used to indicate that the first service chain control is performed in the downlink direction for a certain service flow.
  • the indication information indicates that a certain service flow should not only perform the first service chain control in the uplink direction, but also perform the service chain control in the downlink direction.
  • the indication information in the PCC rule originates from step 604, that is, the first request message sent by the AF to the PCF also contains indication information. Therefore, the session management network element 10 determines to acquire one or more of the first dedicated tunnel information and the second dedicated tunnel information according to the instruction information.
  • 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 offloading entity 20.
  • the session management network element 10 acquiring the first dedicated tunnel information and the second dedicated tunnel information from the first offloading entity 20 reference may be made to the description in the following step 607 to step 609.
  • Step 607 The session management network element 10 sends the first indication information to the first offload entity 20, so that the first offload entity 20 receives the first indication information from the session management network element 10.
  • the first indication information is used to instruct the first offload entity 20 to allocate one or more of the first dedicated tunnel information and the second dedicated tunnel information.
  • the first indication information is used to instruct the first offloading entity 20 to establish one or more of the first dedicated tunnel and the second dedicated tunnel, so that the first offloading entity 20 can determine to allocate the first dedicated tunnel information and the second dedicated tunnel.
  • One or more of the dedicated tunnel information is used to instruct the first offload entity 20 to allocate one or more of the first dedicated tunnel information and the second dedicated tunnel.
  • the first indication information is used to instruct the first offload entity 20 to allocate the second dedicated tunnel information, or the first indication information is used to instruct the first offload entity 20 to establish the second dedicated tunnel.
  • 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.
  • the first indication information may be used to instruct the first offload entity 20 to allocate the first dedicated tunnel information, or the first indication information may be used to instruct the first offload entity 20 to establish the first dedicated tunnel.
  • 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 information.
  • Dedicated tunnel and second dedicated tunnel may be used to instruct the first offload entity 20 to allocate the first dedicated tunnel information and the second dedicated tunnel information.
  • the session management network element 10 may send the first indication information to the first offloading entity 20 during the session management process.
  • the session management network element 10 may send the first indication information to the first offloading entity 20 in other processes that interact with the first offloading entity 20 other than the session management process.
  • step 607 can be implemented in the following manner: the session management network element 10 sends an N4 session establishment request to the first offload entity 20.
  • the N4 session establishment request carries the first indication information.
  • the N4 session establishment request can also be replaced by the N4 session modification request.
  • Step 608 The first offloading 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.
  • the first offloading 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 the session management response process or other processes that interact with the session management network element 10. A.
  • 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.
  • the method provided in this embodiment of the present application further includes after step 608:
  • 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.
  • the first dedicated tunnel information is used to establish the first dedicated tunnel, and specifically may 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.
  • 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 offloading entity 20, that is, when the first functional entity 30 sends a service flow to the first offloading entity 20 through the first dedicated tunnel, the packets of the service flow
  • the header carries the first dedicated tunnel information.
  • the second dedicated tunnel refers to the downlink tunnel between the second functional entity 40 and the second offloading entity 20, that is, when the second functional entity 40 sends a service flow to the first offloading entity 20 through the second dedicated tunnel, the traffic of the service flow is
  • the message header carries the second dedicated tunnel information.
  • step 607 and step 608 can be replaced with: the session management network element 10 sends the first dedicated tunnel to the first offloading entity 20 One or more of one dedicated tunnel information and second dedicated tunnel information.
  • the first offloading entity 20 returns a response to the session management network element 10.
  • step 609 can be omitted.
  • the session management network element 10 may also instruct the second functional entity 40 or the first functional entity 30 to use the aforementioned dedicated tunnel to send the service flow.
  • the session management network element 10 instructs the second functional entity 40 or the first functional entity 30 to use the above-mentioned dedicated tunnel to send the service flow, reference may be made to step 610 and step 611.
  • the method provided in the embodiment of the present application further includes:
  • 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.
  • the first forwarding rule is used to instruct the second functional entity 40 to transmit the first service flow to the first offloading entity 20 through the second dedicated tunnel.
  • step 610 it is convenient for the second functional entity 40 to carry the second dedicated tunnel information in the header of the service flow for which the first service chain control is to be performed.
  • the first offloading entity 20 may send the service flow carrying the second dedicated tunnel information in the message header to the first functional entity 30.
  • 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.
  • 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 offloading entity through the first dedicated tunnel.
  • 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.
  • step 611 it is convenient for the first functional entity 30 to carry the first dedicated tunnel information in the header of the service flow for which the first service chain control has been executed.
  • the first offloading entity 20 may send the service flow carrying the first dedicated tunnel information in the message header to the second functional entity 30.
  • step 611 when the first functional entity 30 and the first shunt entity 20 are co-located, step 611 may be omitted.
  • the routing rule is used to instruct the co-located network element to send the upstream traffic flow received through traffic steering control to the second functional entity 40, and/or to instruct the co-located network element to receive the downlink from the second dedicated tunnel
  • the service flow that is, the downlink service flow in which the message header carries the second dedicated tunnel information is sent to the MEC platform, so that the SF in the MEC platform performs traffic steering control.
  • Example 3 The first service flow is associated with the first identifier, and the routing rule is used to instruct the first offloading entity 20 to send the service flow associated with the first identifier to the first functional entity 30.
  • 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 or the access device 50.
  • 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 originates from the second functional entity 40 or the access device 50.
  • the stream is sent to the first functional entity 30 through the first offloading entity 30.
  • 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 offload entity 20.
  • the service flow carrying the second identifier is sent to the second functional entity 40 or the access device 50, it can be determined by combining 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.
  • the flow is still a downstream traffic flow.
  • the service flow D carries the second identifier
  • 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 offload entity 20 may send the service flow D to the second functional entity 40.
  • 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 offloading entity 20 may send the service flow D to the access device 50.
  • the second service flow is associated with the second identifier
  • 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.
  • step 603 in the embodiment of the present application can be implemented in the following manner: the target service flow is associated with the first identifier, and the first offloading entity 20 sends the target service flow to the first functional entity 30; or, The target service flow is associated with the second identifier, and the first offloading entity 20 sends the target service flow to the second functional entity 40.
  • the session management network element 10 can instruct the first offloading entity 20 to send the service flow carrying the first identifier to the first functional entity 30 through the routing rule, and send the service flow carrying the second identifier to the second functional entity 30.
  • Functional entity 40 That is, for the first offloading entity 20, it may regard the service flow carrying the first identifier as the first service flow, and the service flow carrying the second identifier as the second service flow.
  • the method provided in the embodiment of the present application may further include: A functional entity 30 carries the first identifier in the header of the service flow for which the first service chain control has been executed.
  • the second functional entity 40 carries the second identifier in the header of the service flow for which the first service chain control is to be executed.
  • the first functional entity 30 or the second functional entity 40 can autonomously determine to carry the identifier in the packet header of the service flow.
  • the session management network element 10 may instruct to carry the identifier in the header of the service flow.
  • the specific process for the first functional entity 30 or the second functional entity 40 to carry the identifier in the header of the service flow can be Refer to the description of step 612 to step 613 below.
  • the method provided in this embodiment of the present application may further include:
  • 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 header of the first service flow.
  • the third indication information may be implemented through a forwarding rule.
  • 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 the first identifier to the message header.
  • the session management network element 10 may send the third indication information to the second functional entity 40 during the session management process, or to the second functional entity 40 during the process of interacting with the second functional entity 40 outside of the session management process. 40 Send third instruction information.
  • the second functional entity 40 after receiving the third indication information, when the first service flow does not need to perform service chain control at the central DN, the second functional entity 40 is waiting to execute the first service chain control.
  • the first identifier is carried in the header of the first service flow and sent to the first offloading entity 20.
  • the second functional entity 40 has already executed the service chain control by the SF in the central DN and still needs to execute the first service flow controlled by the first service chain.
  • the first identifier is added to the header of the message and sent to the first offloading entity 20.
  • the second functional entity performs the following processing on the message of the first service flow to be controlled by the first service chain: adding the first identifier to the message header.
  • the header of the service flow may be the general packet radio service technology tunnel protocol-user plane header ((General Packet Radio Service, GPRS) tunnel protocol-user plane, GTP-U header).
  • GPRS General Packet Radio Service
  • 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.
  • the fourth indication information may be implemented through a forwarding rule.
  • 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 to the message header.
  • Example 3 when the first functional entity 30 and the first offloading entity 20 are co-located, the first functional entity 30 in step 613 can be replaced by a co-located network element.
  • the routing rule can be used to instruct the co-located network element to send the service flow associated with the first identifier to the MEC platform, so that the SF in the MEC platform performs the first service chain control; and/or the routing rule is used to indicate the collaboration It is assumed that the network element sends the service flow for which the first service chain control has been executed to the second functional entity 40. Wherein, how to mark that a certain service flow has been controlled by the SF in the MEC platform to perform the first service chain control is not limited in the embodiment of this application.
  • the second functional entity 40 records the description information of the service flow, when When the second functional entity receives the description information of the service flow from the MEC platform again, the second functional entity 40 considers the service flow to be a service flow that has been controlled by the first service chain.
  • the terminal moves and moves out of the service area of the first offload entity 20.
  • the session management network element 10 determines that the offload entity has changed from the first offload entity 20 to the second offload entity 60.
  • the second shunt entity 60 corresponds to the third functional entity 70.
  • the third functional entity 70 corresponds to the MEC platform. Therefore, in this scenario, the following step 614 and step 615, or step 614, step 616, and step 617 can be used to implement the first service chain control for the downlink service flow.
  • the method provided in the embodiment of the present application may further include:
  • Step 614 The session management network element 10 determines that the offload entity changes from the first offload entity 20 to the second offload entity 60.
  • 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.
  • 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 instruction information.
  • the fifth indication information is used to instruct the second offload entity 60 to perform any one or more of the following steps:
  • the third service flow is a service flow for which the control of the first service chain has been executed.
  • the fourth service flow is the service flow for which the first service chain control is to be executed.
  • 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.
  • 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 offloading entity 60, where the forwarding rule is used to instruct the second offloading entity 60 to send the third service flow originating from the first offloading entity 20 to the access device 50; and/ Or, the fourth service flow originating from the second functional entity 40 is sent to the third functional entity 70.
  • the second offloading entity 60 can determine to send the third service flow to the access device 50. Or, send the fourth service flow to the third functional entity 70 corresponding to the second offload entity 50.
  • the fifth indication information can be implemented through a forwarding rule.
  • the session management network element 10 sends a forwarding rule to the second offloading 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 first 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.
  • step 614 to 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.
  • the first functional entity 30 sends the third service flow for which the first service chain control has been performed to the first offloading entity 20, and the first offloading entity 20 forwards it to the second offloading entity 60.
  • the second offloading entity 60 that receives the third service flow from the first offloading entity 20, it can forward the third service flow to the access device 50 according to the fifth instruction information in step 615 (that is, the second offloading entity 60 There is no need to send the third service flow to the third functional entity 70).
  • the second offloading entity 60 For the fourth service flow received by the second offloading entity 60 from the second functional entity 40, the second offloading entity 60 sends the fourth service flow to the corresponding second offloading entity 60 according to the fifth instruction information in step 615
  • 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.
  • the method provided in the embodiment of the present application may further include: the session management network element 10 sends instruction information to the first offload entity 20, and the instruction information is used to instruct the first offload entity 20 to send the information from the second functional entity 40
  • the third service flow is sent to the second offloading entity 60.
  • the session management network element 10 sends to the second functional entity 40 instruction information for instructing the second functional entity 40 to send the fourth service flow to the second offload entity 60.
  • the method provided in the embodiment of the present application may further include after step 614:
  • Step 616 The session management network element 10 sends the 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 instruction information.
  • the sixth indication information is used to instruct the first offload entity 20 or the second functional entity 40 to send the fifth service flow to the second offload entity 60.
  • the fifth service flow is a service flow to be executed under the control of the first service chain.
  • Step 617 The session management network element 10 sends the seventh indication information to the second offload entity 60, so that the second offload entity 60 receives the seventh indication information.
  • the seventh indication information is used to instruct the second offload entity 60 to send the fifth service flow to the third functional entity 70 corresponding to the second offload entity 60.
  • the fifth service flow originates from the second functional entity 40 or originates from the first offload entity 20.
  • the session management network element 10 may also send a message to the first offloading entity 20 and the second functional entity. 40 sends the information of the second offload entity 60, such as the tunnel information of the second offload entity 60, including the tunnel endpoint identifier and address of the second offload entity 40.
  • the second offload entity 60 can send the fourth service flow from the second functional entity 40 to the third functional entity 70 corresponding to the second offload entity 60, so that the third functional entity 70 corresponds to The MEC platform performs business chain control.
  • the second offloading entity 60 sends the fourth service flow to the access device 50.
  • the second offloading entity 60 forwards the third service flow to the access device 50. That is, in FIG. 9a, for the third service flow, the second offloading entity 60 does not need to forward it to the third functional entity 70 again. This is because the third service flow has executed service chain control on the MEC platform corresponding to the first functional entity 30.
  • the second offloading entity 60 divides the fifth business
  • the stream is sent to the third functional entity 70 to perform service chain control by the MEC platform corresponding to the third functional entity 70.
  • Figure 9a or Figure 9b is only an example of the path of the SF that performs service chain control on the MEC platform or the central DN, and does not have an indicative meaning.
  • an embodiment of the present application provides a service flow transmission method, including:
  • Step 1001 The session management network element 10 determines 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 30 to pass between the first functional entity 30 and the second functional entity 40.
  • the dedicated tunnel between the two sends the second service flow to the second functional entity 40.
  • the second routing rule is used to instruct the second functional entity 40 to send the first service flow to the first functional entity 30 through a dedicated tunnel.
  • the first service flow is a service flow for which the first service chain control is to be executed
  • the second service flow is a service flow for which the first service chain control has been executed.
  • 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.
  • step 100 for the specific implementation of step 1001, reference may be made to the specific implementation of step 601, which will not be repeated in the embodiment of the present application.
  • Step 1002 The session management network element 10 sends the first routing rule to the first functional entity 30, so that the first functional entity 30 receives the first routing rule.
  • the session management network element 10 may send the first routing rule to the first functional entity 30 during the session management process.
  • Step 1003 The first functional entity 30 processes the second service flow according to the first routing rule.
  • the first functional entity 30 carries the dedicated tunnel information of the second functional entity 40 corresponding to the first functional entity 30 in the header of the second service flow according to the first routing rule. That is, specific PSA tunnel information for L-PSA.
  • 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.
  • the session management network element 10 may send the second routing rule to the second functional entity 40 during the session management process.
  • Step 1005 The second functional entity 40 processes the first service flow according to the second routing rule.
  • the second functional entity 40 carries the dedicated tunnel information of the first functional entity 30 corresponding to the second functional entity 40 in the header of the first service flow according to the second routing rule. That is, specific L-PSA tunnel information for PSA.
  • Service flow C does not need a central DN for service chain control, so 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 as shown in Table 6.1;
  • the specific content of a routing rule, that is, the processing of the service flow C by the first functional entity 30 according to the first routing rule, can be as shown in Table 6.2:
  • Service flow C needs to perform service chain control at the central DN, and the specific content of the second routing rule can be as shown in Table 7:
  • the embodiment of the present application provides a service flow routing method.
  • the session management network element instructs the first functional entity 30 to perform the first service chain control service flow (for example, the second service flow) through a first routing rule.
  • Send 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 through the dedicated tunnel .
  • the first functional entity 30 can determine that the first service flow is the service flow to be controlled by the first service chain, and then transfer the first service The stream is sent to the MEC platform to perform the first business chain control.
  • This method can prevent the first offload entity 20 from transferring the service flow that is interacted between the first functional entity 30 and the second functional entity 40, and simplify the processing logic of the first offload entity 20 on the service flow.
  • the method provided in the embodiment of the present application further includes:
  • Step 1006 The session management network element 10 sends the 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.
  • 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.
  • the dedicated tunnel information of the first functional entity 30 corresponding to the second functional entity 40 may include the tunnel endpoint identifier and address of the first functional entity 30.
  • 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.
  • 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.
  • step 1006 and step 1007 may exist one at a time, or coexist.
  • 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.
  • the dedicated tunnel information of the second functional entity 40 corresponding to the first functional entity 30 may include the tunnel endpoint identifier and address of the second functional entity 40.
  • 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.
  • Step 1008 The second functional entity 40 and/or the first functional entity 30 sends information about the dedicated tunnel to the session management network element 10.
  • 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.
  • 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 first functional entity 30 sends the session management
  • the dedicated tunnel information sent by the network element 10 is the dedicated tunnel information of the first functional entity 30 corresponding to the second functional entity 40.
  • step 1007 there is no order of execution between step 1007 and step 1008.
  • Step 1009 The session management network element 10 obtains information for establishing a dedicated tunnel.
  • the information used to establish the dedicated tunnel may be information of the dedicated tunnel.
  • 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.
  • the corresponding dedicated tunnel information sent by the session management network element 10 to the first functional entity 30 is 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.
  • steps 1006 to 1008 in the embodiment of the present application can be omitted.
  • the first offload entity 20 can be omitted.
  • the first functional entity 30 may send it to the access device 50 through the third dedicated tunnel.
  • the access device 50 may also send it to the first functional entity 30 through the third dedicated tunnel.
  • the first functional entity 30 may be replaced by a co-located network element.
  • the session management network element 10 is an SMF network element
  • the first offloading entity 20 is an I-UPF network element
  • the first functional entity 30 is an L-PSA
  • the second functional entity 40 is a PSA.
  • the access device 50 is an RAN as an example, and a specific process of a service flow routing method in an embodiment of the present application is introduced in detail. The method includes:
  • Step 1101 The AF network element sends an AF request (request) to the PCF network element, so that the PCF network element receives the AF request.
  • the AF request carries the description information of the service flow, the service chain requirements, and the identification of the terminal.
  • step 1101 the transmission path of the terminal's uplink service flow and downlink service flow is: terminal ⁇ - ⁇ RAN ⁇ - ⁇ PSA ⁇ - ⁇ central DN.
  • the description information of the service flow (traffic description information) is used to indicate the service flow targeted by the AF request, which may be specifically represented by an IP quintuple or an IP triplet.
  • the identification of the terminal can be the IP of the terminal, the SUPI of the terminal, and so on.
  • Service chain requirements used to indicate whether the service flow determined by the description information of the service flow performs local service chain control, or used to indicate whether the service flow determined by the description information of the service flow is determined by the SF in the MEC platform corresponding to the L-PSA Perform business chain control.
  • 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.
  • Step 1102 the PCF network element generates PCC rules (rules) according to the AF request.
  • PCC rules contain business chain information.
  • the business chain information can be a business chain strategy identifier.
  • Step 1103 The PCF network element triggers the session policy modification process and sends PCC rules to the SMF network element.
  • step 1103 can be described as the PCF network element calling the Npcf_SMPolicyControl_UpdateNotify request service to notify the PCC rules to the SMF network element.
  • Step 1104 The SMF network element decides to insert I-UPF and L-PSA for the session according to the PCC rules.
  • the I-UPF acts as a shunt point, sending part of the terminal's service flow to the L-PSA, and the other part to the PSA.
  • Step 1105 The SMF network element selects L-PSA.
  • step 1105 For the specific implementation of step 1105, reference may be made to the prior art, which is not described in detail in the embodiment of the present application.
  • 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.
  • Step 1107 The 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.
  • the N4 session establishment response carries L-PSA tunnel information (tunnel information).
  • the SMF network element obtains the tunnel information of the L-PSA.
  • the SMF network element then sends the L-PSA tunnel information to other user plane network elements, such as I-UPF, to establish a tunnel connection between the I-UPF and the L-PSA.
  • I-UPF user plane network elements
  • the L-PSA tunnel information can also be allocated by the SMF network element.
  • the foregoing only uses the L-PSA allocation L-PSA tunnel information as an example for description.
  • the SMF network element allocates the L-PSA tunnel information
  • the SMF network element sends the L-PSA tunnel information to the L-PSA in the N4 session establishment request.
  • tunnel information allocation is involved in the subsequent steps, it can be allocated by SMF network elements, or by L-PSA, or I-UPF or PSA.
  • 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.
  • the N4 session establishment request carries RAN tunnel information, PSA tunnel information, and L-PSA tunnel information.
  • step 1108 in the embodiment of the present application is to establish a user plane connection, that is, to convey the tunnel information of two end points (ie, network elements) on the user plane connection to the opposite end.
  • the A endpoint obtains the tunnel information of the B endpoint
  • the B endpoint obtains the tunnel information of the A endpoint, so that the user plane connection between the A endpoint and the B endpoint is successfully established.
  • This establishment process is all realized through the control plane network element, that is, the SMF network element.
  • RAN tunnel information is used to establish a tunnel between the I-UPF network element and the RAN, and then the RAN tunnel information can be carried in the header of the service flow sent by the I-UPF network element to the RAN. That is, when the I-UPF receives the service flow to be sent to the RAN, it can send it to the RAN. In other words, the tunnel between I-UPF and RAN is successfully established.
  • L-PSA tunnel information is used to establish a tunnel between the I-UPF network element and the L-PSA.
  • the 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 I-UPF and L-PSA is successfully established.
  • the PSA tunnel information is used to establish a tunnel between the I-UPF network element and the PSA.
  • the 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 stream sent to the PSA, it can send it to the PSA. In other words, the tunnel between I-UPF and PSA is successfully established.
  • 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.
  • I-UPF tunnel information for PSA is the tunnel information corresponding to the PSA allocated by the I-UPF.
  • the SMF network element sends this information to the PSA, that is, after the PSA obtains the I-UPF tunnel information for the PSA, the PSA and the I -The tunnel between UPF is successfully established.
  • the header of the service flow sent by the PSA to the I-UPF can carry the I-UPF tunnel information for PSA, that is, the I-UPF can carry the I-UPF tunnel information for PSA in the header of the service flow. , Make sure that the service flow comes from PSA.
  • I-UPF tunnel information for L-PSA is tunnel information corresponding to L-PSA allocated by I-UPF.
  • the SMF network element sends the I-UPF tunnel information for L-PSA to L-PSA, that is, after L-PSA obtains the I-UPF tunnel information for L-PSA, the information between L-PSA and I-UPF The tunnel is successfully established.
  • the header of the service flow sent by the L-PSA to the I-UPF can carry I-UPF tunnel information for L-PSA, that is, the I-UPF can be based on the I-UPF carried in the header of the service flow.
  • tunnel information for L-PSA confirm that the service flow originates from L-PSA.
  • 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 routing rules.
  • routing rules include detection rules and forwarding rules.
  • the detection rules include business flow identification and business 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 RAN, or L-PSA, or PSA.
  • routing rules are used to instruct the I-UPF to perform any one or more of the following steps for the service flow.
  • the uplink service flow In the uplink direction, the embodiment of this application is referred to as the uplink service flow; in the downlink direction, the embodiment of the application is referred to as the downlink service flow:
  • the received upstream service flow from the RAN that is, the service flow carrying I-UPF tunnel information for RAN in the header, is sent to the L-PSA.
  • the received upstream service flow from L-PSA that is, the service flow carrying I-UPF tunnel information for L-PSA in the header, is sent to the PSA.
  • the received downstream service flow from PSA that is, the service flow carrying I-UPF tunnel information for PSA in the header, is sent to L-PSA.
  • the received downlink service flow from L-PSA that is, the service flow carrying I-UPF tunnel information for L-PSA in the header, is sent to the RAN.
  • upstream service flow is represented by SDF1
  • downlink service flow is represented by SDF2
  • the specific routing rules are shown in Table 8:
  • Step 1111 the 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.
  • FIG. 11 uses the sending of routing rules to the I-UPF in the N4 session modification request as an example.
  • the SMF network element can also send the routing rules in the N4 session establishment request, that is, the routing rules are carried in step 1110. If the routing rule is carried in the N4 session establishment request, step 1110 to step 1111 can be omitted. That is, step 1110 can be combined with step 1108, and step 1111 can be combined with step 1109.
  • 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.
  • the session modification request carries I-UPF tunnel information for PSA and the first forwarding rule.
  • the first forwarding rule is used to instruct the PSA to send the downlink service flow to be executed local service chain control to the I-UPF.
  • the PSA carries I-UPF tunnel information for PSA in the header of the downlink service flow.
  • the first forwarding rule is used to instruct the PSA to send to the I-UPF the downstream service flow that has been subjected to service chain control by the central DN. That is, the downstream service flow from the PSA to be executed for local service chain control may be controlled by the service chain already executed by the central DN, or may not be controlled by the service chain executed by the central DN.
  • Step 1113 The PSA sends an N4 session modification response to the SMF network element, so that the SMF network element receives the PSA's N4 session modification response.
  • the N4 session modification response is used to indicate that the I-UPF tunnel information for PSA has been successfully received and the first forwarding rule, or the N4 session modification response is used to indicate the successful reception of the I-UPF tunnel information for PSA, and the first forwarding The response instructions of the rule.
  • Step 1114 The SMF sends an N4 session modification request to the L-PSA, so that the L-PSA receives the N4 session modification request.
  • the N4 session modification request carries the second forwarding rule and I-UPF tunnel information for L-PSA.
  • the second forwarding rule is used to instruct the L-PSA to send to the I-UPF the uplink service flow for which the local service chain control has been executed or the downlink service flow for which the local service chain control has been executed. That is, the L-PSA can carry the I-UPF tunnel information for L-PSA in the header of the uplink service flow for which the local service chain control has been performed or the downlink service flow for which the local service chain control has been performed.
  • Step 1115 The 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.
  • the N4 session modification response is used to indicate that the I-UPF tunnel information for L-PSA has been successfully received, and the second forwarding rule, or the N4 session modification response is used to indicate the successful reception of the I-UPF tunnel information for L-PSA, And the response indication information of the second forwarding rule.
  • FIG. 12 shows another service flow routing method according to an embodiment of the present application.
  • the difference between the embodiment shown in FIG. 12 and the embodiment shown in FIG. 11 is: I-UPF and L -PSA is located in the same network element, that is, the I-UPF and L-PSA in Figure 11 are replaced by co-located network elements.
  • Step 1201 to step 1205 are the same as the above step 1101 to step 1105.
  • the I-UPF and L-PSA selected by the SM are the same network element, that is, the I-UPF and L-PSA are co-located.
  • Step 1206 The SMF network element sends an N4 session establishment request to the co-located network element, so that the co-located network element receives the N4 session establishment request.
  • 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.
  • 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.
  • routing rules include detection rules and forwarding rules.
  • the detection rules include business flow identification and business flow source.
  • the forwarding action is used to indicate the processing logic of the service flow that meets the detection rules, that is, forwarding to the RAN or PSA.
  • the forwarding rule is used to instruct the co-located network element to perform one or more of the following steps for the service flow to be executed or the local service chain control has been executed:
  • the received upstream service flow that has performed local service chain control is sent to the PSA.
  • local service chain control For the received uplink service flow from the RAN (that is, the I-UPF tunnel information for RAN is carried in the message header), local service chain control is performed.
  • the received downlink service flow for which local service chain control has been executed is sent to the RAN.
  • 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 will perform the service for the service.
  • the flow performs local business chain control. That is, in the co-location scenario, if the routing rules instruct the co-located network element to perform local service chain control, it can be understood as instructing the co-located network element to send service flows to the MEC platform so that the SF in the MEC platform performs local service chain control.
  • Step 1209 The co-located 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.
  • Figure 12 takes the example of sending routing rules to the co-located network element in the N4 session modification request.
  • 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 In 1206, SMF sends routing rules to co-located network elements. If the routing rule is carried in the N4 session establishment request, steps 1208-1209 can be omitted.
  • Step 1210 to step 1211 are the same as step 1112 and step 1113, and will not be repeated in this embodiment of the present application.
  • FIG. 13 shows another specific implementation of a service flow routing method provided by an embodiment of the present application, and the method includes:
  • Step 1301 to step 1307 are the same as step 1101 to step 1107, and details are not described herein again in the embodiment of the present application.
  • 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.
  • the N4 session establishment request carries the first indication information, RAN tunnel information, PSA tunnel information, and L-PSA tunnel information.
  • the first indication information is used to instruct the I-UPF to allocate dedicated tunnel information to establish the first dedicated tunnel between the I-UPF and the L-PSA and the second dedicated tunnel between the I-UPF and the PSA.
  • Other parameter information is based on the prior art, such as RAN tunnel information, PSA tunnel information, and L-PSA tunnel information, which will not be repeated in the present invention.
  • 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.
  • specific I-UPF tunnel information for PSA is the above-mentioned second dedicated tunnel information.
  • the specific I-UPF tunnel information for L-PSA is the above-mentioned first dedicated tunnel information.
  • 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.
  • I-UPF that is, combined (Set up network element) assign specific I-UPF tunnel information for PSA, and return an N4 session establishment response to the SMF network element.
  • 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-located, I-UPF may not allocate the following information: I-UPF tunnel information for L-PSA, specific I-UPF tunnel information for L-PSA.
  • 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.
  • the N4 session modification request carries routing rules.
  • the routing rule is used to instruct the I-UPF to perform the following processing for the service flow to be executed or the first service chain control is executed:
  • the service flow received from the first dedicated tunnel ie, the dedicated tunnel between I-UPF and L-PSA, that is, the message header carries specific I-UPF tunnel info for L-PSA is sent to the PSA.
  • the service flow received from the second dedicated tunnel (that is, the dedicated tunnel between the I-UPF and the PSA, that is, the message header carries the specific I-UPF tunnel info for PSA), is sent to the L-PSA.
  • Step 1312. The 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.
  • Figure 13 takes the routing rule sent to the I-UPF in the N4 session modification request as an example.
  • the SMF network element can also send routing rules in the N4 session establishment request, that is, in step 1310, the SMF sends the routing rule to the I-UPF.
  • UPF sends routing rules. If the routing rule is carried in the N4 session establishment request, step 1311 can be omitted.
  • forwarding rules are used to instruct I-UPF (ie co-located network elements) to execute the following steps for the service flow that is to be executed or that has executed the first service chain control One or more of:
  • I-UPF describes its processing logic as shown in Table 9.2:
  • 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.
  • the N4 session modification request successively carries the first forwarding rule, specific I-UPF tunnel information for PSA, and I-UPF tunnel information for PSA.
  • the first forwarding rule is used to instruct the PSA to send the downlink service flow to be executed for local service chain control to the I-UPF through the second dedicated tunnel between the PSA and the I-UPF.
  • the first forwarding rule is used to instruct the PSA to carry specific I-UPF tunnel information for PSA in the header of the downlink service flow to be executed for local service chain control.
  • Step 1314 The PSA returns an N4 session modification response to the SMF network element, so that the network element receives the N4 session modification response.
  • 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.
  • 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.
  • the second forwarding rule is used to instruct the L-PSA to send the upstream 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.
  • the second forwarding rule is used to instruct the L-PSA to carry specific I-UPF tunnel information for L-PSA in the header of the uplink service flow that has performed local service chain control.
  • L-PSA 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.
  • L-PSA is the GTP-U header encapsulated by SDF1 and contains specific I-UPF tunnel information for L-PSA.
  • Step 1316 The 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.
  • step 1315 and step 1316 can be omitted.
  • Figure 14 provides another service flow routing method of the present application.
  • the difference between this method and the embodiment shown in Figure 13 lies in the implementation shown in Figure 14
  • a dedicated tunnel is established between L-PSA and PSA.
  • the transmission of the service flow between L-PSA and PSA needs to be implemented through I-UPF transfer.
  • the method includes:
  • Steps 1401 to 1405 are the same as steps 1101 to 1105, and details are not described herein again in the embodiment of the present application.
  • 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 the 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 PSA and L-PSA.
  • Step 1407 The L-PSA allocates dedicated tunnel information according to the first indication information.
  • Step 1408 The 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.
  • the N4 session establishment response carries L-PSA tunnel information and specific L-PSA tunnel information for PSA.
  • L-PSA tunnel information is used to establish a tunnel connection between I-UPF and L-PSA. This parameter is in the prior art, and will not be repeated in the present invention.
  • 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.
  • the N4 session establishment request carries RAN tunnel information, PSA tunnel information, and L-PSA tunnel information.
  • 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.
  • 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.
  • the first forwarding rule is used to instruct the PSA to send the downstream service flow for which service chain control is to be executed 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 L-PSA through SMF to establish a dedicated tunnel connection between L-PSA and PSA.
  • the second instruction information and the first forwarding rule have the same parameters, that is, the second instruction information is implemented by the first forwarding rule.
  • Step 1412 the PSA allocates dedicated tunnel information according to the second indication information, that is, specific PSA tunnel information for L-PSA, which is used to establish dedicated tunnel information between the L-PSA and the PSA.
  • the dedicated tunnel information between the L-PSA and the PSA is used by the PSA to identify that the service flow originates from the L-PSA, that is, the service flow carrying the dedicated tunnel information indicates that the service flow originates from the PSA.
  • Step 1413 The 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 the PSA according to the second indication information.
  • 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.
  • 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.
  • the second forwarding rule is used to instruct the L-PSA to send the uplink service flow that has performed local service chain control to the PSA through a dedicated tunnel, that is, the packet header of the uplink service flow that has performed local service chain control carries specific PSA tunnel information for L-PSA.
  • 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 packet header of the downlink service flow carries specific L-PSA tunnel information for PSA.
  • I-UPF tunnel information for L-PSA is used to establish a tunnel between L-PSA and I-UPF, that is, the header of the service flow sent by L-PSA to I-UPF carries I-UPF tunnel information for L-PSA.
  • Step 1415 The PSA returns an N4 session modification response to the SMF network element.
  • FIG. 15 shows a specific implementation of another service flow routing method provided by an embodiment of the present application, and the method includes:
  • Step 1501 to step 1505 are the same as step 1101 to step 1105.
  • 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.
  • the N4 session establishment request carries L-PSA tunnel information.
  • Step 1507 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 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, I-UPF tunnel information for RAN.
  • I-UPF tunnel information for PSA used to establish a tunnel between PSA and I-UPF
  • I-UPF tunnel information for L-PSA used to establish a tunnel between L-PSA and I-UPF
  • I-UPF tunnel information for RAN used to establish a tunnel between RAN and I-UPF.
  • 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 routing rules.
  • the routing rule is used to instruct the I-UPF to execute the service flow or the local service chain control has been executed, and perform the following processing:
  • the rule can also be described as: for the received service flow with flag from the L-PSA, send it to the PSA.
  • the rule can also be described as: for the received service flow with flag from the PSA, send it to the L-PSA.
  • routing rule is also used to instruct the I-UPF to send the received downlink service flow to the RAN.
  • I-UPF judges the source of the service flow based on the following information:
  • the upstream service flow originates from the RAN.
  • the upstream service flow comes from L-PSA.
  • the packet header of the service flow carries I-UPF tunnel information for PSA, the downlink service flow comes from the PSA.
  • the downlink service flow comes from L-PSA.
  • Step 1509 The 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.
  • step 1506 the routing rules are carried in step 1506
  • steps 1508 and 1509 can be omitted.
  • no routing rules are carried in step 1508.
  • 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.
  • the N4 session modification request carries the first forwarding rule and I-UPF tunnel information for PSA.
  • the first forwarding rule is used to instruct the PSA to execute the service flow of local service chain control, and perform the following processing:
  • the PSA adds a flag to the header of the service flow for which local service chain control is to be executed and sends it to I-UPF.
  • the PSA adds flag to the header of the downlink service flow that has been executed by the central DN and the service chain control is to be executed. And send it to I-UPF.
  • Step 1511 the PSA returns an N4 session modification response to the SMF network element, so that the SMF network element receives the N4 session modification response.
  • 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.
  • the N4 session modification request carries the second forwarding rule and I-UPF tunnel information for L-PSA.
  • the second forwarding rule is used to instruct L-PSA to perform the following processing on the service flow for which local service chain control has been performed:
  • Step 1513 The 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.
  • the first offload entity 20 is the source I-UPF
  • the second offload entity 60 is the target I-UPF
  • the third functional entity 70 is the L- PSA2
  • the first functional entity 30 is L-PSA1 as an example
  • the method includes:
  • Step 1601 The SMF network element determines to change the I-UPF and L-PSA.
  • the terminal Before step 1601, the terminal has established a certain 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; user plane connection 2 It is: terminal ⁇ RAN ⁇ source I-UPF ⁇ PSA.
  • Step 1602 the SMF network element selects the target L-PSA, that is, L-PSA2.
  • SMF selects L-PSA2 according to the terminal location.
  • 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.
  • Step 1604 The 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 the L-PSA2.
  • the N4 session establishment response carries L-PSA2 tunnel information.
  • L-PSA2 tunnel information is tunnel information allocated by L-PSA2.
  • Step 1605 The SMF network element selects the target I-UPF, and establishes a forwarding tunnel between the target I-UPF and the source I-UPF.
  • 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.
  • the uplink tunnel between the target I-UPF and L-PSA2 can be established through L-PSA2 tunnel information.
  • L-PSA2 tunnel information For example, when the target I-UPF sends a service flow to L-PSA2, when the downstream service flow or the upstream service flow, the L-PSA2 tunnel information is carried in the header of the service flow.
  • a downlink tunnel between the target I-UPF and the RAN can be established.
  • the RAN tunnel information is carried in the packet header of the downlink service flow.
  • an uplink tunnel between the target I-UPF and the PSA can be established.
  • the PSA tunnel information is carried in the header of the uplink service flow.
  • the target I-UPF After that, 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, target I-UPF tunnel information for L-PSA2.
  • target I-UPF tunnel information for L-PSA1 is used to establish a downlink tunnel between target I-UPF and L-PSA1, so that the header of the service flow sent by L-PSA1 to target I-UPF can carry target I-UPF tunnel information for L-PSA1.
  • target I-UPF tunnel information for source I-UPF is used to establish a downlink tunnel between source I-UPF and target I-UPF, so that the header of the service flow sent from source I-UPF to target I-UPF can carry target I-UPF tunnel information for source I-UPF.
  • target I-UPF tunnel information for L-PSA2 is used to establish a downlink tunnel between L-PSA2 and target I-UPF, so that the header of the service flow sent by L-PSA2 to target I-UPF can carry target I- UPF tunnel information for L-PSA2.
  • 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.
  • the N4 session modification request carries target I-UPF tunnel information for source I-UPF.
  • Step 1607 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.
  • the N4 session modification response carries source I-UPF tunnel information for target I-UPF.
  • source I-UPF tunnel information for target I-UPF is used to establish an uplink tunnel between source I-UPF and target I-UPF, so that the header of the service flow sent from target I-UPF to source I-UPF can be carried source I-UPF tunnel information for target I-UPF.
  • 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.
  • the N4 session modification request carries source I-UPF tunnel information for target I-UPF and forwarding rules.
  • 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: when the source I-UPF (that is, from the forwarding tunnel between the source I-UPF and the target I-UPF, the report When the header carries target I-UPF tunnel information for source I-UPF), when the service flow is received, it does not need to be sent to L-PSA2, but can be sent to the RAN.
  • the forwarding rule is also used to instruct the target I-UPF to perform the following processing on the service flow for which local service chain control is to be performed: When the service flow is received from the PSA (that is, the packet header carries the target I-UPF tunnel information for PSA), send L -PSA2.
  • the forwarding rule can also be understood as a kind of indication information.
  • Step 1609 The target I-UPF returns an N4 session modification response to the SMF network element.
  • 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 target I-UPF tunnel information for PSA. PSA returns the N4 session modification response.
  • Step 1611 the SMF network element sends an N4 session modification request to the L-PSA2, so that the L-PSA2 receives the N4 session modification request.
  • the N4 session modification request carries target I-UPF tunnel information for L-PSA2.
  • Step 1612 L-PSA2 returns an N4 session modification response to the SMF network element.
  • 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 L-PSA2, so that L-PSA2 can control the local service chain.
  • 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, which carries the target I-UPF tunnel information for RAN. The RAN returns an N2 response.
  • I-UPF is changed from source I-UPF to target I-UPF in Figure 16, because PSA may also change the downlink service flow C (this downlink service flow C is the service flow to be controlled by the first service chain).
  • the source I-UPF for example, downlink service flow path 1
  • the source I-UPF receives the downlink service flow C from the PSA, it can still send the downlink service flow C to L-PSA1 so that L -The MEC platform corresponding to PSA1 performs service chain control on the downstream service flow C.
  • the source I-UPF sends the downlink service flow C that has executed the service chain control to the target I-UPF, and then sends it back to the RAN.
  • FIG. 17 shows another service flow routing method provided by an embodiment of the present application.
  • the target I-UPF sends the downlink service flow to L-PSA2 uses the MEC corresponding to L-PSA2 to perform traffic steering control on the service flow, and the source I-UPF can forward the downlink service flow from the PSA to the target I-UPF, and it does not need to control the downlink service from the PSA.
  • the flow is forwarded to L-PSA1, so that the MEC corresponding to L-PSA1 performs traffic steering control on the service flow.
  • Step 1701 to step 1704 are the same as step 1601 to step 1604.
  • 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.
  • the N4 session modification request carries target I-UPF tunnel information for source I-UPF and forwarding rules.
  • 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:
  • the source I-UPF sends the downlink service flow to the target I-UPF, That is, the downlink traffic 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 traffic flow is encapsulated with the target I-UPF tunnel information for the source I-UPF.
  • the forwarding rule in step 1705 includes a detection rule and a forwarding action.
  • the detection rule includes the 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 executed for local service chain control is forwarded to the target I-UPF.
  • the source I-UPF it does not need to determine whether the downstream service flow from the PSA is a service flow for which local service chain control is to be performed. Once the source I-UPF determines that it receives the downstream service flow from the PSA, it will send the downstream service flow from the PSA. The service flow is forwarded to the target I-UPF.
  • 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.
  • the N4 session modification response carries source I-UPF tunnel information for target I-UPF.
  • 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.
  • the N4 session modification request carries source I-UPF tunnel info information for target I-UPF and forwarding rules.
  • 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: No matter from the source I-UPF (that is, from the forwarding tunnel between the source I-UPF and the target I-UPF, the report When the header carries the target I-UPF tunnel information for source I-UPF, or when the service flow is received from the PSA (that is, the header carries the target I-UPF tunnel information for PSA), it is sent to L-PSA2.
  • Step 1708 The target I-UPF returns an N4 session modification response to the SMF network element.
  • the forwarding rule in step 1707 includes a detection rule and a forwarding action.
  • the detection rule includes the 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 executed for local service chain control is forwarded to the L-PSA2.
  • the target I-UPF it does not need to determine whether the downlink service flow from the PSA or the downlink service flow from the source I-UPF is a service flow to be executed for local service chain control. Once the target I-UPF determines that it has received the service flow from the PSA or Source the description information of the downlink service flow of the I-UPF exists in the detection rule, and then forward the downlink service flow to L-PSA2.
  • the SMF network element After the SMF network element receives the service chain policy information from the PCF network element, it 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 issue service chain information 1 to the L-PSA according to DNAI and service chain policy information.
  • the service chain strategy corresponds to the upstream direction of service flow C, namely 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.
  • the service chain information 1 sent by the SMF network element to the L-PSA is (only the above behavior examples are explained): SDF1 needs to be processed by SF1 and SF2; the service chain information 2 sent to the PSA is: SDF1 needs to go through SF3, SF4 deal with.
  • the SMF network element 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 corresponding service chain information to L-PSA and PSA respectively.
  • the uplink direction the SMF network element delivers 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.
  • Downlink direction The SMF network element issues service chain information to the PSA.
  • the service chain information indicates that SDF2 needs to be processed by SF3, SF4, SF5, and SF2.
  • each network element such as the session management network element, the first offloading entity, the first functional entity, and the second functional entity, etc., in order to realize the above functions, includes the corresponding hardware structure and/or software module for performing each function. .
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiment of this application can divide the functional units according to the above-mentioned method example session management network element, the first offload entity, the first functional entity, and the second functional entity.
  • each functional unit can be divided corresponding to each function, or two Or two or more functions are integrated in one processing unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 18 shows a communication device involved in the foregoing embodiment, and the communication device may include: a communication unit 102 and a processing unit 101.
  • the communication device is a session management network element, or a chip applied to the session management network element.
  • the processing unit 101 is configured to support the communication device to execute the step 601 in FIG. 6 by the session management network element in FIG. 6 of the foregoing embodiment.
  • the communication unit 102 is configured to support the communication device to perform the sending action performed by the session management network element in step 602 in FIG. 6.
  • the communication unit 102 is further configured to support the communication device to perform the actions received by the session management network element in step 606 in the above embodiment, (step 607, step 610, step 611, step 612, The sending action performed by the session management network element in step 613, step 616, and 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 configured to support the communication device to execute the actions processed by the session management network element in step 609 and step 614 in the foregoing embodiment.
  • the communication device is a first offload entity, or a chip applied to the first offload entity.
  • the communication unit 102 is configured to support the communication device to perform the action received by the first offload entity in step 602 in the foregoing embodiment.
  • the processing unit 101 is configured to support the communication device to perform the action processed by the first offload entity in step 603 in the foregoing embodiment.
  • the communication unit 102 is also used for the communication device to perform the action received by the first offload entity in step 607 and the action received by the first offload entity in step 608 in the foregoing embodiment.
  • the communication device is a session management network element, or a chip applied to the session management network element.
  • the communication unit 102 is configured to support the communication device to perform the action sent by the session management network element in step 1002 in the foregoing embodiment.
  • the processing unit 101 is configured to support the communication device to perform the actions processed by the session management network element in step 1001 of the foregoing embodiment.
  • the communication unit 102 is also used for the communication device to execute the actions sent by the session management network element in step 1004, step 1006, step 1007, and step 1010 in the foregoing 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.
  • the processing unit 101 is configured to support the communication device to perform the action of autonomously acquiring information for establishing a dedicated tunnel by the session management network element in step 1009.
  • FIG. 19 shows a schematic diagram of a possible logical structure of the communication device involved in the foregoing embodiment.
  • 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.
  • the processing module 112 is used to perform information/data processing steps on the communication device.
  • the communication module 113 is used to support the communication device to send or receive information/data.
  • the communication device may further include a storage module 111 for storing program codes and data that can be used by the communication device.
  • the communication device is a session management network element, or a chip applied to the session management network element.
  • the processing module 112 is configured to support the communication device to execute step 601 in FIG. 6 by the session management network element in FIG. 6 of the foregoing embodiment.
  • the communication module 113 is configured to support the communication device to perform the sending action performed by the session management network element in step 602 in FIG. 6.
  • the communication module 113 is also used to support the communication device to perform the actions received by the session management network element in step 606 in the above embodiment, (step 607, step 610, step 611, step 612, The sending action performed by the session management network element in step 613, step 616, and 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 also used to support the communication device to execute the actions processed by the session management network element in step 609 and step 614 in the foregoing embodiment.
  • the communication device is a first offload entity, or a chip applied to the first offload entity.
  • the communication module 113 is used to support the communication device to perform the action received by the first offload entity in step 602 in the above embodiment.
  • the processing module 112 is configured to support the communication device to perform the action processed by the first offload entity in step 603 in the foregoing embodiment.
  • the communication module 113 is also used for the communication device to perform the action received by the first offload entity in step 607 and the action received by the first offload entity in step 608 in the foregoing embodiment.
  • the communication device is a session management network element, or a chip applied to the session management network element.
  • the communication module 113 is configured to support the communication device to execute the action sent by the session management network element in step 1002 in the foregoing embodiment.
  • the processing module 112 is configured to support the communication device to execute the action processed by the session management network element in step 1001 of the foregoing embodiment.
  • the communication module 113 is also used for the communication device to execute the actions sent by the session management network element in step 1004, step 1006, step 1007, and step 1010 in the foregoing embodiment.
  • the communication module 113 is also used to support the communication device to perform the actions received by the session management network element in step 1009.
  • the processing module 112 is configured to support the communication device to perform the action of autonomously acquiring information for establishing a dedicated tunnel by the session management network element in step 1009.
  • the processing module 112 may be a processor or a controller, for example, a central processing unit, a general-purpose 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 logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination that implements computing functions, for example, a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on.
  • the communication module 113 may be a transceiver, a transceiver circuit, or a communication interface.
  • the storage module 111 may be a memory.
  • the processing module 112 is the processor 41 or the processor 45
  • the communication module 113 is the communication interface 43
  • the storage module 111 is the memory 42
  • the communication device involved in this application may be the communication device shown in FIG. 4.
  • FIG. 20 is a schematic diagram of the structure of a chip 150 provided by an embodiment of the present application.
  • the chip 150 includes one or more (including two) processors 1510 and a communication interface 1530.
  • the chip 150 further includes a memory 1540.
  • the memory 1540 may include a read-only memory and a random access memory, and provides operation instructions and data to the processor 1510.
  • a part of the memory 1540 may also include a non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 1540 stores the following elements, execution modules or data structures, or their subsets, or their extended sets.
  • the corresponding operation is executed by calling the operation instruction stored in the memory 1540 (the operation instruction may be stored in the operating system).
  • One possible implementation manner is that the structures of the chips used by the session management network element and the first offload entity are similar, and different devices can use different chips to realize their respective functions.
  • the processor 1510 controls the processing operations of any one of the session management network element and the first offload entity.
  • the processor 1510 may also be referred to as a central processing unit (CPU).
  • the memory 1540 may include a read-only memory and a random access memory, and provides instructions and data to the processor 1510. A part of the memory 1540 may also include NVRAM.
  • the memory 1540, the communication interface 1530, and the memory 1540 are coupled together by a bus system 1520, where the bus system 1520 may include a power bus, a control bus, and a status signal bus in addition to a data bus.
  • bus system 1520 may include a power bus, a control bus, and a status signal bus in addition to a data bus.
  • various buses are marked as the bus system 1520 in FIG. 20.
  • the method disclosed in the foregoing embodiments of the present application may 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 an integrated logic circuit of hardware in the processor 1510 or instructions in the form of software.
  • the above-mentioned processor 1510 may be a general-purpose processor, a digital signal processing (digital signal processing, DSP), an ASIC, an off-the-shelf programmable gate array (field-programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistors. Logic devices, discrete hardware components.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • 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 foregoing method in combination with its hardware.
  • the communication interface 1530 is used to perform the receiving and sending steps of the session management network element and the first offloading entity in the embodiments shown in FIGS. 6-17.
  • the processor 1510 is configured to execute the processing steps of the session management network element and the first offload entity in the embodiments shown in FIG. 6 to FIG. 17.
  • the above communication unit may be a communication interface of the device for receiving signals from other devices.
  • the communication unit is a communication interface for the chip to receive signals or send signals from other chips or devices.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium.
  • the instructions are executed, the functions of the session management network elements shown in Figs. 6-9 and 11-17 are realized.
  • a computer-readable storage medium stores instructions. When the instructions are executed, the functions of the session management network element as shown in FIG. 10 are realized.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium.
  • the instructions are executed, the functions of the first shunt entity as shown in Figs. 6-17 are realized.
  • a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of the session management network element shown in Figure 6 to Figure 17 are realized.
  • a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of the first shunt entity as shown in Figs. 6-17 are realized.
  • a chip is provided.
  • the chip is applied to a network management element.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled with at least one processor.
  • a chip is provided.
  • the chip is applied to a Donor node.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor. The function of the first diverging entity.
  • An embodiment of the present application provides a communication system, which includes: a session management network element and a first offload entity.
  • the session management network element is used to perform any of the steps performed by the session management network element in Figures 6-17
  • the first offloading entity is used to perform any of the steps performed by the first offloading entity in Figures 6 to 17 step.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer programs or instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, network equipment, user equipment, or other programmable devices.
  • 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.
  • the computer program or instruction may be downloaded from a website, computer, The server or data center transmits to another website site, computer, server or data center through wired or wireless means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that integrates one or more available media.
  • the usable medium may be a magnetic medium, such as a floppy disk, a hard disk, and a magnetic tape; it may also be an optical medium, such as a digital video disc (digital video disc, DVD); and it may also be a semiconductor medium, such as a solid state drive (solid state drive). , SSD).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供一种业务流的路由方法、装置及系统, 涉及通信技术领域, 用以实现将业务流在本地执行业务链控制之后继续发送至central DN. 该方法包括: 会话管理网元确定路由规则, 路由规则用于指示第一分流实体将第一业务流发送至第一功能实体,和/或, 将第二业务流发送至第二功能实体或接入设备, 第一业务流为待执行第一业务链控制的业务流, 第二业务流为已执行第一业务链控制的业务流; 在会话管理过程中, 会话管理网元向第一分流实体发送路由规则.

Description

一种业务流的路由方法、装置及系统 技术领域
本申请实施例涉及通信技术领域，尤其涉及一种业务流的路由方法、装置及系统。
背景技术
移动通信的飞速发展促进了各种新型业务的不断涌现，除了传统的移动宽带、物联网之外，移动通信催生了许多应用领域(如增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)、车联网、工业控制、物联网(internet of things，IOT)等)同时对网络带宽、时延等性能也提出了更高的需求，网络负荷进一步加重。
为了给用户提供更好的增值服务，引入了业务链控制(traffic steering control)，业务链控制指的是，业务流由一系列有序的服务功能网元(service function，SF)作增强处理。其中这些SF位于数据网络(data network，DN)中。SF可以是运营商部署的功能网元，也可以是第三方部署的功能网元。
如图1所示，在4G网络中可以由数据包网络网关(packet data network gateway，PGW)根据业务链策略，对收到的业务流执行traffic steering control。具体过程包括：
步骤1、策略与计费规则功能单元(policy and charging rules function，PCRF)确定对业务流激活业务链控制。
步骤2、PCRF向策略及计费执行功能(policy and charging enforcement function，PCEF)发送策略与计费控制(Policy and Charging Control，PCC)规则。其中，PCC规则包括：业务流的标识和业务链策略的标识。其中，PCEF位于PGW中。PGW与PCRF之间的接口为Gx接口。
步骤3、PGW根据业务链策略，对业务流的标识确定的业务流发送给中心(central)DN中的各个SF以执行traffic steering control。
在4G网络中，traffic steering control位于PGW与中心(central)DN之间。但是，PGW所在位置可能距离终端较远，如果由PGW将业务流发送给各个SF执行traffic steering control，可能会产生较大时延。
发明内容
本申请实施例提供一种业务流的传输方法、装置及系统，用以实现将业务流在本地执行业务链控制之后继续发送至central DN。
为了达到上述目的，本申请实施例提供如下技术方案：
第一方面，本申请实施例提供一种业务流的路由方法，包括：会话管理网元确定路由规则，该路由规则用于指示第一分流实体将第一业务流发送至第一功能实体，和/或，将第二业务流发送至第二功能实体或接入设备，第一业务流为待执行第一业务链控制的业务流，第二业务流为已执行第一业务链控制的业务流。在会话管理过程中，会话管理网元向第一分流实体发送路由规则。
本申请实施例提供一种业务流的路由方法，该方法中会话管理网元确定路由规则，并将路由规则发送给第一分流实体，这样第一分流实体便可以根据路由规则，对符合路由规则的业务流执行相应的转发动作。例如，第一分流实体可以将路由规则中记录 的第一业务流转发给第一功能实体，这是由于第一业务流通常为待执行第一业务链控制的业务流，这样可以由第一功能实体对应的MEC平台中的SF对第一业务流执行第一业务链控制。此外，由于第一功能实体通常部署在距离终端较近的位置，这样可以尽早对第一业务流执行第一业务链控制，如视频加速、防火墙、负载均衡功能，以使第一业务流得到尽早处理，如防火墙功能，可以尽早将无效业务流过滤掉。再者，本申请实施例中第一分流实体还可以将路由规则中记录的第二业务流发送至第二功能实体或接入设备。这是由于第二业务流为已执行第一业务链控制的业务流。这样可以实现对业务流执行第一业务链控制后发回第二功能实体。
在一种可能的实现方式中，路由规则包括第一业务流的描述信息和与第一业务流的描述信息关联的第一功能实体的信息，和/或，第二业务流的描述信息和第二业务流的描述信息关联的第二功能实体的信息或接入设备的信息。其中，描述信息包括第一业务流或第二业务流的来源信息。通过向第一分流实体指示向第一功能实体发送的第一业务流的描述信息，这样便于第一分流实体确定接收到的业务流的描述信息与第一业务流的描述信息相同时，将接收到的业务流发送至第一功能实体。通过向第一分流实体指示向第二功能实体发送的第二业务流的描述信息，这样便于第一分流实体确定接收到的业务流的描述信息与第二业务流的描述信息相同时，将接收到的业务流发送至第二功能实体或接入设备。
在一种可能的实现方式中，路由规则包括以下信息中的任一个或多个：第一业务流的描述信息指示第一业务流来自接入设备或第二功能实体时，第一分流实体向第一功能实体发送第一业务流。或，第二业务流的描述信息指示第二业务流来自第一功能实体时，第一分流实体向接入设备或第二功能实体发送第二业务流。
在一种可能的实现方式中，路由规则用于指示第一分流实体向第一功能实体发送来自第二专用隧道的第一业务流，和/或，指示第一分流实体向第二功能实体发送来自第一专用隧道的第二业务流。其中，第二专用隧道位于第一分流实体和第二功能实体之间。第一专用隧道位于第一分流实体和第一功能实体之间。这样便于第一分流实体确定将来自特定专用隧道的业务流发送至相应的功能实体。
在一种可能的实现方式中，本申请实施例提供的方法还包括：会话管理网元获取用于建立第一专用隧道的第一专用隧道信息和用于建立第二专用隧道的第二专用隧道信息中的一个或多个。便于后续建立第一专用隧道和第二专用隧道中的一个或多个。
在一种可能的实现方式中，本申请实施例提供的方法还包括：会话管理网元向第二功能实体发送第二专用隧道信息以及第一转发规则，第一转发规则用于指示第二功能实体通过第二专用隧道向第一分流实体传输第一业务流。通过发送第一转发规则和第一专用隧道信息，这样第二功能实体后续可以将待执行业务链控制的第一业务流由第一专用隧道向第一分流实体传输。
在一种可能的实现方式中，本申请实施例提供的方法还包括：会话管理网元向第一功能实体发送第一专用隧道信息以及第二转发规则，该第二转发规则用于指示第一功能实体通过第一专用隧道向第一分流实体传输第二业务流。通过发送第二转发规则和第一专用隧道信息，这样第一功能实体后续可以将已执行业务链控制的第二业务流通过第一专用隧道传输给第一分流实体。
在一种可能的实现方式中，在会话管理网元获取第一专用隧道信息和第二专用隧道信息中的一个或多个之前，本申请实施例提供的方法还包括：会话管理网元向第一分流实体发送第一指示信息，该第一指示信息用于指示第一分流实体分配第一专用隧道信息和第二专用隧道信息中的一个或多个。相应的，会话管理网元获取第一专用隧道信息和第二专用隧道信息中的一个或多个，包括：会话管理网元接收来自第一分流实体的第一专用隧道信息和第二专用隧道信息中的一个或多个。也即会话管理网元除了可以自主分配第一专用隧道信息和第二专用隧道信息中的一个或多个外，还可以从第一分流实体处获取第一专用隧道信息和第二专用隧道信息中的一个或多个。
在一种可能的实现方式中，第一业务流和第一标识相关联，路由规则用于指示第一分流实体向第一功能实体发送与第一标识关联的业务流。或，第二业务流和第二标识相关联，路由规则用于指示第一分流实体向第二功能实体发送与第二标识关联的业务流。
在一种可能的实现方式中，本申请实施例提供的方法还包括：会话管理网元向第二功能实体发送用于指示第二功能实体在第一业务流的报文头中携带第一标识的第三指示信息。
在一种可能的实现方式中，本申请实施例提供的方法还包括：会话管理网元向第一功能实体发送用于指示第一功能实体在第二业务流的报文头中携带第二标识的第四指示信息。
在一种可能的实现方式中，本申请实施例提供的方法还包括：会话管理网元确定分流实体从第一分流实体变为第二分流实体。会话管理网元向第二分流实体发送用于指示第二分流实体执行以下步骤中的任一个或多个的第五指示信息：向接入设备发送来源于第一分流实体的第三业务流；或，向第二分流实体对应的第三功能实体发送来源于第二功能实体的第四业务流。其中，第三业务流已被执行业务链控制或者第三业务流为已执行第一业务链控制的业务流。第四业务流为待执行第一业务链控制的业务流。该方法可以在分流实体发生变化的情况下，可以将第四业务流发送给第三功能实体，以实现对第四业务流的业务链控制以及将已执行业务链控制的第一业务流由第二分流实体发送给接入设备。
在一种可能的实现方式中，本申请实施例提供的方法还包括：会话管理网元确定分流实体从第一分流实体变为第二分流实体。会话管理网元向第一分流实体发送第六指示信息，第六指示信息用于指示第一分流实体向第二分流实体发送来自第二功能实体的第五业务流。会话管理网元向第二分流实体发送第七指示信息，第七指示信息用于指示第二分流实体向第二分流实体对应的第三功能实体发送第二分流实体接收到的第五业务流。第五业务流为待执行第一业务链控制的业务流。该方法可以在分流实体发生变化的情况下，将第五业务流发送至第三功能实体，以由第三功能实体对应的MEC平台对第五业务流执行业务链控制。
在一种可能的实现方式中，路由规则还用于指示第一分流实体向接入设备或第二功能实体发送第六业务流，第六业务流为不需要执行业务链控制的业务流。
在一种可能的实现方式中，路由规则包括第六业务流的描述信息和第六业务流的描述信息关联的接入设备的信息或第二功能实体的信息。
第二方面，本申请实施例提供的一种业务流的传输方法，包括：在会话的会话管理过程中，第一分流实体接收来自会话管理网元的路由规则，路由规则用于指示第一分流实体将第一业务流发送至第一功能实体，和/或，将第二业务流发送至第二功能实体或接入设备，第一业务流为待执行第一业务链控制的业务流，第二业务流为已执行第一业务链控制的业务流。第一分流实体根据路由规则，传输第一分流实体接收到的目标业务流。
在一种可能的实现方式中，路由规则包括：第一业务流的描述信息和与第一业务流的描述信息关联的第一功能实体的信息，和/或，第二业务流的描述信息和第二业务流的描述信息关联的第二功能实体的信息或接入设备的信息。其中，描述信息包括第一业务流或第二业务流的来源信息。
在一种可能的实现方式中，第一分流实体根据路由规则，传输第一分流实体接收到的目标业务流，包括：目标业务流的描述信息与第一业务流的描述信息相同，第一分流实体向第一功能实体发送目标业务流。和/或，目标业务流的描述信息与第二业务流的描述信息相同，第一分流实体向第二功能实体或接入设备发送目标业务流。
在一种可能的实现方式中，路由规则用于指示第一分流实体向第一功能实体发送来自第二专用隧道的第一业务流，和/或，指示第一分流实体向第二功能实体发送来自第一专用隧道的第二业务流；其中，第二专用隧道位于第一分流实体和第二功能实体之间，第一专用隧道位于第一分流实体和第一功能实体之间。
在一种可能的实现方式中，第一分流实体根据路由规则，传输第一分流实体接收到的目标业务流，包括：目标业务流来源于第二专用隧道，第一分流实体将目标业务流发送至第一功能实体；或，目标业务流来源于第一专用隧道，第一分流实体将目标业务流发送至第二功能实体。
在一种可能的实现方式中，本申请实施例提供的方法还包括：第一分流实体接收来自会话管理网元的用于指示第一分流实体分配第一专用隧道信息和第二专用隧道信息中的一个或多个的第一指示信息。第一专用隧道信息用于建立第一专用隧道。第二专用隧道信息用于建立第二专用隧道。第一分流实体向会话管理网元发送第一专用隧道信息和第二专用隧道信息中的一个或多个。
在一种可能的实现方式中，第一业务流和第一标识相关联，路由规则用于指示第一分流实体向第一功能实体发送与第一标识关联的业务流；或，第二业务流和第二标识相关联，路由规则用于指示第一分流实体向第二功能实体发送与第二标识关联的业务流。
在一种可能的实现方式中，第一分流实体根据路由规则，传输第一分流实体接收到的目标业务流，包括：业务流与第一标识关联，第一分流实体向第一功能实体发送目标业务流；或，目标业务流与第二标识关联，第一分流实体向第二功能实体发送目标业务流。
在一种可能的实现方式中，路由规则还用于指示第一分流实体向接入设备或第二功能实体发送第三业务流，该第三业务流为会话中不需要执行业务链控制的业务流。
在一种可能的实现方式中，路由规则包括第三业务流的描述信息和第三业务流的描述信息关联的接入设备的信息或第二功能实体的信息。
在一种可能的实现方式中，第一分流实体根据路由规则，传输第一分流实体接收到的目标业务流，包括：目标业务流的描述信息与第三业务流的描述信息相同，则第一分流实体向接入设备或第二功能实体发送目标业务流。
第三方面，本申请实施例提供一种业务流的传输方法，包括：会话管理网元获取第一路由规则和第二路由规则中的一个或多个，第一路由规则用于指示第一功能实体通过第一功能实体和第二功能实体之间的专用隧道向第二功能实体发送第二业务流。第二路由规则用于指示第二功能实体通过专用隧道向第一功能实体发送第一业务流；其中，第一业务流为待执行第一业务链控制的业务流，第二业务流为已执行第一业务链控制的业务流；会话管理网元向第一功能实体发送第一路由规则；和/或，会话管理网元向第二功能实体发送第二路由规则。
在一种可能的实现方式中，本申请实施例提供的方法还包括：会话管理网元获取用于建立专用隧道的信息。会话管理网元向第一功能实体或第二功能实体发送专用隧道的信息。
在一种可能的实现方式中，会话管理网元获取用于建立专用隧道的信息之前，本申请实施例提供的方法还包括：会话管理网元向第一功能实体发送用于指示第一功能实体分配用于建立专用隧道的信息的第一指示信息。或，会话管理网元向第二功能实体发送用于指示第二功能实体分配用于建立专用隧道的信息的第二指示信息。
第四方面，本申请实施例提供一种通信装置，该一种通信装置可以实现第一方面或第一方面的任意一种可能的实现方式中描述的一种业务流的路由方法，因此也可以实现第一方面或第一方面任意一种可能的实现方式中的有益效果。该一种通信装置可以为会话管理网元，也可以为可以支持会话管理网元实现第一方面或第一方面的任意一种可能的实现方式中的装置。例如应用于会话管理网元中的芯片。该一种通信装置可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
一种示例，本申请实施例提供一种通信装置，包括：处理单元，用于确定路由规则，路由规则用于指示第一分流实体将第一业务流发送至第一功能实体，和/或，将第二业务流发送至第二功能实体或接入设备，第一业务流为待执行第一业务链控制的业务流，第二业务流为已执行第一业务链控制的业务流；在会话的会话管理过程中，通信单元，用于向第一分流实体发送路由规则。
在一种可能的实现方式中，路由规则包括第一业务流的描述信息和与第一业务流的描述信息关联的第一功能实体的信息，和/或，第二业务流的描述信息和第二业务流的描述信息关联的第二功能实体的信息或接入设备的信息。其中，描述信息包括第一业务流或第二业务流的来源信息。
在一种可能的实现方式中，路由规则包括以下信息中的任一个或多个：第一业务流的描述信息指示第一业务流来自接入设备或第二功能实体时，第一分流实体向第一功能实体发送第一业务流；或，第二业务流的描述信息指示第二业务流来自第一功能实体时，第一分流实体向接入设备或第二功能实体发送第二业务流。
在一种可能的实施例中，路由规则用于指示第一分流实体向第一功能实体发送来自第二专用隧道的第一业务流，和/或，指示第一分流实体向第二功能实体发送来自第一专用隧道的第二业务流。其中，第二专用隧道位于第一分流实体和第二功能实体之 间，第一专用隧道位于第一分流实体和第一功能实体之间。
在一种可能的实现方式中，处理单元，还用于获取用于建立第一专用隧道的第一专用隧道信息和用于建立第二专用隧道的第二专用隧道信息中的一个或多个。
在一种可能的实现方式中，通信单元，还用于向第二功能实体发送第二专用隧道信息以及第一转发规则。该第一转发规则用于指示第二功能实体通过第二专用隧道向第一分流实体传输第一业务流。
在一种可能的实现方式中，通信单元，还用于向第一功能实体发送第一专用隧道信息以及第二转发规则。第二转发规则用于指示第一功能实体通过第一专用隧道向第一分流实体传输第二业务流。
在一种可能的实现方式中，处理单元用于获取第一专用隧道信息和第二专用隧道信息中的一个或多个之前，通信单元，还用于向第一分流实体发送第一指示信息，第一指示信息用于指示第一分流实体分配第一专用隧道信息和第二专用隧道信息中的一个或多个。处理单元，具体用于通过通信单元接收来自第一分流实体的第一专用隧道信息和第二专用隧道信息中的一个或多个。
在一种可能的实现方式中，第一业务流和第一标识相关联，路由规则用于指示第一分流实体向第一功能实体发送与第一标识关联的业务流；或，第二业务流和第二标识相关联，路由规则用于指示第一分流实体向第二功能实体发送与第二标识关联的业务流。
在一种可能的实现方式中，通信单元，还用于向第二功能实体发送第三指示信息，该第三指示信息用于指示第二功能实体在第一业务流的报文头中携带第一标识。
在一种可能的实现方式中，通信单元，还用于向第一功能实体发送第四指示信息，第四指示信息用于指示第一功能实体在第二业务流的报文头中携带第二标识。
在一种可能的实现方式中，处理单元，还用于确定分流实体从第一分流实体变为第二分流实体。通信单元，还用于向第二分流实体发送第五指示信息，第五指示信息用于指示第二分流实体执行以下步骤中的任一个或多个：向接入设备发送来源于第一分流实体的第三业务流；或，向第二分流实体对应的第三功能实体发送来源于第二功能实体的第四业务流。其中，第三业务流已被执行业务链控制或者第三业务流为已执行第一业务链控制的业务流。第四业务流为待执行第一业务链控制的业务流。
在一种可能的实现方式中，处理单元，还用于确定分流实体从第一分流实体变为第二分流实体；通信单元，还用于向第一分流实体发送第六指示信息。该第六指示信息用于指示第一分流实体向第二分流实体发送来自第二功能实体的第五业务流。会话管理网元向第二分流实体发送第七指示信息，第七指示信息用于指示第二分流实体向第二分流实体对应的第三功能实体发送第二分流实体接收到的第五业务流。第五业务流为待执行第一业务链控制的业务流。
在一种可能的实现方式中，路由规则还用于指示第一分流实体向接入设备或第二功能实体发送第六业务流。其中，第六业务流为不需要执行业务链控制的业务流。
另一种示例，本申请实施例提供一种通信装置，该通信装置可以是会话管理网元，也可以是会话管理网元内的芯片。该通信装置可以包括：通信单元和处理单元。当该通信装置是会话管理网元时，该通信单元可以为通信接口。该通信装置还可以包括存 储单元。该存储单元可以是存储器。该存储单元，用于存储计算机程序代码，计算机程序代码包括指令。该处理单元可以是处理器。该处理单元执行该存储单元所存储的指令，以使该会话管理网元实现第一方面或第一方面的任意一种可能的实现方式中描述的一种业务流的路由方法。当该通信装置是会话管理网元内的芯片时，该处理单元可以是处理器，该通信单元可以统称为：通信接口。例如，通信接口可以为输入/输出接口、管脚或电路等。该处理单元执行存储单元所存储的计算机程序代码，以使该会话管理网元实现第一方面或第一方面的任意一种可能的实现方式中描述的一种业务流的路由方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该会话管理网元内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
可选的，处理器、通信接口和存储器相互耦合。
第五方面，本申请实施例提供一种通信装置，该装置可以实现第二方面或第二方面的任意一种可能的实现方式中描述的一种业务流的路由方法，因此也可以实现第二方面或第二方面任意一种可能的实现方式中的有益效果。该一种通信装置可以为第一分流实体，也可以为可以支持第一分流实体实现第二方面或第二方面的任意一种可能的实现方式中的装置。例如应用于第一分流实体中的芯片。该一种通信装置可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
一种示例，本申请实施例提供一种通信装置，包括：在会话的会话管理过程中，通信单元，用于接收来自会话管理网元的路由规则。该路由规则用于指示将第一业务流发送至第一功能实体，和/或，将第二业务流发送至第二功能实体或接入设备，第一业务流为待执行第一业务链控制的业务流，第二业务流为已执行第一业务链控制的业务流。通信单元，还用于根据路由规则，传输第一分流实体接收到的目标业务流。
在一种可能的实现方式中，路由规则包括第一业务流的描述信息和与第一业务流的描述信息关联的第一功能实体的信息，和/或，第二业务流的描述信息和第二业务流的描述信息关联的第二功能实体的信息或接入设备的信息。其中，第二业务流的描述信息包括第二业务流的来源信息。第一业务流的描述信息包括第一业务流的来源。
在一种可能的实现方式中，目标业务流的描述信息与第一业务流的描述信息相同，通信单元，具体用于向第一功能实体发送目标业务流；和/或，目标业务流的描述信息与第二业务流的描述信息相同，通信单元，具体用于向第二功能实体或接入设备发送目标业务流。
在一种可能的实现方式中，路由规则用于指示向第一功能实体发送来自第二专用隧道的第一业务流，和/或，指示向第二功能实体发送来自第一专用隧道的第二业务流。其中，第二专用隧道位于该装置和第二功能实体之间。第一专用隧道位于该装置和第一功能实体之间。
在一种可能的实现方式中，目标业务流来源于第二专用隧道，通信单元，具体用于将目标业务流发送至第一功能实体。或，目标业务流来源于第一专用隧道，通信单元，具体用于将目标业务流发送至第二功能实体。
在一种可能的实现方式中，通信单元，还用于接收来自会话管理网元的用于指示第一分流实体分配第一专用隧道信息和第二专用隧道信息中的一个或多个的第一指示 信息。其中，第一专用隧道信息用于建立第一专用隧道。第二专用隧道信息用于建立第二专用隧道。通信单元，还用于向会话管理网元发送第一专用隧道信息和第二专用隧道信息中的一个或多个。
在一种可能的实现方式中，第一业务流和第一标识相关联，路由规则用于指示向第一功能实体发送与第一标识关联的业务流。或，第二业务流和第二标识相关联，路由规则用于指示向第二功能实体发送与第二标识关联的业务流。
在一种可能的实现方式中，目标业务流与第一标识关联，通信单元，具体用于向第一功能实体发送目标业务流。或，目标业务流与第二标识关联，通信单元，具体用于向第二功能实体发送目标业务流。
另一种示例，本申请实施例提供一种通信装置，该装置可以是第一分流实体，也可以是第一分流实体内的芯片。该通信装置可以包括：通信单元和处理单元。当该通信装置是第一分流实体时，该通信单元可以为通信接口。该通信装置还可以包括存储单元。该存储单元可以是存储器。该存储单元，用于存储计算机程序代码，计算机程序代码包括指令。该处理单元可以是处理器。该处理单元执行该存储单元所存储的指令，以使该第一分流实体实现第二方面或第二方面的任意一种可能的实现方式中描述的一种业务流的路由方法。当该通信装置是第一分流实体内的芯片时，该处理单元可以是处理器，该通信单元可以统称为：通信接口。例如，通信接口可以为输入/输出接口、管脚或电路等。该处理单元执行存储单元所存储的计算机程序代码，以使该第一分流实体实现第二方面或第二方面的任意一种可能的实现方式中描述的一种业务流的路由方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该第一分流实体内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
可选的，处理器、通信接口和存储器相互耦合。
第六方面，本申请实施例提供一种通信装置，该装置可以实现第三方面或第三方面的任意一种可能的实现方式中描述的一种业务流的路由方法，因此也可以实现第三方面或第三方面任意一种可能的实现方式中的有益效果。该一种通信装置可以为会话管理网元，也可以为可以支持会话管理网元实现第三方面或第三方面的任意一种可能的实现方式中的装置。例如应用于会话管理网元中的芯片。该一种通信装置可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
一种示例，本申请实施例提供一种通信装置，包括：处理单元，用于获取第一路由规则和第二路由规则中的一个或多个。第一路由规则用于指示第一功能实体通过第一功能实体和第二功能实体之间的专用隧道向第二功能实体发送第二业务流。第二路由规则用于指示第二功能实体通过专用隧道向第一功能实体发送第一业务流。其中，第一业务流为待执行第一业务链控制的业务流，第二业务流为已执行第一业务链控制的业务流。通信单元，用于向第一功能实体发送第一路由规则；和/或，通信单元，用于向第二功能实体发送第二路由规则。
在一种可能的实现方式中，处理单元，还用于获取用于建立专用隧道的信息。通信单元，还用于向第一功能实体或第二功能实体发送专用隧道的信息。
在一种可能的实现方式中，处理单元，还用于获取用于建立专用隧道的信息之前， 通信单元，还用于向第一功能实体发送用于指示第一功能实体分配用于建立专用隧道的信息的第一指示信息。或，会话管理网元向第二功能实体发送用于指示第二功能实体分配用于建立专用隧道的信息的第二指示信息。
另一种示例，本申请实施例提供一种通信装置，该通信装置可以是会话管理网元，也可以是会话管理网元内的芯片。该通信装置可以包括：通信单元和处理单元。当该通信装置是会话管理网元时，该通信单元可以为通信接口。该通信装置还可以包括存储单元。该存储单元可以是存储器。该存储单元，用于存储计算机程序代码，计算机程序代码包括指令。该处理单元可以是处理器。该处理单元执行该存储单元所存储的指令，以使该会话管理网元实现第三方面或第三方面的任意一种可能的实现方式中描述的一种业务流的路由方法。当该通信装置是会话管理网元内的芯片时，该处理单元可以是处理器，该通信单元可以统称为：通信接口。例如，通信接口可以为输入/输出接口、管脚或电路等。该处理单元执行存储单元所存储的计算机程序代码，以使该会话管理网元实现第三方面或第三方面的任意一种可能的实现方式中描述的一种业务流的路由方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该会话管理网元内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
可选的，处理器、通信接口和存储器相互耦合。
第七方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序或指令，当计算机程序或指令在计算机上运行时，使得计算机执行如第一方面、或第一方面的任一种可能的实现方式中描述的方法。
第八方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序或指令，当计算机程序或指令在计算机上运行时，使得计算机执行如第二方面、或第二方面的任一种可能的实现方式中描述的方法。
第九方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序或指令，当计算机程序或指令在计算机上运行时，使得计算机执行如第三方面、或第三方面的任一种可能的实现方式中描述的方法。
第十方面，本申请实施例提供一种包括指令的计算机程序产品，当指令在计算机上运行时，使得计算机执行如第一方面或第一方面的任意一种可能的实现方式中描述的方法。
第十一方面，本申请实施例提供一种包括指令的计算机程序产品，当指令在计算机上运行时，使得计算机执行如第二方面或第二方面的任意一种可能的实现方式中描述的方法。
第十二方面，本申请实施例提供一种包括指令的计算机程序产品，当指令在计算机上运行时，使得计算机执行如第三方面或第三方面的任意一种可能的实现方式中描述的方法。
第十三方面，本申请实施例提供一种通信装置，该通信装置包括处理器和存储介质，存储介质存储有指令，指令被处理器运行时，实现如第一方面或第一方面的各种可能的实现方式描述的方法。
第十四方面，本申请实施例提供一种通信装置，该通信装置包括处理器和存储介 质，存储介质存储有指令，指令被处理器运行时，实现如第二方面或第二方面的各种可能的实现方式描述的方法。
第十五方面，本申请实施例提供一种通信装置，该通信装置包括处理器和存储介质，存储介质存储有指令，指令被处理器运行时，实现如第三方面或第三方面的各种可能的实现方式描述的方法。
第十六方面，本申请实施例提供一种通信装置，包括：至少一个处理器和通信接口，至少一个处理器和通信接口通过线路互联，至少一个处理器与存储器耦合，存储器用于存储计算机程序或指令，至少一个处理器用于执行存储器中的该计算机程序或指令，使得通信装置执行第一方面或第一方面的各种可能的实现方式中描述的方法。
第十七方面，本申请实施例提供一种通信装置，包括：至少一个处理器和通信接口，至少一个处理器和通信接口通过线路互联，至少一个处理器与存储器耦合，存储器用于存储计算机程序或指令，至少一个处理器用于执行存储器中的该计算机程序或指令，使得通信装置执行第二方面或第二方面的各种可能的实现方式中描述的方法。
第十八方面，本申请实施例提供一种通信装置，包括：至少一个处理器和通信接口，至少一个处理器和通信接口通过线路互联，至少一个处理器与存储器耦合，存储器用于存储计算机程序或指令，至少一个处理器用于执行存储器中的该计算机程序或指令，使得通信装置执行第三方面或第三方面的各种可能的实现方式中描述的方法。
在一种可能的实现方式中，第十六方面、第十七方面、第十八方面任一方面描述的装置中还可以包括：存储器。
第十九方面，本申请实施例提供一种芯片，该芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，至少一个处理器用于运行计算机程序或指令，以实现第一方面或第一方面的各种可能的实现方式中所描述的方法。通信接口用于与芯片之外的其它模块进行通信。
第二十方面，本申请实施例提供一种芯片，该芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，至少一个处理器用于运行计算机程序或指令，以实现第二方面或第二方面的各种可能的实现方式中所描述的方法。通信接口用于与芯片之外的其它模块进行通信。
第二十一方面，本申请实施例提供一种芯片，该芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，至少一个处理器用于运行计算机程序或指令，以实现第三方面或第三方面的各种可能的实现方式中所描述的方法。通信接口用于与芯片之外的其它模块进行通信。
本申请实施例提供的芯片还可以包括存储器，存储器用于存储计算机程序或指令。
第二十二方面，本申请实施例提供了一种通信装置，该通信装置包括一个或者多个模块，用于实现上述第一方面、第二方面、第三方面的方法，该一个或者多个模块可以与上述第一方面、第二方面、第三方面的方法的步骤相对应。
第二十三方面，本申请实施例提供一种通信装置，包括：至少一个处理器，至少一个处理器和存储器耦合，存储器用于存储计算机程序或指令，至少一个处理器用于执行存储器中的该计算机程序或指令，使得通信装置执行第一方面或第一方面的各种可能的实现方式中描述的方法。
第二十四方面，本申请实施例提供一种通信装置，包括：至少一个处理器，至少一个处理器和存储器耦合，存储器用于存储计算机程序或指令，至少一个处理器用于执行存储器中的该计算机程序或指令，使得通信装置执行第二方面或第二方面的各种可能的实现方式中描述的方法。
第二十五方面，本申请实施例提供一种通信装置，包括：至少一个处理器，至少一个处理器和存储器耦合，存储器用于存储计算机程序或指令，至少一个处理器用于执行存储器中的该计算机程序或指令，使得通信装置执行第三方面或第三方面的各种可能的实现方式中描述的方法。
第二十六方面，本申请实施例提供一种通信系统，该通信系统包括：第四方面或第四方面的各种可能的实现方式中描述的通信装置，以及第五方面或第五方面的各种可能的实现方式中描述的通信装置。
在一种可选的实现方式中，该通信系统还可以包括：第一功能实体、第二功能实体和接入设备。
具体的该通信系统中各个通信装置的所执行的具体步骤可以参考相应地方的描述，此处不再赘述。
第二十七方面，本申请实施例提供一种通信系统，该通信系统包括：第六方面或第六方面的各种可能的实现方式中描述的通信装置。
在一种可选的实现方式中，该通信系统还可以包括：第一功能实体、第二功能实体和接入设备。
具体的该通信系统中各个通信装置的所执行的具体步骤可以参考相应地方的描述，此处不再赘述。
本申请中第二方面至第二十七方面及其各种实现方式的有益效果，可以参考第一方面及其各种实现方式中的有益效果分析，此处不再赘述。
附图说明
图1为本申请实施例提供的现有技术中对业务流执行业务链控制的系统架构示意图；
图2a～图2f为本申请实施例提供的一种通信系统的架构示意图；
图3a～图3b为本申请实施例提供的一种5G架构示意图；
图4为本申请实施例提供的一种通信设备的结构示意图；
图5为本申请实施例提供的业务流分流场景示意图；
图6为本申请实施例提供的一种业务流的路由方法的流程示意图一；
图7为本申请实施例提供的一种业务流的路由方法的流程示意图二；
图8为本申请实施例提供的一种业务流的路由方法的流程示意图三；
图9a～图9b为本申请实施例提供的一种分流实体发生变化的架构图；
图10为本申请实施例提供的一种业务流的路由方法的流程示意图四；
图11～图17为本申请实施例提供的一种业务流的路由方法的具体流程示意图；
图18为本申请实施例提供的一种通信装置的结构示意图；
图19为本申请实施例提供的另一种通信装置的结构示意图；
图20为本申请实施例提供的一种芯片的结构示意图。
具体实施方式
本申请中“的(英文：of)”，相应的“(英文corresponding，relevant)”和“对应的(英文：corresponding)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。
为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。例如，第一功能实体和第二功能实体仅仅是为了区分不同的功能实体，并不对其先后顺序进行限定。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
需要说明的是，本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。
本申请实施例描述的系统架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。本申请实施例中以提供的方法应用于NR系统或5G网络中为例进行说明。
在介绍本申请实施例之前首先对本申请涉及到的相关名词作如下介绍：
1)、业务链控制指：在MEC平台或DN中由SF对业务流执行相应处理。例如，诸如执行以下处理中的一个或多个：防火墙功能、视频加速处理功能、负载均衡功能。
2)、本地业务链控制，指由L-PSA(对应第一功能实体)对应的MEC平台对业务流执行业务链控制。
3)、待执行第一业务链控制的业务流可以指该业务流尚未在MEC平台中由SF作处理，或该业务流尚未执行本地业务链控制。但是该业务流有可能已被PSA(对应第二功能实体)对应的DN中的SF处理，或者未被PSA(对应第二功能实体)对应的DN中的SF处理。
4)、已执行第一业务链控制的业务流可以指业务流已由MEC平台中的SF完成 对业务流的处理。
5)、上行业务流指：来自终端或接入设备50，且目的地址为中心DN的业务流。需要说明的是，目的地址为中心DN指的是目的地址为中心DN中的应用服务器的地址，该应用服务器与该业务流对应，为终端提供相应的应用业务。
6)、下行业务流指：来自中心DN，且目的地址为终端的业务流。
为了有效满足移动互联网、物联网高速发展所需的高带宽、低时延的要求并减轻网络负荷，欧洲电信标准化协会(European Telecommunication Standard Institute,ETSI)于2014年提出了移动边缘计算(mobile edge computing，MEC)技术。MEC是基于5G演进架构，是将基站与互联网业务深度融合的一种技术。第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)在无线接入网络(radio access network，RAN)3和业务与架构(service and architecture，SA)2子组中都有MEC相关立项。
基于上述描述，图2a示出了本申请实施例提供的一种业务流的路由方法适用的通信系统，该通信系统包括：会话管理网元10、第一分流实体20、第一功能实体30、第二功能实体40以及接入设备50。
其中，接入设备50可以通过移动管理网元与会话管理网元10通信。会话管理网元10与第一分流实体20通信、第一分流实体20、第一功能实体30和第二功能实体40通信。
本申请实施例中第一分流实体20可以将某些业务流分流到本地路由，或者决定将业务流分流到远端路由。
所谓的本地路由指第一分流实体20将业务流分流至第一功能实体30，由第一功能实体30将业务流传输至与第一功能实体30通信的MEC平台。
所谓的远端路由指第一分流实体20将业务流分流至第二功能实体40，由第二功能实体40将业务流传输至与第二功能实体30通信的数据网络(例如，中心数据网络(central DN))。
为了实现上述业务流的分流，会话管理网元10可以在会话的用户面路径上插入第一分流实体20作为分流点实现。也即第一分流实体20所对应的网元或者实体可以为具有对会话的业务流进行分流的网元。例如，第一分流实体20可以为上行分类器(uplink classifier，ULCL)或者分支点网元(BP，Branching point)。
在一种可选的通信系统中，该通信系统还可以包括：与第一功能实体30通信的MEC平台和与第二功能实体40中心DN。其中，MEC平台包括一个或多个SF(例如，SF1和SF2)。一个或多个SF可以是运营商部署的功能网元，也可以是第三方部署的功能网元。SF可以对业务流做增强处理或者过滤处理。举例：SF可以是具有防火墙功能的网元、具有视频加速处理功能的网元、具有负载均衡功能的网元等。中心DN包括应用服务器(application server，AS)，以及一个或多个SF(比如，SF3和SF4)。
示例性的，部署在中心DN的一个或多个SF可以为具有负载均衡或者计费功能的网元。不同的SF具有的功能可以相同，也可以不相同，本申请实施例对此不作限定。
如图2a中线条1(代表上行业务流1)、线条2(代表上行业务流2)所示，其中上行业务流1为不用执行本地业务链控制的业务流。上行业务流2为要执行本地业务链控制的业务流。
举例来说，第一分流实体20对上行业务流1的处理可以描述为：第一分流实体20将上行业务流1发送至第二功能实体40。第一分流实体20将上行业务流2发送至第一功能实体30。假设下行业务流1不用执行本地业务链控制，下行业务流2已执行本地业务链控制。第一分流实体20对下行业务流的处理可以描述为：第一分流实体20将下行业务流1、下行业务流2聚合到N3隧道(即第一分流实体20与接入设备50之间的隧道)上发送至接入设备50，由接入设备50再发送至终端。
如图2a所示，假设上行业务流2(由线条2标识)在MEC平台的处理经过SF1和SF2。具体处理过程描述为：第一功能实体30向上行业务流2发送至SF1，SF1处理完之后再发回第一功能实体30，第一功能实体30再将由SF1处理后的上行业务流2发送至SF2，SF2处理之后再发送至第一功能实体30；或者SF1处理完之后再发送至SF2，SF2对上行业务流处理之后再发回第一功能实体30，之后，第一功能实体30将已执行业务链控制的上行业务流2发送给第一分流实体20。由第一分流实体20将上行业务流2发送给第二功能实体40；或者上行业务流2由SF1，SF2处理之后，发送至第二功能实体40。
进一步地，上行业务流2传输至第二功能实体40后要执行远端业务链控制，则上行业务流2在中心DN的处理经过SF3、SF4。第二功能实体40对上行业务流2的处理过程与第一功能实体30对上行业务流2的处理类似。如：第二功能实体40将上行业务流2发送至SF3，SF3处理完之后再发回到第二功能实体40。第二功能实体40再发送至SF4，SF4处理完之后再发回到第二功能实体40。第二功能实体40再发送至AS。其它可能的处理过程，本实施例不再赘述。
需要说明的是：图2a仅仅是给出一种示例，并不限定traffic steering control的具体发送方式。比如，traffic steering control的另外一种实现方式：第二功能实体40将上行业务流发送至SF3，SF3处理后发送至SF4，SF4处理后发送至AS。
在一种可能的实现方式中，终端通过接入设备50接入该通信系统。
在本申请实施例中，终端可以分布于整个无线网络中，每个终端可以是静态的或移动的。
如图2b所示，图2b示出了本申请实施例提供的另一种通信系统，该通信系统与图2a所示的通信系统的区别在于：在图2a中第一分流实体20和第一功能实体30独立部署，而在图2b中第一分流实体20和第一功能实体30部署于同一个设备中，可以将该设备称为合设网元。也即该合设网元兼具业务流的分流功能和将待执行第一业务链控制的业务流发送至MEC平台的功能。当第一分流实体20和第一功能实体30位于同一个设备时，该第一分流实体20和第一功能实体30可以为该合设网元中独立存在的模块或单元。或者，在第一分流实体20集成有将待执行第一业务链控制的业务流发送至MEC平台的功能，即第一分流实体20内集成第一功能实体30。
具体的，合设网元具有如下功能：将符合规则1的业务流发送至第二功能实体30，以及将符合规则2的业务流至MEC平台。至于规则1和规则2的具体内容可以参考下述实施例中第一分流实体被配置的路由规则。
在一种可能的实施例中，结合图2a，如图2c所示，本申请实施例中的第一分流实体20和第二功能实体40之间具有第二专用隧道。第一分流实体20和第一功能实体 30之间具有第一专用隧道。其中，第二专用隧道用于传输待执行第一业务链控制的业务流。第一专用隧道用于传输已执行第一业务链控制的业务流。需要说明的是，本申请实施例中可以只建立第一专用隧道，也可以只建立第二专用隧道，也可以同时建立第一专用隧道和第二专用隧道。可选地，第一专用隧道用于传输上行业务流，第二专用隧道用于传输下行业务流。
本申请实施例中的专用隧道也可以称为专用连接。该专用隧道可以用于传输已执行第一业务链控制的业务流或者待执行第一业务链控制的业务流。在如图2a～图2f所示的通信系统中，各个网元之间除了上述涉及到的专用隧道以外还可以存在其他隧道或其他连接。
在一种可能的实施例中，结合图2b，如图2d所示，本申请实施例中的合设网元和第二功能实体40之间具有第二专用隧道。
如图2e或图2f所示，图2e或图2f示出了本申请实施例提供的另一种通信系统。该通信系统与图2a-图2d的区别在于：在图2e中第二功能实体40和第一功能实体30之间具有专用隧道。该第一功能实体30可以通过专用隧道向第二功能实体40发送已执行第一业务链控制的业务流。第二功能实体40可以通过专用隧道向第一功能实体30发送待执行第一业务链控制的业务流。在图2f中专用隧道位于合设网元和第二功能实体40之间。
需要说明的是，当本申请实施例中第一分流实体20和第一功能实体30位于同一个设备时，由于第一分流实体20和第一功能实体30之间的第一专用隧道可以省略，此时，合设网元和第二功能实体40之间的第二专用隧道可以看作专用隧道。在这种情况下，第二专用隧道不仅可以用于第二功能实体40发送待执行第一业务链控制的业务流，还可以用于合设网元在该第二专用隧道上向第二功能实体40发送已执行第一业务链控制的业务流。
需要说明的是，在第二功能实体40和第一功能实体30之间具有专用隧道的情况下，第一专用隧道和第二专用隧道可以不存在，也可以不存在。本申请实施例对此不作限定。
此外，本申请实施例中在图2a-图2f所示的通信系统中，第一分流实体20和接入设备50之间也可以具有第三专用隧道和/或第四专用隧道。其中，接入设备50可以通过第三专用隧道或接入设备50和第一分流实体20之间已有的隧道向第一分流实体20发送待执行业务链控制的上行业务流。接入设备50可以通过第四专用隧道或第一分流实体20和接入设备50之间已有的隧道接收第一分流实体20发送的已执行业务链控制的下行业务流。
当然，在接入设备50和第一分流实体20不具有第三专用隧道的情况下，接入设备50可以通过现有的与第一分流实体20之间的隧道向第一分流实体20发送待执行第一业务链控制的业务流。在接入设备50和第一分流实体20不具有第四专用隧道的情况下，第一分流实体20可以通过现有的与接入设备50之间的隧道向第一分流实体20发送已执行第一业务链控制的业务流。
示例性的，若上述通信分流系统应用于5G网络，则如图3a或图3b所示，第一分流实体20所对应的网元或者实体可以为上行分类器(Uplink classifier，UL CL)或 分支点(Branching Point，BP)。会话管理网元10对应的网元或者实体可以为会话功能管理(session management function，SMF)。第一功能实体30所对应的网元或者实体可以为第一用户面功能(user plan function，UPF)锚点(achor)，也可以称为本地会话锚点(Local PDU session anchor，L-PSA)。第二功能实体40所对应的网元或者实体可以为第二用户面功能(user plan function，UPF)锚点(achor)，也可以称为远端会话锚点(remote PDU session anchor，简称：PSA)。接入设备50可以为接入网络(access network，AN)设备或者无线接入网络(radio access network，RAN)设备。
此外，如图3a或图3b所示，5G网络架构还可以包括：接入和移动性管理功能(access and mobility management function，AMF)网元、策略控制功能(policy control function，PCF)网元、应用功能(application function，AF)网元、数据网络(data network，DN)、鉴权服务器功能或认证服务器功能(authentication server function，AUSF)网元、统一数据库(Unified Data Repository，UDR)(图3a或图3b中未示出)、统一数据管理(Unified Data Management，UDM)等，本申请实施例对此不作具体限定。
其中，如图3a所示，终端通过下一代网络(Next generation，N1)接口(简称N1)与AMF网元通信。接入设备通过N2接口(简称N2)与AMF网元通信。接入设备通过N3接口(简称N3)与ULCL/BP通信。ULCL/BP通过N9接口与第二UPF网元和第一UPF网元通信。第一UPF网元通过N6接口(简称N6)与MEC平台通信。第二UPF网元通过N6接口(简称N6)与DN通信任意两个UPF网元之间通过N9接口(简称N9)通信。ULCL/BP通过N4接口(简称N4)与SMF网元通信。AMF网元通过N11接口(简称N11)与SMF网元通信。AMF网元通过N8接口(简称N8)与UDM网元通信。SMF网元通过N7接口(简称N7)与PCF网元通信。SMF网元通过N10接口(简称N10)与UDM网元通信。AMF网元通过N12接口(简称N12)与AUSF网元通信。AMF网元通过N22接口(简称N22)与NSSF网元通信。AUSF网元通过N13接口(简称N13)与UDM网元通信。UDM网元与UDR网元通信。PCF网元与UDR网元通信。ULCL/BP可以通过UPF来实现。
如图3b示出了5G网络架构中基于服务化接口的架构，该架构与图3a的区别在于，在图3b中5GC中的控制面网元也可以采用服务化接口进行交互。例如，AMF网元、AUSF网元、SMF网元、UDM网元、UDR网元或者PCF网元采用服务化接口进行交互。比如，AMF网元对外提供的服务化接口可以为Namf。SMF网元对外提供的服务化接口可以为Nsmf。UDM网元对外提供的服务化接口可以为Nudm。UDR网元对外提供的服务化接口可以为Nudr。PCF网元对外提供的服务化接口可以为Npcf。应理解，图3b中各种服务化接口的名称的相关描述可以参考23501标准中的5G系统架构(5G system architecture)图，在此不予赘述。
需要说明的是，图3a或图3b中的各个网元之间的接口名字只是一个示例，具体实现中接口名字可能为其他名字，本申请实施例对此不作具体限定。
需要说明的是，图3a或图3b的接入设备、AF网元、AMF网元、SMF网元、AUSF网元、UDM网元、UPF网元和PCF网元等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，接入设备、AF网元、AMF网元、SMF网元、AUSF网元、UDM网元、UPF网元和PCF网元所对应的网元也可以是其他的名字， 本申请实施例对此不作具体限定。例如，该UDM网元还有可能被替换为用户归属服务器(home subscriber server，HSS)或者用户签约数据库(user subscription database，USD)或者数据库实体，等等，在此进行统一说明，后续不再赘述。
图3a或图3b中的终端、(R)AN、UPF和DN一般被称为用户层网络功能实体，终端的数据流量可以通过终端和DN之间建立的协议数据单元(Protocol data unit，PDU)会话(Session)进行传输，传输会经过(R)AN和UPF这两个网络功能(实体)；而其他的部分则被称为控制层网络功能和实体，主要负责认证和鉴权、注册管理、会话管理、移动性管理以及策略控制等功能，从而实现用户层流量可靠稳定的传输。本申请实施例中涉及到的PDU会话指在终端与数据网络之间提供PDU连接服务的一种连接(association between the UE and a Data Network that provides a PDU connectivity service)。
图3a-图3b是应用于本申请实施例的网络架构。下面对该网络架构中涉及的各个部分或网元在5G网络中的功能为例分别进行说明。
如图3a所示，终端的一个会话具有多个锚点(PDU session anchor)。例如，第一UPF网元和第二UPF网元。对于上行业务流(UL data/traffic)，BP/ULCL按照转发规则将接收到的上行业务流发送到不同的锚点；对于下行业务流(DL data/traffic)，BP/ULCL按照转发规则将下行业务流发送至终端。
1)、终端(terminal)可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication，MTC)终端、用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal device)或者中继用户设备等。其中，中继用户设备例如可以是5G家庭网关(residential gateway，RG)。为方便描述，本申请中，上面提到的设备统称为终端。
应理解，本申请实施例中的终端可以为物联网终端设备、港口、智能工厂、铁路交通、物流、无人机、无人驾驶汽车等多种垂直行业应用领域中的终端。例如：移动机器人(Mobile Robot)、自动导引车(Automated Guided Vehicle，AGV)，无人驾驶汽车，列车上的控制设备和传感器、工厂中部署的控制设备和传感器(Sensor)等。
作为示例，在本申请实施例中，该终端还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。该终端还可以为应用于工厂的传感器 设备。
(2)、接入设备用于为特定区域的授权终端提供入网功能，并能够根据终端的级别，业务的需求等使用不同质量的传输隧道。接入设备能够管理无线资源，为终端设备提供接入服务，进而完成控制信号和终端设备数据在终端设备和核心网之间的转发，接入设备也可以理解为传统网络中的基站。例如，可以负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。
接入设备可以是无线网络中的设备。接入设备也可以称为无线接入设备或者网络设备。例如将终端接入到无线网络的无线接入网(radio access network，RAN)节点。目前，一些接入设备的举例为：第五代(5th generation，5G)系统中的下一代节点B(The Next Generation Node B，gNB)、传输接收点(transmission reception point，TRP)、LTE系统中的演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，或无线保真(wireless fidelity，Wifi)接入点(access point，AP)等。在一种网络结构中，网络设备可以包括集中单元(centralized unit，CU)节点、或分布单元(distributed unit，DU)节点、或包括CU节点和DU节点的RAN设备。接入设备还可以是无线回传设备，车载设备，可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等。在第三代(3rd generation，3G)系统中，称为节点B(Node B)等。
(3)、移动管理网元，属于核心网网元，主要负责信令处理部分，例如：接入控制、移动性管理、附着与去附着以及网关选择等功能。移动管理网元为终端的会话提供服务的情况下，会为该会话提供控制面的存储资源，以存储会话标识、与会话标识关联的SMF网元标识等。
在5G通信系统中，该移动管理网元可以是AMF网元。在未来通信系统中，移动管理网元仍可以是AMF网元，或者，还可以有其它的名称，本申请不做限定。
(4)、会话管理网元，负责用户面网元选择，用户面网元重定向，因特网协议(internet protocol，IP)地址分配，承载的建立、修改和释放以及QoS控制。会话管理、终端的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中，该会话管理网元可以是SMF网元。在未来通信系统中，会话管理网元仍可以是SMF网元，或者，还可以有其它的名称，本申请不做限定。
(5)、用户面网元，负责终端中用户数据(例如，业务流)的转发和接收。可以从数据网络接收用户数据，通过接入设备传输给终端；用户面网元还可以通过接入设备从终端接收用户数据，转发到数据网络。用户面网元中为终端提供服务的传输资源和调度功能由会话管理网元管理控制的。
在5G通信系统中，该用户面网元可以是UPF网元或UPF模块。在未来通信系统中，用户面网元仍可以是UPF网元或UPF模块，或者，还可以有其它的名称，本申请不做限定。
(6)、认证服务器功能网元，主要提供认证功能，支持3GPP接入和Non-3GPP 接入的认证，具体可参考3GPP TS 33.501。
在未来通信系统中，认证服务器功能网元仍可以是AUSF网元，或者，还可以有其它的名称，本申请不做限定。
(7)、NEF网元，主要支持3GPP网络和第三方应用安全的交互，NEF能够安全的向第三方暴露网络能力和事件，用于加强或者改善应用服务质量，3GPP网络同样可以安全的从第三方获取相关数据，用以增强网络的智能决策；同时该网元支持从统一数据库恢复结构化数据或者向统一数据库中存储结构化数据。
(8)、UDR网元，主要负责存储结构化数据，存储的内容包括签约数据和策略数据、对外暴露的结构化数据和应用相关的数据。
(9)、AF网元，主要支持与3GPP核心网交互来提供服务，例如影响数据路由决策，策略控制功能或者向网络侧提供第三方的一些服务。
(10)、网络存储网元，用于维护网络中所有网络功能服务的实时信息。NRF保存有部署的网络功能(Network function，NF)组件的信息，例如NF组件的标识和网络地址、支持的网络切片的标识、或者数据面实例的信息等，NRF向其它NF提供NF组件的注册和发现等服务。
在未来通信系统中，网络存储网元仍可以是NRF网元，或者，还可以有其它的名称，本申请不做限定。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
(11)、数据网络(Data Network，DN)指的是为终端提供数据传输服务的运营商网络，如IMS(IP Multi-media Service，IP多媒体业务)、Internet等。
终端通过建立终端到RAN到UPF到DN之间的会话(PDU session)，来访问数据网络。
如图4所示，图4示出了本申请实施例中的一种通信设备的硬件结构示意图。会话管理网元10、第一分流实体20、第一功能实体30和第二功能实体40的结构可以参考图4所示的结构。该通信设备包括处理器41，通信线路44以及至少一个通信接口(图4中仅是示例性的以包括通信接口43为例进行说明)。
可选的，该通信设备还可以包括存储器42。
处理器41可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路44可包括一通路，在上述组件之间传送信息。
通信接口43，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器42可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact  disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路44与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器42用于存储执行本申请方案的计算机执行指令，并由处理器41来控制执行。处理器41用于执行存储器42中存储的计算机执行指令，从而实现本申请下述实施例提供的一种业务流的路由方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器41可以包括一个或多个CPU，例如图4中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备可以包括多个处理器，例如图4中的处理器41和处理器45。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
如图5所示，引入MEC平台之后，ULCL/BP可以将业务流分流至L-PSA，由L-PSA将业务流发送至MEC平台，由MEC平台中的SF执行traffic steering control。但是，业务流由MEC平台中的SF执行traffic steering control之后，如何将处理后的业务流发送至central DN是亟需解决的技术问题。有鉴于如图5所示的通信系统描述的方法所存在的技术问题，本申请实施例中会话管理网元10可以为ULCL/BP配置路由规则，这样ULCL/BP可以根据路由规则将路由规则中描述的来源于L-PSA，且指向PSA的业务流发送PSA。同理，对于下行业务流，ULCL/BP根据路由规则将来源于接入设备或PSA且指向L-PSA的业务流发送给L-PSA。
在本申请实施例中，一种业务流的路由方法的执行主体的具体结构，本申请实施例并未特别限定，只要可以通过运行记录有本申请实施例的一种业务流的路由方法的代码的程序，以根据本申请实施例的一种业务流的路由方法进行通信即可。例如，本申请实施例提供的一种业务流的路由方法的执行主体可以是会话管理网元中能够调用程序并执行程序的功能模块，或者为应用于会话管理网元中的通信装置，例如，芯片。本申请实施例提供的一种业务流的路由方法的执行主体可以是第一分流实体中能够调用程序并执行程序的功能模块，或者为应用于第一分流实体中的通信装置，例如，芯片。本申请对此不进行限定。本申请实施例提供的一种业务流的路由方法的执行主体可以是第一功能实体中能够调用程序并执行程序的功能模块，或者为应用于第一功能实体中的通信装置，例如，芯片。本申请实施例提供的一种业务流的路由方法的执行主体可以是第二功能实体中能够调用程序并执行程序的功能模块，或者为应用于第二功能实体中的通信装置，例如，芯片。下述实施例以一种业务流的方法的执行主体为会话管理网元、第一功能实体、第一分流实体、第二功能实体为例进行描述。
需要指出的是，本申请各实施例之间可以相互借鉴或参考，例如，相同或相似的步骤，方法实施例、装置实施例或系统实施例之间，均可以相互参考，不予限制。
结合图2a～图2d，如图6所示，本申请实施例提供一种业务流的路由方法，该方法包括：
步骤601、会话管理网元10确定路由规则。其中，路由规则用于指示第一分流实体20将第一业务流发送至第一功能实体30，和/或，将第二业务流发送至第二功能实体40或接入设备50。其中，第一业务流为待执行第一业务链控制的业务流，第二业务流为已执行第一业务链控制的业务流。其中，第一业务链控制可以对应上述本地业务链控制。
应理解的是，第一业务流可以代表某个会话中的一个或多个待执行第一业务链控制的业务流，第二业务流可以代表某个会话中的一个或多个已执行第一业务链控制的业务流，并不具有指示性含义。第一业务流和第二业务流可以为同一个业务流，也可以为不同的业务流。例如，第一业务流执行完业务链控制后，即为已执行第一业务链控制的业务流。第一业务流和第二业务流可以为同一个会话中的业务流，也可以为不同会话中的业务流。
例如，第一业务流可以代表会话中的业务流1和业务流2。其中，业务流1和业务流2均为待执行第一业务链控制的业务流。第二业务流可以代表会话中的业务流1和业务流3，业务流1和业务流3均为已执行第一业务链控制的业务流。
需要说明的是，本申请实施例中第一分流实体20具有对业务流进行分流的功能，对于第一分流实体20而言，其可能不需要判断业务流已执行业务链控制，或者未执行业务链控制。或者判断业务流为待执行第一业务链控制的业务流。一旦第一分流实体20接收到的业务流符合路由规则时，第一分流实体20便可以根据路由规则转发业务流。
本申请实施例中的第一业务流可以为某个会话中来自终端的上行业务流，该上行业务流的目的地址为第二功能实体40对应的中心DN。或者第一业务流可以为某个会话中来自第二功能实体40对应的中心DN的下行业务流，此时下行业务流的目的地址可以为终端。当第一业务流为某个会话中来自第二功能实体40对应的中心DN的下行业务流时，该下行业务流可以由第二功能实体40对应的中心DN中的SF执行过业务链控制，但是仍需要由第一功能实体30对应的MEC平台中的SF执行业务链控制。或者，该下行业务流可以未由第二功能实体40对应的SF执行业务链控制，只由第一功能实体30对应的MEC平台中的SF执行业务链控制。中心DN中的SF与MEC平台中的SF可以相同，可以不同。本申请实施例对此不作限定。
本申请实施例中的第二业务流可以为某个会话中的上行业务流，也可以为某个会话中的下行业务流。如果第二业务流为下行业务流，该下行业务流可能来自于第二功能实体40，也可能来自于第一功能实体30，则路由规则用于指示第一分流实体20将第二业务流发送至接入设备50。如果第二业务流为上行业务流，该上行业务流可能来自于解饿如设备50，也可能来自于第一功能实体30，则路由规则用于指示第一分流实体20将第二业务流发送至第二功能实体40。至于业务流究竟为上行业务流还是下行业务流可以结合其源地址/目的地址或者源端口/目的端口号识别，本申请实施例对此不作限定。
步骤602、在会话的会话管理过程中，会话管理网元10向第一分流实体20发送 路由规则，以使得第一分流实体20在会话的会话管理过程中接收来自会话管理网元10的路由规则。
示例性的，该会话管理过程可以为会话建立过程或者会话更新(修改)过程或者会话删除过程。
作为一种可能的实现方式，以会话管理过程为会话建立过程为例，步骤602可以通过以下方式具体实现：会话管理网元10向第一分流实体20发送N4会话建立请求，该会话建立请求中携带路由规则。
作为另一种可能的实现方式，以会话管理过程为会话建立或会话修改过程为例，步骤602可以通过以下方式具体实现：会话管理网元10向第一分流实体20发送N4会话修改请求，该会话修改请求中携带路由规则。
当然，该路由规则还可以携带在会话管理过程中新建立的请求消息。或者，该路由规则还可以在第一分流实体20对第一业务流或第二业务流实现分流之前的任何过程中由会话管理网元10发送给第一分流实体20，本申请实施例对此不作限定。或者，会话管理网元10可以在会话管理网元10与第一分流实体20交互的其他流程中向第一分流实体20发送该路由规则。
步骤603、第一分流实体20根据路由规则，处理第一分流实体20接收到的目标业务流。
本申请实施例提供一种业务流的路由方法，该方法中会话管理网元确定路由规则，并将路由规则发送给第一分流实体，这样第一分流实体便可以根据路由规则，对符合路由规则的业务流执行相应的转发动作。例如，第一分流实体可以将路由规则中记录的第一业务流转发给第一功能实体，这是由于第一业务流通常为待执行第一业务链控制的业务流，这样可以由第一功能实体对应的MEC平台中的SF对第一业务流执行第一业务链控制。此外，由于第一功能实体通常部署在距离终端较近的位置，这样可以尽早对第一业务流执行第一业务链控制，如视频加速、防火墙、负载均衡功能，以使第一业务流得到尽早处理，如防火墙功能，可以尽早将无效业务流过滤掉。再者，本申请实施例中第一分流实体还可以将路由规则中记录的第二业务流发送至第二功能实体或接入设备。这是由于第二业务流为已执行第一业务链控制的业务流。这样可以实现对业务流执行第一业务链控制后发回第二功能实体。
作为一种可能的具体实现方式，本申请实施例中的步骤601可以通过以下方式实现：会话管理网元10根据策略信息，确定路由规则。
其中，策略信息中包括待执行第一业务链控制的业务流的描述信息，以及已执行第一业务链控制的业务流的描述信息。
作为本申请的另一种可能的实施例，本申请实施例提供的方法在步骤601之前还可以包括：会话管理网元10获取策略信息(例如，PCC rules)。
一种实现方式，该策略信息可以配置在会话管理网元10本地。
另一种实现方式，会话管理网元10从PCF网元处获取策略信息，本申请实施例对此不作限定。
关于会话管理网元10从PCF网元处获取策略信息的具体方式可以参考步骤604-步骤606中的描述。
作为本申请的另一种可能的实施例，如图7所示，本申请实施例提供的方法在步骤601之前还可以包括：
步骤604、AF网元向PCF网元发送第一请求消息，以使得PCF网元接收第一请求消息。
其中，第一请求消息携带一个或多个业务流对应的以下信息中的任一个或多个：描述信息、终端的标识、业务链需求。
其中，业务链需求用于指示该一个或多个业务流为待执行第一业务链控制的业务流，即该业务流要被执行本地业务链控制。或者业务链需求还可以用于指示该一个或多个业务流不用执行第一业务链控制。
作为一种具体实现，第一请求消息可以为AF request。
步骤605、PCF网元根据AF request生成PCC rules。PCC rules包含业务链信息。
其中，业务链信息，可以是业务链策略标识，该业务链策略标识为预先配置在会话管理网元10和/或PCF网元上的一个标识。具体的，会话管理网元通过该标识，可以获取到该标识对应的业务链策略，如对业务流执行第一业务链控制的一个或多个SF，以及一个或多个SF的执行顺序。
步骤606、PCF网元向会话管理网元10发送PCC rules，以使得会话管理网元10接收PCC rules。这样便于会话管理网元10根据PCC rules确定路由规则。
鉴于本申请实施例中的路由规则可以通过多种形式指示第一分流实体20将第一业务流发送至第一功能实体30，和/或，将第二业务流发送至第二功能实体40或接入设备50。下述将分别介绍：
示例1)、路由规则包括第一业务流的描述信息和与第一业务流的描述信息关联的第一功能实体30的信息，和/或，第二业务流的描述信息和第二业务流的描述信息关联的第二功能实体40的信息或接入设备50的信息。其中，描述信息包括第一业务流或第二业务流的来源信息。
本申请实施例中可以将描述信息称作为检测规则，将描述信息对应的业务流转发到的功能实体称作转发动作。转发动作用于表明对符合检测规则的业务流的处理逻辑，即转发至接入设备50或第一功能实体30、或第二功能实体40。
需要说明的是，检测规则还可以是以下任一项或多项：隧道信息、网络实例、服务质量流标识(QoS Flow Identifier，QFI)、应用标识等。网络实例具体可以是虚拟局域网(Virtual Local Area Network，VLAN)标识。本申请实施例中将业务流描述信息记作SDF(service data flow)为例进行说明。
示例性的，描述信息可以包括终端的标识、五元组信息(例如，IP五元组)、三元组信息(例如，IP三元组)、隧道信息、应用标识、数据网络名称(data network name，DNN)、或单网络切片选择辅助信息(Single Network Slice Selection Assistance Information，S-NSSAI)中的一个或多个。例如，IP五元组包括源IP地址，源端口号，目的IP地址，目的端口号，传输层协议。
示例性的，第二功能实体40的信息可以为第二功能实体40的地址，或者第二功能实体40的标识或者第二功能实体40的端口号中的一个或多个组合。
示例性的，接入设备50的信息可以为接入设备50的地址，或者接入设备50的标 识或者接入设备50的端口号中的一个或多个组合。
示例性的，第一功能实体30的信息可以为第一功能实体30的地址，或者第一功能实体30的标识或者第一功能实体30的端口号中的一个或多个组合。
相应的，本申请实施例中的步骤603可以通过以下方式实现：目标业务流的描述信息与第一业务流的描述信息相同，第一分流实体20向第一功能实体30发送目标业务流。和/或，目标业务流的描述信息与第二业务流的描述信息相同，第一分流实体20向第二功能实体40或接入设备50发送目标业务流。
考虑业务流的方向，一个业务流的上行方向、下行方向对应的描述信息不同，比如业务流A上行方向对应的IP五元组和下行方向对应的IP五元组的具体内容可以参考表1中的描述。
举例说明，假设上行业务流的描述信息包括IP五元组1，对应源IP地址＝IP1，源端口号＝port1，目的IP地址＝IP2，目的端口号＝port2，传输层协议＝UDP；下行业务流的描述信息包括IP五元组2，对应源IP地址＝IP2，源端口号＝port2，目的IP地址＝IP1，目的端口号＝port1，传输层协议＝UDP。以表格的形式示意出了本申请实施例中的路由规则的具体内容，如表1所示：
表1 路由规则的具体内容
Figure PCTCN2019116803-appb-000001
举例说明，如果目标业务流为业务流C，其描述信息包括：IP五元组1，且该业务流C的报文头包括接入设备50的信息，即该业务流C来源于接入设备50，则第一 分流实体20将业务流C转发至第一功能实体30。第一分流实体20接收到的业务流C的描述信息包括：IP五元组2，且该业务流C的报文头包括第三功能实体40的信息，即该业务流C来源于第三功能实体40，则第一分流实体20将业务流C转发至第一功能实体30。其中，接入设备50的信息指的是与接入设备50的信息对应的第一分流实体20的隧道信息；第三功能实体40的信息指的是与第三功能实体40的信息对应的第一分流实体20的隧道信息。
如果业务流C的描述信息包括：IP五元组1，且该业务流C的报文头包括第一功能实体30的信息，即该业务流C来源于第一功能实体30，则第一功能实体30将业务流C发送至第二功能实体40。其中，第一功能实体30的信息指的是与第一功能实体30对应的第一分流实体20的隧道信息。
如果业务流C的描述信息包括：IP五元组2，且该业务流C的报文头包括第一功能实体30的信息，即该业务流C来源于第一功能实体30，则第一功能实体30将业务流C发送至接入设备50。其中，第一功能实体30的信息指的是与第一功能实体30对应的第一分流实体的隧道信息。
本申请实施例中第一分流实体20可以通过以下方式来确定业务流的来源：第一分流实体20可以通过业务流的报文头中的隧道信息(tunnel information)来判断业务流来源。例如，第二业务流的报文头中携带与第一功能实体30对应的第一分流实体20的隧道信息，即I-UPF tunnel information for L-PSA，则第一分流实体20可以确定第二业务流来源于第一功能实体30。如果第一业务流的报文头中携带与第二功能实体40对应的第一分流实体的20的隧道信息，即I-UPF tunnel information for PSA，则第一分流实体20可以确定第一业务流来源于第二功能实体40。同理，第一业务流的报文头中携带与接入设备50对应的第一分流实体20的隧道信息，即I-UPF tunnel information for RAN，则第一分流实体20可以确定第一业务流来源于接入设备50。
作为一种可能的实现：路由规则包括以下信息中的任一个或多个：第一业务流的描述信息指示第一业务流来自接入设备50或第二功能实体40时，第一分流实体20向第一功能实体30发送第一业务流。或，第二业务流的描述信息指示第二业务流来自第一功能实体30时，第一分流实体20向接入设备50或第二功能实体40发送第二业务流。
需要说明的是，上述示例以描述信息包括五元组信息为例，当然在实际过程中描述信息的各个内容可以解耦也可以组合。例如，描述信息中可以不包括五元组信息或三元组信息，如果路由规则中的描述信息为QFI，以及转发动作，则第一分流实体20可以将携带指定的QFI的业务流发送至转发动作指示的网元，也即对于某个终端的上行业务流X和下行业务流Y，如果该上行业务流X对应于指定的QFI且来源于接入设备50，则第一分流实体20将上行业务流X发送至第二功能实体40。如果该下行业务流Y对应于指定的QFI且来源于第二功能实体40，则第一分流实体20将下行业务流Y发送至第一功能实体30。如果该上行业务流X对应于指定的QFI且来源于第一功能实体30，则第一分流实体20将上行业务流X发送至第二功能实体40。如果该下行业务流Y对应于指定的QFI且来源于第一功能实体30，则第一分流实体20将下行业务流Y发送至接入设备50。可以理解的是，如果描述信息为指定QFI，则表示该指定 QFI对应的下行业务流和上行业务流均需要执行业务链控制。
对于描述信息为其它描述方式，如网络实例、隧道信息、应用标识，的具体实现可以参考描述信息为终端的标识的示例，此处不再赘述。
需要说明的是，示例1可以适用于图2a～图2d中任一个所示的通信系统。也即在不具有第一专用隧道和第二专用隧道的基础上，例如图2a或图2b所示的场景，会话管理网元10可以为第一分流实体20配置转发至第一功能实体30的一个或多个第一业务流的描述信息。和/或，会话管理网元10为第一分流实体20配置转发至第二功能实体40或接入设备50的一个或多个第二业务流的描述信息。在这种情况下，第一分流实体20可以通过与第一功能实体30之间具有的除第一专用隧道外的其余隧道向第一功能实体30发送第一业务流。第一分流实体20可以通过与第二功能实体40之间具有的除第二专用隧道外的其余隧道向第二功能实体30发送第二业务流。
当然，在具有第一专用隧道和第二专用隧道的基础上，例如图2c或图2d所示的场景，会话管理网元10依然可以为第一分流实体20配置转发至第一功能实体30的一个或多个第一业务流的描述信息。和/或，会话管理网元10为第一分流实体20配置转发至第二功能实体40或接入设备50的一个或多个第二业务流的描述信息。
示例2)、结合图2c或图2d，路由规则用于指示第一分流实体20向第一功能实体30发送来自第二专用隧道的第一业务流，和/或，指示第一分流实体20向第二功能实体40发送来自第一专用隧道的第二业务流。其中，第二专用隧道位于第一分流实体20和第二功能实体40之间。第一专用隧道位于第一分流实体20和第一功能实体30之间。第一专用隧道用于传输已执行第一业务链控制的业务流。第二专用隧道用于传输待执行第一业务链控制的业务流。
相应的，本申请实施例中的步骤603可以通过以下实现：目标业务流来源于第一专用隧道，第一分流实体20将目标业务流发送至第一功能实体30。或，目标业务流来源于第二专用隧道，第一分流实体20将目标业务流发送至第二功能实体40。
作为一种具体实现，第一分流实体20可以根据目标业务流的报文头中携带的隧道信息确定该目标业务流来源于第一专用隧道还是第二专用隧道。
举例来说，目标业务流的报文头中携带第一专用隧道信息，则目标业务流来源于第一专用隧道。目标业务流的报文头中携带第二专用隧道信息，则目标业务流来源于第二专用隧道。
需要说明的是，本申请实施例中第一专用隧道和第二专用隧道可以并存，或者二者中存在一个。例如，对于图2c所示的场景，可以具有第一专用隧道和第二专用隧道。或者可以具有第一专用隧道，但不具有第二专用隧道。或者具有第二专用隧道，但不具有第一专用隧道。
应理解，示例2可以适用于具有第二专用隧道和/或第一专用隧道的场景。本申请实施例中第一专用隧道信息和第二专用隧道信息中的一个或多个可以由会话管理网元10分配。当然，该第一专用隧道信息也可以由UPF网元分配，即由第一分流实体20为第一功能实体30分配，第二专用隧道信息也可以由UPF网元分配，即由第一分流实体20为第二功能实体40分配，本申请实施例对此不作限定。
在由第一分流实体20分配第一专用隧道信息和/或第二专用隧道信息的情况下， 如图7所示，本申请实施例提供的方法在步骤601之前还可以包括：会话管理网元10获取第一专用隧道信息和第二专用隧道信息中的一个或多个。
一种实现方式，会话管理网元10可以自主获取第一专用隧道信息和第二专用隧道信息中的一个或多个。
作为一种可能的实现方式，会话管理网元10可以根据PCC规则确定获取第一专用隧道信息和第二专用隧道信息中的一个或多个。例如，PCC规则中除了包含业务流描述信息外，还包含指示信息。指示信息用于指示对某个业务流在上行方向执行第一业务链控制。或者指示信息用于指示对某个业务流在下行方向执行第一业务链控制。或者指示信息指示某个业务流不仅要在上行方向执行第一业务链控制，也要在下行方向执行业务链控制。
可选的，该PCC规则中指示信息来源于步骤604，即AF向PCF发送的第一请求消息还包含指示信息。从而，会话管理网元10根据该指示信息确定获取第一专用隧道信息和第二专用隧道信息中的一个或多个。
另一种方式，会话管理网元10可以从第一分流实体20处获取获取第一专用隧道信息和第二专用隧道信息中的一个或多个。关于会话管理网元10从第一分流实体20处获取获取第一专用隧道信息和第二专用隧道信息中的一个或多个实现方式可以参考下述步骤607-步骤609中的描述。
步骤607、会话管理网元10向第一分流实体20发送第一指示信息，以使得第一分流实体20接收来自会话管理网元10的第一指示信息。该第一指示信息用于指示第一分流实体20分配第一专用隧道信息和第二专用隧道信息中的一个或多个。或者，第一指示信息用于指示第一分流实体20建立第一专用隧道和第二专用隧道中的一个或多个，这样第一分流实体20便可以确定要分配第一专用隧道信息和第二专用隧道信息中的一个或多个。
对于图2d所示的场景，第一指示信息用于指示第一分流实体20分配第二专用隧道信息，或者第一指示信息用于指示第一分流实体20建立第二专用隧道。
对于图2c所示的场景，第一指示信息可以用于指示第一分流实体20分配第二专用隧道信息，或者第一指示信息用于指示第一分流实体20建立第二专用隧道。
对于图2c所示的场景，第一指示信息可以用于指示第一分流实体20分配第一专用隧道信息，或者第一指示信息用于指示第一分流实体20建立第一专用隧道。
对于图2c所示的场景，第一指示信息可以用于指示第一分流实体20分配第一专用隧道信息和第二专用隧道信息，或者第一指示信息用于指示第一分流实体20建立第一专用隧道和第二专用隧道。
示例性的，会话管理网元10可以在会话管理过程中向第一分流实体20发送第一指示信息。或者会话管理网元10可以在会话管理过程以外的其他与第一分流实体20交互的流程中向第一分流实体20发送第一指示信息。例如，以会话管理过程为会话建立流程为例，步骤607可以通过以下方式实现：会话管理网元10向第一分流实体20发送N4会话建立请求。其中，N4会话建立请求中携带第一指示信息。当然，N4会话建立请求还可以使用N4会话修改请求替换。
步骤608、第一分流实体20向会话管理网元10发送第一专用隧道信息和第二专 用隧道信息中的一个或多个。
示例性的，第一分流实体20可以在会话管理响应过程或其他与会话管理网元10交互的流程中向会话管理网元10发送第一专用隧道信息和第二专用隧道信息中的一个或多个。
例如，第一分流实体20可以向会话管理网元10发送N4会话建立响应消息，该会话建立响应消息中包括第一专用隧道信息和第二专用隧道信息中的一个或多个。
因此，作为一种可能的实施例，如图7所示，本申请实施例提供的方法在步骤608之后还包括：
步骤609、会话管理网元10接收来自第一分流实体20的第一专用隧道信息和第二专用隧道信息中的一个或多个。
其中，第一专用隧道信息用于建立第一专用隧道，具体可以是与第一功能实体30对应的第一分流实体20的隧道信息。第二专用隧道信息用于建立第二专用隧道，具体可以是与第二功能实体40对应的第一分流实体20的隧道信息。
作为一种实现，第一专用隧道和第二专用隧道为单向隧道。第一专用隧道指第一功能实体30和第一分流实体20之间的下行隧道，即第一功能实体30通过第一专用隧道向第一分流实体20发送业务流时，该业务流的报文头携带第一专用隧道信息。第二专用隧道指的是第二功能实体40和第二分流实体20之间的下行隧道，即第二功能实体40通过第二专用隧道向第一分流实体20发送业务流时，该业务流的报文头携带第二专用隧道信息。
需要说明的是，在由会话管理网元10分配第二专用隧道和/或第一专用隧道的场景下，步骤607和步骤608可以替换为：会话管理网元10向第一分流实体20发送第一专用隧道信息和第二专用隧道信息中的一个或多个。第一分流实体20向会话管理网元10返回应答。此时，步骤609可以省略。
在具有第二专用隧道和/或第一专用隧道的场景下，会话管理网元10还可以指示第二功能实体40或第一功能实体30利用上述专用隧道发送业务流。关于会话管理网元10指示第二功能实体40或第一功能实体30利用上述专用隧道发送业务流的具体实现方式，可以参考步骤610和步骤611。
作为一种可能的实施例，如图7所示，本申请实施例提供的方法还包括：
步骤610、会话管理网元10向第二功能实体40发送第二专用隧道信息以及第一转发规则，以使得第二功能实体40接收第二专用隧道信息以及第一转发规则。
其中，第一转发规则用于指示第二功能实体40通过第二专用隧道向第一分流实体20传输第一业务流。
通过执行步骤610便于第二功能实体40在待执行第一业务链控制的业务流的报文头中携带第二专用隧道信息。后续业务流传输过程中，第一分流实体20便可以将报文头中携带第二专用隧道信息的业务流发送至第一功能实体30。
示例性的，会话管理网元10可以在会话管理过程中向第二功能实体40发送第二专用隧道信息以及第一转发规则。
步骤611、会话管理网元10向第一功能实体30发送第一专用隧道信息以及第二转发规则，以使得第一功能实体30接收第一专用隧道信息以及第二转发规则。第二转 发规则用于指示第一功能实体通过第一专用隧道向第一分流实体传输第二业务流。
示例性的，会话管理网元10可以在会话管理过程中向第二功能实体40发送第一专用隧道信息以及第二转发规则。
通过执行步骤611便于第一功能实体30在已执行第一业务链控制的业务流的报文头中携带第一专用隧道信息。后续业务流传输过程中，第一分流实体20便可以将报文头中携带第一专用隧道信息的业务流发送至第二功能实体30。
需要说明的是，在示例2中当第一功能实体30和第一分流实体20合设时，步骤611可以省略。此时，路由规则用于指示合设网元将接收到经过traffic steering control的上行业务流发送至第二功能实体40，和/或，指示合设网元将接收到来自第二专用隧道的下行业务流，即报文头携带第二专用隧道信息的下行业务流发送至MEC平台，以由MEC平台中的SF执行traffic steering control。
示例3)、第一业务流和第一标识相关联，路由规则用于指示第一分流实体20向第一功能实体30发送与第一标识关联的业务流。或，第二业务流和第二标识相关联，路由规则用于指示第一分流实体20向第二功能实体40或接入设备50发送与第二标识关联的业务流。
示例性的，第一标识用于表示该业务流来源于第二功能实体40或接入设备50，也即第一标识可以表示将来源于第二功能实体40或接入设备50的第一业务流通过第一分流实体30发送给第一功能实体30。
示例性的，第二标识用于表示该业务流来源于第一功能实体30。也即第二标识可以表示将来源于第一功能实体30的第二业务流通过第一分流实体20发送给第二功能实体40。
具体的，对于携带第二标识的业务流是发送给第二功能实体40还是发送给接入设备50，可以结合业务流的描述信息，如目的地址或者目的端口判断，或者该业务流是上行业务流还是下行业务流。例如，如果业务流D携带第二标识，且业务流D为上行业务流或者业务流D的目的地址指向第二功能实体40，则第一分流实体20可以将业务流D发送给第二功能实体40。如果业务流D携带第二标识，且业务流D为下行业务流或者业务流D的目的地址指向终端，则第一分流实体20可以将业务流D发送给接入设备50。
一种可能的实现方式，第二业务流和第二标识相关联，路由规则用于指示第一分流实体20向第二功能实体40发送与第二标识关联的业务流。
相应的，如图8所示，本申请实施例中的步骤603可以通过以下方式实现：目标业务流与第一标识关联，第一分流实体20向第一功能实体30发送目标业务流；或，目标业务流与第二标识关联，第一分流实体20向第二功能实体40发送目标业务流。
也即在示例3中，会话管理网元10可以通过路由规则指示第一分流实体20对携带第一标识的业务流发送至第一功能实体30，对携带第二标识的业务流发送至第二功能实体40。也即对于第一分流实体20而言，其可以将携带第一标识的业务流认为是第一业务流，将携带第二标识的业务流认为是第二业务流。
在第一分流实体20基于业务流中携带的第一标识或第二标识确定将业务流转发至第一功能实体30还是第二功能实体40时，本申请实施例提供的方法还可以包括： 第一功能实体30在已执行第一业务链控制的业务流的报文头中携带第一标识。第二功能实体40在待执行第一业务链控制的业务流的报文头中携带第二标识。
一种实现方式，第一功能实体30或第二功能实体40可以自主确定在业务流的报文头中携带标识。
另一种实现方式，可以由会话管理网元10指示在业务流的报文头中携带标识关于第一功能实体30或第二功能实体40在业务流的报文头中携带标识的具体过程可以参考下述步骤612-步骤613中的描述。
作为一种可能的实施例，如图8所示，本申请实施例提供的方法在步骤603之前还可以包括：
步骤612、会话管理网元10向第二功能实体40发送第三指示信息，以使得第二功能实体40接收来自会话管理网元10的第三指示信息。其中，第三指示信息用于指示第二功能实体40在第一业务流的报文头中携带第一标识。
一种可能的实现方式中，第三指示信息可以通过转发规则实现。例如，会话管理网元10向第二功能实体40发送转发规则，该转发规则用于指示第二功能实体40对第一业务流的报文进行如下处理：在报文头中添加第一标识。
示例性的，会话管理网元10可以在会话管理过程中向第二功能实体40发送第三指示信息，或者在会话管理流程外的其他与第二功能实体40交互的过程中向第二功能实体40发送第三指示信息。
具体的，对于第二功能实体40而言，其接收到第三指示信息后，当第一业务流不需要在central DN执行业务链控制时，第二功能实体40在待执行第一业务链控制的第一业务流的报文头中携带第一标识，并发送给第一分流实体20。当第一业务流需要由central DN中的SF执行业务链控制时，第二功能实体40在已由central DN中的SF执行业务链控制，且仍需要执行第一业务链控制的第一业务流的报文头中添加第一标识，并发送给第一分流实体20。换句话说，第二功能实体根据步骤612中的第三指示信息，对待执行第一业务链控制的第一业务流的报文进行如下处理：在报文头中添加第一标识。
举例说明，业务流的报文头可以为通用分组无线服务技术隧道协议—用户面报文头((General Packet Radio Service，GPRS)tunnel protocol–user plane，GTP-U header)。
举例说明，以待执行第一业务链控制的业务流C为例进行说明，假设业务流C的上行业务流用SDF(service data flow)1表示，下行业务流用SDF2表示，则第二功能实体40对业务流C的处理逻辑如下表2或表3所示：
表2
Figure PCTCN2019116803-appb-000002
表3
Figure PCTCN2019116803-appb-000003
Figure PCTCN2019116803-appb-000004
步骤613、会话管理网元10向第一功能实体30发送第四指示信息，以使得第一功能实体30接收来自会话管理网元10的第四指示信息。其中，第四指示信息用于指示第一功能实体30在第二业务流的报文头中携带第二标识。
一种可能的实现方式中，第四指示信息可以通过转发规则实现。例如，会话管理网元10向第一功能实体30发送转发规则，该转发规则用于指示第一功能实体30对第二业务流的报文进行如下处理：在报文头中添加第二标识。
举例说明，仍以业务流C为例，则第一功能实体30对业务流C的处理逻辑如下表4所示：
表4
Figure PCTCN2019116803-appb-000005
需要说明的是，在示例3中，当第一功能实体30和第一分流实体20合设时，则步骤613中的第一功能实体30可以由合设网元替换。此时，路由规则可以用于指示合设网元将与第一标识关联的业务流发送至MEC平台，以由MEC平台中的SF执行第一业务链控制；和/或路由规则用于指示合设网元向第二功能实体40发送已执行第一业务链控制的业务流。其中，如何标记某业务流已由MEC平台中的SF执行第一业务链控制，本申请实施例不做限定，例如可以通过如下方式实现：第二功能实体40记录该业务流的描述信息，当第二功能实体从MEC平台再次收到该业务流的描述信息时，则第二功能实体40认为该业务流为已执行第一业务链控制的业务流。
由于在实际过程中，可能会存在第一分流实体20和第一功能实体30发生变化的场景，例如终端发生移动，移出了第一分流实体20的服务区域。如图9a或图9b所示，会话管理网元10确定分流实体从第一分流实体20变为第二分流实体60。其中，第二分流实体60对应第三功能实体70。第三功能实体70对应MEC平台。因此，在该场景下，可以通过下述步骤614和步骤615，或，步骤614、步骤616、以及步骤617实现下行业务流执行第一业务链控制。
结合图9a，如图7或图8所示，作为本申请的再一个实施例，本申请实施例提供的方法还可以包括：
步骤614、会话管理网元10确定分流实体从第一分流实体20变为第二分流实体60。
例如，会话管理网元10根据终端的位置，确定将分流实体从第一分流实体20变为第二分流实体60。换句话说，会话管理网元10确定终端移出了第一分流实体20的服务区域。
步骤615、会话管理网元10向第二分流实体60发送第五指示信息，以使得第二分流实体60接收第五指示信息。该第五指示信息用于指示第二分流实体60执行以下步骤中的任一个或多个：
向接入设备50发送来源于第一分流实体20的第三业务流；或，向第二分流实体60对应的第三功能实体70发送来源于第二功能实体40的第四业务流。其中，第三业务流为已执行第一业务链控制的业务流。第四业务流为待执行第一业务链控制的业务流。
进一步地，第五指示信息还用于指示第二分流实体60对来源于第一分流实体20的第三业务流不发送至第三功能实体70。
一种可能的实现方式，第五指示信息具体可以是转发规则。即，会话管理网元10向第二分流实体60发送转发规则，该转发规则用于指示第二分流实体60将来源于第一分流实体20的第三业务流发送至接入设备50；和/或，将来源于第二功能实体40的第四业务流发送至第三功能实体70。
相应的，第二分流实体60接收到第五指示信息之后，便可以确定向接入设备50发送第三业务流。或，向第二分流实体50对应的第三功能实体70发送第四业务流。
具体的，第五指示信息可以通过转发规则实现。例如：会话管理网元10向第二分流实体60发送转发规则，转发规则包括第三业务流的描述信息和第三业务流的描述信息对应的接入设备50的信息，和/或，包括第四业务流的描述信息和第四业务流的描述信息对应的第三功能实体70的信息。
需要说明的是，在步骤614-步骤615中，由第一功能实体30对应的MEC平台中的SF对第三业务流执行第一业务链控制。之后，第一功能实体30将已执行第一业务链控制的第三业务流发送至第一分流实体20，由第一分流实体20再转发至第二分流实体60。对于第二分流实体60接收到来自第一分流实体20的第三业务流，根据步骤615中的第五指示信息将第三业务流转发至接入设备50即可(也即第二分流实体60无需将第三业务流发送给第三功能实体70)。对于第二分流实体60从第二功能实体40处接到的第四业务流，则第二分流实体60根据步骤615中的第五指示信息将第四业务流发送至第二分流实体60对应的第三功能实体70，由第三功能实体70将第四业务流发送至第三功能实体对应的MEC平台执行第一业务链控制。
需要说明的是，本申请实施例提供的方法还可以包括：会话管理网元10向第一分流实体20发送指示信息，该指示信息用于指示第一分流实体20将来自第二功能实体40的第三业务流发送至第二分流实体60。
进一步地，会话管理网元10向第二功能实体40发送用于指示第二功能实体40将第四业务流发送至第二分流实体60的指示信息。
结合图9b，如图7或图8所示，作为本申请的再一个实施例，本申请实施例提供的方法在步骤614之后还可以包括：
步骤616、会话管理网元10向第一分流实体20或第二功能实体40发送第六指示 信息，以使得第一分流实体20接收第六指示信息。该第六指示信息用于指示第一分流实体20或第二功能实体40向第二分流实体60发送第五业务流。其中，第五业务流为待执行第一业务链控制的业务流。
步骤617、会话管理网元10向第二分流实体60发送第七指示信息，以使得第二分流实体60接收第七指示信息。该第七指示信息用于指示第二分流实体60向第二分流实体60对应的第三功能实体70发送第五业务流。第五业务流来源于第二功能实体40或者来源于第一分流实体20。
在图9a或图9b所示的场景中，当分流实体从第一分流实体20变为第二分流实体60的情况下，会话管理网元10还可以向第一分流实体20和第二功能实体40发送第二分流实体60的信息，如第二分流实体60的隧道信息，包括第二分流实体40的隧道端点标识和地址。这一部分为现有技术，本申请实施例在此不再赘述。
综上所述，在图9a中第二分流实体60可以将来自第二功能实体40的第四业务流发送至第二分流实体60对应的第三功能实体70，以由第三功能实体70对应的MEC平台执行业务链控制。在第三功能实体70对应的MEC平台对第四业务流执行业务链控制后，由第二分流实体60将第四业务流发送至接入设备50。但是，对于来自第一分流实体20的第三业务流，则第二分流实体60将第三业务流转发给接入设备50即可。也即在图9a中，对于第三业务流，第二分流实体60不需要将其再转发给第三功能实体70。这是由于第三业务流已在第一功能实体30对应的MEC平台处执行业务链控制。
在图9b所示的场景中，以第五业务流为来源于第一分流实体20的业务流a或来源于第二功能实体40的业务流b为例，第二分流实体60将第五业务流发送至第三功能实体70，以由第三功能实体70对应的MEC平台执行业务链控制。
图9a或图9b仅是对MEC平台或中心DN执行业务链控制的SF的路径的一种示例，并不具有指示性含义。
结合图2e或图2f，如图10所示，本申请实施例提供一种业务流的传输方法，包括：
步骤1001、会话管理网元10确定第一路由规则和第二路由规则中的一个或多个，第一路由规则用于指示第一功能实体30通过第一功能实体30和第二功能实体40之间的专用隧道向第二功能实体40发送第二业务流。第二路由规则用于指示第二功能实体40通过专用隧道向第一功能实体30发送第一业务流。其中，第一业务流为待执行第一业务链控制的业务流，第二业务流为已执行第一业务链控制的业务流。
此外，第一路由规则还用于指示第一功能实体30对从专用隧道接收到的第一业务流执行第一业务链控制。即第一路由规则还用于指示第一功能实体30将来自专用隧道的第一业务流发送至MEC平台。
具体的，步骤1001的具体实现可以参考步骤601的具体实现，本申请实施例在此不再赘述。
步骤1002、会话管理网元10向第一功能实体30发送第一路由规则，以使得第一功能实体30接收第一路由规则。
示例性的，会话管理网元10可以在会话管理过程中向第一功能实体30发送第一路由规则。
步骤1003、第一功能实体30根据第一路由规则处理第二业务流。
例如，作为步骤1003的一种具体实现，第一功能实体30根据第一路由规则在第二业务流的报文头中携带与第一功能实体30对应的第二功能实体40的专用隧道信息，即specific PSA tunnel information for L-PSA。
举例说明，以待执行本地业务链控制的业务流C为例进行说明，假设业务流C上行业务流用SDF1表示，下行业务流用SDF2表示，则第一路由规则的具体内容可以入表5所示：
表5
Figure PCTCN2019116803-appb-000006
步骤1004、会话管理网元10向第二功能实体40发送第二路由规则，以使得第二功能实体40接收第二路由规则。
示例性的，会话管理网元10可以在会话管理过程中向第二功能实体40发送第二路由规则。
步骤1005、第二功能实体40根据第二路由规则处理第一业务流。
例如，作为步骤1005的一种具体实现，第二功能实体40根据第二路由规则在第一业务流的报文头中携带与第二功能实体40对应的第一功能实体30的专用隧道信息，即specific L-PSA tunnel information for PSA。
举例说明，以待执行本地业务链控制的业务流C为例进行说明，假设业务流C上行业务流用SDF1表示，下行业务流用SDF2表示。
场景1、业务流C不需要central DN进行业务链控制，则第二路由规则的具体内容，即第二功能实体40根据第二路由规则对业务流C的处理，可以如表6.1所示；第一路由规则的具体内容，即第一功能实体30根据第一路由规则对业务流C的处理，可以如表6.2所示：
表6.1第二路由规则
Figure PCTCN2019116803-appb-000007
表6.2第一路由规则
Figure PCTCN2019116803-appb-000008
场景2、业务流C需要在central DN执行业务链控制，则第二路由规则的具体内容可以如表7所示：
表7
Figure PCTCN2019116803-appb-000009
本申请实施例提供一种业务流的路由方法，该方法中会话管理网元通过第一路由规则指示第一功能实体30将已执行第一业务链控制的业务流(例如，第二业务流)通过该专用隧道发送至第二功能实体40，或者会话管理网元10通过第二路由规则指示第二功能实体40将待执行业务链控制的第一业务流利用专用隧道发送至第一功能实体30。通过利用第一功能实体30和第二功能实体40之间建立的专用隧道，这样第一功能实体30便可以确定第一业务流为待执行第一业务链控制的业务流，进而将第一业务流发送至MEC平台以执行第一业务链控制。该方法可以避免第一分流实体20中转第一功能实体30和第二功能实体40之间交互的业务流，简化第一分流实体20的对业务流的处理逻辑。
在一种可能的实施例中，如图10所示，本申请实施例提供的方法在步骤1001之前还包括：
步骤1006、会话管理网元10向第一功能实体30发送第一指示信息，以使得第一功能实体30接收来自会话管理网元10的第一指示信息。其中，第一指示信息用于指示第一功能实体30分配用于建立专用隧道的信息。
示例性的，第一功能实体30分配的用于建立专用隧道的信息为与第二功能实体40对应的第一功能实体30的专用隧道信息。例如，与第二功能实体40对应的第一功能实体30的专用隧道信息可以包括第一功能实体30的隧道端点标识、地址。例如， 与第二功能实体40对应的第一功能实体30的专用隧道信息可以为下述实施例中的specific L-PSA tunnel information for PSA。
步骤1007、会话管理网元10向第二功能实体40发送第二指示信息，所述第二指示信息用于指示第二功能实体40分配用于建立专用隧道的信息。
需要说明的是，步骤1006和步骤1007可以存在一个，或者共存。
示例性的，第二功能实体40分配的用于建立专用隧道的信息为与第一功能实体30对应的第二功能实体40的专用隧道信息。例如，与第一功能实体30对应的第二功能实体40的专用隧道信息可以包括第二功能实体40的隧道端点标识、地址。例如，与第一功能实体30对应的第二功能实体40的隧道信息可以为下述实施例中的specific PSA tunnel information for L-PSA。
步骤1008、第二功能实体40和/或第一功能实体30向会话管理网元10发送专用隧道的信息。
其中，专用隧道信息包括以下至少一项：与第一功能实体30对应的第二功能实体40的专用隧道信息、与第二功能实体40对应的第一功能实体30的专用隧道信息。一种可能的实现方式，第二功能实体40向会话管理网元10发送的专用隧道信息为与第一功能实体30对应的第二功能实体40的专用隧道信息，第一功能实体30向会话管理网元10发送的专用隧道信息为与第二功能实体40对应的第一功能实体30的专用隧道信息。
需要说明的是步骤1007和步骤1008之间无执行先后顺序。
步骤1009、会话管理网元10获取用于建立专用隧道的信息。
示例性的，用于建立专用隧道的信息可以为专用隧道的信息。
步骤1010、会话管理网元10向第一功能实体30和/或第二功能实体40发送相应的专用隧道的信息。
一种可能的实现方式，会话管理网元10向第一功能实体30发送的相应的专用隧道信息为第一功能实体30对应的第二功能实体40的专用隧道信息。会话管理网元10向第二功能实体40发送的相应的专用隧道信息为与第二功能实体40对应的第一功能实体30的专用隧道信息。
需要说明的是，当用于建立专用隧道的信息为会话管理网元10自主获取时，例如，会话管理网元10分配专用隧道信息，本申请实施例中的步骤1006～步骤1008可以省略。
需要说明的是，如果第一功能实体30和接入设备50之间也具有第三专用隧道，则第一分流实体20可以省略。对于已在MEC平台执行第一业务链控制的下行业务流，第一功能实体30可以通过第三专用隧道发送至接入设备50。对于来源于接入设备50待执行第一业务链控制的上行业务流，则接入设备50也可以通过第三专用隧道发送至第一功能实体30。此外，当结合图2b描述图10所示的方法时，第一功能实体30可以由合设网元替换。
如图11所示，图11以会话管理网元10为SMF网元，以第一分流实体20为I-UPF网元、第一功能实体30为L-PSA、第二功能实体40为PSA、接入设备50为RAN为例，详细介绍本申请实施例中的一种业务流的路由方法的具体流程，该方法包括：
步骤1101、AF网元向PCF网元发送AF请求(request)，以使得PCF网元接收AF请求。其中，AF请求携带业务流的描述信息，业务链需求，以及终端的标识。
可以理解的是，在步骤1101之前，终端的上行业务流、下行业务流的传输路径为：终端<-→RAN<-→PSA<-→central DN。
其中，业务流的描述信息(traffic description information)，用于表示AF request针对的业务流，具体可以由IP五元组、或IP三元组等表示。终端的标识，可以是终端的IP，终端的SUPI等。
业务链需求，用于指示对业务流的描述信息确定的业务流是否执行本地业务链控制，或者用于指示对业务流的描述信息确定的业务流是否由L-PSA对应的MEC平台中的SF执行业务链控制。
也即通过步骤1101，AF网元向PCF网元提供要执行本地业务链控制的业务流的描述信息。
步骤1102、PCF网元根据AF request生成PCC规则(rules)。PCC rules包含业务链信息。业务链信息，可以是业务链策略标识。
步骤1103、PCF网元触发会话策略修改过程，向SMF网元发送PCC rules。
体现到服务化接口操作上，则步骤1103可以描述为PCF网元调用Npcf_SMPolicyControl_UpdateNotify request服务，将PCC rules通知到SMF网元。
步骤1104、SMF网元根据PCC rules，决定为会话插入I-UPF、L-PSA。
其中，I-UPF充当分流点，将终端的部分业务流发送至L-PSA，另一部分发送至PSA。
步骤1105、SMF网元选择L-PSA。
步骤1105的具体实现可以参考现有技术，本申请实施例对此不作赘述。
步骤1106、SMF网元向L-PSA发送N4会话建立请求，以使得L-PSA接收N4会话建立请求。
步骤1107、L-PSA向SMF网元发送N4会话建立响应，以使得SMF网元接收N4会话建立响应。其中，N4会话建立响应中携带L-PSA隧道信息(tunnel information)。
应理解，通过步骤1106和步骤1107，SMF网元获取到了L-PSA的隧道信息。之后SMF网元将L-PSA隧道信息发送至其它用户面网元，如I-UPF，以建立I-UPF与L-PSA之间的隧道连接。
需要说明的是，L-PSA tunnel information也可以由SMF网元分配，上述仅以L-PSA分配L-PSA tunnel information为例进行说明。当由SMF网元分配L-PSA tunnel information时，SMF网元在N4会话建立请求中，将L-PSA tunnel information发送至L-PSA。同理，后续步骤中涉及tunnel information分配时，都是既可以由SMF网元分配，也可以由L-PSA、或I-UPF或PSA分配。
步骤1108、SMF网元向I-UPF网元发送N4会话建立请求，以使得I-UPF网元接收N4会话建立请求。其中，N4会话建立请求携带RAN tunnel information、PSA tunnel information、L-PSA tunnel information。
本申请实施例中的步骤1108的目的在于：建立用户面连接，即将用户面连接上的两个端点(即网元)的隧道信息传达到对端。例如，A端点获取到B端点的隧道信息、 B端点获取到A端点的隧道信息，这样A端点和B端点之间的用户面连接建立成功。这个建立过程，都是通过控制面网元，即SMF网元实现的。
其中，RAN tunnel information用于建立I-UPF网元和RAN之间的隧道，之后I-UPF网元向RAN发送的业务流的报文头中便可以携带RAN tunnel information。即，I-UPF收到要发往RAN的业务流时，可以将其发送至RAN。换句话说，I-UPF与RAN之间的隧道建立成功了。
L-PSA tunnel information用于建立I-UPF网元和L-PSA之间的隧道，之后I-UPF网元向L-PSA发送的业务流的报文头中便可以携带L-PSA tunnel information。即，I-UPF收到发往L-PSA的业务流时，可以将其发送至L-PSA了。换句话说，I-UPF与L-PSA之间的隧道建立成功了。
PSA tunnel information用于建立I-UPF网元和PSA之间的隧道，之后I-UPF网元向PSA发送的业务流的报文头中便可以携带PSA tunnel information。即，I-UPF收到发往PSA的业务流时，可以将其发送至PSA了。换句话说，I-UPF与PSA之间的隧道建立成功了。
步骤1109、I-UPF网元向SMF网元返回N4会话建立响应，以使得SMF网元接收N4会话建立响应。其中，N4会话建立响应中携带I-UPF tunnel information for PSA，I-UPF tunnel information for L-PSA。
其中，I-UPF tunnel information for PSA为I-UPF分配的与PSA对应的隧道信息，当SMF网元将该信息发送到PSA后，即PSA获取到I-UPF tunnel information for PSA后，PSA和I-UPF之间的隧道建立成功。之后，PSA向I-UPF发送的业务流的报文头中便可以携带I-UPF tunnel information for PSA，也即I-UPF可以根据业务流的报文头中携带的I-UPF tunnel information for PSA，确定业务流来源于PSA。
其中，I-UPF tunnel information for L-PSA为I-UPF分配的与L-PSA对应的隧道信息。当SMF网元将该I-UPF tunnel information for L-PSA发送至L-PSA后，即L-PSA获取到该I-UPF tunnel information for L-PSA后，L-PSA与I-UPF之间的隧道建立成功。之后，L-PSA向I-UPF发送的业务流的报文头中便可以携带I-UPF tunnel information for L-PSA，也即I-UPF可以根据业务流的报文头中携带的I-UPF tunnel information for L-PSA，确定业务流来源于L-PSA。
步骤1110、SMF网元向I-UPF发送N4会话修改请求，以使得I-UPF接收N4会话修改请求。其中，N4会话修改请求携带路由规则。其中，路由规则包含检测规则和转发规则。检测规则包括业务流标识和业务流来源。转发动作，用于表明对符合检测规则的业务流的处理逻辑，即转发至RAN、或L-PSA、或PSA。
示例性的，假设某业务流需要执行本地业务链控制或已经执行本地业务链控制，路由规则用于指示I-UPF对该业务流执行以下步骤中的任一个或多个，其中该业务流的上行方向，本申请实施例称为上行业务流；下行方向，本申请实施例称为下行业务流：
-对接收到的来自RAN的上行业务流，即报文头中携带I-UPF tunnel information for RAN的业务流，发送至L-PSA。
-对接收到的来自L-PSA的上行业务流，即报文头中携带I-UPF tunnel information for L-PSA的业务流，发送至PSA。
-对接收到的来自PSA的下行业务流，即报文头中携带I-UPF tunnel information for PSA的业务流，发送至L-PSA。
-对接收到的来自L-PSA的下行业务流，即报文头中携带I-UPF tunnel information for L-PSA的业务流，发送至RAN。
举例说明，以业务流C为待执行或需要执行本地traffic steering control的业务流(上行业务流用SDF1表示，下行业务流用SDF2表示)为例进行说明，则路由规则具体如表8所示：
表8
Figure PCTCN2019116803-appb-000010
步骤1111、I-UPF向SMF网元发送N4会话修改响应，以使得SMF网元接收N4会话修改响应。
需要说明的是，图11以在N4会话修改请求中向I-UPF发送路由规则为例，当然，SMF网元也可以在N4会话建立请求中发送路由规则，即在步骤1110中携带路由规则。如果路由规则携带在N4会话建立请求中，则步骤1110-步骤1111可以省略。也就是说，步骤1110可以与步骤1108合并，步骤1111可以与步骤1109合并。
步骤1112、SMF网元向PSA发送N4会话修改请求，以使得PSA接收N4会话修改请求。其中，会话修改请求中携带I-UPF tunnel information for PSA，以及第一转发规则。
其中，第一转发规则用于指示PSA将待执行本地业务链控制的下行业务流发送至I-UPF。具体的，PSA在下行业务流的报文头中携带I-UPF tunnel information for PSA。
需要说明的是，对于业务流需要central DN也执行业务链控制时，第一转发规则用于指示PSA对已由central DN执行业务链控制的下行业务流发送至I-UPF。也即来自PSA的待执行本地业务链控制的下行业务流可以由central DN已执行业务链控制，也可以未由central DN已执行业务链控制。
步骤1113、PSA向SMF网元发送N4会话修改响应，以使得SMF网元接收PSA的N4会话修改响应。其中，N4会话修改响应用于表示已成功接收I-UPF tunnel information for PSA，以及第一转发规则，或者N4会话修改响应中携带用于指示成功接收I-UPF tunnel information for PSA，以及第一转发规则的响应指示信息。
步骤1114、SMF向L-PSA发送N4会话修改请求，以使得L-PSA接收N4会话修 改请求。其中，N4会话修改请求中携带第二转发规则、以及I-UPF tunnel information for L-PSA。
其中，第二转发规则用于指示L-PSA对已执行本地业务链控制的上行业务流、或已执行本地业务链控制的下行业务流发送至I-UPF。即L-PSA可以在已执行本地业务链控制的上行业务流、或已执行本地业务链控制的下行业务流的报文头中携带I-UPF tunnel information for L-PSA。
步骤1115、L-PSA向SMF网元发送N4会话修改响应，以使得SMF网元接收N4会话修改响应。
其中，N4会话修改响应用于表示已成功接收I-UPF tunnel information for L-PSA，以及第二转发规则，或者N4会话修改响应中携带用于指示成功接收I-UPF tunnel information for L-PSA，以及第二转发规则的响应指示信息。
如图12所示，图12示出了本申请实施例的另一种业务流的路由方法，该图12所示的实施例与图11所示的实施例的区别在于：I-UPF与L-PSA位于同一个网元，也即图11中的I-UPF与L-PSA由合设网元替代。
步骤1201-步骤1205，同上述步骤1101-步骤1105。
在该实施例中，SM选择在的I-UPF与L-PSA是同一个网元，即I-UPF与L-PSA合设。
步骤1206、SMF网元向合设网元发送N4会话建立请求，以使得合设网元接收N4会话建立请求。
步骤1207、合设网元向SMF网元发送N4会话建立响应，以使得SMF网元接收L-PSA的N4会话建立响应。其中，N4会话管理响应中携带I-UPF tunnel information for PSA，I-UPF tunnel information for RAN。
步骤1208、SMF网元向合设网元发送N4会话修改请求，以使得合设网元接收N4会话修改请求。其中，N4会话修改请求中携带路由规则。其中，路由规则包含检测规则和转发规则。检测规则包括业务流标识和业务流来源。转发动作，用于表明对符合检测规则的业务流的处理逻辑，即转发至RAN、或PSA。
转发规则，用于指示合设网元对待执行或已执行本地业务链控制的业务流执行以下步骤中的一个或多个：
对于接收到的已执行本地业务链控制的上行业务流发送至PSA。
对于接收到的来自RAN(即报文头中携带I-UPF tunnel information for RAN)的上行业务流，执行本地业务链控制。
对于接收到来自PSA(即报文头中携带I-UPF tunnel information for PSA)的下行业务流执行本地业务链控制。
对于接收到的已执行本地业务链控制的下行业务流发送至RAN。
举例说明，以待执行或已执行本地业务链控制的业务流C为例进行说明，假设业务流C的上行业务流用SDF1表示，下行业务流用SDF2表示，则路由规则具体如表9.1所示：
表9.1
Figure PCTCN2019116803-appb-000011
Figure PCTCN2019116803-appb-000012
需要说明的是，本申请实施例中指示合设网元执行本地业务链控制可以指指示合设网元将需要执行业务链控制的业务流发送至MEC平台，由MEC平台中的SF对该业务流执行本地业务链控制。也即在合设场景，如果路由规则指示合设网元执行本地业务链控制可以理解为指示合设网元将业务流发送至MEC平台以由MEC平台中的SF执行本地业务链控制。
步骤1209、合设网元向SMF网元发送N4会话修改响应，以使得SMF网元接收N4会话修改响应。
需要说明的是，图12以在N4会话修改请求中向合设网元发送路由规则为例，当然，SMF网元也可以在N4会话建立请求中向合设网元发送路由规则，即在步骤1206中，SMF向合设网元发送路由规则。如果路由规则携带在N4会话建立请求中，则步骤1208-1209中可以省略。
步骤1210-步骤1211，同步骤1112和步骤1113，本申请实施例在此不再赘述。
如图13所示，图13示出了本申请实施例提供的一种业务流的路由方法的另一种具体实现，该方法包括：
步骤1301-步骤1307，同步骤1101-步骤1107，本申请实施例在此不再赘述。
步骤1308、SMF网元向I-UPF发送N4会话建立请求，以使得I-UPF网元接收N4会话建立请求。其中，N4会话建立请求中携带第一指示信息、RAN tunnel information、PSA tunnel information、L-PSA tunnel information。
其中，第一指示信息用于指示I-UPF分配专用隧道信息，以建立I-UPF与L-PSA之间的第一专用隧道、以及I-UPF与PSA之间的第二专用隧道。
其它参数信息为现有技术，如RAN tunnel information、PSA tunnel information、L-PSA tunnel information，本发明不再赘述。
步骤1309、I-UPF根据第一指示信息，分配专用(specific)I-UPF tunnel information for L-PSA、specific I-UPF tunnel information for PSA。
其中，specific I-UPF tunnel information for PSA即上述第二专用隧道信息。specific I-UPF tunnel information for L-PSA即上述第一专用隧道信息。
步骤1310、I-UPF向SMF网元返回N4会话建立响应，以使得SMF网元接收N4会话建立响应。其中，N4会话建立响应中携带I-UPF tunnel information for L-PSA、 I-UPF tunnel information for PSA、I-UPF tunnel information for RAN、以及specific I-UPF tunnel information for L-PSA、specific I-UPF tunnel information for PSA。
需要说明的是，对于I-UPF与L-PSA合设的场景，为方便描述，本发明称I-UPF与L-PSA合设后的网元依然为I-UPF：I-UPF(即合设网元)分配specific I-UPF tunnel information for PSA，并向SMF网元返回N4会话建立响应，此时N4会话建立响应中携带I-UPF tunnel information for PSA、I-UPF tunnel information for RAN、以及specific I-UPF tunnel information for PSA。由于I-UPF与L-PSA合设，因此I-UPF可以不分配如下信息：I-UPF tunnel information for L-PSA、specific I-UPF tunnel information for L-PSA。
步骤1311、SMF网元向I-UPF发送N4会话修改请求，以使得I-UPF接收N4会话修改请求。其中，N4会话修改请求中携带路由规则。
其中，路由规则用于指示I-UPF对待执行业务链控制或已执行第一业务链控制的业务流执行如下处理：
-对从第一专用隧道(即I-UPF与L-PSA之间的专用隧道，即报文头携带specific I-UPF tunnel info for L-PSA)上接收到的业务流，发送至PSA。
-对从第二专用隧道(即I-UPF与PSA之间的专用隧道，即报文头携带specific I-UPF tunnel info for PSA)上接收到的业务流，发送至L-PSA。
步骤1312、I-UPF向SMF网元发送N4会话修改响应，以使得SMF网元接收N4会话修改响应。
需要说明的是，图13以在N4会话修改请求中向I-UPF发送路由规则为例，当然，SMF网元也可以在N4会话建立请求中发送路由规则，即在步骤1310中SMF向I-UPF发送路由规则。如果路由规则携带在N4会话建立请求中，则步骤1311中可以省略。
需要说明的是，对于I-UPF与L-PSA合设的场景，转发规则用于指示I-UPF(即合设网元)对待执行或已执行第一业务链控制的业务流执行下述步骤中的一个或多个：
-接收到已执行本地traffic steering control的上行业务流，发送至PSA。
-接收到来自第二专用隧道(即I-UPF与PSA之间的专用隧道)的下行业务流，即报文头携带specific I-UPF tunnel info for PSA时，发送至MEC平台，以执行本地traffic steering control。
举例说明，以待执行或已执行本地traffic steering control的业务流C(上行业务流用SDF1表示，下行业务流用SDF2表示)为例，I-UPF对其处理逻辑描述如下表9.2所示：
表9.2
Figure PCTCN2019116803-appb-000013
Figure PCTCN2019116803-appb-000014
步骤1313、SMF网元向PSA发送N4会话修改请求，以使得PSA接收N4会话修改请求。其中，N4会话修改请求先后携带第一转发规则、specific I-UPF tunnel information for PSA、I-UPF tunnel information for PSA。
其中，第一转发规则用于指示PSA将待执行本地业务链控制的下行业务流，通过PSA与I-UPF之间的第二专用隧道发送至I-UPF。或者也可以理解为第一转发规则用于指示PSA在待执行本地业务链控制的下行业务流的报文头中携带specific I-UPF tunnel information for PSA。
举例说明，以待执行本地业务链控制或已执行本地业务链控制的业务流C为例进行说明，假设业务流C的上行业务流用SDF1表示，下行业务流用SDF2表示，则PSA对业务流C的处理逻辑如下：
当业务流C不需要在central DN中进行业务链控制时，则第一转发规则的具体内容可以参考表10：
表10
Figure PCTCN2019116803-appb-000015
当业务流C需要在central DN中进行业务链控制时，则第一转发规则的具体内容可以参考表11：
表11
Figure PCTCN2019116803-appb-000016
步骤1314、PSA向SMF网元返回N4会话修改响应，以使得网元接收N4会话修 改响应。
步骤1315、SMF网元向L-PSA发送N4会话修改请求，以使得L-PSA接收N4会话修改请求。其中，N4会话修改请求中携带第二转发规则、I-UPF tunnel information for L-PSA、specific I-UPF tunnel information for L-PSA。
其中，第二转发规则用于指示L-PSA对已经进行了本地业务链控制的上行业务流，通过L-PSA与I-UPF之间的第一专用隧道发送至I-UPF。换言之，第二转发规则用于指示L-PSA对已经进行了本地业务链控制的上行业务流的报文头中携带specific I-UPF tunnel information for L-PSA。
举例说明，对待执行或已执行本地traffic steering control的业务流C(上行业务流用SDF1表示，下行业务流用SDF2表示)而言，L-PSA对其处理逻辑描述如下表12所示：
表12
Figure PCTCN2019116803-appb-000017
对于已执行本地业务链控制的SDF1，L-PSA通过L-PSA与I-UPF之间的第一专用隧道将SDF1发送至I-UPF。换句话说，L-PSA为SDF1封装的GTP-U header包含specific I-UPF tunnel information for L-PSA。
步骤1316、L-PSA向SMF网元返回N4会话修改响应，以使得SMF网元接收N4会话修改响应。
需要说明的是，对于I-UPF与L-PSA合设的场景，步骤1315和步骤1316可以省略。
结合图2e或图2f，如图14所示，图14提供了本申请的另一种业务流的路由方法，该方法与图13所示的实施例的区别在于，在图14所示的实施例中，在L-PSA与PSA之间建立专用隧道。而在图13所示的实施例中，L-PSA与PSA的业务流的传输，需要通过I-UPF中转来实现。该方法包括：
步骤1401-步骤1405，同步骤1101-步骤1105，本申请实施例在此不再赘述。
步骤1406、SMF网元向L-PSA发送N4会话建立请求，以使得L-PSA接收N4会话建立请求。其中，N4会话建立请求中携带第一指示信息。该第一指示信息用于指示 L-PSA分配专用隧道信息，即分配specific L-PSA tunnel information for PSA。该专用隧道信息用于建立PSA与L-PSA之间的专用隧道连接。
步骤1407、L-PSA根据第一指示信息，分配专用隧道信息。
步骤1408、L-PSA向SMF网元返回N4会话建立响应，以使得SMF网元接收N4会话建立响应。其中，N4会话建立响应中携带L-PSA tunnel information、以及specific L-PSA tunnel information for PSA。
其中，L-PSA tunnel information用于建立I-UPF与L-PSA之间的隧道连接。该参数为现有技术，本发明不再赘述。
步骤1409、SMF网元向I-UPF发送N4会话建立请求，以使得SMF网元接收N4会话建立请求。其中，N4会话建立请求中携带RAN tunnel information、PSA tunnel information、L-PSA tunnel information。
步骤1410、I-UPF向SMF网元发送N4会话建立响应，以使得SMF网元接收来自I-UPF的N4会话建立响应。其中，N4会话建立响应中携带I-UPF tunnel information for PSA、I-UPF tunnel information for L-PSA。
步骤1411、SMF网元向PSA发送N4会话修改请求，以使得PSA接收N4会话修改请求。其中，N4会话修改请求中携带第一转发规则、第二指示信息、specific L-PSA tunnel information for PSA、I-UPF tunnel information for PSA。
其中，第一转发规则用于指示PSA对待执行业务链控制的下行业务流，通过专用隧道发送至L-PSA，即报文头携带specific L-PSA tunnel information for PSA。第二指示信息用于指示PSA分配专用隧道信息，即指示PSA分配specific PSA tunnel information for L-PSA。该专用隧道信息通过SMF发送至L-PSA，以建立L-PSA与PSA之间的专用隧道连接。
一种可能的实现方式，第二指示信息与第一转发规则为相同的参数，即第二指示信息由第一转发规则实现。
具体示例可以参考表10，此处不再赘述。
步骤1412、PSA根据第二指示信息分配专用隧道信息，即specific PSA tunnel information for L-PSA，用于建立L-PSA和PSA之间的专用隧道信息。该L-PSA和PSA之间的专用隧道信息用于PSA识别业务流来源于L-PSA，即携带该专用隧道信息的业务流，即可表明该业务流来源于PSA。
步骤1413、PSA向SMF网元返回N4会话修改响应，以使得SMF网元接收N4会话修改响应。其中，N4会话修改响应中携带PSA根据第二指示信息分配的specific PSA tunnel information for L-PSA。
步骤1414、SMF网元向L-PSA发送N4会话修改请求，以使得L-PSA接收N4会话修改请求。其中，N4会话修改请求中携带第二转发规则、specific PSA tunnel information for L-PSA、I-UPF tunnel information for L-PSA。
其中，第二转发规则用于指示L-PSA对已执行本地业务链控制的上行业务流通过专用隧道发送至PSA，即已执行本地业务链控制的上行业务流的报文头携带specific PSA tunnel information for L-PSA。此外，第二转发规则还可以指示L-PSA对从专用隧道接收到的下行业务流发送至MEC平台，由MEC平台对下行业务流执行本地业务链 控制，即下行业务流的报文头携带specific L-PSA tunnel information for PSA。其中，I-UPF tunnel information for L-PSA用于建立L-PSA和I-UPF之间的隧道，也即L-PSA向I-UPF发送的业务流的报文头中携带I-UPF tunnel information for L-PSA。
步骤1415、PSA向SMF网元返回N4会话修改响应。
如图15所示，图15示出了本申请实施例提供的另一种业务流的路由方法的具体实现，该方法包括：
步骤1501-步骤1505，同步骤1101-步骤1105。
步骤1506、SMF网元向I-UPF发送N4会话建立请求，以使得I-UPF接收N4会话建立请求。其中，N4会话建立请求中携带L-PSA tunnel information。
步骤1507、I-UPF向SMF网元发送N4会话建立响应，以使得SMF网元接收I-UPF网元的N4会话建立响应。其中，N4会话建立响应中携带I-UPF tunnel information for PSA、I-UPF tunnel information for L-PSA、I-UPF tunnel information for RAN。I-UPF tunnel information for PSA，用于建立PSA与I-UPF之间的隧道；I-UPF tunnel information for L-PSA，用于建立L-PSA与I-UPF之间的隧道；I-UPF tunnel information for RAN，用于建立RAN与I-UPF之间的隧道。
步骤1508、SMF网元向I-UPF发送N4会话修改请求，以使得I-UPF接收N4会话修改请求。其中，N4会话修改请求中携带路由规则。其中，路由规则用于指示I-UPF对待执行或已执行本地业务链控制的业务流，进行如下处理：
-对于接收到的来自RAN的上行业务流，发送至L-PSA。
-对于接收到的带有flag的上行业务流，发送至PSA。和/或，该项规则还可以描述为：对于接收到的来自L-PSA的带有flag的业务流，发送至PSA。
-对于接收到的带有flag的下行业务流，发送至L-PSA。和/或，该项规则还可以描述为：对于接收到的来自PSA的带有flag的业务流，发送至L-PSA。
另外，路由规则还用于指示I-UPF对于接收到的下行业务流，发送至RAN。
I-UPF根据如下信息判断业务流的来源：
若业务流的报文头携带I-UPF tunnel information for RAN，则该上行业务流来源于RAN。
若业务流的报文头携带I-UPF tunnel information for L-PSA，则该上行业务流来源于L-PSA。
若业务流的报文头携带I-UPF tunnel information for PSA，则该下行业务流来自PSA。
若业务流的报文头携带I-UPF tunnel information for L-PSA，则该下行业务流来自L-PSA。
举例如下：假设待执行第一业务链控制的业务流C，其上行业务流用SDF1表示，下行业务流用SDF2表示。I-UPF上的路由规则如下表13所示：
表13
Figure PCTCN2019116803-appb-000018
Figure PCTCN2019116803-appb-000019
步骤1509、I-UPF向SMF网元发送N4会话修改响应，以使得SMF网元接收N4会话修改响应。
需要说明的是，如果SMF网元向I-UPF发送的N4会话建立请求中携带路由规则，即在步骤1506中携带路由规则，则步骤1508和步骤1509可以省略。或者步骤1508中不携带路由规则。
步骤1510、SMF网元向PSA发送N4会话修改请求，以使得PSA接收N4会话修改请求。其中，N4会话修改请求中携带第一转发规则、I-UPF tunnel information for PSA。
第一转发规则用于指示PSA对待执行本地业务链控制的业务流，进行如下处理：
-当待执行本地业务链控制的业务流不需要在central DN执行业务链控制时，PSA在待执行本地业务链控制的业务流的报文头中添加flag，并发送给I-UPF。
-当待执行本地业务链控制的业务流需要在central DN执行业务链控制时，PSA在已由central DN执行业务链控制，且待执行业务链控制的下行业务流的报文头中添加flag，并发送给I-UPF。
步骤1511、PSA向SMF网元返回N4会话修改响应，以使得SMF网元接收N4会话修改响应。
步骤1512、SMF网元向L-PSA发送N4会话修改请求，以使得L-PSA接收N4会话修改请求。其中，N4会话修改请求中携带第二转发规则、I-UPF tunnel information for L-PSA。
第二转发规则用于指示L-PSA对已执行本地业务链控制的业务流，进行如下处理：
-对接收到的已执行本地业务链控制的业务流，在报文头中添加flag并发送至I-UPF。
步骤1513、L-PSA向SMF网元返回N4会话修改响应，以使得SMF网元接收N4会话修改响应。
结合图9a，如图16所示，图16中以第一分流实体20为源(source)I-UPF、第二分流实体60为目标(target)I-UPF、第三功能实体70为L-PSA2、第一功能实体30为L-PSA1为例，该方法包括：
步骤1601、SMF网元确定更改I-UPF、L-PSA。
在步骤1601之前，终端已建立了某会话，该会话对应的用户面连接1为：终端→RAN→source I-UPF→L-PSA1→本地业务链控制→L-PSA1→PSA；用户面连接2为：终端→RAN→source I-UPF→PSA。
步骤1602、SMF网元选择目标L-PSA，即L-PSA2。
例如：当终端发生移动时，SMF根据终端位置选择L-PSA2。
步骤1603、SMF网元向L-PSA2发送N4会话建立请求，以使得L-PSA2接收N4 会话建立请求。
步骤1604、L-PSA2向SMF网元发送N4会话建立响应，以使得SMF网元接收来自L-PSA2的N4会话建立响应。其中，N4会话建立响应中携带L-PSA2 tunnel information。
其中，L-PSA2 tunnel information为L-PSA2分配的隧道信息。
步骤1605、SMF网元选择target I-UPF，并建立target I-UPF与source I-UPF之间的转发隧道。
具体的步骤1605可以通过以下方式实现：SMF网元向target I-UPF发送N4会话建立请求，以使得target I-UPF接收N4会话建立请求。其中，N4会话建立请求中携带L-PSA2 tunnel information、RAN tunnel information、PSA tunnel information。
应理解，通过L-PSA2 tunnel information可以建立target I-UPF与L-PSA2之间的上行隧道。例如，target I-UPF向L-PSA2发送业务流时，如下行业务流或者上行业务流时，在业务流的报文头中携带L-PSA2 tunnel information。
通过RAN tunnel information可以建立target I-UPF与RAN之间的下行隧道。例如，target I-UPF向RAN发送下行业务流时，在下行业务流的报文头中携带RAN tunnel information。
通过PSA tunnel information可以建立target I-UPF与PSA之间的上行隧道。例如，target I-UPF向PSA发送上行业务流时，在上行业务流的报文头中携带PSA tunnel information。
之后，target I-UPF向SMF网元返回N4会话建立响应，以使得SMF网元接收N4会话建立响应。其中，N4会话建立响应中携带target I-UPF tunnel information for L-PSA1、target I-UPF tunnel information for source I-UPF、target I-UPF tunnel information for L-PSA2。
其中，target I-UPF tunnel information for L-PSA1用于建立target I-UPF和L-PSA1之间的下行隧道，这样L-PSA1向target I-UPF发送的业务流的报文头中可以携带target I-UPF tunnel information for L-PSA1。
target I-UPF tunnel information for source I-UPF用于建立source I-UPF和target I-UPF之间的下行隧道，这样source I-UPF向target I-UPF发送的业务流的报文头中可以携带target I-UPF tunnel information for source I-UPF。
target I-UPF tunnel information for L-PSA2用于建立L-PSA2和target I-UPF之间的下行隧道，这样L-PSA2向target I-UPF发送的业务流的报文头中可以携带target I-UPF tunnel information for L-PSA2。
步骤1606、SMF网元向source I-UPF发送N4会话修改请求，以使得source I-UPF接收N4会话修改请求。其中，N4会话修改请求中携带target I-UPF tunnel information for source I-UPF。
步骤1607、source I-UPF向SMF网元返回N4会话修改响应，以使得SMF网元接收N4会话修改响应。
可选的，N4会话修改响应中携带source I-UPF tunnel information for target I-UPF。source I-UPF tunnel information for target I-UPF用于建立source I-UPF和target I-UPF  之间的上行隧道，这样target I-UPF向source I-UPF发送的业务流的报文头中可以携带source I-UPF tunnel information for target I-UPF。
步骤1608、SMF网元向target I-UPF发送N4会话修改请求，以使得target I-UPF接收N4会话修改请求。
其中，N4会话修改请求中携带source I-UPF tunnel information for target I-UPF、以及转发规则。
其中，转发规则用于指示target I-UPF对待执行本地业务链控制的业务流进行如下处理：当从source I-UPF(即从source I-UPF与target I-UPF之间的转发隧道，即报文头携带target I-UPF tunnel information for source I-UPF)接收到该业务流时，可以不用发送至L-PSA2，发送至RAN即可。转发规则还用于指示target I-UPF对待执行本地业务链控制的业务流进行如下处理：当从PSA(即报文头携带target I-UPF tunnel information for PSA)接收到该业务流时，发送L-PSA2。
需要说明的是，转发规则也可以理解为一种指示信息。
步骤1609、target I-UPF向SMF网元返回N4会话修改响应。
步骤1610、SMF网元更新PSA的下行用户面信息。具体的，SMF向PSA发送N4会话修改请求，携带target I-UPF tunnel information for PSA。PSA返回N4会话修改响应。
步骤1611、SMF网元向L-PSA2发送N4会话修改请求，以使得L-PSA2接收N4会话修改请求。其中，N4会话修改请求中携带target I-UPF tunnel information for L-PSA2。
步骤1612、L-PSA2向SMF网元返回N4会话修改响应。
至此，待执行本地业务链控制的下行业务流的传输路径为：
(1)下行业务流路径1
PSA→target I-UPF→L-PSA2→traffic steering control→L-PSA2→target I-UPF→RAN→终端。
(2)下行业务流路径2
PSA→source I-UPF→L-PSA1→traffic steering control→L-PSA1→source I-UPF→target I-UPF→RAN→终端。
在下行业务流路径2中target I-UPF对来自source I-UPF的业务流转发至RAN。即无须将业务链发送至L-PSA2，以使L-PSA2进行本地业务链控制。
步骤1613、SMF网元更新RAN的上行用户面信息。具体的，SMF网元通过AMF网元向RAN发送N2请求，携带target I-UPF tunnel information for RAN。RAN返回N2响应。
综上，在图16中虽然I-UPF从source I-UPF变为target I-UPF，但是由于PSA还可能将下行业务流C(该下行业务流C为待执行第一业务链控制的业务流)发送给source I-UPF(例如，下行业务流路径1)，因此当source I-UPF接收到来自PSA的下行业务流C时，仍然可以将下行业务流C发送给L-PSA1，以由L-PSA1对应的MEC平台对下行业务流C执行业务链控制。在下行业务流C已执行完业务链控制之后，由source I-UPF将已执行完业务链控制的下行业务流C发送给target I-UPF，进而发送回 RAN。
如图17所示，图17示出了本申请实施例提供的另一种业务流的路由方法，该方法与图16的区别在于，在图17中由target I-UPF将下行业务流发送至L-PSA2，以由L-PSA2对应的MEC对业务流执行traffic steering control，而source I-UPF可以将来自PSA的下行业务流转发给target I-UPF即可，不需要对来自PSA的下行业务流转发给L-PSA1，以由L-PSA1对应的MEC对业务流执行traffic steering control。
步骤1701-步骤1704，同步骤1601-步骤1604。
步骤1705、SMF网元向source I-UPF发送N4会话修改请求，以使得source I-UPF接收N4会话修改请求。其中，N4会话修改请求中携带target I-UPF tunnel information for source I-UPF、转发规则。
其中，转发规则用于指示source I-UPF对待执行本地业务链控制的业务流进行如下处理：当从PSA收到该下行业务流时，source I-UPF将下行业务流发送至target I-UPF，即通过source I-UPF与target I-UPF之间的转发隧道将下行业务流发送至target I-UPF，也即为下行业务流的报文头封装target I-UPF tunnel information for source I-UPF。
可以理解的是，步骤1705中的转发规则中包括检测规则和转发动作。其中，检测规则包括待执行本地业务链控制的业务流的描述信息。转发动作用于表示将待执行本地业务链控制的业务流的描述信息确定的业务流转发给target I-UPF。对于source I-UPF而言，其无需判断来自PSA的下行业务流是否为待执行本地业务链控制的业务流，source I-UPF一旦确定接收到来自PSA的下行业务流，则将来自PSA的下行业务流转发给target I-UPF。
步骤1706、source I-UPF向SMF网元返回N4会话修改响应，以使得SMF网元接收N4会话修改响应。可选的，N4会话修改响应中携带source I-UPF tunnel information for target I-UPF。
步骤1707、SMF网元向target I-UPF发送N4会话修改请求，以使得target I-UPF接收N4会话修改请求。其中，N4会话修改请求中携带source I-UPF tunnel info information for target I-UPF、转发规则。
其中，转发规则用于指示target I-UPF对待执行本地业务链控制的业务流进行如下处理：无论从source I-UPF(即从source I-UPF与target I-UPF之间的转发隧道，即报文头携带target I-UPF tunnel information for source I-UPF)接收到该业务流时，还是从PSA(即报文头携带target I-UPF tunnel information for PSA)接收到该业务流时，则发送至L-PSA2。
步骤1708、target I-UPF向SMF网元返回N4会话修改响应。
可以理解的是，步骤1707中的转发规则中包括检测规则和转发动作。其中，检测规则包括待执行本地业务链控制的业务流的描述信息。转发动作用于表示将待执行本地业务链控制的业务流的描述信息确定的业务流转发给L-PSA2。对于target I-UPF而言，其无需判断来自PSA的下行业务流或来自source I-UPF的下行业务流是否为待执行本地业务链控制的业务流，target I-UPF一旦确定接收到来自PSA或source I-UPF的下行业务流的描述信息存在于检测规则中，则将该下行业务流转发给L-PSA2。
本申请实施例中，当业务流不仅要由MEC执行本地业务链控制还要由central DN 执行业务链控制时，如何下发业务链信息，如业务流策略标识。
思路1：SMF网元从PCF网元接收到业务链策略信息后，向L-PSA下发业务链信息1、向PSA下发业务链信息2。具体的，SMF网元根据DNAI、业务链策略信息，决定向L-PSA下发业务链信息1、向PSA下发业务链信息2。
举例：业务链策略对应的是业务流C的上行方向，即SDF1，经过SF1、SF2、SF3、SF4处理；下行方向，经过SF3、SF4、SF5、SF2处理。其中SF1、SF2位于MEC平台，L-PSA可以访问MEC平台。SF3、SF4位于central DN，PSA可以访问central DN。
因此SMF网元向L-PSA下发的业务链信息1为(仅以上行为例进行说明)：SDF1需要经过SF1、SF2处理；向PSA下发的业务链信息2为：SDF1需要经过SF3、SF4处理。
思路2、SMF网元从PCF网元接收到业务链策略信息后，向L-PSA发送业务链信息，或向PSA发送业务链信息。即SMF网元分别向L-PSA、PSA下发相应的业务链信息。举例：以上述例子进行说明，那么上行方向：SMF网元向L-PSA下发业务链信息，该业务链信息指示SDF1需要经过SF1、SF2、SF3、SF4处理。下行方向：SMF网元向PSA下发业务链信息，该业务链信息指示SDF2需要经过SF3、SF4、SF5、SF2处理。
上述主要从各个网元之间交互的角度对本申请实施例的方案进行了介绍。可以理解的是，各个网元，例如会话管理网元、第一分流实体、第一功能实体和第二功能实体等为了实现上述功能，其包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例会话管理网元、第一分流实体、第一功能实体和第二功能实体进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
上面结合图6至图17，对本申请实施例的方法进行了说明，下面对本申请实施例提供的执行上述方法的通信装置进行描述。本领域技术人员可以理解，方法和装置可以相互结合和引用，本申请实施例提供的通信装置可以执行上述通信方法中由会话管理网元、第一分流实体执行的步骤。
在采用集成的单元的情况下，图18示出了上述实施例中所涉及的一种通信装置，该通信装置可以包括：通信单元102和处理单元101。
一种示例，该通信装置为会话管理网元，或者为应用于会话管理网元中的芯片。在这种情况下，处理单元101用于支持该通信装置执行上述实施例的图6中由会话管理网元执行图6中的步骤601。通信单元102，用于支持该通信装置执行图6的步骤 602中由会话管理网元执行的发送的动作。
在一种可能的实施例中，通信单元102，还用于支持通信装置执行上述实施例中的步骤606中由会话管理网元接收的动作、(步骤607、步骤610、步骤611、步骤612、步骤613、步骤616、步骤617)中由会话管理网元执行的发送的动作，步骤608或步骤609中会话管理网元接收的动作、步骤611。处理单元101，还用于支持通信装置执行上述实施例中的步骤609、步骤614中由会话管理网元处理的动作。
另一种示例，该通信装置为第一分流实体，或者为应用于第一分流实体中的芯片。在这种情况下，通信单元102，用于支持该通信装置执行上述实施例中的步骤602中由第一分流实体接收的动作。处理单元101，用于支持该通信装置执行上述实施例中的步骤603中由第一分流实体处理的动作。
在一种可能的实施例中，该通信单元102还用于该通信装置执行上述实施例中的步骤607中由第一分流实体接收的动作、步骤608中由第一分流实体接收的动作。
再一种示例，该通信装置为会话管理网元，或者为应用于会话管理网元中的芯片。通信单元102，用于支持该通信装置执行上述实施例中的步骤1002中由会话管理网元发送的动作。处理单元101用于支持该通信装置执行上述实施例的步骤1001中由会话管理网元处理的动作。
在一种可能的实施例中，该通信单元102还用于该通信装置执行上述实施例中的步骤1004、步骤1006、步骤1007、步骤1010中由会话管理网元发送的动作。通信单元102还用于支持该通信装置执行步骤1009中由会话管理网元接收的动作。或者处理单元101用于支持该通信装置执行步骤1009中由会话管理网元自主获取用于建立专用隧道的信息的动作。
在采用集成的单元的情况下，图19示出了上述实施例中所涉及的通信装置的一种可能的逻辑结构示意图。该通信装置包括：处理模块112和通信模块113。处理模块112用于对通信装置的动作进行控制管理，例如，处理模块112用于执行在通信装置进行信息/数据处理的步骤。通信模块113用于支持通信装置进行信息/数据发送或者接收的步骤。
在一种可能的实施例中，通信装置还可以包括存储模块111，用于存储通信装置可的程序代码和数据。
一种示例，该通信装置为会话管理网元，或者为应用于会话管理网元中的芯片。在这种情况下，处理模块112用于支持该通信装置执行上述实施例的图6中由会话管理网元执行图6中的步骤601。通信模块113，用于支持该通信装置执行图6的步骤602中由会话管理网元执行的发送的动作。
在一种可能的实施例中，通信模块113，还用于支持通信装置执行上述实施例中的步骤606中由会话管理网元接收的动作、(步骤607、步骤610、步骤611、步骤612、步骤613、步骤616、步骤617)中由会话管理网元执行的发送的动作，步骤608或步骤609中会话管理网元接收的动作、步骤611。处理模块112，还用于支持通信装置执行上述实施例中的步骤609、步骤614中由会话管理网元处理的动作。
另一种示例，该通信装置为第一分流实体，或者为应用于第一分流实体中的芯片。在这种情况下，通信模块113，用于支持该通信装置执行上述实施例中的步骤602中 由第一分流实体接收的动作。处理模块112，用于支持该通信装置执行上述实施例中的步骤603中由第一分流实体处理的动作。
在一种可能的实施例中，该通信模块113还用于该通信装置执行上述实施例中的步骤607中由第一分流实体接收的动作、步骤608中由第一分流实体接收的动作。
再一种示例，该通信装置为会话管理网元，或者为应用于会话管理网元中的芯片。通信模块113，用于支持该通信装置执行上述实施例中的步骤1002中由会话管理网元发送的动作。处理模块112用于支持该通信装置执行上述实施例的步骤1001中由会话管理网元处理的动作。
在一种可能的实施例中，该通信模块113还用于该通信装置执行上述实施例中的步骤1004、步骤1006、步骤1007、步骤1010中由会话管理网元发送的动作。通信模块113还用于支持该通信装置执行步骤1009中由会话管理网元接收的动作。或者处理模块112用于支持该通信装置执行步骤1009中由会话管理网元自主获取用于建立专用隧道的信息的动作。
其中，处理模块112可以是处理器或控制器，例如可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。通信模块113可以是收发器、收发电路或通信接口等。存储模块111可以是存储器。
当处理模块112为处理器41或处理器45，通信模块113为通信接口43时，存储模块111为存储器42时，本申请所涉及的通信装置可以为图4所示的通信设备。
图20是本申请实施例提供的芯片150的结构示意图。芯片150包括一个或两个以上(包括两个)处理器1510和通信接口1530。
可选的，该芯片150还包括存储器1540，存储器1540可以包括只读存储器和随机存取存储器，并向处理器1510提供操作指令和数据。存储器1540的一部分还可以包括非易失性随机存取存储器(non-volatile random access memory，NVRAM)。
在一些实施方式中，存储器1540存储了如下的元素，执行模块或者数据结构，或者他们的子集，或者他们的扩展集。
在本申请实施例中，通过调用存储器1540存储的操作指令(该操作指令可存储在操作系统中)，执行相应的操作。
一种可能的实现方式中为：会话管理网元、第一分流实体所用的芯片的结构类似，不同的装置可以使用不同的芯片以实现各自的功能。
处理器1510控制会话管理网元、第一分流实体中任一个的处理操作，处理器1510还可以称为中央处理单元(central processing unit，CPU)。
存储器1540可以包括只读存储器和随机存取存储器，并向处理器1510提供指令和数据。存储器1540的一部分还可以包括NVRAM。例如应用中存储器1540、通信接口1530以及存储器1540通过总线系统1520耦合在一起，其中总线系统1520除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图20中将各种总线都标为总线系统1520。
上述本申请实施例揭示的方法可以应用于处理器1510中，或者由处理器1510实现。处理器1510可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1510中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1510可以是通用处理器、数字信号处理器(digital signal processing，DSP)、ASIC、现成可编程门阵列(field-programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1540，处理器1510读取存储器1540中的信息，结合其硬件完成上述方法的步骤。
一种可能的实现方式中，通信接口1530用于执行图6-图17所示的实施例中的会话管理网元、第一分流实体的接收和发送的步骤。处理器1510用于执行图6-图17所示的实施例中的会话管理网元、第一分流实体的处理的步骤。
以上通信单元可以是该装置的一种通信接口，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该通信单元是该芯片用于从其它芯片或装置接收信号或发送信号的通信接口。
一方面，提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令被运行时，实现如图6-图9、图11-图17中会话管理网元的功能。
一方面，提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令被运行时，实现如图10中会话管理网元的功能。
另一方面，提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令被运行时，实现如图6-图17中第一分流实体的功能。
一方面，提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图6-图17中会话管理网元的功能。
又一方面，提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图6-图17中第一分流实体的功能。
一方面，提供一种芯片，该芯片应用于网管网元中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图6-图17中会话管理网元的功能。
又一方面，提供一种芯片，该芯片应用于Donor节点中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图6-图17中第一分流实体的功能。
本申请实施例提供一种通信系统，该通信系统包括：会话管理网元和第一分流实体。其中，会话管理网元用于执行图6-图17中的任一个由会话管理网元执行的步骤，第一分流实体用于执行图6-图17中的任一个由第一分流实体执行的步骤。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算 机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘(digital video disc，DVD)；还可以是半导体介质，例如，固态硬盘(solid state drive，SSD)。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看附图、公开内容、以及所附权利要求书，可理解并实现公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (46)

  1. 一种业务流的路由方法，其特征在于，包括：
    会话管理网元确定路由规则，所述路由规则用于指示第一分流实体将第一业务流发送至第一功能实体，和/或，将第二业务流发送至第二功能实体或接入设备，所述第一业务流为待执行第一业务链控制的业务流，所述第二业务流为已执行所述第一业务链控制的业务流；
    在会话管理过程中，所述会话管理网元向所述第一分流实体发送所述路由规则。
  2. 根据权利要求1所述的方法，其特征在于，所述路由规则包括：所述第一业务流的描述信息和与所述第一业务流的描述信息关联的所述第一功能实体的信息，和/或，所述第二业务流的描述信息和所述第二业务流的描述信息关联的所述第二功能实体的信息或接入设备的信息；其中，所述描述信息包括所述第一业务流的来源信息或所述第二业务流的来源信息。
  3. 根据权利要求2所述的方法，其特征在于，所述路由规则包括以下信息中的任一个或多个：
    所述第一业务流的描述信息指示所述第一业务流来自所述接入设备或所述第二功能实体时，所述第一分流实体向所述第一功能实体发送所述第一业务流；或，
    所述第二业务流的描述信息指示所述第二业务流来自所述第一功能实体时，所述第一分流实体向所述接入设备或所述第二功能实体发送所述第二业务流。
  4. 根据权利要求1所述的方法，其特征在于，所述路由规则用于指示所述第一分流实体向所述第一功能实体发送来自第二专用隧道的所述第一业务流，和/或，指示所述第一分流实体向所述第二功能实体发送来自第一专用隧道的所述第二业务流；
    其中，所述第二专用隧道位于所述第一分流实体和所述第二功能实体之间，所述第一专用隧道位于所述第一分流实体和所述第一功能实体之间。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元获取第一专用隧道信息和第二专用隧道信息中的一个或多个；所述第一专用隧道信息用于建立所述第一专用隧道；所述第二专用隧道信息用于建立所述第二专用隧道。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元向所述第二功能实体发送所述第二专用隧道信息以及第一转发规则，所述第一转发规则用于指示所述第二功能实体通过所述第二专用隧道向所述第一分流实体传输所述第一业务流。
  7. 根据权利要求5或6所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元向所述第一功能实体发送所述第一专用隧道信息以及第二转发规则，所述第二转发规则用于指示所述第一功能实体通过所述第一专用隧道向所述第一分流实体传输所述第二业务流。
  8. 根据权利要求5-7任一项所述的方法，其特征在于，所述会话管理网元获取第一专用隧道信息和第二专用隧道信息中的一个或多个之前，所述方法还包括：
    所述会话管理网元向所述第一分流实体发送第一指示信息，所述第一指示信息用于指示所述第一分流实体分配第一专用隧道信息和第二专用隧道信息中的一个或多个；
    所述会话管理网元获取第一专用隧道信息和第二专用隧道信息中的一个或多个，包括：
    所述会话管理网元接收来自所述第一分流实体的所述第一专用隧道信息和所述第二专用隧道信息中的一个或多个。
  9. 根据权利要求1所述的方法，其特征在于，
    所述第一业务流和第一标识相关联，所述路由规则用于指示所述第一分流实体向所述第一功能实体发送与所述第一标识关联的业务流；或，
    所述第二业务流和第二标识相关联，所述路由规则用于指示所述第一分流实体向所述第二功能实体发送与第二标识关联的业务流。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元向所述第二功能实体发送第三指示信息，所述第三指示信息用于指示所述第二功能实体在所述第一业务流的报文头中携带所述第一标识。
  11. 根据权利要求9或10所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元向所述第一功能实体发送第四指示信息，所述第四指示信息用于指示所述第一功能实体在所述第二业务流的报文头中携带所述第二标识。
  12. 根据权利要求1-11任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元确定分流实体从所述第一分流实体变为第二分流实体；
    所述会话管理网元向所述第二分流实体发送第五指示信息，所述第五指示信息用于指示所述第二分流实体执行以下步骤中的任一个或多个：
    向所述接入设备发送来源于所述第一分流实体的第三业务流；所述第三业务流为已执行第一业务链控制的业务流；或，
    向所述第二分流实体对应的第三功能实体发送来源于所述第二功能实体的第四业务流，所述第四业务流为待执行第一业务链控制的业务流。
  13. 根据权利要求1-11任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元确定分流实体从所述第一分流实体变为第二分流实体；
    所述会话管理网元向所述第一分流实体或第二功能实体发送第六指示信息，所述第六指示信息用于指示所述第一分流实体或第二功能实体向所述第二分流实体发送第五业务流；所述第五业务流为待执行第一业务链控制的业务流；
    所述会话管理网元向所述第二分流实体发送第七指示信息，所述第七指示信息用于指示所述第二分流实体向所述第二分流实体对应的第三功能实体发送所述第五业务流。
  14. 一种业务流的路由方法，其特征在于，包括：
    在会话管理过程中，第一分流实体接收来自会话管理网元的路由规则，所述路由规则用于指示所述第一分流实体将第一业务流发送至第一功能实体，和/或，将第二业务流发送至第二功能实体或接入设备，所述第一业务流为待执行第一业务链控制的业务流，所述第二业务流为已执行所述第一业务链控制的业务流；
    所述第一分流实体根据所述路由规则，传输所述第一分流实体接收到的目标业务流。
  15. 根据权利要求14所述的方法，其特征在于，所述路由规则包括：所述第一业 务流的描述信息和与所述第一业务流的描述信息关联的所述第一功能实体的信息，和/或，所述第二业务流的描述信息和所述第二业务流的描述信息关联的所述第二功能实体的信息或接入设备的信息；其中，所述描述信息包括所述第一业务流或所述第二业务流的来源信息。
  16. 根据权利要求15所述的方法，其特征在于，所述第一分流实体根据所述路由规则，传输所述第一分流实体接收到的目标业务流，包括：
    所述目标业务流的描述信息与所述第一业务流的描述信息相同，所述第一分流实体向所述第一功能实体发送所述目标业务流；和/或，
    所述目标业务流的描述信息与所述第二业务流的描述信息相同，所述第一分流实体向所述第二功能实体或所述接入设备发送所述目标业务流。
  17. 根据权利要求14所述的方法，其特征在于，所述路由规则用于指示所述第一分流实体向所述第一功能实体发送来自第二专用隧道的所述第一业务流，和/或，指示所述第一分流实体向所述第二功能实体发送来自第一专用隧道的所述第二业务流；其中，所述第二专用隧道位于所述第一分流实体和所述第二功能实体之间，所述第一专用隧道位于所述第一分流实体和所述第一功能实体之间。
  18. 根据权利要求17所述的方法，其特征在于，所述第一分流实体根据所述路由规则，传输所述第一分流实体接收到的目标业务流，包括：
    所述目标业务流来源于所述第一专用隧道，所述第一分流实体将所述目标业务流发送至所述第二功能实体；或，
    所述目标业务流来源于所述第二专用隧道，所述第一分流实体将所述目标业务流发送至所述第一功能实体。
  19. 根据权利要求17或18所述的方法，其特征在于，所述方法还包括：
    所述第一分流实体接收来自所述会话管理网元的第一指示信息，所述第一指示信息用于指示所述第一分流实体分配第一专用隧道信息和第二专用隧道信息中的一个或多个，所述第一专用隧道信息用于建立所述第一专用隧道；所述第二专用隧道信息用于建立所述第二专用隧道；
    所述第一分流实体向所述会话管理网元发送所述第一专用隧道信息和第二专用隧道信息中的一个或多个。
  20. 根据权利要求14所述的方法，其特征在于，所述第一业务流和第一标识相关联，所述路由规则用于指示所述第一分流实体向所述第一功能实体发送与所述第一标识关联的业务流；或，
    所述第二业务流和第二标识相关联，所述路由规则用于指示所述第一分流实体向所述第二功能实体发送与第二标识关联的业务流。
  21. 根据权利要求20所述的方法，其特征在于，所述第一分流实体根据所述路由规则，传输所述第一分流实体接收到的目标业务流，包括：
    所述目标业务流与第一标识关联，所述第一分流实体向所述第一功能实体发送所述业务流；或，
    所述目标业务流与第二标识关联，所述第一分流实体向所述第二功能实体发送所述业务流。
  22. 一种通信装置，其特征在于，包括：
    处理单元，用于确定路由规则，所述路由规则用于指示所述第一分流实体将第一业务流发送至第一功能实体，和/或，将第二业务流发送至第二功能实体或接入设备，所述第一业务流为待执行第一业务链控制的业务流，所述第二业务流为已执行所述第一业务链控制的业务流；
    在会话管理过程中，通信单元，用于向所述第一分流实体发送所述路由规则。
  23. 根据权利要求22所述的装置，其特征在于，所述路由规则包括所述第一业务流的描述信息和与所述第一业务流的描述信息关联的所述第一功能实体的信息，和/或，所述第二业务流的描述信息和所述第二业务流的描述信息关联的所述第二功能实体的信息或接入设备的信息；其中，所述描述信息包括所述第一业务流或所述第二业务流的来源信息。
  24. 根据权利要求23所述的装置，其特征在于，所述路由规则包括以下信息中的任一个或多个：
    所述第一业务流的描述信息指示所述第一业务流来自所述接入设备或所述第二功能实体时，所述第一分流实体向所述第一功能实体发送所述第一业务流；或，
    所述第二业务流的描述信息指示所述第二业务流来自所述第一功能实体时，所述第一分流实体向所述接入设备或所述第二功能实体发送所述第二业务流。
  25. 根据权利要求22所述的装置，其特征在于，所述路由规则用于指示所述第一分流实体向所述第一功能实体发送来自第二专用隧道的所述第一业务流，和/或，指示所述第一分流实体向所述第二功能实体发送来自第一专用隧道的所述第二业务流；其中，所述第二专用隧道位于所述第一分流实体和所述第二功能实体之间，所述第一专用隧道位于所述第一分流实体和所述第一功能实体之间。
  26. 根据权利要求25所述的装置，其特征在于，所述处理单元，还用于获取第一专用隧道信息和第二专用隧道信息中的一个或多个；所述第一专用隧道信息用于建立所述第一专用隧道；所述第二专用隧道信息用于建立所述第二专用隧道。
  27. 根据权利要求26所述的装置，其特征在于，所述通信单元，还用于向所述第二功能实体发送所述第二专用隧道信息以及第一转发规则，所述第一转发规则用于指示所述第二功能实体通过所述第二专用隧道向所述第一分流实体传输所述第一业务流。
  28. 根据权利要求26或27所述的装置，其特征在于，所述通信单元，还用于向所述第一功能实体发送所述第一专用隧道信息以及第二转发规则，所述第二转发规则用于指示所述第一功能实体通过所述第一专用隧道向所述第一分流实体传输所述第二业务流。
  29. 根据权利要求26-28任一项所述的装置，其特征在于，所述处理单元用于获取第一专用隧道信息和第二专用隧道信息中的一个或多个之前，所述通信单元，还用于向所述第一分流实体发送第一指示信息，所述第一指示信息用于指示所述第一分流实体分配第一专用隧道信息和第二专用隧道信息中的一个或多个；
    所述处理单元，具体用于通过所述通信单元接收来自所述第一分流实体的所述第一专用隧道信息和所述第二专用隧道信息中的一个或多个。
  30. 根据权利要求22所述的装置，其特征在于，
    所述第一业务流和第一标识相关联，所述路由规则用于指示所述第一分流实体向所述第一功能实体发送与所述第一标识关联的业务流；或，
    所述第二业务流和第二标识相关联，所述路由规则用于指示所述第一分流实体向所述第二功能实体发送与第二标识关联的业务流。
  31. 根据权利要求30所述的装置，其特征在于，所述通信单元，还用于向所述第二功能实体发送第三指示信息，所述第三指示信息用于指示所述第二功能实体在所述第一业务流的报文头中携带所述第一标识。
  32. 根据权利要求30或31所述的装置，其特征在于，所述通信单元，还用于向所述第一功能实体发送第四指示信息，所述第四指示信息用于指示所述第一功能实体在所述第二业务流的报文头中携带所述第二标识。
  33. 根据权利要求22-30任一项所述的装置，其特征在于，所述处理单元，还用于确定分流实体从所述第一分流实体变为第二分流实体；
    所述通信单元，还用于向所述第二分流实体发送第五指示信息，所述第五指示信息用于指示所述第二分流实体执行以下步骤中的任一个或多个：
    向所述接入设备发送来源于所述第一分流实体的第三业务流；所述第三业务流为已执行第一业务链控制的业务流；或，
    向所述第二分流实体对应的第三功能实体发送来源于所述第二功能实体的第四业务流，所述第四业务流为待执行第一业务链控制的业务流。
  34. 根据权利要求22-33任一项所述的装置，其特征在于，所述处理单元，还用于确定分流实体从所述第一分流实体变为第二分流实体；
    所述通信单元，还用于向所述第一分流实体发送第六指示信息，所述第六指示信息用于指示所述第一分流实体向所述第二分流实体发送第五业务流；所述第五业务流为待执行第一业务链控制的业务流；
    所述通信单元，还用于向所述第二分流实体发送第七指示信息，所述第七指示信息用于指示所述第二分流实体向所述第二分流实体对应的第三功能实体发送所述第五业务流。
  35. 一种通信装置，其特征在于，包括：
    在会话管理过程中，通信单元，用于接收来自会话管理网元的路由规则，所述路由规则用于指示将第一业务流发送至第一功能实体，和/或，将第二业务流发送至第二功能实体或接入设备，所述第一业务流为待执行第一业务链控制的业务流，所述第二业务流为已执行所述第一业务链控制的业务流；
    通信单元，还用于根据所述路由规则，传输所述第一分流实体接收到的目标业务流。
  36. 根据权利要求35所述的装置，其特征在于，所述路由规则包括所述第一业务流的描述信息和与所述第一业务流的描述信息关联的所述第一功能实体的信息，和/或，所述第二业务流的描述信息和所述第二业务流的描述信息关联的所述第二功能实体的信息或接入设备的信息；其中，所述描述信息包括所述第一业务流或所述第二业务流的来源信息。
  37. 根据权利要求36所述的装置，其特征在于，所述目标业务流的描述信息与所 述第一业务流的描述信息相同，所述通信单元，具体用于所述第一分流实体向所述第一功能实体发送所述目标业务流；和/或，
    所述目标业务流的描述信息与所述第二业务流的描述信息相同，所述通信单元，具体用于向所述第二功能实体或所述接入设备发送所述目标业务流。
  38. 根据权利要求35所述的装置，其特征在于，所述路由规则用于指示向所述第一功能实体发送来自第二专用隧道的所述第一业务流，和/或，指示向所述第二功能实体发送来自第一专用隧道的所述第二业务流；其中，所述第二专用隧道位于所述装置和所述第二功能实体之间，所述第一专用隧道位于所述装置和所述第一功能实体之间。
  39. 根据权利要求38所述的装置，其特征在于，所述目标业务流来源于所述第二专用隧道，所述通信单元，具体用于将所述目标业务流发送至所述第一功能实体；或，
    所述目标业务流来源于所述第二专用隧道，所述通信单元，具体用于将所述目标业务流发送至所述第一功能实体。
  40. 根据权利要求38或39所述的装置，其特征在于，所述通信单元，还用于接收来自所述会话管理网元的第一指示信息，所述第一指示信息用于指示所述第一分流实体分配第一专用隧道信息和第二专用隧道信息中的一个或多个，所述第一专用隧道信息用于建立所述第一专用隧道；所述第二专用隧道信息用于建立所述第二专用隧道；
    所述通信单元，还用于向所述会话管理网元发送所述第一专用隧道信息和第二专用隧道信息中的一个或多个。
  41. 根据权利要求35所述的装置，其特征在于，第一业务流和第一标识相关联，所述路由规则用于指示向所述第一功能实体发送与所述第一标识关联的业务流；或，
    所述第二业务流和第二标识相关联，所述路由规则用于指示向所述第二功能实体发送与第二标识关联的业务流。
  42. 根据权利要求41所述的装置，其特征在于，
    所述目标业务流与第一标识关联，所述通信单元，具体用于向所述第一功能实体发送所述目标业务流；或，
    所述目标业务流与第二标识关联，所述通信单元，具体用于向所述第二功能实体发送所述目标业务流。
  43. 一种计算机可读存储介质，其特征在于，所述可读存储介质中存储有指令，当所述指令被执行时，实现如权利要求1-13任一项所述的方法，或者，如权利要求14-21任一项所述的方法。
  44. 一种芯片，其特征在于，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行计算机程序或指令，以实现如权利要求1-13任一项所述的方法，或者，如权利要求14-21任一项所述的方法，所述通信接口用于与所述芯片之外的其它模块进行通信。
  45. 一种通信装置，其特征在于，包括：处理器和通信接口，其中，所述通信接口用于执行如权利要求1-13任一项所述的方法中在所述会话管理网元中进行消息收发的操作；所述处理器运行指令以执行如权利要求1-13任一项所述的方法中在所述会话管理网元中进行处理或控制的操作；
    或者，
    所述通信接口用于执行如权利要求14-21任一项所述的方法中在所述第一分流实体中进行消息收发的操作；所述处理器运行指令以执行如权利要求14-21任一项所述的方法中在所述第一分流实体中进行处理或控制的操作。
  46. 一种通信系统，其特征在于，所述系统包括：如权利要求22-34任一项所述的通信装置，以及如权利要求35-42任一项所述的通信装置。
PCT/CN2019/116803 2019-11-08 2019-11-08 一种业务流的路由方法、装置及系统 WO2021088018A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
PCT/CN2019/116803 WO2021088018A1 (zh) 2019-11-08 2019-11-08 一种业务流的路由方法、装置及系统
EP19952041.2A EP4044666A4 (en) 2019-11-08 2019-11-08 TRAFFIC FLOW ROUTING METHOD, DEVICE AND SYSTEM
CN201980101714.2A CN114631350B (zh) 2019-11-08 2019-11-08 一种业务流的路由方法、装置及系统
US17/738,782 US11963032B2 (en) 2019-11-08 2022-05-06 Traffic routing method, apparatus, and system
US18/616,049 US20240236755A1 (en) 2019-11-08 2024-03-25 Traffic routing method, apparatus, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/116803 WO2021088018A1 (zh) 2019-11-08 2019-11-08 一种业务流的路由方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/738,782 Continuation US11963032B2 (en) 2019-11-08 2022-05-06 Traffic routing method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2021088018A1 true WO2021088018A1 (zh) 2021-05-14

Family

ID=75849271

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/116803 WO2021088018A1 (zh) 2019-11-08 2019-11-08 一种业务流的路由方法、装置及系统

Country Status (4)

Country Link
US (2) US11963032B2 (zh)
EP (1) EP4044666A4 (zh)
CN (1) CN114631350B (zh)
WO (1) WO2021088018A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115396873B (zh) * 2022-08-23 2024-05-03 中国联合网络通信集团有限公司 一种通信方法、装置、服务器及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109275160A (zh) * 2017-07-17 2019-01-25 华为技术有限公司 数据分流方法、设备及系统
CN109428909A (zh) * 2017-08-23 2019-03-05 中兴通讯股份有限公司 会话锚点的控制方法、装置和服务器
US20190109721A1 (en) * 2017-10-09 2019-04-11 Comcast Cable Communications, Llc Ethernet type packet data unit session communications

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9509549B2 (en) * 2013-03-15 2016-11-29 Cisco Technology, Inc. Extending routing rules from external services
US9634867B2 (en) * 2014-05-02 2017-04-25 Futurewei Technologies, Inc. Computing service chain-aware paths
US9722927B2 (en) * 2014-06-05 2017-08-01 Futurewei Technologies, Inc. Service chain topology map construction
WO2017125168A1 (en) * 2016-01-22 2017-07-27 Telefonaktiebolaget Lm Ericsson (Publ) Charging for services in telecommunications networks
US10079767B2 (en) * 2016-06-13 2018-09-18 Cisco Technology, Inc. Multi-mobile core networks and value-added services
EP3485608B1 (en) * 2016-07-13 2020-06-24 Telefonaktiebolaget LM Ericsson (PUBL) Methods and servers for managing traffic steering policies
US10531420B2 (en) * 2017-01-05 2020-01-07 Huawei Technologies Co., Ltd. Systems and methods for application-friendly protocol data unit (PDU) session management
CN108989194B (zh) * 2017-05-31 2021-07-09 微软技术许可有限责任公司 分布式IPSec网关
KR102364802B1 (ko) * 2017-06-23 2022-02-17 후아웨이 테크놀러지 컴퍼니 리미티드 서비스 연속성 구현 방법, 장치 및 서비스 연속성 구현 시스템
WO2019011398A1 (en) * 2017-07-10 2019-01-17 Motorola Mobility Llc CONNECTING MULTIPLE ACCESS DATA IN A MOBILE NETWORK
KR102412288B1 (ko) * 2017-08-14 2022-06-23 삼성전자 주식회사 제 3자 응용 서버에서 단말의 무선 연결 타입 변경을 확인하는 방법
CN115225214A (zh) * 2018-04-03 2022-10-21 华为技术有限公司 报文传输方法、装置和系统
US10778527B2 (en) * 2018-10-31 2020-09-15 Oracle International Corporation Methods, systems, and computer readable media for providing a service proxy function in a telecommunications network core using a service-based architecture
CN110167088A (zh) * 2019-05-29 2019-08-23 中国联合网络通信集团有限公司 一种会话的管理方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109275160A (zh) * 2017-07-17 2019-01-25 华为技术有限公司 数据分流方法、设备及系统
CN109428909A (zh) * 2017-08-23 2019-03-05 中兴通讯股份有限公司 会话锚点的控制方法、装置和服务器
US20190109721A1 (en) * 2017-10-09 2019-04-11 Comcast Cable Communications, Llc Ethernet type packet data unit session communications

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
3GPP TS 33.501
CHINA MOBILE: "23.503:PCF provides local traffic routing policy to SMF based on AF request", 3GPP DRAFT; S2-1909158 503PCF PROVIDES LOCAL TRAFFIC ROUTING POLICY TO SMF BASED ON AF REQUEST, vol. SA WG2, 2 October 2019 (2019-10-02), Split, Croatia, pages 1 - 15, XP051795277 *
HUAWEI: "Traffic Steering Control support of Provisioning of PCC rules;", 3GPP DRAFT; C3-183846 WAS 3751 WAS 3463 WAS 3162 TRAFFIC STEERING CONTROL SUPPORT OF PROVISIONING OF PCC RULES, vol. CT WG3, 28 May 2018 (2018-05-28), Osaka, Japan, pages 1 - 5, XP051459026 *
See also references of EP4044666A4

Also Published As

Publication number Publication date
EP4044666A1 (en) 2022-08-17
US11963032B2 (en) 2024-04-16
US20220264356A1 (en) 2022-08-18
CN114631350A (zh) 2022-06-14
EP4044666A4 (en) 2022-10-19
US20240236755A1 (en) 2024-07-11
CN114631350B (zh) 2024-09-10

Similar Documents

Publication Publication Date Title
CN110831070B (zh) 一种处理业务流的方法、通信方法及装置
US11765686B2 (en) Packet transmission method and apparatus for communicating between terminals of a same 5G LAN group
WO2020199896A1 (zh) 一种业务流路由控制方法、装置及系统
CN112511534B (zh) 一种业务流的传输方法、通信方法及装置
EP4106482A1 (en) Communication method and apparatus
WO2020001562A1 (zh) 一种通信方法及装置
US20230247418A1 (en) Network edge computing method and communication apparatus
WO2019084822A1 (zh) 通信方法、设备及系统
CN113676924A (zh) 通信方法、装置及系统
US20240236755A1 (en) Traffic routing method, apparatus, and system
WO2020034869A1 (zh) 一种业务流的传输方法、通信方法及装置
WO2021058029A1 (zh) 一种控制业务流传输的方法、装置及系统
US20240214874A1 (en) Communication method, apparatus, and system
US12101838B2 (en) Communications method, apparatus, and system
CN112714506B (zh) 数据传输方法和装置
EP4436133A1 (en) Communication method and communication apparatus
WO2022267652A1 (zh) 一种通信方法、通信装置及通信系统
JP2024514748A (ja) 次世代セルラーネットワークにおけるサービス機能チェイニングのための拡張サービス分類
JP2024514749A (ja) 第６世代（６ｇ）システムアーキテクチャ及び機能
WO2021128225A1 (zh) 一种业务流的处理方法、装置及系统
WO2021042381A1 (zh) 一种通信方法、装置及系统
JP7534029B2 (ja) データ伝送方法、リンク品質検出方法、通信装置、及び記憶媒体
WO2024037256A1 (zh) 一种业务流路由方法及装置
WO2024012376A1 (zh) 一种通信方法、通信装置及通信系统
WO2021238794A1 (zh) 业务流的用户量统计方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19952041

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019952041

Country of ref document: EP

Effective date: 20220512

NENP Non-entry into the national phase

Ref country code: DE